Go-live checklist
Work through this list before you take your first live payment.
On this page
Keys and endpoints
- You created a live key (
cp_live_) and keep it only on your server, never in a browser, an app or a repository. - You created a live webhook endpoint. Test endpoints receive only test events, so a live integration needs its own. You can have at most 5 endpoints per mode.
- Your live endpoint uses the live endpoint’s own signing secret, not the test one.
- If the operator pays you out, you saved where your payouts go in Settings. Without a payout address, payouts wait on hold until you add one.
Payments
- Every
POST /v1/paymentssends anIdempotency-Key, one per order attempt, reused when you retry after a timeout. - Your return page does not assume the buyer paid. It shows the order as waiting until your server has confirmed the payment.
- You handle every final status:
paid,failed,canceled,expired, andpaid_late(money that arrived after the time limit, which you review by hand). See Payment status. - You compute your net from
charge.net_amountandfee, which are in the same currency, not fromamount. See Amounts, currencies and VAT. - You handle
429and503by waiting for the seconds inRetry-After.
Webhooks
- You verify
CP-Signatureon the raw body and reject a timestamp more than 5 minutes from your clock. - You drop duplicate events by their
id, and you do not rely on the order in which events arrive. - Before you fulfil an order you read the payment with
GET /v1/payments/{id}and act on that status. - Your endpoint answers 2xx within 10 seconds, does not redirect, and has a certificate from a publicly trusted authority.
- You watch the delivery log in your dashboard and resend a delivery that failed.