Travel Rule Message Builder
Build and validate IVMS101-compliant Travel Rule messages per Regulation (EU) 2023/1113
Originating VASP
Originator (Customer)
Beneficiary (Recipient)
Beneficiary VASP
Transaction Details
34 fields missing
Missing fields:
- Originating VASP LEI
- Originating VASP name
- Originating VASP street
- Originating VASP city
- Originating VASP postal code
- ... and 29 more
What This POC Does Not Implement
- ❌ VASP Directory Lookup — Does not verify that beneficiary VASP exists or is MiCA-compliant in a real registry
- ❌ Message Transmission — Does not actually send the IVMS101 message to the beneficiary VASP
- ❌ Blockchain Integration — Does not interact with actual blockchain nodes to confirm transfers
- ❌ Cryptographic Signing — Does not cryptographically sign the message per IVMS101 PKI requirements
- ❌ Counterparty Compliance Validation — Does not check if beneficiary VASP supports IVMS101 or Travel Rule compliance
- ❌ NCA Reporting — Does not submit transaction records to National Competent Authority (NCA)
MiCA Compliance Context
Regulation (EU) 2023/1113 (Travel Rule): Requires that information concerning the originator and beneficiary of a transfer of crypto-assets shall be transmitted along with the transfer.
IVMS101 Standard (v1.0): Defines the message structure for VASP-to-VASP originator and beneficiary information exchange. This POC implements the core fields required per IVMS101.
EU Scope: Regulation 2023/1113 establishes EUR 1,000 threshold for certain information requirements (self-hosted transfers). Threshold rules differ for VASP-to-VASP transfers. This POC focuses on message structure, not threshold enforcement.
Disclaimer: This is an educational POC. It does not constitute compliance certification. Actual Travel Rule compliance requires integration with real VASP infrastructure, NCA reporting systems, and cryptographic verification.