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

# CryptoSwift

#### Integration type

Travel Rule Platform

#### Description

CryptoSwift interoperability allows Ospree customers to exchange Travel Rule information with VASPs reachable through the CryptoSwift network.

CryptoSwift uses **STRIP (Simple Travel Rule Information Protocol)**, an open-source JSON-based standard for exchanging Travel Rule information.

### How it works

1. **Counterparty identification** — Ospree identifies whether the beneficiary VASP is reachable through CryptoSwift.
2. **Data exchange** — Ospree routes the required Travel Rule information through CryptoSwift.
3. **Counterparty response** — The receiving VASP reviews and responds to the transfer.
4. **Status update** — Relevant responses are reflected in the Ospree Travel Rule workflow.

### Integration

Ospree customers continue using the standard **Ospree Travel Rule API**. No direct CryptoSwift integration is required.

Ospree manages the protocol-specific communication and uses CryptoSwift as an interoperability route when the selected counterparty is reachable through the network.

### References

* [CryptoSwift](https://cryptoswift.eu/)