> 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/dashboard/travel-rule/interoperability.md).

# Interoperability

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.

<figure><img src="/files/6m5OtA7wSN9S66o7MYI9" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
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>.
{% endhint %}

## **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.

<figure><img src="/files/EKQa5UNNeZRa03ytxbNc" alt=""><figcaption></figcaption></figure>