> 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/ospree.md).

# Ospree

#### Description

Ospree Flow is Ospree’s native method for managing and exchanging Travel Rule information. It supports two primary transfer categories:

* **VASP-to-VASP transfers:** Transfers between two virtual asset service providers. Ospree enables the participating VASPs to exchange, review, and respond to the required originator, beneficiary, and transaction information. When both participants are Ospree customers, Ospree is used by default unless another supported protocol is selected.
* **VASP-to-self-hosted wallet transfers:** Deposits from or withdrawals to wallets controlled directly by an individual or entity rather than another VASP. Ospree supports the collection of wallet-owner information, ownership attestations, address-verification results, and other data required by the VASP’s policies and applicable regulations.

Both transfer categories can be managed manually through the Ospree Dashboard or automated through the Ospree API. Ospree Flow manages the compliance workflow and transfer record but does not execute the underlying blockchain transaction.

#### **Technical Overview**

* Integration: Ospree Flow is available through the Ospree Dashboard and real-time REST APIs. Customers can create, retrieve, update, approve, and reject Travel Rule transfers, while webhooks provide real-time status notifications.
* Data standards and validation: Ospree uses IVMS101-compatible data structures and supports compatibility with ISO 20022 messaging standards. Data pre-validation APIs identify missing or invalid information before submission.
* Security and routing: API requests use bearer-token authentication. Connections are protected with TLS encryption, and customer data is encrypted in transit and at rest. Ospree routes compliance information exchanges and manages transfer records.

#### Prerequisites and limitations

* For a VASP-to-VASP transfer, at least one participating VASP must be an active Ospree customer with access to the Travel Rule module.
* The counterparty VASP must have an approved Ospree account before Travel Rule information can be exchanged through Ospree.
* Ospree Flow does not automatically connect to counterparties available exclusively through external protocols or platforms. The active Ospree customer must approve the counterparty before initiating an exchange.

#### Technical owner

[www.ospree.io](https://www.ospree.io)