# Double charge after deploy: first 30 minutes checklist

Source: https://releasefailures.com/incidents/double-charge-after-deploy/
Content version: 1.0.0
Verified on: 2026-10-22
Licence: CC BY 4.0

Definition: A customer is charged twice for one purchase after a release changes retry or idempotency behaviour.
- [ ] FM-01 Count transactions with more than one gateway submission since the deploy, grouped by client library and gateway.
- [ ] FM-02 Merge duplicate-charge reports arriving through separate support channels into one incident and match their first timestamp to the deploy time.
- [ ] FM-03 Revert the deploy that changed the API response or the transaction workflow if duplicate submissions are still appearing.
- [ ] FM-04 Confirm after the revert that no new transaction id receives a second gateway submission.
- [ ] FM-05 Tell customers not to retry errored transactions until each one is checked against the gateway record.
- [ ] FM-06 Send merchants the list of duplicated transaction ids and the steps to void each duplicate in their gateway portal.
- [ ] FM-07 Post a status update that names the affected client library or gateways and the time window of duplicate submissions.