A successful sandbox payment proves the basic path. Production readiness means the same path remains safe during retries, delays, invalid requests, outages, and operational incidents.
Your launch checklist
Keys and access
- Merchant status is active.
- Production secrets are stored in a managed secret store.
- Every key has only the permissions it needs.
- Your team can revoke and rotate an exposed key.
Payment safety
- Amounts use whole cents and are created on your server.
- Every write has a stable idempotency key tied to your operation.
- Orders are fulfilled only after confirmed succeeded status.
- Refund and cancellation states update your records.
Webhook reliability
- Your public endpoint uses HTTPS.
- The raw body is verified before JSON parsing.
- Processed event IDs are stored to prevent duplicate work.
- Long-running work continues after a quick successful response.
Operations
- Logs preserve error codes and correlation IDs without secrets.
- Alerts cover payment failures, webhook failures, and reconciliation drift.
- An on-call owner knows how to pause fulfilment and escalate.
- The team tested recovery from an uncertain payment outcome.
Confirmed SavaPay platform protections
| Area | Protection |
|---|---|
| API keys | Hashed at rest, shown once, scoped, and revocable. |
| Request safety | Idempotency is enforced on writes to prevent duplicate money movement. |
| Access control | Merchant ownership is checked on payment, cancellation, refund, and reconciliation operations. |
| Webhook integrity | Events are HMAC-SHA256 signed and support constant-time verification. |
| Traffic protection | Merchant-keyed rate limits and fraud controls protect the v1 API. |
| Money-path protection | Payment and refund operations are retry-safe, with compensation for interrupted movement. |
| Operational controls | Daily merchant limits, health checks, structured metrics, alerts, and audit logging are built in. |
Go-live sequence
- Complete the full sandbox test matrix.
- Submit merchant onboarding and required KYC documents.
- Confirm production credentials and the production webhook destination.
- Run one small live payment through the complete order flow.
- Compare payment, order, webhook, and reconciliation records.
- Increase traffic gradually while monitoring failures and delivery delays.