Compliance workflows
How CryptoSwift fits into your transfer process
CryptoSwift helps VASPs handle the information and checks around crypto transfers. It gives your team three capabilities:
- Travel Rule messaging to send and receive information about a transfer with another provider.
- Self-hosted wallet verification to collect evidence that a customer controls a wallet, when your policy requires it.
- Wallet Intelligence (KYW) as an optional signal when you need help identifying the type of wallet involved.
Your VASP runs the transfer and makes the compliance decision. CryptoSwift supplies messages, verification results, and status updates alongside your existing systems. These pages help compliance, operations, and product teams design the process; the integration guides show engineers how to build it.
Throughout these docs, VASP refers to both Virtual Asset Service Providers and Crypto Asset Service Providers (CASPs).
The basic workflow
- Identify the wallet involved in the transfer. Decide whether another provider controls it, your customer controls it, or you need more information. Use your existing process; KYW is available as an additional signal.
- Follow the relevant path. For a transfer involving another provider, exchange Travel Rule information. For a customer-controlled self-hosted wallet, follow your wallet verification policy. If the wallet type is unclear, apply your review process.
- Handle the result. Review incoming messages, track outgoing delivery and responses, resolve exceptions, and keep the evidence your policy requires. CryptoSwift exposes messages and status changes through its dashboard, API, and webhooks.
For a fuller explanation of the service and your team's responsibilities, read How CryptoSwift works.
For Sandbox tests, add and confirm a few test wallets. Before handling live incoming transfers, maintain the real custodial wallets your VASP controls in Production. This inventory helps CryptoSwift match messages to you and is separate from the customer or counterparty wallet you assess for each transfer.
Find your topic
- Planning the process: Designing your operations covers policies, responsibilities, and handoffs.
- Deciding which path applies: Custodial vs self-hosted wallets explains the decision, with KYW as an optional tool.
- Travel Rule messaging: Start with the message lifecycle, then read the outgoing or incoming workflow.
- Self-hosted wallets: Start with the verification strategy, then consider additional evidence if your policy calls for it.
- Controls and records: Explore the Rule Engine, risk score, required data, and PII handling.
Set up your VASP
Start in the Sandbox: build and test the integration and submit onboarding materials there. After review, CryptoSwift sends production credentials automatically.