FATF Recommendation 16: VASP Travel Rule Obligations

Frequently Asked Questions

01.What is the FATF Recommendation 16 threshold for VASP Travel Rule transfers?

FATF recommends a de minimis threshold of USD or EUR 1,000 for virtual asset transfers. Above that amount, the originating and beneficiary VASPs must exchange verified originator and beneficiary information, including names and wallet identifiers. Individual jurisdictions set their own limits, so the United States applies a 3,000 dollar recordkeeping threshold under the Bank Secrecy Act while the EU applies the 1,000 euro standard, and a VASP operating across borders must satisfy the strictest applicable limit on each transfer.

02.How does counterparty VASP screening differ from sanctioned-address screening?

Sanctioned-address screening checks an on-chain wallet against sanctions and high-risk lists before settlement, while counterparty VASP screening verifies the institution on the other side of a transfer. Counterparty due diligence confirms the receiving VASP is licensed, can accept and process Travel Rule data, and maintains an adequate anti-money-laundering program. Both controls are required because a clean address can still belong to an unregulated or non-responsive exchange that cannot lawfully receive the originator information FATF Recommendation 16 mandates.

03.Do VASPs have to file suspicious activity reports under FATF standards?

Yes. FATF Recommendation 20 requires VASPs to report suspicious transactions to their national financial intelligence unit when there are reasonable grounds to suspect money laundering or terrorist financing. Travel Rule data exchange under Recommendation 16 feeds these reports by surfacing mismatched, missing, or evasive counterparty information. A VASP must wire its Travel Rule, transaction-monitoring, and sanctions-screening outputs into a single case-management workflow so a suspicious signal becomes a filed report inside regulatory deadlines.