Environments & base URLs
MidasPay exposes two fully isolated environments. Use sandbox for every integration and QA activity; only switch the base URL and credentials once your integration is certified for production.
Base URLs
| Environment | API base URL | Purpose |
|---|---|---|
| 🧪 Sandbox | https://sandbox-pay.centauriglobal.com | Integration, QA, automated testing |
| 🟢 Production | https://pay.midaspayment.com | Live traffic, real money |
Each reference page's "Try it" console is configured with the correct base URLs, so you can target either environment directly from this site.
Data isolation
- Sandbox and production do not share any data — orders, merchants, credentials, webhooks and reports live in separate databases.
- Credentials are environment-specific. A sandbox certificate / key-pair is useless in production, and vice versa. Generate a fresh pair when you promote.
- Webhook URLs are configured per environment (commonly
webhooks.dev.example.comvswebhooks.example.com).
Promotion workflow
Before you receive production credentials, your MidasPay merchant manager will typically walk through a readiness review covering:
- At least one end-to-end happy-path transaction in sandbox.
- At least one declined transaction handled correctly in your code.
- Webhook endpoint verifies the signature and returns 2xx promptly with a
{"processed": true}body. - Idempotency (correct use of
reference_id) observed under duplicate-request simulation. - Refund / void flows exercised where applicable.
- PCI-DSS attestation on file if your integration sees card data.
Differences you should know
| Aspect | Sandbox | Production |
|---|---|---|
| Rate limits | Lower than production | Set contractually |
| Channel coverage | A subset of channels, each with sandbox test credentials | All contracted channels |
| 3DS challenge | Simulated by the channel's sandbox | Real issuer ACS |
| Settlement | None — test money | Real settlement to your bank account |
| Support SLA | Best-effort during business hours | As specified in your contract |
For exact numbers (quotas, retries, retention) in either environment, consult the Merchant Portal or your merchant manager — published figures depend on your contract and region.
Operational notes
- Credential updates (uploading a new certificate, rotating a key) propagate within the Merchant Portal. Allow a short grace period before exercising the new credential in production.
- Scheduled maintenance is announced in advance by email to the merchant's technical contact.