Travel Rule – FATF Recommendation 16 (Crypto-Asset Transfers)

The Travel Rule refers to FATF Recommendation 16 as applied to crypto-asset transfers. It obliges Virtual Asset Service Providers (VASPs) to collect and transmit originator and beneficiary data when transferring crypto-assets to the receiving VASP — analogous to the accompanying wire transfer information requirement in the traditional banking system.

• Threshold: Applies to transfers of USD/EUR 1,000 or above (or equivalent crypto value)
• Data transmission: Name, account number/wallet address and address of originator
• Challenge: Unlike banking, there is no central SWIFT-equivalent network for VASPs
• Market solutions: Various Travel Rule protocols (TRISA, OpenVASP, Sygna Bridge, TRP)

The original Travel Rule for banks was issued by FinCEN in 1996 as a regulation (31 CFR 103.33(g)), based on the Annunzio-Wylie Anti-Money Laundering Act of 1992 under the Bank Secrecy Act. It required financial institutions to transmit accompanying information for wire transfers of USD 3,000 or more.

FATF explicitly extended Recommendation 16 to Virtual Asset Service Providers (VASPs) in 2019, setting a threshold of USD/EUR 1,000. Implementation proved technically difficult, as no existing infrastructure (analogous to SWIFT) existed for VASPs.

The EU implemented the Travel Rule through the Transfer of Funds Regulation (TFR, Regulation 2023/1113), which from December 30, 2024 requires basic originator and beneficiary data for all VASP-to-VASP crypto transfers (full verification above EUR 1,000). Switzerland and many Asian countries followed with their own implementing legislation.

The Travel Rule applies to:

• VASPs: Crypto exchanges, brokers, custodial wallet providers, OTC desks
• Transfers: VASP-to-VASP transmissions above threshold (varies by country)
• Geographically: Across over 200 jurisdictions in the global FATF network (40 FATF members plus FATF-Style Regional Bodies), with varying levels of implementation

Special case unhosted wallets: Transfers to non-custodied (unhosted) wallets — regulatorily contested, subject to enhanced due diligence above certain thresholds under the EU TFR.

• Originator data: Name, wallet/account number, address or date of birth of originator
• Beneficiary data: Name and wallet/account number of beneficiary
• Data transmission: Immediate forwarding to receiving VASP before or with the transfer
• Screening: Checking transmitted data against sanctions lists and suspicious patterns
• Sunrise problem: VASPs must also handle counterparties not yet Travel Rule compliant
• Technical interoperability: Use of a compatible protocol (TRISA, TRP, etc.)

3 corrections:
- Collective implementation date for Singapore, Switzerland, Japan is incorrect
- EU TFR application date wrong: December 2024 instead of October 2023
- last_amended date wrong: should reflect TFR crypto application December 2024
1 update:
- Missing mention: FATF Plenary 2024 report on Travel Rule compliance
4 clarifications.
1 note.