Designing your operations
Align product, compliance, and operations
Use this track to define how your organisation applies the Travel Rule across customer journeys. Each guide focuses on decision points, regulatory expectations, and stakeholder responsibilities - no code required.
How to use this section
Pair these conceptual guides with the technical resources in Get started. Once a workflow makes sense, follow the linked integration pages to see the exact API calls.
Terminology
Throughout the docs we use VASP as shorthand for both Virtual Asset Service Providers and Crypto Asset Service Providers (CASPs).
Design your operations
Our philosophy is straightforward: compliance should not disrupt the core payment experience. Start with the end-to-end lifecycle, then map the steps below into your own operating model.
- Define data collection expectations - Align product flows and KYC systems on the required Travel Rule data. Confirm how missing fields will be backfilled.
- Set outgoing delivery rules - Decide when to allow concurrent messaging vs when to wait for counterparty confirmation. Use the outgoing transactions overview to choose between post-transaction and pre-transaction flows.
- Set incoming handling rules - Define how inbound Travel Rule messages map to your customer accounts and when funds can be released. The incoming transactions workflow covers status updates and escalation triggers.
- Handle self-hosted wallets - Determine how you differentiate custodial vs self-hosted destinations and when to verify ownership. Start with custodial vs self-hosted wallets, then map verification in self-hosted wallet strategy.
- Improve data quality - Reduce delivery failures by collecting beneficiary VASP names and wallet types. See Improving data quality for practical inputs that boost routing success.
- Align privacy and evidence retention - Ensure your policies match PII data handling and the CryptoSwift Compliance Documentation.