Travel Rule (Crypto)

What Is the Travel Rule in Crypto?

Money that moves between banks has always carried a label. When you send a wire transfer, your bank attaches your name and account number, and the receiving bank sees who the money came from. The Travel Rule is the legal requirement behind that label: identifying information must “travel” with the payment.

In the US, the rule dates to 1996, when the Treasury’s anti-money-laundering rules required banks to pass sender and recipient details on transfers of $3,000 or more. Crypto transfers originally carried no such label, because a blockchain records wallet addresses, not names. In June 2019, the FATF closed that gap by telling its member countries to apply the same obligation to virtual asset service providers (VASPs), a category that covers exchanges, brokers and custodial wallet services.

Customer verification is the foundation. An exchange that already knows who its users are through KYC/AML compliance now has to share part of that knowledge whenever a user sends funds to another provider.

How Does the Travel Rule Work?

The mechanism matters most at the moment you withdraw, so it helps to follow one transfer. Before sending, the originating provider collects the sender’s name, account or wallet identifier and a further detail such as a physical address, national ID number or date of birth. It also collects the recipient’s name and wallet address. That data goes to the receiving provider through a separate, encrypted messaging channel, while the crypto itself moves on the blockchain as usual.

Providers use shared data formats and networks to do this. IVMS 101 is the common standard for how names and addresses are structured, and competing protocols, such as TRISA and TRP, carry the messages between firms. The receiving provider checks that the recipient named in the message matches its own customer record before crediting the funds.

Suppose Anna withdraws 2 BTC, worth a hypothetical $120,000, from Exchange A to her account at Exchange B. Exchange A sends a Travel Rule message stating that Anna Novak, verified customer, is sending 2 BTC to Anna Novak at Exchange B. Exchange B matches the name to its own customer file and credits the deposit.

If the names did not match, or Exchange A had never heard of Exchange B, the process would stall. Exchange B could hold or return the deposit, and Exchange A could refuse to send until it identified the counterparty. That friction is intended: it makes it harder to move stolen or laundered funds through regulated platforms under someone else’s name.

How Do Travel Rule Thresholds Differ by Jurisdiction?

FATF sets the recommendation, but each country writes its own law, so the details differ. The FATF standard suggests collecting full information for transfers of 1,000 dollars or euros and above, with lighter checks below that amount. The US applies its long-standing $3,000 threshold to crypto transfers between financial institutions.

Europe went further. Under the EU’s revised Transfer of Funds Regulation, which applies together with the MiCA Regulation from 30 December 2024, crypto transfers between providers must carry sender and recipient data with no minimum amount. For transfers above €1,000 to or from a self-hosted wallet, the provider must also take steps to confirm that the customer owns or controls that wallet, for example by asking the customer to sign a message or send a small test transaction.

Travel Rule vs. KYC

KYC answers “who is my customer?” and the Travel Rule answers “who is on the other end of this payment?” A provider needs the first to do the second.

Why Is the Travel Rule Important for Traders?

The Travel Rule changes how withdrawals feel. Traders moving funds between exchanges may be asked for the recipient’s name, the receiving platform or proof that a wallet is theirs, and a missing detail can delay a transfer by hours or days. Knowing the rule exists turns a confusing hold into a routine request.

Its biggest practical limitation is the “sunrise problem”: countries adopted the rule at different times, so a provider in a strict jurisdiction may have to send funds to one in a country that has not yet implemented it. With no counterpart to receive the message, providers must decide whether to block the transfer, collect more data themselves or accept the risk. Competing messaging protocols add to the friction, because two exchanges on different networks cannot always talk to each other.

Privacy is the other concern. Every Travel Rule message spreads personal data to another company, and each additional copy is one more place it can leak. Supporters argue the trade-off keeps crypto connected to regulated finance; critics see it as a step away from the pseudonymity many users value in self-custody.

Key Takeaways

• The crypto Travel Rule requires regulated providers to pass sender and recipient information along with a crypto transfer, just as banks do for wire transfers.
• FATF extended the rule to virtual asset service providers in 2019 and recommends a threshold of 1,000 dollars or euros, but each country sets its own figure.
• The personal data moves privately between providers through messaging protocols, while the transaction itself settles on the blockchain as normal.
• Transfers involving self-hosted wallets are handled differently, and some jurisdictions require proof that the customer owns the wallet above a set amount.
• Uneven adoption across countries, incompatible protocols and privacy risks are the rule’s main weaknesses.