Sandbox / staging environment
Test your integration against the staging stack before going live.
payzum provides a full sandbox/staging environment — the complete stack, not just the API — so you can build and test your integration end to end before touching production.
Base URLs
| Surface | URL |
|---|---|
| API | https://staging.payzum.com/v1/* |
| Widget script | https://staging.payzum.com/widget/v1/payzum.js |
| Hosted checkout | https://staging.payzum.com/pay/<id> |
Getting sandbox credentials
Register on the staging dashboard — the flow is identical to production: create an account → create a merchant → the API key is shown once on the reveal page. Copy it before leaving.
Credentials are per environment: staging and production are separate stacks with separate databases, and there are no test_/live_ key prefixes — a key only works on the host where it was created. See Authentication for details.
Do not use production keys against staging or staging keys against production — they will simply fail authentication on the other host.
Data persistence
Staging data is test data and may be purged periodically. Do not rely on staging invoices, merchants, or history persisting — re-create what you need when you return.
Networks and testnets
Staging operates under a PAYZUM_NETWORK_MODE setting that may offer testnets. Do not hardcode a currency list — query the live set at runtime:
curl -s "https://staging.payzum.com/v1/currencies" | jq .Two additional testnet paths exist:
- Mass payouts — inside production, individual payout orders can be created with
mode=testnet. See Payouts overview. - x402 (Payzum for Agents) — the testnet is Base Sepolia using the free public facilitator. See x402 overview.
Next steps
Follow the Quick start with PAYZUM_BASE=https://staging.payzum.com to create your first sandbox invoice.