Go-live checklist
What to check before your integration uses live keys and real money. Each item links to the page that explains it; your ticks stay in this browser only.
- Restricted keys
A live key acts on real customers and real money. A restricted key carries only the scopes you grant, so a leaked key can do no more than the job it was made for.
- Verify signatures
The signature proves an event came from the server and was not changed on the way. Reject any event whose signature or timestamp does not verify.
- Idempotency
When a request times out and you send it again with the same key, the server returns the first result instead of creating a second invoice or payment.
- Errors
Error codes are stable and listed on the errors page. The detail text is written for people and may change or be translated.
- Rate limits
A 429 answer says how long to wait. Waiting that long, and longer after each refusal, keeps your integration inside its request budget.
- Team and roles
Each person and each key should hold only the access their work needs; remove what nobody uses before real data arrives.
- The sandbox
A test key works only against the test account with sample data, so a production path that still holds one sends real work to sample records.