Skip to main content

Travel Rule

What is the Travel Rule in crypto?

A FATF recommendation, adopted into regulation by most major financial jurisdictions, requiring virtual asset service providers (VASPs) to collect and transmit originator and beneficiary information for transfers above a threshold (typically $1,000 or equivalent). Designed to extend the same anti-money laundering controls that apply to wire transfers. The rule applies between VASPs but creates a compliance gap at the boundary with self-hosted wallets, where there is no counterpart VASP to receive the data. Implementation varies significantly across jurisdictions. See also: KYC/AML.

FATF Recommendation 16 requires that originator and beneficiary information travel alongside a transfer, extended to virtual asset service providers in 2019. Above a threshold, commonly $1,000 or EUR 1,000 depending on jurisdiction, the sending institution must transmit name, account identifier and certain address or identity details to the receiving institution. IVMS101 is the data standard that makes those messages interoperable.

The friction is structural. A blockchain transfer carries value with no message layer attached, so the compliance data has to move over a completely separate channel and be matched to the on-chain transaction at the other end. That requires the receiving institution to be identifiable, reachable, and running a compatible protocol, none of which the blockchain provides.

Two problems follow. The sunrise issue: jurisdictions adopted the rule at different times, so compliant institutions routinely transact with counterparties under no equivalent obligation. And self-hosted wallets, which have no institution on the other side at all, are treated inconsistently, with some regimes requiring additional verification above a threshold and others declining to extend the rule to them. Both gaps remain open.