FATF Recommendation 16 - Virtual Asset Travel Rule
FATF Recommendation 16 (Wire Transfers) was extended to Virtual Asset Service Providers (VASPs) in October 2018 + June 2019 (R.15 + Interpretive Note to R.15 + the FATF October 2018 Public Statement) operationalising the TRAVEL RULE for virtual asset transfers. The 2024 FATF Targeted Update on Virtual Assets + VASPs (R.15 / R.16) refined implementation expectations. CORE REQUIREMENTS: VASPs must obtain + hold + transmit required originator and beneficiary information for virtual asset transfers; the de minimis threshold is set at USD/EUR 1,000 (lower than for traditional wire transfers); information includes originator name + originator account number / wallet identifier + originator address or national identity number / customer identification number / date and place of birth + beneficiary name + beneficiary account number / wallet identifier. The recipient VASP must conduct counterparty VASP due diligence (CVDD) to determine that the counterparty VASP is licensed/registered + has appropriate AML/CFT controls + risk-rates the counterparty + applies enhanced measures where appropriate. The 'SUNRISE PROBLEM' refers to cross-jurisdictional implementation gaps where some jurisdictions have transposed FATF R.16 for VASPs but others have not - leaving VASPs in compliant jurisdictions transferring to or receiving from VASPs in non-compliant jurisdictions facing ambiguity. UNHOSTED WALLET TRANSFERS (transfers to or from self-hosted / non-custodial wallets) raise additional risks; the 2024 FATF Targeted Update reinforced that VASPs should apply risk-based + enhanced measures + collect originator information for outbound transfers to unhosted wallets + assess incoming transfers from unhosted wallets. EU implementation via Transfer of Funds Regulation (TFR) (Regulation (EU) 2023/1113) + complementing the MiCA + AMLR. US implementation via FinCEN 31 CFR 1010.410(f) (Travel Rule) covering CVCs (Convertible Virtual Currencies). UK implementation via the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017. Travel Rule technical infrastructure includes the InterVASP Messaging Standard (IVMS101) for data exchange + multiple competing networks (TRP, TRUST, Sygna Bridge, OpenVASP, Notabene, Sumsub Travel Rule). Travel Rule compliance is a precondition for VASP licensing in most jurisdictions + a barrier to market access for non-compliant VASPs.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (7)
R.16 VATR: Counterparty VASP Due Diligence and Sanctions Screening
| Code | Title |
|---|---|
| R.16-VATR.CVDD | Counterparty VASP Due Diligence (CVDD) |
| R.16-VATR.Sanctions | Sanctions screening of Travel Rule data |
R.16 VATR: Record Retention, Audit, Training and Status
| Code | Title |
|---|---|
| R.16-VATR.Governance | Governance, training and independent testing |
| R.16-VATR.Record | Record retention for Travel Rule data (FATF R.11 + R.16) |
| R.16-VATR.Status | FATF R.16 Virtual Asset Travel Rule - corpus status, 2024 update + implementation pipeline |
R.16 VATR: Required Originator and Beneficiary Information
| Code | Title |
|---|---|
| R.16-VATR.Beneficiary | Beneficiary information requirements |
| R.16-VATR.Originator | Originator information requirements |
R.16 VATR: Scope, Applicability and Governance
| Code | Title |
|---|---|
| R.16-VATR.Scope | Scope and applicability of Travel Rule to VASPs (R.16 + Interpretive Note to R.15/R.16) |
R.16 VATR: Sunrise Problem, Cross-Border and Intermediary Handling
| Code | Title |
|---|---|
| R.16-VATR.CrossBorder | Cross-border transfer controls + intermediary VASP handling |
| R.16-VATR.SunriseSproblem | Sunrise Problem - cross-jurisdictional implementation gaps |
R.16 VATR: Technical Infrastructure (IVMS101) and Data Quality
| Code | Title |
|---|---|
| R.16-VATR.DataQuality | Data accuracy, validation and quality assurance |
| R.16-VATR.IVMS101 | InterVASP Messaging Standard (IVMS101) and Travel Rule technical infrastructure |
R.16 VATR: Unhosted Wallet Transfers and Risk-Based Measures
| Code | Title |
|---|---|
| R.16-VATR.Unhosted | Unhosted (self-hosted / non-custodial) wallet transfers - 2024 Targeted Update |
Your Compliance Coverage
If you comply with FATF Recommendation 16 - Virtual Asset Travel Rule, you already cover:
Pakistan Personal Data Protection Bill 2023
15%
2 controls mapped
Compare →Italy Personal Data Protection Code (Legislative Decree No. 196/2003, amended 2018)
15%
2 controls mapped
Compare →Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (UAE PDPL)
15%
2 controls mapped
Compare →+ 85 more: NIST AI Risk Management Framework (AI RMF 1.0) (15%), Albania Law on Protection of Personal Data (Law No. 9887, 2008, amended 2014) (15%)
See all 88 mapped frameworks ↓Maps to 88 other frameworks
Frequently Asked Questions
What is FATF Recommendation 16 - Virtual Asset Travel Rule?
FATF Recommendation 16 - Virtual Asset Travel Rule is a compliance framework from International (FATF — 40 members) with 7 domains and 13 controls. FATF Recommendation 16 (Wire Transfers) was extended to Virtual Asset Service Providers (VASPs) in October 2018 + June 2019 (R.15 + Interpretive Note to R.15 + the FATF October 2018 Public Statement) operationalising the TRAVEL RULE for virtual asset transfers. The 2024 FATF Targeted Update on Virtual Assets + VASPs (R.15 / R.16) refined implementation expectations. CORE REQUIREMENTS: VASPs must obtain + hold + transmit required originator and beneficiary information for virtual asset transfers; the de minimis threshold is set at USD/EUR 1,000 (lower than for traditional wire transfers); information includes originator name + originator account number / wallet identifier + originator address or national identity number / customer identification number / date and place of birth + beneficiary name + beneficiary account number / wallet identifier. The recipient VASP must conduct counterparty VASP due diligence (CVDD) to determine that the counterparty VASP is licensed/registered + has appropriate AML/CFT controls + risk-rates the counterparty + applies enhanced measures where appropriate. The 'SUNRISE PROBLEM' refers to cross-jurisdictional implementation gaps where some jurisdictions have transposed FATF R.16 for VASPs but others have not - leaving VASPs in compliant jurisdictions transferring to or receiving from VASPs in non-compliant jurisdictions facing ambiguity. UNHOSTED WALLET TRANSFERS (transfers to or from self-hosted / non-custodial wallets) raise additional risks; the 2024 FATF Targeted Update reinforced that VASPs should apply risk-based + enhanced measures + collect originator information for outbound transfers to unhosted wallets + assess incoming transfers from unhosted wallets. EU implementation via Transfer of Funds Regulation (TFR) (Regulation (EU) 2023/1113) + complementing the MiCA + AMLR. US implementation via FinCEN 31 CFR 1010.410(f) (Travel Rule) covering CVCs (Convertible Virtual Currencies). UK implementation via the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017. Travel Rule technical infrastructure includes the InterVASP Messaging Standard (IVMS101) for data exchange + multiple competing networks (TRP, TRUST, Sygna Bridge, OpenVASP, Notabene, Sumsub Travel Rule). Travel Rule compliance is a precondition for VASP licensing in most jurisdictions + a barrier to market access for non-compliant VASPs. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does FATF Recommendation 16 - Virtual Asset Travel Rule have?
FATF Recommendation 16 - Virtual Asset Travel Rule has 13 controls organised across 7 domains. The largest domains are R.16 VATR: Record Retention, Audit, Training and Status (3 controls), R.16 VATR: Counterparty VASP Due Diligence and Sanctions Screening (2 controls), R.16 VATR: Required Originator and Beneficiary Information (2 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does FATF Recommendation 16 - Virtual Asset Travel Rule map to?
FATF Recommendation 16 - Virtual Asset Travel Rule maps to 88 other compliance frameworks. The top mapping partners are Pakistan Personal Data Protection Bill 2023 (15% coverage), Italy Personal Data Protection Code (Legislative Decree No. 196/2003, amended 2018) (15% coverage), Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (UAE PDPL) (15% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with FATF Recommendation 16 - Virtual Asset Travel Rule compliance?
Start your FATF Recommendation 16 - Virtual Asset Travel Rule compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about FATF Recommendation 16 - Virtual Asset Travel Rule requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 13 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required