Sandbox vs production
CashXChain provides two fully separated environments — sandbox and production. Each has its own subdomains for the API, web app, developer portal, and authentication. Documentation, status, and the marketing site are shared.
This separation is intentional and stricter than what many other platforms do.
Full separation, by design
There is no shared session and no single sign-on between environments. You sign in to each one independently. Concretely:
- Separate user accounts. A sandbox account is not a production account.
- Separate API keys.
cx_sandbox_...keys never authenticate against the production API and vice versa. - Separate auth domains, web apps, and developer portals.
- Separate data. No sandbox object is visible from production and no production object is visible from sandbox.
- Separate webhooks. A sandbox webhook endpoint is registered only in the sandbox dashboard.
Both environments are self-serve. You can register for either or both at any time — just create a separate account for each. Production registration is open without prior approval; KYB completion and product enablement gate the ability to send live payments, not the ability to sign up.
The recommended flow is to start in sandbox, build and validate the integration, and then register for production when you are ready to go live.
Environment URLs
| Service | Production | Sandbox |
|---|---|---|
| API | https://api.cashxchain.com | https://api.sandbox.cashxchain.com |
| Web app | https://app.cashxchain.com | https://app.sandbox.cashxchain.com |
| Developer portal | https://dev.cashxchain.com | https://dev.sandbox.cashxchain.com |
| Authentication | https://auth.cashxchain.com | https://auth.sandbox.cashxchain.com |
| — Sign up | https://auth.cashxchain.com/register | https://auth.sandbox.cashxchain.com/register |
| — Sign in | https://auth.cashxchain.com/login | https://auth.sandbox.cashxchain.com/login |
| Documentation | https://docs.cashxchain.com | https://docs.cashxchain.com |
| Status | https://status.cashxchain.com | https://status.cashxchain.com |
| Marketing site | https://www.cashxchain.com | https://www.cashxchain.com |
The web app (app.*) is the operational dashboard for both environments. The developer portal (dev.*) is where you manage API keys, webhook endpoints, sandbox simulators, and integration settings. Authentication uses the same /login and /register paths in both environments.
Sandbox
Sandbox is for development, testing, and integration validation. It uses simulated or test partner behavior and does not move real funds.
Use sandbox to test:
- API authentication.
- Account onboarding states.
- Beneficiary creation.
- FX quote requests.
- Payment creation.
- Payment status transitions.
- Webhook delivery and retries.
- Error handling.
- Statement exports.
Production
Production is for live payments and real operational workflows. Sign-up is self-serve at auth.cashxchain.com/register — you do not need prior approval to create an account. To send live payments you then need to complete KYB, accept the relevant contractual terms, pass partner and security review, and have the relevant products enabled on your account.
Differences
| Feature | Sandbox | Production |
|---|---|---|
| Funds | Simulated | Real |
| API keys | cx_sandbox_... | cx_live_... |
| Webhooks | Test events | Live events |
| Partner execution | Simulated or test-mode | Regulated partner systems |
| KYB | Simulated states | Required review |
| Statements | Test records | Operational records |
Test scenarios
Sandbox supports simulated scenarios such as:
- Payment completed.
- Payment failed.
- Payment returned.
- Quote expired.
- Beneficiary requires more information.
- Account restricted.
- Webhook delivery failure.
Go-live checklist
Before production:
- Complete KYB and account approval.
- Configure production webhook endpoints.
- Verify webhook signatures.
- Implement idempotency.
- Review rate limits.
- Test failure and return handling.
- Validate reconciliation exports.
- Store production API keys in a secret manager.