Design Stripe’s Idempotent Payments API · System Design Interview

Design Stripe’s Idempotent Payments APIDesign the intake of a payments API at Stripe’s size, where the network drops responses, clients retry, and charging someone twice is the one thing that must never happen. Correctness under retries is the whole exercise.What it has to do

A retried request returns the original result rather than acting a second time

A client whose response was lost can retry safely, and does

A caller can find out, definitively, whether a payment happened

Scale

API requests per second at peak: 100,000

Payments per day: 200 million

Out of scope

Card networks and bank integrations

Fraud scoring

The dashboard

Payouts and reporting

Currency conversion

Practise this challengeAll system design challenges

LetsDiscuss

Loading your session…