> For the complete documentation index, see [llms.txt](https://docs.ospree.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ospree.io/developers/travel-rule/interoperability/trp.md).

# TRP

#### Integration type

Travel Rule Protocol

#### Description

The Travel Rule Protocol (TRP) is an open-source, decentralized standard created to help Virtual Asset Service Providers (VASPs) comply with the Financial Action Task Force (FATF) Travel Rule. It facilitates the secure exchange of required originator and beneficiary information between transacting parties during cryptocurrency transfers. Unlike centralized compliance networks, TRP utilizes standard RESTful APIs, allowing VASPs to communicate point-to-point without relying on a central authority. By standardizing the data payload and communication flow, TRP ensures privacy, interoperability, and regulatory compliance across different jurisdictions while maintaining the decentralized ethos of the digital asset ecosystem. It simplifies secure identity verification processes globally.

#### **Technical Overview**

* Peer-to-peer data exchange between VASPs
* Endpoint discovery using standardized identifiers - Secure transmission of Travel Rule payloads
* No central directory or operator dependency

#### Prerequisites and limitations

TRP requires a standard web server hosting publicly accessible RESTful APIs. It is fully decentralized, meaning there is no central network to register with. Security relies on standard SSL/TLS certificates and bilateral authentication (like API keys or mutual TLS). Configuration primarily involves setting up specific REST endpoints (e.g., for transfers) and routing transactions using protocol-specific "Travel Addresses."

#### Important terminology

* Travel Address: A protocol-specific address/identifier provided by a beneficiary VASP. The decision flows indicate that a Travel Address must be available to route a transfer specifically via the TRP protocol.

#### Technical owner

<https://www.openvasp.org/>&#x20;