FATF Recommendation 16 - Payment Transparency (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.
FATF Recommendation 16 - Payment Transparency (Travel Rule) is a compliance framework from Global (FATF members and FSRB members; transposed by national law) with 7 domains and 31 controls that map to 77 other frameworks. The largest domains are Exceptions and differentiated requirements (INR.16 paragraphs 13 to 19) – FATF Recommendation 16 - Payment Transparency (Travel Rule) (7 controls), Information requirements for cross-border and domestic payments (INR.16 paragraphs 4 to 12) – FATF Recommendation 16 - Payment Transparency (Travel Rule) (7 controls), Beneficiary financial institution and MVTS providers (INR.16 paragraphs 28 to 32) – FATF Recommendation 16 - Payment Transparency (Travel Rule) (5 controls). Every control below carries what it requires and what an assessor expects to see.
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)
Beneficiary financial institution and MVTS providers (INR.16 paragraphs 28 to 32) – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.28 | INR16.28 Beneficiary institution: reasonable measures to identify missing information |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.29 | INR16.29 Beneficiary institution: verification of beneficiary identity above the threshold |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.30 | INR16.30 Beneficiary institution: detecting misdirected payments through alignment checks |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.31 | INR16.31 Beneficiary institution: risk-based policies on execution, rejection or suspension |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.32 | INR16.32 Money or value transfer service providers |
Exceptions and differentiated requirements (INR.16 paragraphs 13 to 19) – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.13 | INR16.13 No information required for institution-to-institution transfers |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.14 | INR16.14 Net settlements and their underlying transactions |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.15 | INR16.15 Batch transfers from a single originator |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.16 | INR16.16 Card payments for goods and services |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.17 | INR16.17 Card used for other transfers |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.18 | INR16.18 Domestic cash withdrawals |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.19 | INR16.19 Cross-border cash withdrawals |
Information requirements for cross-border and domestic payments (INR.16 paragraphs 4 to 12) – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.10 | INR16.10 Domestic transfers below the de minimis threshold |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.11 | INR16.11 Domestic transfers above the threshold: full information or availability by other means |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.12 | INR16.12 Originator information within three business days; immediate production for law enforcement |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.4 | INR16.4 Structured information sufficient to identify originator and beneficiary |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.7 | INR16.7 Servicing institutions and their countries identifiable; no disguised account numbers |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.8 | INR16.8 Cross-border transfers below the de minimis threshold |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.9 | INR16.9 Cross-border transfers above the threshold: the full information set |
Intermediary financial institution (INR.16 paragraphs 24 to 27) – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.24 | INR16.24 Intermediary institution: information retained with the transfer |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.25 | INR16.25 Intermediary institution: five-year record where technical limits prevent pass-through |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.26 | INR16.26 Intermediary institution: reasonable measures to identify missing information |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.27 | INR16.27 Intermediary institution: risk-based policies on execution, rejection or suspension |
Ordering financial institution (INR.16 paragraphs 20 to 23) – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.20 | INR16.20 Ordering institution: required and accurate originator information above the threshold |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.21 | INR16.21 Ordering institution: names and account or reference numbers below the threshold |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.22 | INR16.22 Ordering institution: retention of originator and beneficiary information |
| fatf-recommendation-16-payment-transparency-travel-rule::INR16.23 | INR16.23 Ordering institution: no execution of non-compliant transfers |
Screening, freezing and monitoring under Recommendation 16 – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::R16-MON | R16-MON Monitoring for transfers lacking required information |
| fatf-recommendation-16-payment-transparency-travel-rule::R16-TFS | R16-TFS Freezing action and prohibited transactions with designated persons in the payment chain |
Virtual asset transfers (INR.15 paragraph 7(b)) – FATF Recommendation 16 - Payment Transparency (Travel Rule)
| Code | Title |
|---|---|
| fatf-recommendation-16-payment-transparency-travel-rule::INR15.7b-BEN | INR15.7b-BEN Beneficiary VASP: obtain and hold information and apply the other R.16 duties |
| fatf-recommendation-16-payment-transparency-travel-rule::INR15.7b-ORIG | INR15.7b-ORIG Originating VASP: obtain, hold and submit originator and beneficiary information |
Your Compliance Coverage
If you comply with FATF Recommendation 16 - Payment Transparency (Travel Rule), you already cover:
Pakistan Personal Data Protection Bill 2023
5%
2 controls mapped
Compare →Italy Personal Data Protection Code (Legislative Decree No. 196/2003, amended 2018)
5%
2 controls mapped
Compare →Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (UAE PDPL)
5%
2 controls mapped
Compare →+ 74 more: UAE Virtual Asset Regulatory Authority (VARA) Regulations (5%), ISO/IEC 29147:2018 (5%)
See all 77 mapped frameworks ↓Maps to 77 other frameworks
Coverage is not the same as your position
This page shows what FATF Recommendation 16 - Payment Transparency (Travel Rule) overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is FATF Recommendation 16 - Payment Transparency (Travel Rule) and who does it apply to?
FATF Recommendation 16 - Payment Transparency (Travel Rule) is a compliance framework from Global (FATF members and FSRB members; transposed by national law) with 7 domains and 31 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.
What does FATF Recommendation 16 - Payment Transparency (Travel Rule) actually require?
FATF Recommendation 16 - Payment Transparency (Travel Rule) has 31 controls organised across 7 domains. The largest domains are Exceptions and differentiated requirements (INR.16 paragraphs 13 to 19) – FATF Recommendation 16 - Payment Transparency (Travel Rule) (7 controls), Information requirements for cross-border and domestic payments (INR.16 paragraphs 4 to 12) – FATF Recommendation 16 - Payment Transparency (Travel Rule) (7 controls), Beneficiary financial institution and MVTS providers (INR.16 paragraphs 28 to 32) – FATF Recommendation 16 - Payment Transparency (Travel Rule) (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of FATF Recommendation 16 - Payment Transparency (Travel Rule) do I already cover?
FATF Recommendation 16 - Payment Transparency (Travel Rule) maps to 77 other compliance frameworks. The top mapping partners are Pakistan Personal Data Protection Bill 2023 (5% coverage), Italy Personal Data Protection Code (Legislative Decree No. 196/2003, amended 2018) (5% coverage), Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (UAE PDPL) (5% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement FATF Recommendation 16 - Payment Transparency (Travel Rule)?
Start your FATF Recommendation 16 - Payment Transparency (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 - Payment Transparency (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 31 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 704 frameworks.
Get Started Free →Free forever — no credit card required