Go-live checklist

What we certify against before enabling production.

The first five items are the integration itself. The rest are what separates an integration that works from one that stays working.

Integration#

1. Receive your base URL and API key during onboarding.
2. Call GET /payment-methods to confirm which methods are enabled.
3. Create a payment with POST /payments, remembering the idempotency_key.
4. Set up your webhook endpoint and verify signatures.
5. Reconcile using GET /transactions and GET /wallets.

Robustness#

• The API key is held server side and is not in source control.
• An idempotency key is generated and persisted before the request is sent.
• A timed-out request is retried with the same key, not a new one.
• Webhook handlers are idempotent and tolerate duplicate delivery.
• Webhooks older than 5 minutes are rejected.
• Nothing is settled internally on a 202 or a non-final status.
• Unknown response fields are ignored rather than causing a failure.
• Amounts are built as minor-unit strings everywhere, with no float arithmetic in the path.

Operations#

• A sweep job re-checks non-final transactions.
• Daily reconciliation runs against the ledger and wallet balance.
• Outbound calls are logged with the transaction id and idempotency key.
• Someone owns the webhook endpoint's uptime and alerting.
• There is a documented procedure for a suspected key compromise.