Introduction

CryptoSwift supports both post-transaction and pre-transaction Travel Rule workflows.

Start with the fastest integration path for Travel Rule messaging, then add pre-transaction risk checks and automated compliance decisions when your operating model requires them.

Compliance and product teams can define policies and workflows in the Client Dashboard, while engineering teams integrate the API into existing transaction systems.

Start with the documentation that matches what you need to implement or operate first.

CryptoSwift supports both post-transaction and pre-transaction workflows. You can start with straightforward Travel Rule messaging and introduce pre-transaction decisioning where additional controls are required.

CryptoSwift combines API infrastructure with tools for compliance and operations teams. Use the components your workflow requires.

Exchange Travel Rule data and integrate transaction workflows through REST endpoints and webhooks.

Supports outgoing and incoming Travel Rule messaging, transaction status updates and integration with existing systems.

Integration Guides

Manage transactions, review exceptions and operate Travel Rule workflows without relying on engineering teams for everyday compliance operations.

Client Dashboard

Apply your compliance policies automatically using Travel Rule status, counterparty and wallet risk, transaction attributes and integrated risk signals.

Use Rule Engine outcomes to proceed with low-risk activity or escalate exceptions for review.

Rule Engine documentation

Verify ownership or control of self-hosted wallets using CryptoSwift verification workflows.

Choose between direct API integration and supported hosted or embedded verification flows.

Wallet Verification documentation

Travel Rule messaging tells you who is involved in a transfer, but operational compliance often requires additional context.

CryptoSwift can combine:

• Travel Rule message status
• counterparty VASP information
• Travel Rule Risk Score
• wallet and on-chain risk
• transaction attributes
• integrated AML/KYT signals
• your own Rule Engine policies

These signals can support automated decisions or provide compliance teams with the information needed for manual review.

Compliance Workflows

Define policies, review exceptions, investigate transactions and maintain the audit trail around Travel Rule activity.

Recommended starting point: Compliance Workflows

Design how Travel Rule requirements, wallet verification and risk decisions fit into customer deposit and withdrawal journeys.

Recommended starting point: Compliance Workflows and Integration Guides

Integrate CryptoSwift APIs, webhooks and verification workflows into existing transaction infrastructure.

Recommended starting point: Quickstart Guide

CryptoSwift provides the infrastructure for Travel Rule messaging, risk signals, workflow automation and audit evidence.

Your organisation remains responsible for defining its compliance policies, risk appetite, approval rules and customer handling procedures.

The Rule Engine helps apply those policies consistently, while compliance teams retain control over configuration and manual exceptions.

CryptoSwift in your compliance operations

Use the CryptoSwift Test Environment to develop and validate your integration without affecting production data or workflows.

Test authentication, Travel Rule transactions, webhooks, wallet verification and other supported workflows before requesting production access.

Test Environment

Quickstart Guide →

Set up API access and create your first Travel Rule workflow.

Compliance Workflows →

Define policies, approvals, risk decisions and exception handling.

API Reference →

Review available endpoints, request schemas and responses.