FATF Travel Rule
Financial Action Task Force Recommendation 16 – Virtual Asset Travel Rule
VASPs must collect and transmit originator and beneficiary information for virtual asset transfers of USD/EUR 1,000 or more.
What this covers
FATF Recommendation 16 (the Travel Rule) requires VASPs to collect and transmit originator and beneficiary information alongside any transfer at or above USD/EUR 1,000. The rule mirrors what banks have done for wire transfers since 1996 – FATF extended it to crypto in 2019.
Over 50 jurisdictions have now implemented or are implementing it. The EU went with MiCA Travel Rule. The UK used its own statutory instrument under the Money Laundering Regulations. Singapore, Japan, and South Korea each have national-level rules in force. The US has existing FinCEN Travel Rule requirements that cover VASPs under the Bank Secrecy Act.
Implementation varies more than the FATF text suggests. The de minimis threshold, treatment of unhosted wallets, and sunrise period rules differ by jurisdiction. A VASP operating across multiple regions needs to track which rules apply to which transaction leg – which is where multi-jurisdiction KYC platforms have an edge.
Frequently asked questions
What is the FATF Travel Rule threshold?
The FATF threshold is USD/EUR 1,000. Transfers at or above this amount require originator and beneficiary information to travel with the transaction.
Which countries have implemented the FATF Travel Rule?
As of 2026, over 50 jurisdictions have implemented or are implementing FATF Recommendation 16, including the EU (via MiCA), UK (FCA PS22/1), US (FinCEN), Singapore (MAS PSA), and Japan (FSA).
Does FATF Travel Rule apply to unhosted wallets?
FATF guidance recommends applying the travel rule to transfers involving unhosted wallets when the counterparty VASP cannot verify the wallet ownership. Individual jurisdiction implementation varies.