What data has to travel?
Under the EU rule, the sending provider must attach to each transfer:
- About the sender. Name; the blockchain address and, where one exists, the account number at the provider; and the sender's address, official document number, customer identification number, or date and place of birth.
- About the recipient. Name; the blockchain address and, where one exists, the account number at the receiving provider.
The receiving provider must check that the data arrived and is complete, and has to decide what to do when it is not: ask for it, hold the funds, or return them. Both sides keep the records. For a business payout the "name" is the company's legal name, and many providers also ask for a registration number or LEI.
Where does it sit in a payout flow?
A payout without travel rule data is either blocked by your own provider or held by the receiving one. So the data step comes before signing, not after:
- Collect. When a recipient is onboarded, store the fields the rule needs, in the IVMS101 format, next to the wallet address.
- Identify the other side. Work out whether the address belongs to another regulated provider (a hosted wallet) or to the recipient (a self-hosted wallet). Address attribution services and the travel rule networks both help.
- Send the data. Through your provider's API, or through a travel rule protocol if you are the regulated party. Many protocols wait for the receiving side to confirm before the transfer goes on-chain.
- Sign and broadcast. Only after the data step has passed, or after a documented decision when the other side cannot receive it.
- Store and reconcile. Keep the message, the response and the transaction hash together, so an auditor can follow any payout from request to chain.
The payout architecture guide shows where this sits among the other parts of the flow.
What about payouts to self-hosted wallets?
Many payout recipients, especially contractors and creators, hold their own wallets. No provider sits on the other side to receive the data, so the rule changes shape. The sending provider still collects and keeps the sender and recipient data. If the transfer is above 1,000 euros and the wallet belongs to the provider's own customer, the provider must also check that the customer owns or controls it.
Common ways to prove control:
- Sign a message with the wallet's key, for example during onboarding in your app.
- Send a small test amount from the wallet, or to it with a code the recipient confirms.
- Connect the wallet to your app through a standard wallet connection, which also signs a message.
Build the proof into recipient onboarding, not into the first payout. A recipient who has to prove control while waiting for money opens a support ticket.
The sunrise problem
Countries adopted the travel rule at different times and with different thresholds. A provider in the EU must send data for every transfer, but the receiving provider may sit in a country where the rule does not apply yet, or applies only above 1,000 dollars, and may not be able to receive the message at all. The EU rule asks providers to use their best effort in that case and to treat the counterparty with a risk-based approach.
For payouts this means a corridor plan: for each country you pay into, which providers your recipients use, whether they can receive travel rule messages, and what you do when they cannot. Write the decision down per corridor before launch.
Protocols and networks
There is no single network. Providers exchange data over several protocols, and travel rule vendors bridge between them:
- IVMS101. The data model, not a protocol: the agreed fields and formats that most messages carry.
- TRP (Travel Rule Protocol). An open protocol maintained by OpenVASP, used by many exchanges.
- TRISA. An open-source protocol with certificate-based identity for providers.
- Commercial networks. Vendors that run their own networks and bridge to the open protocols, and add counterparty discovery, wallet attribution and dashboards.
If your payout provider performs the transfer, it already speaks one or more of these. Ask which, and how many of your recipients' providers it can reach.
What usually goes wrong?
| Failure | Effect | Fix |
|---|---|---|
| Recipient data collected as free text | Messages rejected or held | Store IVMS101 fields from onboarding, with validation |
| No answer from the receiving provider | Payouts stuck before signing | Timeouts and a documented fallback per corridor |
| Hosted address treated as self-hosted | Wrong checks, data not sent | Address attribution before every new address |
| Self-hosted wallet ownership not proven | Payouts above €1,000 blocked | Signed message at onboarding |
| Message and transfer stored apart | Audit cannot trace payouts | One record linking message, response and transaction hash |
| Incoming transfers without data | Funds you cannot release | Inbound checks and a return procedure |
How we work with this
We do not sell compliance or AML services. We build the payout flow so the travel rule step is part of it: the data model, the calls to your provider or protocol, the held and returned states in the payout state machine, and the records that tie every message to its transfer. In the Stablecoin Payouts Launch, screening and travel rule data are part of the flow, and where they apply to your corridors, a held payout is written into the acceptance tests you sign in week 1.
FAQ
Q01Is there a minimum amount for the travel rule in the EU?
No. Between crypto-asset service providers in the EU, sender and recipient data must accompany every transfer, whatever the amount. Many other countries apply the FATF threshold of 1,000 US dollars or euros.
Q02Does the travel rule apply to payouts to self-hosted wallets?
Yes, in a lighter form. The provider must collect and keep the sender and recipient data. For transfers above 1,000 euros to or from a self-hosted wallet of its own customer, it must also check that the customer owns or controls that wallet.
Q03Who is responsible if our payout provider sends the transfer?
The provider that performs the transfer for its client sends the travel rule data. Your job is to give it complete and correct data about the sender and recipient, and to handle the cases where a transfer is held or returned.
Q04What is IVMS101?
The common data model for travel rule messages: field names and formats for the names, addresses, account numbers and identifiers of the sender and recipient. Most travel rule protocols carry IVMS101 data.
Q05Do you sell travel rule or AML services?
No. We build the payout flow so that it sends, receives and stores travel rule data through the provider or protocol you choose, and handles held and returned transfers.
Sources
This guide is a summary for engineering and product teams, not legal advice. Vareger holds no licence and receives no fees from any provider named here.
