Originator + beneficiary data sufficiency, across five regimes that don't agree.
Configure your VASP's originator + beneficiary data-collection policy and score it against FATF Recommendation 16 and four jurisdictional implementations: EU TFR (Regulation 2024/1624, applicable from 30 December 2024), FinCEN 31 CFR 1010.410(f), UK MLR 2017, and MAS Notice PSN02. The matrix surfaces which fields each regime requires and the de-minimis threshold each applies. Exports an AP2 mandate the agentic runtime can enforce on every VASP-to-VASP send.
FATF Recommendation 16 (the "Travel Rule") extends originator+beneficiary data-sufficiency obligations from wire transfers to virtual asset transfers between VASPs. The EU Transfer of Funds Regulation (Regulation (EU) 2024/1624, applicable from 30 December 2024) implements R.16 with no de-minimis for crypto-asset transfers. In the US, FinCEN 31 CFR 1010.410(f) applies at $3,000 with a 2020 NPR proposing a $250 threshold for cross-border crypto (still pending). The EU AML Authority (AMLA) (Regulation 2024/1620) begins direct supervision of selected obliged entities, including VASPs, in 2028.
Pick the home regime
The primary jurisdiction sets baseline expectations; the matrix below scores your policy against all five regimes regardless.
Originator fields
Toggle which fields your VASP collects on every outbound transfer. R = required, O = optional, — = not required.
| Field | FATF | EU TFR | FinCEN | UK MLR | MAS | Collected |
|---|
Beneficiary fields
Beneficiary requirements are universally lighter than originator. The unique reference (address or wallet ID) is the universal floor.
| Field | FATF | EU TFR | FinCEN | UK MLR | MAS | Collected |
|---|
De-minimis & sunrise handling
Composite + per-jurisdiction
Compose with
Pair with #8 — Stablecoin Issuer Readiness (every issuer's redemption / on-and-off-ramp partners are travel-rule counterparties) or #11 — AML TM Rule Builder for the AML programme overlay. The mandate this demo emits is consumable by #27 — Agentic Mandate Sandbox via a custom-schema paste once a corresponding eval engine is registered. Position: Tool Chain Composer, T126 in the AML/KYC cluster.