Go-live checklist
- Intended country, currency and products are enabled for the merchant.
- Test environment integration, failure cases and merchant-order queries have passed before production enablement.
- The fixed production outbound IPs are approved in the platform security group, WAF or API Gateway.
- The
live-mode API Key has been created and enabled in Portal; required Webhook endpoints are created separately. amount.valueremains a decimal string and respects the selected productCode currency precision and limits.- API and Webhook Secrets are stored only in a backend secret manager.
- Each required HTTPS Webhook endpoint has the correct event subscriptions and is enabled independently from the API Key.
- Every request uses a fresh
nonceand current Unix timestamp text. merchantOrderNois persisted before every create request.- No business create request is automatically retried.
- HTTP
200, HTTP4xx, HTTP5xx, timeout and network-loss flows are tested; uncertain create results are queried by the originalmerchantOrderNo. - If repeated queries still find no order, only the same
merchantOrderNoand unchanged request are resent, and never concurrently. - The Webhook receiver returns HTTP
200 OKafter the event is stored or processed; any other2xxis also treated as successful receipt by the platform. - Merchant order numbers, platform order numbers,
Request-Idand necessary response details are retained. - Webhook raw-body verification, timestamp checks and event deduplication pass.
- Balance and merchant-order query APIs were tested independently from Webhook delivery.
- Order-state decisions use
status, Webhook events and query results consistently. - Production rate expectations have been confirmed with platform operations.
- Logs and support exports redact API Secret, Webhook Secret, signatures and recipient details.
- The exact interface
1.0OpenAPI, SDK release and Demo versions are recorded.
Run the signing golden vectors in the merchant deployment environment before enabling production traffic.
