Confidential by defaultEstablished 201072 Jurisdictions

Travel Rule

The travel rule requires the firm sending a transfer to pass identifying information about the originator and the beneficiary to the firm receiving it, so that the data travels with the money. It began as a banking wire rule and now reaches virtual asset transfers as well.

Also called: FATF Recommendation 16 · crypto travel rule

The travel rule is a data obligation rather than a payment one. The sending institution has to collect specified details about the originator and the beneficiary — typically name, account or wallet identifier, and some form of address or identifying number — and transmit them to the receiving institution with, or alongside, the transfer, so the receiving side can screen the parties and investigators can follow a chain afterwards.

Where it came from

It began as a wire transfer requirement for banks. The international standard is FATF Recommendation 16, which now reaches transfers of virtual assets as well, and that is what brought exchanges, custodians and brokers — virtual asset service providers — inside a rule originally written for correspondent banking. FATF revised the standard at its plenary in June 2025, and the US Treasury says the revised version is to take effect no later than 2030.

There is no single threshold

Assuming there is one is the most common error. In the European Union a transfer of crypto-assets must carry the prescribed originator and beneficiary information whatever its size, domestic and cross-border alike, while an EU transfer of funds below EUR 1,000 attracts a simplification that reduces, but does not remove, what has to accompany it or be made available. In the United States the recordkeeping and travel rule threshold is USD 3,000; a 2020 proposal to lower it to USD 250 for cross-border transfers was never finalized. The exact fields required, and the treatment of transfers involving an unhosted wallet, are national too, and they differ.

Two operational problems follow. The first is timing: jurisdictions adopted the rule at different points, so a compliant firm regularly transacts with a counterparty in a country that has no equivalent requirement and no means of receiving the data. The second is plumbing. There is no single messaging standard for virtual asset transfers; several competing protocols exist, and a sending firm has to reach the receiving firm on one of them — which also means satisfying itself that the counterparty is who it claims to be before handing over a customer’s personal data.

In practice

There is no single global threshold, and writing “above a threshold” as the general rule is simply wrong. In the European Union crypto-asset transfers carry the requirement regardless of amount, EU transfers of funds have a EUR 1,000 simplification, and the United States works from USD 3,000. FATF Recommendation 16 is a standard countries commit to implement, not a law in itself — the threshold, the required fields and the enforcement come from the national rule, and not every jurisdiction has written one. That is the position as things stand in September 2026.

Example

An exchange sends stablecoins for a customer to an account at another exchange. Alongside the on-chain transfer it transmits the sender’s name and account reference and the beneficiary details, over a messaging protocol both firms support. The same customer’s withdrawal to a wallet they control themselves has no receiving institution to send anything to, which is why jurisdictions treat that case separately.

Commonly confused with

TermHow it differs
FATF Recommendation 16Recommendation 16 is the international standard behind the travel rule; a firm’s actual obligation comes from the national rule that implements it, which may differ in threshold and scope.
Know Your TransactionKYT is analysis a firm performs on transfers it can see; the travel rule is a duty to hand specified data to another firm.

See also

Go deeper

Regulatory information checked: 22/Sep/2026

← All glossary terms

Page Last Updated: 22/Sep/2026