Clarify the payment flow
Separate authorization, capture, settlement, payout, and refunds so you know which transitions require strong guarantees.
Free Stripe breakdown
How to answer Design Stripe in a system design interview.
Stripe is one of the clearest ways to tell whether a candidate understands correctness or just knows infrastructure nouns. Strong answers start with what must never go wrong before they start naming queues or databases.
Free to share
Targets "Design Stripe"
No signup wall
Center of gravity
Correctness before convenience.
Idempotency
Ledger integrity
No double charge
The pivot
Start with correctness, not throughput.
Weak Stripe answers jump to a queue, payment gateway, and database. Strong answers start by protecting the invariants: a payment should not be created twice, balances should not drift, and retries should not duplicate money movement.
Protect with idempotency
Every client retry and webhook retry should map back to the same logical payment operation instead of creating duplicates.
Use a ledger as source of truth
Treat balance updates like accounting entries, not mutable counters you can patch later.
30-second answer shape
What a stronger answer sounds like.
State the boundary
“I want strong correctness around payment creation, ledger writes, and state transitions, even if some downstream notifications are eventually consistent.”
Name the backbone
“I would persist the payment request once, enforce idempotency on the write path, and treat the ledger as append-only.”
Close with tradeoffs
“I accept some latency and workflow complexity in exchange for never double-charging or letting balances drift.”
Common mistake
Do not make Stripe sound like generic CRUD plus Kafka.
Wrong start
“We have an API gateway, Redis cache, Kafka, and a relational database.” That sounds like infrastructure, not judgment.
Better start
“The hard part is preventing duplicate money movement while preserving a clean audit trail through retries and downstream failures.”
Why it wins
The interviewer immediately hears that you understand the business boundary the system exists to protect.
Want the full version?
The paid Stripe book goes much deeper than this page.
The full breakdown covers authorizations, captures, settlements, webhooks, ledger modeling, retries, payouts, and how to answer follow-up questions without drifting off the real problem.