Origin and objectives
TRISA was developed starting in 2019 within the context of the CipherTrace initiative (later part of Mastercard) and published as an open standard. This was in response to the 2019 update of Recommendation 16 by the Financial Action Task Force (FATF), the so-called Travel Rule. This rule requires Virtual Asset Service Providers (VASPs) to collect and forward certain information about the originator and beneficiary when transferring crypto assets to the receiving service provider.
TRISA aims to enable this data exchange without altering the underlying blockchain protocols and without making the transferred customer data publicly visible. The standard is maintained by a non-profit organization, the TRISA Working Group.
Technical Functionality
TRISA is based on established internet technologies. Communication between service providers takes place via mutually authenticated TLS (mutual TLS) and the gRPC protocol. Each participating VASP receives a digital certificate from a central certificate authority, which confirms its identity.
A central directory (Global Directory Service) enables participants to locate each other and verify the authenticity of the other party. The actual customer data is structured in the standardized format of the IVMS-101 specification and transmitted end-to-end encrypted. The blockchain transaction itself and the data exchange are separate processes (off-chain).
Classification and connections
TRISA is one of several competing or complementary approaches to implementing the Travel Rule. Other protocols and networks include OpenVASP, the TRP (Travel Rule Protocol), and commercial solutions from providers such as Notabene or Sygna. Because these systems employ different approaches, efforts are underway to achieve interoperability between the networks.
The IVMS-101 data structure serves as a common denominator used by several of these protocols. TRISA is considered an open-source, vendor-neutral option and is primarily used by service providers who prefer a free basic infrastructure.
Frequently Asked Questions
TRISA stands for Travel Rule Information Sharing Architecture. It is an open-source framework designed to facilitate the secure exchange of information required under the FATF Travel Rule.
Since 1 October 2026, the Swiss-based OpenVASP Association has owned and stewarded the TRISA network, Working Group and TRISA Envoy open-source codebases. Rotational Labs continues to operate and support the infrastructure on behalf of OpenVASP.
No. TRISA continues to operate and existing implementations remain supported. TRISA and TRP are separate but interoperable approaches to Travel Rule compliance, now both under OpenVASP stewardship.
TRISA is based on open-source software, and TRISA Envoy is available under the MIT License. Organisations can inspect, modify and self-host the software. However, operational, integration and commercial hosting costs may apply.
Both are open approaches to Travel Rule data exchange, but they use different technical architectures and counterparty discovery mechanisms. TRISA uses its Global Directory Service (GDS) for institutional trust and discovery, while TRP uses Travel Addresses to identify the receiving VASP and its data exchange endpoint. The two established interoperability in 2023 and can be used together.
The GDS is TRISA's institutional trust and discovery layer. It provides mTLS certificates and enables participating VASPs to discover and authenticate counterparties. It does not function as a central repository for Travel Rule transaction information.
Yes. TRISA Envoy supports both TRISA and TRP messaging, uses IVMS101 and provides a REST/JSON API. It can also be self-hosted within an institution's own infrastructure.
No. Travel Rule information is exchanged off-chain, directly between authenticated counterparties. The GDS facilitates institutional trust and discovery but does not centrally store Travel Rule transaction data.
OpenVASP provides a neutral, member-governed organisational home for TRISA and TRP. Its stewardship aims to improve interoperability, support open-source development and reduce fragmentation between Travel Rule solutions while maintaining privacy-preserving data exchange.