This article is designed to help those completing onboarding forms for ether Sandbox or Production. Each heading correlates to a question on the onboarding forms.

Company Domain

Please enter a company domain. e.g. mycompany.com

This is the domain of your company. e.g. the main portion of your web address. This helps Trustology match your records together.

Email

Please enter your email address. e.g. [email protected]

This is the email address that will receive all system generated emails such as transaction status and policy changes.

Contacts

  • Technical contact - who does Trustology contact for technical issues?

    • Please enter an email address.

  • Admin contact - who does Trustology contact for general admin or policy changes?

    • Please enter an email address.

  • Compliance contact - who does Trustology contact for compliance issues?

    • Please enter an email address.

  • Finance contact - who does Trustology contact for billing issues?

    • Please enter an email address.

Go Live Date / Sandbox Required Date

Please choose a suitable date.

This help us understand your timelines so we can be ready with your new wallets.

Do you already have a TrustVault accounts?

Please enter Yes (and the email registered and the environment - Sandbox or Production) or No.

If you have previously signed up as an individual or a different organisation it is useful for us to know so we can see if the accounts need to be tied together. Mention if you have use either a Sandbox or Production account.

Account Type

Please select one option

  • Individual Account - An individual account is owned by a single user. All KYC will be completed as a single user and only a single user has legal rights to the account and assets.

  • Organisation Account - An organisation account is owner by a company. All KYB will be completed as a company. The company has legal rights to the account and assets.

Contact Email

Please enter your email address. e.g. [email protected]

This is the email address that will receive all system generated emails such as transaction status and policy changes.

Company Name

Please enter the name of your registered company. e.g. My Crypto Company

This is the name that the organisation will be called

Organisation Users (Organisation Account only)

Please enter a list of email addresses and first name, last name.

This specifies the users who will have access to the main TrustVault account. Being added to this group and having set your PIN will allow:

  • Access to TrustVault iOS App

  • Access to TrustVault Web

  • Ability to view all the wallets and sub-wallets for your organisation

  • Ability to view all portfolio balances

  • Ability to initiate unsigned transactions from either TrustVault Web or TrustVault iOS App

  • Ability to cancel any transaction that appears in the TrustVault iOS App "inbox"

  • Ability to connect any sub-wallet to MetaMask and view data there or initiate an unsigned transaction

NB: You can add up to 50 users to this organisation and they will need access to iOS devices with TrustVault iOS app install to set the PIN.

Please list each email individually. If you required more than four, please contact us. Each person in the list will be invited to download the TrustVault iOS App and required to set a PIN. (An email will be sent to them when we onboard them)

Signing Users (Organisation Account only)

Please enter a list the email addresses of those that will required Signing functionality and who will be specified in wallet policies. Each email MUST be in the Organisation Users lists.

A sub-set of Organisation Users are Signing Users. These users have additional permissions as they will be added to wallet policies. These users have the:

  • Ability to sign a transaction

  • Ability to sign wallet creation

Signing users will be required to install the iOS App, set their PIN (as Organisation user) but the specific iOS device they sign up with will be used to create a secure publicKey that will be added to the wallet policies.

Number of Wallets Required?

Please enter a number greater than 0.

Most plans allow for 2 wallets. This is often used for segregating funds or different user types (Treasury vs Client funds for example).

Remember: wallets only define the policy (who can sign). The specific asset type s(e.g. Bitcoin or Ethereum) are defined by sub-wallets.

Number of Sub-Wallets Required?

Please enter a number greater than or equal to 20.

Each wallet can hold a very large number of sub-wallets (10,000s). However, there is a soft limit of 20 wallets and sub-wallets against the organisation. if you plan to use more than this, please let us know so we can raise the limit.

Do you need Multisig for each wallet?

Please select Yes or No.

Do you require more than a single user to sign transactions from ANY of your wallets? For sandbox access we recommend simple multisig rules for production we recommend you chat to us about your specific requirements.

Multi-sig rules (if multisig required)

Please enter a text detailing the wallet policy. e.g. 1 of 2 (Alice or Bob)

This is where you specific they 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 enter Yes or No.

The co-signing service (explained at the bottom of this arcticle) is a service that Trustology can run that can co-sign your transactions based on rules. Please contact us if you require further information.

Webhoooks required?

Please enter Yes or No.

Do you require webhooks? If so, please specify your webhook URL and the events you wish to listen to. The events that can be subscribed to, are listed here on our developer portal.

API Access

Please enter Yes or No.

Do you require API Access? This is often if you would like to build different UIs or create transactions automatically. This is often used in conjuction with Webhooks. NB: We don't offer read-only API keys yet.

External Key signing

Please enter Yes or No.

External Key signing is where you plan to use the API to sign transactions in parallel or instead of the iOS devices. You will be required to securely create an external signing key and store it very securely. You will be required

Please note this feature has some additional technical constraints and we will contact you to go through them if you select this option.

Did this answer your question?