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

Interoperability

What interoperability means in the context of Ospree

Interoperability enables Ospree to exchange Travel Rule information with external platforms and protocols through standardized, secure integration flows. It allows customers to communicate with counterparties that use different technology providers while maintaining consistent compliance, operational, and data-handling processes. Ospree supports interoperability by translating integration requirements into common workflows for counterparty discovery, information exchange, validation, transfer status updates, and audit records. This reduces fragmentation across the Travel Rule ecosystem and helps customers manage multiple connectivity options through Ospree. The availability and behavior of each integration may vary according to the protocol, provider, jurisdiction, environment, and supported version.

How interoperability works

Ospree builds and maintains integrations with different Travel Rule protocols and platforms. However, technical interoperability does not mean that every customer or counterparty is automatically activated for every integration. Each protocol may have prerequisites such as registration, membership approval, identity verification, certificates, keys, legal agreements, environment configuration, or provider-specific onboarding. Customers must complete the applicable requirements before an integration can be enabled for production use. Activation status, supported capabilities, and prerequisites are documented separately for each protocol.

Future interoperability options: Fireblocks · TRUSTHubs · GTR Further updates will be shared as progress is made.