FATF Travel Rule Compliance
The FATF Travel Rule requires that originator and beneficiary information accompany virtual asset transfers above a specified threshold. CRYMBO Oracle automates Travel Rule compliance through encrypted identity exchange and on-chain attestation.
How CRYMBO Implements the Travel Rule
- Transaction detected — Oracle identifies a transaction that meets Travel Rule thresholds
- Rule matching — AI Compliance Agent determines jurisdictional requirements for both sender and receiver
- Identity request — Originator information is requested from the sending institution
- Encrypted exchange — PII is encrypted end-to-end and transmitted to the beneficiary institution
- Validation — Validators verify completeness and compliance
- Attestation — On-chain attestation confirms Travel Rule compliance
- Transaction proceeds — Smart contracts allow execution based on attestation
Required Data Fields (IVMS101)
Originator
- Full name
- Account number or wallet address
- Physical address, national identity number, or date and place of birth
Beneficiary
- Full name
- Account number or wallet address
Threshold Handling
| Jurisdiction | Threshold | Action Below |
|---|---|---|
| FATF Recommendation | $1,000 USD | Simplified or no data exchange |
| EU (MiCA) | €0 (all transfers) | Full data exchange required |
| US (FinCEN) | $3,000 USD | Simplified below threshold |
Interoperability
CRYMBO supports Travel Rule data exchange with:
- Other CRYMBO Oracle participants (native)
- TRISA-compatible endpoints
- Notabene network participants
- OpenVASP-compatible systems
- IVMS101-compliant messaging systems