Skip to content

Introduction

What CryptoSwift offers and where to start

CryptoSwift helps VASPs handle the information and checks around crypto transfers. Use the parts that fit your process:

  • Travel Rule messaging: Exchange transfer information with another VASP. CryptoSwift supports outgoing and incoming messages and reports delivery and response statuses.
  • Self-hosted wallet verification: Collect evidence that a customer controls a wallet when your policy requires it. Choose a hosted or embedded flow or build one with the API.
  • Wallet Intelligence (KYW): Get an optional signal about whether a wallet is custodial, self-hosted, or unknown. Your VASP can also make this decision using its own information and tools.

Your team decides which checks apply and when a transfer can proceed. CryptoSwift provides the API, dashboard, and webhooks to support those decisions.

Terminology

Throughout these docs, VASP refers to both Virtual Asset Service Providers and Crypto Asset Service Providers (CASPs).

Choose the path for a transfer

First identify who controls the wallet involved in the incoming or outgoing transfer. If another provider controls it, follow the Travel Rule messaging path. If your customer controls a self-hosted wallet, follow your wallet verification policy. If the type remains unclear, gather more information or use your review process. Custodial vs self-hosted wallets explains this decision in more detail.

For outgoing Travel Rule messaging, you can send the message before settlement or alongside the transfer. See the outgoing guide to choose the timing. For live incoming transfers, register and confirm the custodial wallets your VASP controls in Production so CryptoSwift can match messages to you. Use a small test inventory in the Sandbox. Your own inventory is separate from the customer or counterparty wallet you assess for each transfer.

Start building in the Sandbox

  1. Sign up in the Sandbox and get an API key.
  2. Follow the Quickstart to send a test Travel Rule message, then use the relevant incoming or wallet verification guide for your process.
  3. Test webhooks and the flows you plan to use. Submit your onboarding materials through the Sandbox dashboard while you build.
  4. After CryptoSwift reviews the materials, your VASP receives production credentials automatically. Follow the onboarding guide for the full sequence.

Find the next guide