Design a payment system
Accept card payments for online merchants, move money correctly and never charge anyone twice, like Stripe.
Functional requirements
- Merchants create charges and refunds
- Process cards through banks and card networks
- Merchants get webhooks and payouts
Non-functional requirements
- Never double-charge or lose a payment
- Every cent is accounted for
- Highly available, with strict security
Scale
- 10M payments per day
- Peaks of 2K payments per second
- Records kept for 7+ years
How you’ll be scored
9 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design a payment system”, that starts with: Merchants create charges and refunds; Process cards through banks and card networks; Merchants get webhooks and payouts. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (10M payments per day; Peaks of 2K payments per second; Records kept for 7+ years) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Never double-charge or lose a payment; Every cent is accounted for; Highly available, with strict security. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe payments, idempotency and ledger here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.