Design Peer-to-Peer Payments
A peer-to-peer (P2P) payments app lets one person send money to another from a phone. Each user has a balance held by the platform. They can top it up from a linked bank account, send it to friends, and cash it out to their bank. Money between two balances moves instantly. Money that touches a bank moves over ACH (the Automated Clearing House, the US network banks use for batch transfers), and it takes a day or two to arrive. The round is mostly about tables. Which rows exist, what columns they carry, how they relate, and which rows change in each scenario. Endpoints and response shapes come next. Scale is modest, and a single well-run Postgres cluster covers it for years. Correctness is what makes it hard: balances that always match the history, money that is pending versus money that is final, and a bank that can take money back after you thought it was done.
AffirmPremium lesson · System design round
The Affirm design, worked end to end.
- The API and data modelSystem design
- The design, drawn out2 diagrams
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports · guide updated
Affirm interview guideKnow what Affirm asks before you walk in.
23 coding · 4 system design · 13 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.