Skip to content
Interview rounds

Concurrency & payments · Production incident

One order, two charges

A retried payment request charges the customer twice. How do you make sure a payment happens once?

BackendSenior12 min
Interview-style scenarioLast reviewed: Checked against official documentation

Monday 09:20 · payment-serviceIllustrative scenario, not a real incident

Support: 31 customers were charged twice for a single order since Friday evening

The checkout calls POST /payments on the payment service, which charges the card through an external processor and then writes a row to the payments table.

Each affected order has two successful charges of the same amount a few seconds apart. Nothing was deployed last week, and most payments were fine.

What the dashboards and logs show

Affected orders
31, all between Friday 18:00 and Sunday night
payments table
two rows per affected order, different payment ids
Processor report
two captures per affected order, both successful
Deploys
none since the Tuesday before

Clarify · optional · scored under "Hypothesis before change"

Ask the interviewer

0 of 3 asked

Each question reveals a fact. What you ask before you act is part of your score.

First move · scored under "Mitigate before root cause"

Customers are still being charged twice while you investigate. What do you do first?

Your rubric score, the model answer, the follow-up questions and the related lessons appear once you have answered the last step.