Skip to content

Designing your operations

Align product, compliance, and operations

Use this track to define how your organization applies the Travel Rule across customer journeys. Each guide focuses on decision points, regulatory expectations, and stakeholder responsibilities; no code is 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.

  1. Choose the wallet-type decision process - Use your own tools and customer information, or KYW as an optional signal. Define a fallback for unknown results. The wallet types guide connects each result to the next flow.
  2. Register your own custodial wallets - Maintain your real deposit addresses in Production so incoming messages can be matched to your VASP and handled without avoidable PII delays. Use a small test set in the Sandbox.
  3. Define data collection expectations - Align product flows and KYC systems on the required Travel Rule data. Confirm how missing fields will be backfilled.
  4. Set outgoing delivery rules - If the wallet is custodial, decide when concurrent dispatch meets your applicable requirements and when you need a pre-transaction decision before funds move. Use the outgoing transactions overview and the Rule Engine if you want CryptoSwift to automate those policies.
  5. 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.
  6. Handle self-hosted wallets - Decide when your policy requires proof of customer control. Start with the self-hosted wallet strategy, then choose a widget or API integration.
  7. Improve data quality - Reduce delivery failures by collecting beneficiary VASP names and wallet types. See Improving data quality.
  8. Align privacy and evidence retention - Ensure your policies match PII data handling and the CryptoSwift Compliance Documentation.

Next steps