Skip to content

How CryptoSwift works

Start with Wallet Intelligence, then follow the Travel Rule or self-hosted wallet verification workflow.

CryptoSwift connects wallet intelligence, Travel Rule messaging, and self-hosted wallet verification to your transaction systems. Start with Wallet Intelligence (KYW) to determine the likely wallet type, then use the result to choose the appropriate compliance workflow. Your team sets the policies, makes the approval decisions, and controls when funds move. The video and diagram below show how these steps fit together.

High level overview

The flow starts with the wallet involved in a transfer: the destination wallet for a withdrawal, or the originating wallet when reviewing a deposit. Your system sends the wallet address and blockchain to the CryptoSwift Wallet Intelligence API (known also as Know Your Wallet). KYW returns the likely wallet type, confidence, and attribution reason so your system or compliance team can choose the next step.

Wallet Intelligence resultNext workflow
Custodial: controlled by an exchange or another custodial provider.Follow the Travel Rule message flow. Exchange the required information, track responses, and apply your Travel Rule policies through the Rule Engine when configured.
Self-hosted (non-custodial): controlled directly by the wallet owner.Apply your self-hosted wallet verification policy. Verify wallet control when required by your policy.
Unknown or insufficient confidenceAsk the customer for more information or route the case to manual review before choosing a path.

Wallet classification supports the routing decision; it does not prove wallet ownership. Your VASP decides which confidence levels are sufficient and what evidence is required. Supplement the KYW result with your own tools and customer information where further checks are needed.

Your system uses the Travel Rule delivery and response statuses, Rule Engine results, or wallet verification outcomes to continue, hold, or escalate the case according to your policies. The Rule Engine applies to Travel Rule workflows; self-hosted wallet verification has its own results and review steps.

Your systems execute the on-chain transfer. For withdrawals, complete the required checks before approving and sending funds. For deposits, use the available Travel Rule context and wallet intelligence to decide what is needed before releasing funds to the customer.

Travel Rule responsibilities

On the custodial path, CryptoSwift handles the information exchanged with the other VASP. You create a Travel Rule message through the API or dashboard, and CryptoSwift stores and forwards it. Depending on your workflow and applicable requirements, you can send the message before or alongside the transfer.

As the originating VASP, you need to:

  • Collect required Travel Rule data from your customers.
  • Create Travel Rule messages using the CryptoSwift API or Dashboard before or at the time of making a crypto payment.

As the beneficiary VASP, you need to:

  • Receive and review incoming Travel Rule messages, and respond according to your policies.
  • Handle missing Travel Rule information through your review, backfill, or claims process.

To receive and review those messages efficiently, register and confirm the custodial wallet addresses your VASP controls. This inventory is separate from the customer wallets you may classify or verify.

Self-hosted wallet verification

Customers verify wallet control through an embedded widget or hosted page, or a verification flow built into your application. Your policy may also require additional checks, such as liveness or Source of Funds / Source of Wealth documents. These are optional additions to the workflow, with results separate from wallet ownership verification.

Where CryptoSwift fits

  • Wallet intelligence - CryptoSwift helps determine wallet type and provides confidence and attribution context to support the choice of workflow.
  • Message exchange - CryptoSwift transports Travel Rule messages to counterparties, tracks delivery statuses, and stores an audit-ready trail of what was sent and when.
  • Verification workflows - For self-hosted wallets, CryptoSwift runs ownership checks and supports additional evidence steps, with manual review where needed.
  • Operational visibility - The Client Dashboard and APIs expose incoming messages, status updates, and manual review queues.

What stays with your compliance team

  • Policy decisions - Classification confidence thresholds, verification requirements, and when to pause or reject transfers, including any Travel Rule policies you choose to automate through the Rule Engine.
  • Data collection - How your product gathers the required originator and beneficiary information from customers.
  • Customer communication - Follow-ups, remediation requests, and disclosures for missing or incorrect data.

Typical handoffs in a compliance case

  1. Prepare the case - Collect transfer and customer details, check the wallet type, and start the relevant workflow.
  2. Apply the outcome - Use the results and later status updates to approve, hold, reject, or escalate according to your policies. Your systems handle any payment or deposit release.
  3. Keep the evidence - Store the KYW result, message logs or verification evidence, and decision notes with the transaction for audits.

Next steps