Introduction
In order to be compliant with Travel Rule, additional information is required for some transactions which result in the transfer(s) of assets.
You can provide us this information via a mutation being added to our GraphQL API, updateTravelRuleInfo or you can use TrustVault Web Transactions view to add the data.
What is Required?
The exact guidelines are covered in our Travel Rule blog but this table should help you understand exactly what data should be added to each transaction.
As the guidelines get clearer, TrustVault will attempt to pre-fill much of this information for you
What is an intermediary?
An intermediary is a Cryptoasset Business that performs actions on behalf of someone else, e.g. their customers.
The Travel Rule information required depends on what kind of business you are and what kind of transactions you perform. Your company can be listed as an intermediary on not. If you are an intermediary, you need to provide additional information on who you are operating on behalf of when sending or receiving transactions.
The setting will be discussed during onboarding and can be changed later if necessary.
If you are a broker (and acting on behalf of someone else for this transaction) aka intermediary, use the following table:
Transaction Direction | Fields |
Outbound | Originator Info: I am the originator: Deselect this option, or if using the API set the value of Full Name: Registered company name or full name for natural person sending the funds AccountId: This should be address you are sending from, for Bitcoin use the transaction requestId CustomerId: This should be your customerId for the person or company on who's behalf you are sending the funds
Beneficiary Info: Full Name: Registered company name or full name for natural person AccountId:This should be address you are sending to CustomerId: This is not required and can be left blank |
Inbound | Originator Info: Full Name: Registered company name or full name for natural person sending the funds AccountId: This should be the address you are receiving funds from or the transactionHash CustomerId: This should be provided by the sending VASP. Not required if sending from an un-hosted wallet
Beneficiary Info: I am the beneficiary: Deselect this option, or if using the API set the value of Full Name: Registered company name or full name for natural person AccountId: This should be address receiving funds CustomerId: If this transaction was sent from another VASP and they have provided you with a customerId of the user sending the funds enter it here. Otherwise, leave as N/A. |
If you are acting on behalf of yourself (whether you are a broker or not), use the following table:
Transaction Direction | Fields |
Outbound | Originator Info: I am the originator: Select this option, or if using the API set the value of Full Name: Registered company name or full name for natural person sending the funds AccountId: This should be address you are sending from, for Bitcoin use the transaction requestId CustomerId: This is your customerId with us and can be pre-filled by selecting "I am the originator" in TrustVault Web or using the
Beneficiary Info: Full Name: Registered company name or full name for natural person AccountId: This should be the address you are sending to CustomerId: This is not required and can be left blank |
Inbound | Originator Info: Full Name: Registered company name or full name for natural person sending the funds AccountId: This should be the address you are receiving funds from or the transactionHash CustomerId: This should be provided by the sending VASP. Not required if receiving from an un-hosted wallet
Beneficiary Info: I am the beneficiary: Select this option, or if using the API set the value of Full Name: Your registered company name or full name for natural person AccountId: This should be address receiving funds CustomerId: This is not required and can be left blank |
Contact us
If you have any issues, please get in touch. For technical support reach out to help@bitpandacustody.com. For compliance issues reach out to travelrule@bitpanda.com