CSE Roadmap

Core tier · about 5 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes fourth in Level 12

In this module you will

  • Scope a payment backend and show that its rate is small but its correctness bar is high.
  • Draw the pay-in flow with a payment service, executor, PSP, wallet and ledger.
  • Explain the double-entry principle and why money amounts are never stored as floating-point numbers.
  • Use a hosted payment page, and say why card numbers never reach your servers.
  • Make payments safe with retries, idempotency keys, dead letter queues and reconciliation.

This is the first case where a small error costs real money and trust. The rate is tiny, so the lesson is not speed. It is correctness under failure: charging once, never zero times by mistake, and being able to prove where every cent went. It builds on idempotency (Level 1), transactions (Level 5), queues (page 1 of this level) and the booking case in Level 11. The book used is "System Design Interview, Volume 2" by Alex Xu, the payment system chapter. Numbers marked "made up" only show the idea. This page explains design ideas, and is not legal or financial advice.