Introduction

CryptoSwift supports both post-transaction and pre-transaction Travel Rule workflows. Teams can start with the fastest integration path for compliance, then add more advanced decisioning before funds move when their operating model requires it.

Product and compliance leads can map policies without touching code, while engineers layer in the API when they are ready.

Jump into the core docs based on what you need to ship first.

Use the post-transaction flow when you want the fastest implementation path with minimal workflow changes. It is a strong fit when your AML, KYT, and release controls already exist outside CryptoSwift and the goal is to add Travel Rule messaging without redesigning withdrawal approval logic.

In this model, the blockchain transaction already exists when the Travel Rule message is created. You still receive useful transaction data and status updates, including message status, counterparty context, and any configured risk evaluation outputs. See Outgoing transactions and the end-to-end Travel Rule lifecycle.

Use the pre-transaction flow when you need a decision before funds move. CryptoSwift lets you send the Travel Rule message before broadcasting the blockchain transaction and evaluate more than just a counterparty confirmation.

Pre-transaction decisions can combine multiple inputs, including:

• counterparty response
• Travel Rule Risk Score
• transaction amount
• beneficiary VASP
• wallet risk
• other attributes evaluated by the Rule Engine

These decision workflows can be automated through the Rule Engine configured in the Client Dashboard. See Travel Rule Risk Score for how the score is derived across outgoing and incoming transactions. Teams commonly start with post-transaction integration, then introduce pre-transaction automation only for selected flows, counterparties, or risk tiers.

• Product and compliance: Understand how CryptoSwift supports regulatory obligations and where approval workflows, KYC controls, and escalation paths fit.
  • Align the operating model - Use Compliance workflows to confirm policies, approval steps, and compliance triggers.
  • Visualise the experience - Share the end-to-end Travel Rule lifecycle with operations teams to show how messages move between counterparties.
• Engineering: See the building blocks you can automate immediately and how they connect to existing systems.
  • Start integrating - Follow Get started.
  • Travel Rule foundations - Review the Travel Rule data model so you know which fields your systems must collect.

The CryptoSwift API exposes every Travel Rule capability through REST endpoints. See the API Reference and Test environment section for more information.

The Client Dashboard gives teams a ready-made UI so you can go live without rebuilding every workflow on day one. Automate the high-frequency actions in code and fall back to the dashboard for manual reviews or low-volume scenarios. The dashboard is also where compliance teams configure Rule Engine policies for automated pre-transaction decisions. Every dashboard feature is available via the API, so you can migrate functionality into your own product whenever it makes sense.

The CryptoSwift Wallet Verification Widget is a flexible solution for authenticating you user's self-hosted wallets. Choose the integration method that fits your workflow:

• Web Component: Embed the widget directly into your frontend with a few lines of HTML/JS for a smooth, in-app experience.
• Hosted Flow: Redirect users to a secure, CryptoSwift-hosted URL. This requires zero frontend configuration and is managed entirely on our infrastructure.

See the Wallet verification widget for more details.

• Quickstart Guide
• Test Environment
• Webhook Notifications
• Compliance workflows
• Travel Rule Risk Score
• Rule Engine