Skip to content
RegTech Codex
Directory

Fatf AML KYC Transaction Monitoring

FATF Recommendation 16 & EU TFR 2023/1113: Crypto & Wire Travel Rule Compliance Audits

Applicable across the EU since December 30, 2024, Regulation (EU) 2023/1113 enforces a EUR 0 Travel Rule threshold on all CASP-to-CASP crypto transfers alongside strict EUR 1,000 self-hosted wallet ownership proofs.

By Victoria Ashworth, LL.M, CAMSReview not recorded
FATF Recommendation 16 & EU TFR 2023/1113: Crypto & Wire Travel Rule Compliance Audits — RegTech Codex 2026 quantitative & supervisory data card
RegTech Codex (FATF Recommendations, CDD/EDD Beneficial Ownership & SAR Typologies): Zero-threshold EU crypto Travel Rule, IVMS101 pre-broadcast sync, and EUR 1,000 unhosted proofs.Source: RegTech Codex Institutional Research DeskLicense: CC-BY-4.0

Full enforcement of Regulation (EU) 2023/1113 (Recast Transfer of Funds Regulation / EU TFR) alongside the European Banking Authority Travel Rule Guidelines (EBA/GL/2024/11) eliminated anonymous institutional crypto routing across Europe: every transfer mediated by an EU Crypto-Asset Service Provider—such as EU entities of Coinbase or Anycoin Direct—is subject to a EUR 0 threshold requiring synchronous IVMS101 originator and beneficiary identity transmission prior to or simultaneously with on-chain settlement. Globally, FATF Recommendation 16 & EU TFR Standards are enforced in tandem by US FinCEN, the UK FCA, HKMA, and Korea KOFIU (KRW 1,000,000 rule). Consult our FATF AML/KYC Compliance Playbook 2026 inside the FATF AML/KYC hub.

Interoperability Across IVMS101 Messaging Protocols & SWIFT ISO 20022 pacs.008#

Under 2026 FATF Travel Rule Benchmark Standards, compliance architects manage two parallel payment-transparency rails: traditional fiat correspondent wires migrating to structured ISO 20022 pacs.008 postal address tags (eliminating unstructured free-text line 1–4 truncation) and VASP-to-VASP IVMS101.2023 encrypted off-chain pre-flight handshakes:

Quantitative Distribution · Governing Rule
Governing Rule
01EU CASP -> EU CASP (Any Val…Reg (EU) 2023/1…02EU CASP <-> Self-Hosted (<=…Reg (EU) 2023/1…03EU CASP <-> Self-Hosted (> …Art. 14(5) & Ar…04Cross-Border Fiat Wire (pac…FATF Rec 16 / E…
Transfer ScenarioGoverning RuleMandatory Payload StandardPre-Settlement GateUncompliant Counterparty Action
EU CASP -> EU CASP (Any Value)Reg (EU) 2023/1113 Art. 14IVMS101 (Name, DLT addr, Address + DOB/ID or LEI)Synchronous pre-broadcast ACK + sanctions screenBlock outbound broadcast until IVMS101 ACK
EU CASP <-> Self-Hosted (<= €1,000)Reg (EU) 2023/1113 Art. 14(5)Collect counterparty name + chain analytics scoreBlockchain risk screen (mixers/sanctions)Quarantine if KYT risk score exceeds floor
EU CASP <-> Self-Hosted (> €1,000)Art. 14(5) & Art. 16(2)Above + ownership proof if client-controlled walletVerify EIP-4361 / BIP-322 signature or Satoshi testHold inbound in suspense until ownership/risk cleared
Cross-Border Fiat Wire (pacs.008)FATF Rec 16 / EU TFR Ch. IIStructured PstlAdr (TwnNm, Ctry) + BIC/LEIStrip-detection & cover-payment pacs.009COV checkReject wire stripping (MT202 misuse without COV)
Pre-broadcast EU TFR 2023/1113 and FATF Recommendation 16 crypto Travel Rule handshake and unhosted wallet verification flow
Pre-broadcast EU TFR 2023/1113 and FATF Recommendation 16 crypto Travel Rule handshake and unhosted wallet verification flowVerified Exhibit

Counterparty VASP Due Diligence & Sunrise-Jurisdiction Controls#

Transmitting sensitive IVMS101 personally identifiable information (PII) to an unverified offshore endpoint risks catastrophic GDPR data breaches and sanctions leaks. Therefore, before opening a TRISA or TRP channel, EU and APAC exchanges—including Binance TH and DigiFinex—conduct Counterparty VASP Due Diligence: verifying regulatory registration on EU MiCA CASP Registers, Estonia FIU, or Lithuania FCIS, validating GLEIF LEI records, and testing ISO 27001 / DORA encryption posture.

Quantitative Travel Rule Completeness & Suspense Routing Model#

Compliance engines evaluate every inbound or outbound transfer payload using a deterministic Travel Rule Completeness & Counterparty Gate ($G_{\text{tr}}$):

Formula or model from the articleNot independently verified
G_tr = (1 - I_sanction_kyt) * [ I_hosted * (B_vasp_kyb * B_ivms101_schema) + (1 - I_hosted) * (I_le_1000 + (1 - I_le_1000) * B_wallet_proof) ]
  • Where:
  • Isanctionkyt = 1 if originator/beneficiary name OR on-chain cluster hits SDN/EU/UN or darknet/mixer list
  • I_hosted = 1 if counterparty DLT address clusters to a VASP; 0 if self-hosted wallet
  • Bvaspkyb = 1 if counterparty VASP passed regulatory & data-protection due diligence; else 0
  • Bivms101schema = 1 if all Art. 14 mandatory fields pass non-null, non-placeholder schema validation (no "N/A" or "123 Main")
  • Ile1000 = 1 if transfer + linked rolling 30-day transfers <= EUR 1,000; else 0
  • Bwalletproof = 1 if cryptographic EIP-4361/BIP-322 signature or verified third-party check completed
  • Worked Inbound Case (EUR 4,800 USDT Arriving from Offshore VASP With Originator Address = "Unknown"):
  • Ihosted = 1, Bvaspkyb = 1, Bivms101schema = 0 -> Gtr = 0 (Quarantine in Suspense Wallet; Issue 3-Day RFI)
Breakdown of inbound Travel Rule suspense-queue triggers at European MiCA CASPs in 2025-2026
Breakdown of inbound Travel Rule suspense-queue triggers at European MiCA CASPs in 2025-2026Verified Exhibit

Safeguarding GDPR Personal Data Security Across TRP & TRISA Channels#

Under Regulation (EU) 2023/1113 Article 15 and GDPR, originator PII transmitted via Travel Rule protocols may never be reused for commercial marketing and must travel exclusively over mutually authenticated mTLS or end-to-end public-key encrypted channels after verifying counterparty VASP data-protection adequacy.

Connecting Travel Rule Screening to On-Chain Mixers & Sanctions Tuning#

Because syndicates attempt to bypass EUR 1,000 unhosted wallet gates by splitting transfers or hopping through intermediate decentralized bridges, pair IVMS101 gateways directly with crypto mixer and cross-chain bridge AML heuristics, structuring and smurfing threshold-evasion models, and OFAC/EU/UN fuzzy name-matching calibration.

Frequently asked questions

What originator and beneficiary fields are mandatory under EU TFR Regulation (EU) 2023/1113?

Under Article 14 of Regulation (EU) 2023/1113, the originator CASP must transmit the originator’s full name, distributed ledger address (and crypto-asset account number), and verified residential address (plus official personal document number, customer ID, or date/place of birth—or LEI for legal entities), alongside the beneficiary’s name and DLT address.

How do regulated exchanges solve the Travel Rule "Sunrise Issue" with non-compliant offshore VASPs?

When a counterparty VASP operates in a jurisdiction that has not yet enforced FATF Recommendation 16 or supports a different messaging protocol (TRP, TRISA, Notabene, Sygna), EBA Guidelines require VASP counterparty due diligence (VASP KYB), sanctions screening, and risk-based restrictions or out-of-band capture before settlement.

How is ownership of an unhosted wallet above EUR 1,000 technically verified?

Under EBA Travel Rule Guidelines (EBA/GL/2024/11), acceptable technical proofs include cryptographic digital-signature challenges (EIP-4361 Sign-In with Ethereum / BIP-322 message signing), micro-deposit "Satoshi tests" from the exact source address, or institutional MPC custody attestations—avoiding easily forged wallet screenshots.

What happens when an inbound crypto transfer arrives at an EU CASP with missing originator data?

Under Articles 16–17 of Regulation (EU) 2023/1113, the beneficiary CASP must detect missing or incomplete IVMS101 data prior to crediting the client’s spendable balance, hold or reject the transfer on a risk-sensitive basis, request missing fields within 3 working days, and assess repeated failures for FIU STR filing.

Publication record

Published
14 November 2026
Updated
14 November 2026
Author
Victoria Ashworth, LL.M, CAMS
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
3 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Victoria Ashworth, LL.M, CAMS. (2026, November 14). FATF Recommendation 16 & EU TFR 2023/1113: Crypto & Wire Travel Rule Compliance Audits. RegTech Codex. https://regtechcodex.org/briefings/fatf-recommendation-16-eu-tfr-crypto-wire-travel-rule-audit
Explore Fatf AML KYC Transaction Monitoring Hub (20) →

RegTech Codex Data, Benchmarks & Contributor Records

FATF Rec 16 & EU TFR 2023/1113 Travel Rule Audit (2026) | RegTech Codex