POC 2 · FATF Rec 16 · Data Transmission Layer

Travel Rule Validator

Cross-border transfers ≥$1,000 must include originator and beneficiary identifying information. This tool builds and validates IVMS101-compliant Travel Rule messages with threshold analysis and protocol compatibility checks.

Dual-Track Comparison

Travel Rule Data Flow vs. P2P Gap

The top track shows a regulated VASP-to-VASP transfer with all 8 stages populated. The bottom track shows a P2P unhosted wallet transfer — 5 empty stations reveal the compliance gap the FATF warns about.

REC 16 TRAVEL RULE: REGULATED VS. P2POFAC / SANCTIONS SCREENING ZONERec 16 Travel RuleP2P Unhosted①Intent②Identity③Discovery④Negotiation⑤Transport⑥Authorization⑦Facilitation⑧Finality

Interactive Proof of Concept

IVMS101 Message Builder

How it works: Enter transfer details or select a pre-loaded scenario. The validator builds an IVMS101 message and checks compliance.

  • Threshold gate — transfers ≥$1,000 trigger full Travel Rule requirements
  • Completeness score — shows what percentage of required fields are populated
  • Protocol compatibility — tests against TRUST, Notabene, Sygna, OpenVASP, and TRP
Transfer Details
Quick Scenarios
Originator
Beneficiary
IVMS101 Message
Click "Validate IVMS101" to generate message.

Reference

Rec 16 Thresholds & Deadlines

What to know: The Travel Rule applies differently based on transfer amount, type, and jurisdiction.

  • Cross-border ≥$1,000 — full originator and beneficiary info must travel with the transfer
  • Domestic ≥$1,000 — if full info not sent, must be available within 3 business days on request
  • Below $1,000 — simplified due diligence; basic originator info only
  • October 2026 — FATF assessment methodology deadline for all jurisdictions
  • December 2030 — global Travel Rule implementation deadline
  • 85 of 117 jurisdictions have passed or are processing Travel Rule legislation (73% compliance rate)