This article aims to assist you with filling out the onboarding forms for either Sandbox or Production. Each section corresponds to a question on the onboarding forms.
Company Domain
Please provide your company domain, for example, mycompany.com. This represents your company's main web address and helps Bitpanda Custody organize your records.
Please enter your email address, such as admin@mycompany.com. This email will receive all system-generated messages, including transaction updates and policy changes.
Contacts
- Technical contact - Who should Bitpanda Custody reach out to for technical issues?
- Admin contact - Who should Bitpanda Custody contact for general admin or policy changes?
- Compliance contact - Who should Bitpanda Custody contact for compliance issues?
- Finance contact - Who should Bitpanda Custody contact for billing issues?
- Go Live Date / Sandbox Required Date - Please select an appropriate date. This helps us understand your timeline so we can prepare your new wallets in advance.
Do you already have a TrustVault account?
Please respond with Yes (and include the registered email and the environment - Sandbox or Production) or No. If you've previously signed up as an individual or under a different organization, it's helpful for us to know so we can determine if the accounts need to be linked. Please specify if you have used either a Sandbox or Production account.
Contact Email
Please enter your email address, such as admin@mycompany.com. This email will receive all system-generated messages, including transaction updates and policy changes.
Company Name
Please provide the name of your registered company, for example, My Crypto Company. This is the name that will represent your organization.
Authorized Administrators
Please provide a list of email addresses along with first and last names. This identifies the users who will have access to the main TrustVault account. Being part of this group grants permissions as outlined here: Please note that you can add up to 50 users to this organization, and they will need access to iOS devices with the TrustVault iOS app installed to set their PIN. Please list each email separately. If you need to add more than four users, feel free to reach out to us. Each person on the list will be invited to download the TrustVault iOS App and will need to set a PIN. (An email will be sent to them when we onboard them.)
Authorized Signers
Please provide a list of email addresses for those who will need signing functionality and will be specified in wallet policies. Each email must be part of the Organization Users list. A subset of Organization Users are Signing Users, who have additional permissions as they will be included in wallet policies. These users have the:
- Ability to sign a transaction
- Ability to sign wallet creation
Signing users will need to install the iOS App and set their PIN (as Organization users), but the specific iOS device they sign up with will be used to create a secure public key that will be added to the wallet policies.
Authorized Users
Authorized users will need to install the iOS App and set their PIN (as Organization users), and the specific iOS device they sign up with will be used to create a secure public key that will be added to the wallet policies.They can view balances, transaction histories, and reports but cannot make or approve any transactions.
Number of Wallets Required?
Please provide a number greater than 0. Most plans include for 2 wallets, which is often used for separating funds or different user types (like Treasury vs Client funds). Additional wallets may be chargeable.
Keep in mind: wallets only define the policy (who can sign). The specific asset types (e.g., Bitcoin or Ethereum) are defined by sub-wallets.
Number of Sub-Wallets Required?
Please provide a number greater than or equal to 20. Each wallet can hold a significant number of sub-wallets (in the thousands). However, there is a soft limit of 20 wallets and sub-wallets per organization. If you plan to use more than this, please let us know so we can adjust the limit.
Do you need Multi-sig for each wallet?
Please select Yes or No. Do you require more than one user to sign transactions from any of your wallets? For sandbox access, we recommend simple multisig rules, and for production, we suggest discussing your specific needs with us.
Multi-sig rules (if multisig required)
Please provide details of the wallet policy, for example, 1 of 2 (Alice or Bob). This is where you specify the wallet policy rules for who can sign. We expect this answer to be something like:
- 2 Signing Users from the list of "Alice", "Bob", or "Charlie."
OR
- 1 Signing User from the list of "Duncan."
Co-signing Service Required?
Please respond with Yes or No. The co-signing service (explained at the bottom of this article) is a service that Bitpanda Custody can provide to co-sign your transactions based on rules. Please reach out to us if you need more information.
Webhooks Required?
Please respond with Yes or No. Do you need webhooks? If so, please specify your webhook URL and the events you wish to monitor. The events available for subscription are listed on our developer portal.
API Access
Please respond with Yes or No. Do you need API Access? This is often requested if you want to create different UIs or automate transactions. This is commonly used alongside Webhooks. Please note that we don't offer read-only API keys at this time.
External Key Signing
Please respond with Yes or No. External Key Signing refers to using the API to sign transactions in parallel or instead of using iOS devices. You will need to securely create an external signing key and store it safely. Please note that this feature has some additional technical requirements, and we will reach out to discuss them if you select this option.