Network Integration & Prerequisites
Prepare shared VASP directories and choose the right bidirectional Travel Rule network flow.
CryptoSwift integrates with external Travel Rule networks to support bidirectional compliance messaging between CryptoSwift customers and VASPs that participate in the partner network. Direction is defined from the system that sends the Travel Rule message:
| Direction | Integration model |
|---|---|
Partner -> CryptoSwift | Standardized Partner API. The partner network sends Travel Rule messages into CryptoSwift using /partners endpoints. |
CryptoSwift -> Partner | Custom partner contract. CryptoSwift sends Travel Rule messages to the partner network using the partner's API and payload rules. |
The Partner -> CryptoSwift path uses CryptoSwift's standard Partner API for entity lookup, encrypted IVMS101 delivery, and follow-up transaction data updates. The CryptoSwift -> Partner path is usually implemented as a custom contract because partner networks often already operate their own API models, routing identifiers, encryption conventions, and message lifecycle states.
Prerequisite: Shared VASP Directories
To integrate with CryptoSwift, the partner must make their participant VASP data available to CryptoSwift through an API or an automated distribution pipeline. This directory exchange is a prerequisite because both networks need a reliable way to resolve VASP identifiers, metadata, and participation status before routing Travel Rule messages.
Two use cases depend on the shared directory:
| Use case | Why it matters |
|---|---|
Partner -> CryptoSwift validation | When the partner network transmits a Travel Rule message to CryptoSwift, the partner provides the ID of their participating VASP. CryptoSwift uses the shared directory to look up that VASP's metadata, including legal name, country, and status. |
CryptoSwift -> Partner routing | When a CryptoSwift customer wants to send a transaction to an external wallet or VASP, CryptoSwift checks the partner's participant list to verify whether the destination VASP participates in the partner network. |
Partners can mirror CryptoSwift's own Entities API behavior when exposing this data. At minimum, the directory should let CryptoSwift list verified participants, identify an entity by its partner-side ID, and retrieve the public key needed for encrypted message exchange. See the verified entity lookup reference for the CryptoSwift-side model.
Bidirectional Flow Routing
Partner -> CryptoSwift Flow
For Travel Rule messages sent from the partner network to CryptoSwift, CryptoSwift provides a standard high-performance Partner API. Continue to the Travel Rule Messaging Overview for VASP resolution, encrypted IVMS101 delivery, and transaction data update examples.
CryptoSwift -> Partner Flow
For Travel Rule messages moving from CryptoSwift to the partner network, CryptoSwift can build against the partner's native API contract. Start with the CryptoSwift-to-Partner Custom Contract Page to define the API, payload, encryption, and operational contract we should implement.