Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

DRAFT

Travel Rule Protocol (TRP)

What is TRP? The Travel Rule Protocol (TRP) is an open, decentralized protocol designed to enable VASPs to exchange Travel Rule data directly with one another. It focuses on minimizing centralized dependencies by allowing parties to discover endpoints and exchange information in a peer-to-peer manner. TRP is maintained by the OpenVASP initiative and is commonly adopted by infrastructure-focused and protocol-native ecosystems.

How Ospree Helps with TRP Integration - Ospree abstracts TRP complexity by:

  • Handling TRP message formatting and lifecycle management

  • Abstracting mTLS and protocol-specific requirements

  • Managing counterparty discovery and protocol routing

  • Providing unified monitoring, logging, and audit trails

  • Allowing customers to interact with TRP via Ospree’s API and Console without building protocol-specific logic

TRP Workflows Using Ospree Travel Rule API:

When interacting with counterparties through TRP, a travel address is used to resolve the transfer request to the correct counterparty VASP.

  • Transfer Request - for initiating a transfer request through TRP, use Create Transfer endpoint, specifying "trp" as the protocol and passing the travel address received from the counterparty. The example below assumes that the originator_account and beneficiary_account already exists. Refer to Create Transfer page for more details. 

curl -X POST https://sandbox.ospree.io/api/v2/travelrule/transfers

-h 'Content-Type: application/json' \
-h 'Accept: application/json' \
-h 'Authorization: ••••••' \
-d '{
    "amount": 1.21,
    "dti": "4H95J0R2X",
    "protocol": "trp",
    "reference_id": "reference-transfer-01",
    "travel_address": "ta3J3bcpjsAEtGt9M5Q7GkD166VE22iDX6odePdJee1aBb5dX",
    "originator_address": "3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy",
    "originator_account_reference_id": "random-ref-id-101",
    "beneficiary_address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
    "beneficiary_account_reference_id": "random-ref-id-102"
}'

  • Transfer Inquiry Resolution - for approving or rejecting an incoming TRP transfer request, use Action Transfer endpoint.

Approve transfer example:

Reject transfer example:

  • Transfer Confirmation - for confirming or canceling the crypto transfer, use Action Transfer endpoint.

Confirm transfer example:

Cancel transfer example:

References

  • https://www.openvasp.org/trp

  • https://gitlab.com/OpenVASP/travel-rule-protocol

TRISA

What is TRISA? The Travel Rule Information Sharing Alliance (TRISA) is a framework and protocol designed to enable compliant and secure information sharing between VASPs. TRISA emphasizes identity verification, mutual authentication, and trust frameworks to support regulated financial institutions. TRISA is commonly adopted by regulated entities seeking strong identity assurances and structured governance.

How Ospree Helps with TRISA Integration - Ospree simplifies TRISA adoption by:

  • Managing certificate handling and identity verification flows

  • Abstracting mTLS and protocol-specific requirements

  • Unifying TRISA interactions with other Travel Rule protocols

  • Providing centralized reporting, auditability, and operational visibility

  • Customers integrate once with Ospree and gain TRISA support without building or maintaining protocol-specific infrastructure.

TRISA Workflows Using Ospree Travel Rule API:

  • Transfer Request - for initiating a transfer request through TRISA, use Create Transfer endpoint, specifying "trisa" as the protocol.

  • Transfer Accepted - for accepting an incoming TRISA transfer request, use Action Transfer endpoint.

  • Transfer Completed - for completing the crypto transfer, use Action Transfer endpoint.

  • Transfer Rejected - for rejecting the transfer, use Action Transfer endpoint.

References

  • https://travelrule.io/

  • https://github.com/trisacrypto/trisa