Sandbox
Build and validate CryptoSwift integrations in an isolated sandbox.
CryptoSwift provides the Sandbox so you can build, iterate, and validate Travel Rule workflows without touching Production data. Build and validate your integration there before going live to avoid accidental PII forwarding and to verify Travel Rule flows safely.
Start by signing up in the Sandbox. You can build and test there and submit your VASP onboarding materials through the Sandbox dashboard. After CryptoSwift reviews the materials, your VASP receives production access credentials automatically. Follow the onboarding steps.
Each environment has its own Base URL and requires a separate API key.
For creating, rotating, and revoking keys after initial setup, see Manage API keys.
Building with an AI coding agent? See AI Agent Integration and AI Agent Prompts.
Environments
| Environment | API Reference | Client Dashboard | Wallet Verification Widget | API key |
|---|---|---|---|---|
| Sandbox | Sandbox API Reference | Sandbox Client Dashboard | Sandbox widget | Get via self-service |
| Production | Production API Reference | Production Client Dashboard | Production widget | Provided by CryptoSwift separately |
Important: Make sure you use the correct API key for the environment you’re accessing. Using a test key in the live environment (or vice versa) will result in authentication errors. You can find your API keys by signing in to the Client Dashboard for the respective environment.
Testing and validating your integration
The Sandbox includes known wallets and emulation services to help you validate your integration before going live. See Test webhook notifications for details.
If your VASP receives deposits, add a few test wallets to Sandbox My Wallets before testing incoming messages. The simulator needs a matching destination there. Maintain your full real custodial inventory in Production, as described in the wallet inventory guide.