Travel Rule data exchange flows
Work with Travel Rule transactions to ensure data exchange compliance.
Travel Rule data exchange transactions help you exchange the required transfer information with another VASP as part of a compliant virtual asset transfer flow.
In most cases, the data exchange takes place before the blockchain transaction is submitted. In some cases, it starts after an on-chain deposit has already been received.
You can use Travel Rule data exchange transactions to:
- Notify the beneficiary VASP before sending virtual assets on-chain.
- Retrieve missing originator information after receiving an on-chain deposit.
- Review and respond to transfer requests sent to a wallet that belongs to your user.
Travel Rule flow scenarios
Refer to the table below to select the right guide based on your transaction scenario.
| Transaction scenario | Your role | When the data exchange happens | Flow |
|---|---|---|---|
| You are sending funds from your user's wallet to another entity. | Originating VASP | Before the on-chain withdrawal | Before Withdrawal: Initiate outbound data exchange |
| Your user received an on-chain deposit, but no Travel Rule data exchange was delivered. | Beneficiary VASP | After the on-chain deposit | After deposit: Create incoming data exchange |
| Another VASP wants to send funds to your user's wallet and asks you to confirm the transfer details | Beneficiary VASP | Before the other VASP submits the on-chain transfer | Respond to incoming transfer requests |
NoteBefore using any Travel Rule flow, check this article and make sure that you have your integration set up properly.
Updated about 2 hours ago