IVMS101: The Test of True Travel Rule Compliance

Interoperability has become the real measure of readiness under the Travel Rule. The interVASP Messaging Standard 101 (IVMS101) was developed to create a single, consistent data format for originator and beneficiary information between Virtual Asset Service Providers (VASPs). In principle, it should allow identity data to move seamlessly between systems and jurisdictions. In practice, it has not yet achieved that goal.

Five years after its introduction, adoption remains uneven, translation layers are emerging across networks, and technical incompatibilities persist even among institutions that claim compliance. The question facing regulators and industry is whether voluntary alignment can deliver genuine interoperability, or whether a more prescriptive framework is now required to safeguard financial integrity at scale.

A Standard Born from Collaboration

IVMS101 was introduced in 2020 by the Joint Working Group on interVASP Messaging Standards (JWG), a consortium including the Chamber of Digital Commerce, Global Digital Finance (GDF), and the International Digital Asset Exchange Association (IDAXA). Its purpose was to provide a common schema for transmitting originator and beneficiary details in line with the Financial Action Task Force’s (FATF) Recommendation 16, the Travel Rule (interVASP.org).

The standard defines how key identity fields should be structured, encoded, and transmitted between counterparties, and was designed to be protocol-agnostic. Governance now sits under GDF’s Open Standards Council, with an interVASP Standards Working Group (ISWG) responsible for maintenance and updates. On 4 June 2024 the ISWG ratified a new version of IVMS101 that improved “consistency, maintainability and technical clarity” (VASPnet, 2024).

Yet the wider ecosystem has not kept pace. The FATF’s Targeted Update on Implementation of the FATF Standards on Virtual Assets and Virtual Asset Service Providers (July 2024) found that “progress remains uneven,” citing “deficiencies in some compliance tools, limited interoperability testing, and weak supervision” (FATF, 2024). These observations underline that a technical specification alone cannot ensure compliance where governance diverges.

IVMS101 in Practice: When Compliance Does Not Mean Connection

Two VASPs can each claim Travel Rule compliance yet fail to communicate effectively. One reason lies in protocol diversity. Frameworks such as TRISA, TRP, and OpenVASP all use IVMS101 but differ in trust models and message validation. The open-source collaboration between TRISA and TRP, announced in November 2023, demonstrated interoperability when message semantics and trust anchors are aligned (TRISA.io, 2023).

Variation within the standard compounds the problem. Industry commentary shows that some vendors modify or reinterpret IVMS101, treating optional fields as mandatory or changing field naming conventions. OpenVASP’s IVMS validator, which supports both TRP and TRUST variations, implicitly acknowledges that real-world conformity requires testing as well as documentation (OpenVASP, 2024).

Regulatory asynchrony adds further complexity. The so-called “sunrise problem” means jurisdictions adopt the Travel Rule at different times and with differing thresholds. The European Union’s Regulation (EU) 2023/1113 established detailed requirements for crypto-asset transfers, but many non-European markets remain years behind. This divergence can depress message acceptance rates and force manual remediation where counterparties’ data obligations do not align.

Interoperability as a Measure of Integrity

Interoperability is not merely a technical issue. It is a measure of financial integrity. Inconsistent data exchange breaks traceability and creates systemic risk. Each failed or delayed transfer fragments the audit trail that investigators depend upon. The result is friction, false rejections, and diminished intelligence value.

This is not a uniquely crypto-native problem. The global payments sector has already undergone a similar transformation through ISO 20022. SWIFT’s PMPG Hybrid Postal Address guidance and migration roadmap mandate structured address fields to enhance sanctions screening accuracy (Swift, 2024). The Bank of England’s ISO 20022 Handbook for CHAPS and RTGS sets the same expectation: richer, more structured data means better compliance and faster investigations (Bank of England, 2023).

Aligning IVMS101 attributes to ISO 20022 data concepts would likely improve data integrity and reduce reconciliation failures across hybrid fiat-crypto flows. It would also help normalise Travel Rule messaging within the broader discipline of structured payments data, reinforcing the principle that traceability depends on precision, not protocol.

The Case for Prescriptive Alignment

The FATF’s 2024 update called for “further strengthening of technical interoperability” and for jurisdictions to ensure that “VASPs can exchange required information efficiently and securely.” (FATF, 2024) This is a clear signal that self-regulation is no longer sufficient.

The next step should be a minimal interoperable profile for IVMS101; defining encoding, field types, and mandatory attributes with greater precision. Open-source conformance suites could then verify that any system claiming compliance meets a uniform operational benchmark. The FATF need not prescribe architecture, but it could define the non-negotiable elements of structure and validation that every protocol must respect.

Supervisors could reference these test suites in guidance and supervision. That would close the gap between nominal compliance and practical interoperability, aligning supervisory expectations with measurable technical outcomes.

Building a Shared Future

The progress of 2023–2025 shows that harmonisation is possible. The TRISA–TRP bridge proved that protocols can interoperate. GDF’s stewardship of IVMS101 ensures neutral governance. And a growing number of VASPs are participating in cross-network testing. What remains is collective commitment. Competing on proprietary implementations only prolongs fragmentation and raises compliance costs for everyone.

The Travel Rule is ultimately about trust and traceability. When originator and beneficiary data can move securely and consistently across networks, legitimate business benefits and regulators gain meaningful visibility. Fragmentation achieves the opposite: uncertainty, inefficiency, and erosion of credibility across the ecosystem.

Conclusion

The promise of the Travel Rule lies not in the volume of messages exchanged but in the integrity of the data they carry. IVMS101 gave the sector a common language; it did not guarantee fluency. To realise its potential, the standard must now evolve from description to prescription.

Interoperability will determine who succeeds in the next phase of global compliance. The industry has the technology, the FATF has the authority, and the incentives are aligned. What remains is a collective decision to standardise not only what we collect, but how we exchange it.

Is your Travel Rule compliance truly interoperable, or just technically compliant?

If your systems exchange data but not trust, interoperability remains theoretical. At OpusDatum, we build the controls that make WTR compliance real.

Discover how WireCheck delivers real-time WTR monitoring for PSPs and VASPs.

Request a demo now.