Explain idempotent payments.
Skip to solutionKEEP THE
hardSystem Design
How do you make a payment system reliable against retries?
993 views
01
Understand the problem
paymentsidempotency
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
Step 1: Outline use cases and constraints
Gather requirements and scope the problem. Ask questions to clarify use cases and constraints. Discuss assumptions.
Use cases
We'll scope the problem to handle only the following use cases
- User triggers How do you make a payment system reliable against r
Solution ready — 2 min read
Classified // press E to declassify
04
Read the code
Idempotent charge with status
Run Playgroundcharges = {} # idempotency_key -> record (Redis/DB in production)
def charge(key, amount, provider):
rec = charges.get(key)
if rec and rec["status"] == "succeeded":
print("retry of", key, "-> no second charge")
return rec # safe to retry
charges[key] = {"status": "pending", "amount": amount} # record intent FIRST
ref = provider(key, amount) # provider call is also keyed
charges[key] = {"status": "succeeded", "amount": amount, "ref": ref}
return charges[key]
def fake_provider(key, amount):
print(" charging", amount, "for", key)
return "txn_" + key
print(charge("k1", 4999, fake_provider))
print(charge("k1", 4999, fake_provider)) # retry -> deduped, no double charge05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 51 of 99 decoded in the System Design track. One more won't hurt.