FATF Recommendation 16
Travel Rule implementation by jurisdiction
The bottom line: FATF Recommendation 16 requires virtual asset service providers to transmit originator and beneficiary information during transfers — the crypto equivalent of the bank wire "Travel Rule." Adoption is accelerating but uneven. This map tracks which jurisdictions have enforced, implemented, or partially adopted Travel Rule requirements for stablecoin and crypto-asset transfers.
Classification
How implementation status is assessed
Enforced
What it means: Travel Rule for virtual asset transfers is enacted in law and actively enforced. Regulators conduct inspections, issue penalties for non-compliance, and mandate specific data fields. Examples: EU (TFR — zero threshold), US (FinCEN $3,000), Japan (zero threshold), Switzerland (zero threshold), South Korea, Singapore.
Implemented
What it means: Travel Rule regulation adopted and VASPs are required to comply, but enforcement is still ramping up. May face "sunrise issue" — counterparty VASPs in other jurisdictions cannot yet receive data. Examples: UK (zero threshold since Sept 2023), Canada, UAE, Hong Kong, Australia.
Partial
What it means: Some Travel Rule elements adopted — typically customer identification and suspicious transaction reporting — but full originator/beneficiary data transmission between VASPs not yet mandated or technically implemented. Examples: Brazil, India, Thailand, South Africa, Turkey, Mexico, Indonesia.
Not Implemented
What it means: No Travel Rule for virtual assets. Either the jurisdiction has banned crypto (China, Russia) or has no VASP framework (Egypt). The majority of jurisdictions globally fall into this category — FATF's 2024 assessment found only 29% of jurisdictions have begun implementing R15/R16 for VAs.
Context
Why the Travel Rule matters for stablecoins
What is FATF R16? The "Travel Rule" requires financial institutions to include originator and beneficiary information with fund transfers. FATF extended this to virtual assets in June 2019 (the "crypto Travel Rule"). VASPs must collect, hold, and transmit: originator name, account number, address or national ID, and beneficiary name and account number.
The sunrise problem. Travel Rule only works when both the sending and receiving VASP can exchange data. Jurisdictions that implement early face the "sunrise issue" — their VASPs must collect and hold data even when counterparty VASPs abroad are not yet equipped to receive it. The EU TFR addresses this by requiring CASPs to assess counterparty risk before executing transfers.
Technology protocols. Several interoperability solutions enable VASP-to-VASP data exchange: Notabene (broadest adoption, 200+ VASPs), Sygna Bridge (Asia-Pacific focus, JVCEA-standard in Japan), TRP (Travel Rule Protocol, open-source), OpenVASP (Swiss origin), and TRUST (Travel Rule Universal Solution Technology, Coinbase-led consortium). No single protocol dominates globally.
Threshold divergence. FATF recommends a $1,000/€1,000 de minimis threshold, but jurisdictions diverge significantly. The EU (TFR) and Japan apply zero threshold — all transactions, regardless of size. The US applies $3,000. Switzerland applies zero. South Korea applies ~$750. This divergence creates compliance complexity for cross-border stablecoin transfers.
Sources: FATF Updated Guidance for a Risk-Based Approach to VAs and VASPs (Oct 2021), FATF 5th Round Mutual Evaluation Reports, EU Transfer of Funds Regulation (EU) 2023/1113, FinCEN 31 CFR 1010.410, national financial authority publications. Technology protocol data from Notabene Travel Rule Tracker. Updated quarterly.