Ospree docs
API ReferenceWebsiteSocials
  • GETTING STARTED
    • Intro to Ospree
      • What is the Travel Rule?
      • Types of Travel Rule transfers
      • What is a wallet address?
      • What is an Account at Ospree?
      • What is a VASP or CASP?
    • Account
      • Understand user roles
      • Add and manage users
      • Change your password
      • Set up two-factor authentication (2FA)
      • Log in with 2FA-enabled
  • DASHBOARD
    • Overview
    • Travel Rule
      • Start a transfer
      • Search and filter transfers
      • Interoperability
      • Self-hosted wallets
    • Accounts Directory
      • Create an account
      • Edit an account
      • Create a recipient
      • Edit a recipient
      • Add a new wallet
      • VASPs
        • Search and filter
        • Request a VASP
  • OSPREE API
    • Overview
    • API integration flows
    • Authentication
    • Breaking Changes
    • Errors
    • Token Identifier
    • Webhooks
      • Webhook events
      • Webhook request
      • Webhook management
    • Travel Rule
      • Create Transfer
      • List Transfers
      • Retrieve Transfer
      • Update Transfer
      • Action Transfer
    • Accounts Directory
      • Create Account
      • List Accounts
      • Retrieve Account
      • Update Account
      • Remove account
      • Search account
      • Retrieve VASP
      • Search VASP
      • List VASPs
    • Blockchain Analytics
      • Create Address
      • List Addresses
      • Retrieve Address
      • Assign an address to account
      • Create Transaction (Beta)
      • List Transactions (Beta)
      • Retrieve Transaction (Beta)
  • Resources and Help
    • Data pre-validation
    • Sunrise Issue
Powered by GitBook
On this page
  • Ospree-to-Ospree Transfer
  • Multi-Protocol Transfer
  1. DASHBOARD
  2. Travel Rule

Interoperability

Last updated 1 month ago

One of the greatest challenges in complying with the Travel Rule for VASP-to-VASP transactions is ensuring interoperability across various protocols. As businesses and financial institutions adopt different Travel Rule solutions, the ability to exchange information seamlessly across these platforms becomes essential for efficient and secure transactions.

Ospree-to-Ospree Transfer

When an Ospree client initiates a transfer to another Ospree client, the platform will default to using the Ospree Flow unless the client specifies otherwise.

Note: Ospree is actively expanding support for additional Travel Rule protocol. Some integrations are already available, and others are on the roadmap. For the latest updates or specific requests, please contact support@ospree.io.

Multi-Protocol Transfer

When an Ospree client sends or receives a transfer from a non-Ospree client using a travel rule solution connected through a shared protocol, the platform automatically selects that protocol. If multiple protocols are available, and unless the client specifies otherwise, the platform will default to the fastest, most cost-effective, and highly compatible option.