FATF Travel Rule · R.16 VASP $1,000 K KYC Information Transmission

Wiki route

This entry sits under fintech index. Read it with Japan Financial Regulation — Legal Framework for Tokens, Crypto Assets, and Payments for adjacent context and Three-Layer Structure of Japan's Stablecoin Regulatory Regime (JPYC, USDC, Project Pax) for the broader system boundary.

[!info] TL;DR FATF Recommendation 16 is the global VASP industry’s unified AML/CFT information-transmission standard — when a VASP transfer reaches or exceeds USD/EUR 1,000 , sharing of originator and beneficiary KYC information is mandatory. It is a transplant of the 1996 BSA Travel Rule into the crypto asset domain. The BTS (Business-To-Service) layer of Notabene / TRISA / Sygna / TRP etc. has become mandatory compliance infrastructure — without connection to a Travel Rule protocol, a VASP cannot obtain operating qualification.

Key facts

• FATF established in 1989 by G7 · 40 member countries + 9 regional bodies ^•
• R.15 + R.16 crypto extension at 2019-06 G20 Osaka summit ^•
• R.16 threshold: USD/EUR 1,000 global floor ^•
• 1996 BSA Travel Rule (31 CFR §1010.410(f)) originally covered only ≥ $3,000 wire transfers ^•
• 2019-05 FinCEN FIN-2019-G001 clarified BSA Travel Rule application to CVCs ^•
• 2024 US FATF MER rated “Largely Compliant” ^•
• 2026-Q3 FinCEN proposed reducing US threshold from $3,000 to $1,000 (aligning with FATF) ^•

Mechanism / How it works

R.16 requires that for VASP transfers ≥ USD/EUR 1,000 , the following must be shared: Originator name + account number / wallet address, Beneficiary name + account number / wallet address. VASP-to-VASP information sharing is mandated. The biggest technical challenge: CVC transfers are often sent to wallet addresses, not to institutions → the lack of a “receiving financial institution” concept gave birth to the BTS (Business-To-Service) protocol layer.

Major BTS protocols:

• Notabene (US 2020 · largest market share): Bitstamp / Luno / OKX
• TRISA (open-source · distributed TLS): Binance (partial)
• Sygna Bridge (CoolBitX · Asia-Pacific priority): South Korea / Taiwan VASPs
• TRP (TRP Group · OpenAPI): Coinbase / Kraken / Gemini
• Shyft (token incentive · on-chain discovery): early participant
• OpenVASP (Europe · EVM-based): early European

Interoperability problem: protocols are mutually incompatible → multi-protocol connection or choice of largest network is required. Notabene + TRP together cover approximately 80% of global VASP flow volume for 2026 年. For Travel Rule implementation within Japan VASP self-regulation, see JVCEA: Overview of the Self-Regulatory Framework; for Japan VASP timeline, see Domestic Crypto-Asset VASP Regulatory Timeline (2014–2026).

Origin & evolution

1996 FinCEN + Fed jointly issued the BSA Travel Rule (31 CFR §1010.410(f)), originally covering only ≥ $3,000 wire transfers. 2019-05 FinCEN FIN-2019-G001 clarified BSA Travel Rule application to CVCs. 2019-06 G20 Osaka summit: FATF announced R.15 + R.16 crypto extension → global floor established. 2024-12-30 EU Transfer of Funds Regulation (TFR) 2023/1113 set EU threshold at EUR 0 (strictest). 2026-Q3 FinCEN proposed reducing US threshold from $3,000 to $1,000 (aligning with FATF). For cross-border four-layer stack details, see FATF Travel Rule Cross-Border Four-Layer Stack · Jurisdictional Threshold Divergence + §501 Linkage.

Related

• Wiki Index
• FATF Travel Rule Cross-Border Four-Layer Stack · Jurisdictional Threshold Divergence + §501 Linkage
• FATF Grey List / Black List and the AML/CFT Country Evaluation Mechanism
• GENIUS Act §501
• Deep dive into MiCA EMT vs ART sub-classification · Product shaping based on regulatory burden

Sources