TodayZendesk→ Stripe→ New Relic→ Slack engineering→ wait→ Stripe→ ZendeskWith SupahelpPaste the ticket→ read the answer→ approve
01
The ticket
A customer writes in. Paste the link, or forward it from Zendesk.
Ticket 48213 Open
“Hi, we were charged $49 twice for March. Can you refund one of them? Ana, Fenwick Ceramics”
Nov 3 · annual plan · priority normal
02
What it checks
Four tools, in 18 seconds. Sentry stays closed because nothing points to an error.
Checked 4 tools in 18sNot needed: Sentry
ZendeskTicket 482132s
Fenwick Ceramics, annual plan, card ending 4242.
Stripecharges, last 7 days5s
Two charges of $49.00 at 9:14:03 and 9:14:07.
New Reliccheckout-api6s
A 504 timeout on POST /checkout, then one retry.
GitHubbilling-api5s
The retry in src/charge.ts:88 sends no idempotency key.
SentryClosed
No error reported for this customer.
03
What it found
Each finding says where it came from, and goes into the case for the next person.
Findings · CS-1042
ConfirmedTwo charges, 4s apart · Stripe
ConfirmedCheckout timed out, client retried · New Relic
ConfirmedRetry sends no idempotency key · src/charge.ts:88
04
What you approve
The refund waits for your yes. After you approve, it checks the refund went through in Stripe.
Wrenfield
Needs approvalRefund the duplicate charge
Amount
$49.00 USD
Charge
ch_3PqL…2cD
Customer
Fenwick Ceramics
Check after
refund status in Stripe
ApproveChangeCancel
05
The reply
Drafted from what was confirmed. Edit it, or send it as it is.
Reply to ticket 48213 Draft
To: Ana, Fenwick Ceramics
Hi Ana, you were right: a checkout timeout charged your card twice on Nov 3. We refunded the second $49.00 today. It shows on your statement in 5 to 10 days.
Send in ZendeskEdit
06
The playbook
Save the checks once. The next double charge runs the same way, for anyone on the team.
Refund a duplicate charge
Read the ticket and find the customer
List their Stripe charges from the last 7 days
Check checkout logs around each charge
If two charges match within 60 seconds, propose refunding the later one