Crypto transfers move in seconds. Compliance data now has to move with them.
Send a bank wire and you send more than money. Somewhere in that message sits the name of the person paying and the person being paid.
Crypto never really worked that way. For a long time, a wallet address was about all you got.
That’s changing, and faster than many teams expected. The reason is the Crypto Travel Rule. Crypto businesses now have to tell each other who is sending and who is receiving when they move digital assets between themselves.
For exchanges, custodians, payment platforms and fintechs with a crypto feature, this isn’t something to plan for later. It’s already part of the plumbing.
What does it actually ask for, then, and why does it give teams so much trouble?
What Is the Crypto Travel Rule?
The rule traces back to FATF Recommendation 16. That global standard was written for plain old wire transfers.
Then in 2019, the Financial Action Task Force (FATF) applied it to virtual assets as well, and to Virtual Asset Service Providers (VASPs): exchanges, custodial wallet providers, brokers.
When one VASP sends crypto to another, the originator and beneficiary details have to “travel” with it, immediately and securely.
Worth saying clearly: the rule isn’t there to stop crypto transfers. It’s there to make them traceable, the way regulated fiat payments already are.
What Information Has to Travel?
Details differ by country. FATF guidance generally asks for the originator’s name, their account number or wallet address, and one extra identifier: a physical address, national ID number, customer ID, or date and place of birth.
On the receiving side, it’s the beneficiary’s name and their account number or wallet address.
FATF suggests a de minimis threshold of USD/EUR 1,000. Above that, the full data set should be collected and shared. Below it, a reduced set still applies, so small transfers don’t get a free pass.
Thresholds Are Not the Same Everywhere
Here’s where it gets messy. Each jurisdiction is free to implement the rule its own way.
A few examples:
United States: a USD 3,000 threshold applies to certain transfers under Bank Secrecy Act rulesEuropean Union: Regulation (EU) 2023/1113 has applied since 30 December 2024. If an EU crypto asset service provider is involved, originator and beneficiary information is required, whatever the amountSelf-hosted wallets in the EU: over EUR 1,000, the provider has to check whether the customer really owns or controls that wallet
Serving several markets? Then one workflow rarely covers it. Usually you end up maintaining a few.
Why the Travel Rule Is Hard to Implement
1. The Sunrise Problem
Not every country has adopted the rule yet. The ones that have don’t all enforce it the same way.
That leaves a compliant VASP in an awkward spot. It may have to send data to a counterparty in a country where the rule doesn’t apply yet, or to one that simply can’t receive the data.
2. Counterparty Identification
Before any data goes out, a VASP needs to know who is on the other end. Is the destination wallet held by another VASP, or is it self-hosted?
Answering that usually means combining blockchain analytics and wallet attribution data with due diligence on the counterparty VASP. Sometimes it also means simply asking the customer to declare it.
3. Interoperability Between Protocols
Travel Rule solutions don’t all speak the same language.
Most of the industry has settled on IVMS101 as a common data standard. Even so, two VASPs on different Travel Rule networks can still have trouble swapping information cleanly. A shared format doesn’t automatically mean a shared pipe.
4. Self-Hosted Wallets
With a self-hosted wallet, there’s no second VASP waiting to receive anything.
Depending on the jurisdiction, a business may have to collect the information from its own customer, verify who owns the wallet, or run extra risk-based checks instead.
5. Data Protection
Travel Rule data is personal data. That part gets overlooked.
VASPs have to share it securely and still meet their data protection obligations. In practice, that puts encryption, access control and secure API integration right at the centre of the build.
Where the Industry Stands in 2026
There’s real progress. It’s just uneven.
FATF’s seventh Targeted Update on virtual assets, published in July 2026, puts some numbers on it:
83% of surveyed jurisdictions (91 of 109) have passed Travel Rule legislation, up from 73% in 2025Another 11 jurisdictions say implementation is under wayAlmost half of jurisdictions with Travel Rule laws haven’t yet taken any related supervisory or enforcement action
Laws on paper, in other words, are running ahead of enforcement.
FATF also points out that most identified on-chain illicit activity now involves stablecoins. For payment businesses running on stablecoin rails, that ties Travel Rule compliance directly to how they move money every day.
What VASPs Should Build Into Their Infrastructure
A workable Travel Rule setup tends to include:
KYC and KYB data that’s ready to shareCounterparty VASP discovery and due diligenceWallet screening and blockchain analyticsA messaging solution that supports IVMS101Rules for missing or incomplete informationSelf-hosted wallet verification workflowsSecure data storage and record keepingThreshold logic for each jurisdiction
The point is to have compliance happen inside the transaction flow. Not as a manual review someone does after the money has already moved, because by then fixing a missing field is far harder.
The Future of Travel Rule Compliance
Stablecoin payments, on and off ramps, tokenized assets. All of it is drifting into mainstream finance, and the Travel Rule keeps dragging crypto infrastructure toward traditional AML frameworks.
A bank getting into digital assets will run into this. So will a fintech adding a crypto wallet, or a payment provider settling in stablecoins. Each ends up asking the same thing: can our systems share compliance data as fast as they move value?
In regulated crypto, the on-chain transfer is only half of it. The other half is the information that travels with it.
Build it in now and the later conversations get easier, with regulators, with banking partners, and when it’s time to expand.
The Crypto Travel Rule Explained: What VASPs Need to Know was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.