hard20 pts · first answer countsidempotencyapi-designpayments

Safe retries for payments

A mobile app calls POST /payments. The network times out, so the app retries, and the customer is charged twice. What is the most robust fix?

A.Client sends a unique Idempotency-Key; the server stores it with the result under a unique constraint and returns the saved result for repeatsB.Disable retries in the mobile app completelyC.Change the endpoint from POST to GET so it becomes idempotentD.Check if a payment with the same amount was made in the last 10 seconds and skip it

Discussion 0

Join free to post in the discussion.

Safe retries for payments

Discussion 0

Related questions