The Travel Rule for Crypto and Wire Transfers

The Travel Rule is one of the most consequential anti-money-laundering requirements in payments, and it has become a defining challenge for crypto. The core idea is simple: information about who is sending and receiving money must travel with the transfer, so that intermediaries and receiving institutions can screen it. Applying that simple idea to different rails is where the complexity lives.

Where the rule comes from

The Travel Rule originated in traditional wire transfers. In the United States, a Bank Secrecy Act rule dating to 1996 requires financial institutions to pass certain originator and beneficiary information along the payment chain for funds transfers at or above $3,000. Internationally, the standard is set by the Financial Action Task Force (FATF) under Recommendation 16, sometimes called the wire transfer rule, which requires that originator and beneficiary information accompany cross-border and certain domestic transfers.

For conventional wires, this fits naturally: SWIFT and other messaging standards already carry structured fields for the ordering and beneficiary parties. The obligation is essentially to populate those fields accurately and not strip them out as the payment passes through correspondents.

What information must travel

The specifics vary by jurisdiction and threshold, but the required data typically includes:

• The originator's name, account or reference number, and address or other identifying detail.
• The beneficiary's name and account or reference number.
• Enough information for the receiving institution to identify the parties and run sanctions and AML screening.

The point is that receiving and intermediary institutions should never be handling a transfer blind. If they cannot see who is behind it, they cannot screen it against sanctions lists or spot suspicious patterns.

FATF extends it to crypto

In 2019, FATF made explicit that Recommendation 16 applies to virtual assets and Virtual Asset Service Providers (VASPs) — crypto exchanges, custodians, and similar businesses. When a VASP sends crypto on behalf of a customer to another VASP, above the applicable threshold, the same originator and beneficiary information must travel with the transaction. In principle, this simply extends a decades-old wire rule to a new rail.

In practice, it is hard, for reasons rooted in how blockchains work.

Why crypto makes it difficult

• Blockchains carry no identity fields. A blockchain transaction records addresses and amounts, not names and account numbers. There is no native place to attach originator and beneficiary identity, so the data must travel over a separate, off-chain channel that both VASPs support.
• No universal messaging standard. Traditional wires share SWIFT. Crypto has no single equivalent, so competing Travel Rule protocols and standards emerged, and two VASPs must speak a compatible one to exchange data.
• The counterparty may not be a VASP. A withdrawal might go to a self-hosted (unhosted) wallet with no institution on the other side to receive the information, complicating compliance.
• Identifying the receiving VASP. Before you can send data to the beneficiary institution, you must work out which institution controls the destination address — a non-trivial discovery problem.

How the industry responds

VASPs have adopted interoperability protocols to exchange Travel Rule data securely off-chain, alongside blockchain analytics to attribute addresses to known services. Regulators in many jurisdictions have set their own thresholds and timelines for enforcement, so a global VASP must handle a patchwork of local rules layered on the FATF baseline. The direction is clear: crypto transfers are expected to carry the same identity transparency as bank wires, even though the underlying technology gives no help in doing so.

The sunrise problem

One practical complication deserves its own name: the sunrise issue. Because jurisdictions adopt and enforce the Travel Rule at different times, a compliant VASP in one country may need to send data to a counterparty in another country where the rule is not yet in force — and where the receiving VASP has no obligation or ability to accept it. This uneven global rollout means Travel Rule compliance is not simply a matter of implementing a protocol; it is a matter of both parties being ready at the same time. Until adoption is near universal, VASPs must decide how to handle transfers to counterparties that cannot yet receive Travel Rule information, balancing regulatory expectations against the reality of an incomplete network.

Key takeaways

• The Travel Rule requires originator and beneficiary information to travel with a transfer so intermediaries can screen it.
• It began with traditional wires — the US Bank Secrecy Act applies it at or above $3,000 — and is set globally by FATF Recommendation 16.
• Wires satisfy it naturally because messaging standards like SWIFT carry structured party fields.
• FATF extended the rule to virtual assets and VASPs in 2019, requiring the same data on qualifying crypto transfers.
• Crypto makes compliance hard: blockchains carry no identity fields, there is no universal messaging standard, and counterparties may be unhosted wallets.