What Is the Travel Rule?
The Travel Rule requires a virtual asset service provider (VASP) sending a transfer above a set threshold to collect and pass on identifying information about both the sender and the recipient to the VASP on the other end. The name comes from the fact that this information must travel with the transaction rather than staying siloed inside the sending institution, and the underlying concept is not new to crypto at all. It is the digital-asset application of a rule that has governed traditional wire transfers for years, extended by the Financial Action Task Force, the global standard-setter for anti-money laundering policy, through Recommendation 16 and clarified specifically for virtual assets in its 2019 guidance. The goal is straightforward: prevent large transfers of value from moving anonymously between institutions in a way that would make money laundering and terrorist financing trivially easy to conceal.
The Threshold That Actually Triggers It
Most jurisdictions that have implemented the Travel Rule use a threshold in the range of $1,000 or €1,000 per transaction, above which the full data package must accompany the transfer. Below that threshold, many jurisdictions still require the originating VASP to collect and retain basic originator information, just without the same obligation to transmit it to the counterparty in real time. The specific number and the specific requirements below it vary by jurisdiction: the FATF sets the baseline standard, but individual regulators, from the EU’s Transfer of Funds Regulation to individual state-level regimes in Africa and Asia, implement it with their own thresholds and enforcement timelines, which is part of why compliance teams at exchanges operating across multiple markets describe Travel Rule implementation as one of the more operationally painful parts of running a licensed VASP.
Figure 1. Above the threshold, originator and beneficiary data must travel with the transfer.
What Information Actually Has to Move
The core data package is narrower than many people assume. At a minimum, it typically includes the originator’s full name and their account or wallet identifier, plus the same two fields for the beneficiary. Larger transfers, or transfers into higher-risk jurisdictions, often add the originator’s physical address, date of birth, or a national identification number. What is not typically required is a full transaction history or details unrelated to the specific transfer in question; the Travel Rule is narrowly scoped to identifying the two parties to a single transaction, not a general surveillance mandate over a customer’s entire account activity.
Figure 2. A narrow, specific data package, not a general surveillance mandate.
How the Data Actually Moves
The blockchain transaction itself and the compliance data travel on two separate rails. The on-chain transfer settles exactly as it would without any Travel Rule obligation attached; the required data moves through a separate, off-chain secure messaging channel between the originating and beneficiary VASPs. A handful of industry protocols have emerged to standardise this exchange, often built around the IVMS 101 data model that defines a common format for originator and beneficiary information, with providers such as Notabene and Sygna offering the messaging infrastructure that lets VASPs that have never dealt with each other before still exchange this data reliably. Getting this right at scale, particularly when counterparties sit in different jurisdictions with different technical standards, is one of the more genuinely difficult integration problems in crypto compliance today.
Figure 3. The blockchain moves the asset. A separate channel moves the compliance data.
Where This Actually Bites in Practice
The hardest edge case is the self-hosted wallet, a wallet the customer controls directly rather than one held in custody by a VASP. When a customer withdraws from an exchange to their own wallet, there is no receiving VASP to exchange data with, and different jurisdictions have taken meaningfully different approaches to what the sending exchange must still verify or collect in that scenario. A second recurring friction point is what the industry calls the sunrise problem: because different countries have implemented the Travel Rule on different timelines, a VASP in a jurisdiction with a mature regime may be sending data to a counterparty in a jurisdiction that has not yet built the infrastructure to receive it, forcing exchanges to maintain fallback processes for incomplete compliance coverage across their counterparty network.
The Travel Rule doesn’t ask crypto to behave any differently than a bank wire. It asks it to prove, transaction by transaction, that it can.
Related reading on Blockchain People
What Is a Virtual Asset Service Provider (VASP)? · What Is Proof of Reserves? · Blockchain People Glossary
External References
FATF Recommendation 16 and Virtual Assets Guidance (FATF) · IVMS 101 Data Standard (InterVASP Messaging Standards)
About The Author
