Sandbox to production onboarding

Sign up in the sandbox, build and test your VASP integration, submit onboarding materials, and receive production access after review.

CryptoSwift onboarding begins in the Sandbox. Your VASP can create an account and start building before production access is approved. The sandbox and production environments have separate credentials and data.

1. Sign up in the Sandbox

Create your account through Sandbox self-service signup, verify your email, and get your Sandbox API key from the Sandbox Client Dashboard. Use the Quickstart to make your first request.

2. Build and test the flows you need

Decide how your VASP determines whether a transaction involves another custodial provider or a self-hosted wallet. You can use your own process or CryptoSwift Wallet Intelligence (KYW) to inform that decision. Then implement the relevant Travel Rule messaging or self-hosted wallet verification flow.

If you receive deposits, add and confirm a small set of test wallets in the Sandbox before testing incoming messages. Keep your full real custodial wallet inventory in Production once you have access; the wallet inventory guide explains both environments. Set up webhooks and use the Sandbox test scenarios to check responses and status changes.

3. Submit onboarding materials in the Sandbox

Submit your VASP onboarding materials through the Sandbox dashboard. You can continue building and validating the integration while CryptoSwift reviews those materials.

4. Receive production access

After CryptoSwift reviews the submitted materials, we onboard your VASP to production. You receive production access credentials automatically from CryptoSwift. Use those credentials with the Production API and Dashboard; a Sandbox key does not work in production.

Before going live, register and test your webhook URL in Production separately from the Sandbox setting, add and confirm your real custodial wallet inventory in Production, and run through the outgoing, incoming, or self-hosted flows that your VASP will use. The Sandbox testing guide describes test-only scenarios; use production credentials only after onboarding.