System designHard~20 minCore Designs / 6 of 30

Interview question

Design a checkout API where clients may retry requests due to timeouts. How would you avoid duplicate orders or charges?

Design an idempotent checkout backend

Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would require an idempotency key for checkout requests and store the key with the user, request hash, order id, status, and response outcome. If the client retries with the same key, the API returns the existing result instead of creating a second order. Order creation and payment intent state would be persisted with clear states like pending, payment_authorized, confirmed, failed, and cancelled. The client gets a stable response even when the first request timed out.

Full answer below

Practice focus

Idempotency keys, transaction boundaries, payment side effects, order state, outbox, retries, and client contracts.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Checkout is a classic backend design because correctness matters more than returning quickly. The design needs to survive retries, timeouts, partial failures, and external payment side effects.
I would require an idempotency key for checkout requests and store the key with the user, request hash, order id, status, and response outcome. If the client retries with the same key, the API returns the existing result instead of creating a second order. Order creation and payment intent state would be persisted with clear states like pending, payment_authorized, confirmed, failed, and cancelled. The client gets a stable response even when the first request timed out.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would separate internal state changes from external side effects. The database transaction can create the order and idempotency record, while payment confirmation or messages can use an outbox or a controlled worker so failures are retried safely. If the same key arrives with a different request body, I would reject it as a conflict. I would also design user-visible recovery: show pending checkout, allow retry by key, and reconcile with the payment provider when status is uncertain.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would treat checkout as a consistency boundary. Unique constraints enforce idempotency, provider idempotency keys protect payment calls, and observability tracks duplicate attempts, uncertain payment states, and reconciliation jobs. The design would define timeouts, compensation, and manual support workflows for edge cases. I would avoid distributed transactions with external providers and instead make every step recoverable through durable state and reconciliation.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Relying only on client-side button disabling.
No idempotency key or unique constraint.
Charging the card before durable order state exists.
No recovery path for uncertain payment status.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain what happens after a client timeout.
Creates duplicate orders on retry.
Mixes external payment side effects into an unclear transaction.
Has no reconciliation or support story.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How would you validate an idempotency key?
What happens if payment succeeds but the API times out?
How would you reconcile payment provider state?

Continue the section

Next in Core Designs: Multi-tenant Boundary

Step 7 of 30

Design a multi-tenant SaaS backend boundary

Opening drill

System designHard~20 minCore Designs / 6 of 30

Interview question

Design a checkout API where clients may retry requests due to timeouts. How would you avoid duplicate orders or charges?

Design an idempotent checkout backend

Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Idempotency keys, transaction boundaries, payment side effects, order state, outbox, retries, and client contracts.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Checkout is a classic backend design because correctness matters more than returning quickly. The design needs to survive retries, timeouts, partial failures, and external payment side effects.
I would require an idempotency key for checkout requests and store the key with the user, request hash, order id, status, and response outcome. If the client retries with the same key, the API returns the existing result instead of creating a second order. Order creation and payment intent state would be persisted with clear states like pending, payment_authorized, confirmed, failed, and cancelled. The client gets a stable response even when the first request timed out.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would separate internal state changes from external side effects. The database transaction can create the order and idempotency record, while payment confirmation or messages can use an outbox or a controlled worker so failures are retried safely. If the same key arrives with a different request body, I would reject it as a conflict. I would also design user-visible recovery: show pending checkout, allow retry by key, and reconcile with the payment provider when status is uncertain.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would treat checkout as a consistency boundary. Unique constraints enforce idempotency, provider idempotency keys protect payment calls, and observability tracks duplicate attempts, uncertain payment states, and reconciliation jobs. The design would define timeouts, compensation, and manual support workflows for edge cases. I would avoid distributed transactions with external providers and instead make every step recoverable through durable state and reconciliation.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Relying only on client-side button disabling.
No idempotency key or unique constraint.
Charging the card before durable order state exists.
No recovery path for uncertain payment status.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain what happens after a client timeout.
Creates duplicate orders on retry.
Mixes external payment side effects into an unclear transaction.
Has no reconciliation or support story.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How would you validate an idempotency key?
What happens if payment succeeds but the API times out?
How would you reconcile payment provider state?

Continue the section

Next in Core Designs: Multi-tenant Boundary

Step 7 of 30

Design a multi-tenant SaaS backend boundary

Design a checkout API where clients may retry requests due to timeouts. How would you avoid duplicate orders or charges?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Design a checkout API where clients may retry requests due to timeouts. How would you avoid duplicate orders or charges?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section