# Go-live checklist

- [ ] Create live API keys (sk_live_ / sk_rlive_) with minimal scopes

  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.
- [ ] Configure HTTPS webhook endpoint and verify Standard Webhooks 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.
- [ ] Send Idempotency-Key on all POST create requests

  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.
- [ ] Handle API errors by error_code (not detail text)

  Error codes are stable and listed on the errors page. The detail text is written for people and may change or be translated.
- [ ] Implement exponential backoff respecting Retry-After on 429

  A 429 answer says how long to wait. Waiting that long, and longer after each refusal, keeps your integration inside its request budget.
- [ ] Review team roles and revoke unused access

  Each person and each key should hold only the access their work needs; remove what nobody uses before real data arrives.
- [ ] Remove all sk_test_ sandbox keys from production code

  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.
