Mock Interviewer

Ask Coach

Ask Coach
Clarify requirements before you design — kept separate from your stage notes.

Tap a question to start, or type your own below.

Payment Gateway System Design

Visual Problem Diagram

Payment Gateway System Design architecture diagram

Scenario

A shopper double-clicks Pay and two $2,400 charges settle because idempotency keys never reached the processor—support tickets spike while your ledger still shows one order. The gateway interview is idempotency, PCI scope, reconciliation, and exactly-once money movement semantics, not drawing Visa logos.

Design a payment gateway that merchants use to charge customers via cards and wallets with authorize/capture/refund flows. Money bugs are irreversible—idempotency, clear state machines, and reconciliation matter more than raw QPS.

You should support payment intents, idempotent APIs, webhooks, fraud hooks, and internal ledger. Be ready to explain PCI boundaries, duplicate retry safety, and settlement reconciliation.

Constraints

Functional

Create payment, authorize, capture, refund, idempotent APIs, merchant webhooks, fraud check hook

Non-functional

99.99% availability, < 500 ms p95 auth, ACID ledger, PCI scoped card handling

Scale

10K TPS peak, millions merchants, billions $/month, global multi-currency

Stages ahead

1Requirement Analysis
2API Design
3High-Level Design
4HLD Extensions
5Trade-offs

Log in to start practicing

Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.