Common Problems
Payment System
Try This Problem Yourself
Practice with guided hints and real-time feedback
Understanding the Problem
Functional Requirements
- Merchants should be able to initiate payment requests (charge a customer for a specific amount).
- Users should be able to pay for products with credit/debit cards.
- Merchants should be able to view status updates for payments (e.g., pending, success, failed).
- Customers should be able to save payment methods for future use.
- Merchants should be able to issue full or partial refunds.
- Merchants should be able to view transaction history and reports.
- Support for alternative payment methods (e.g., bank transfers, digital wallets).
- Handling recurring payments (subscriptions).
- Payouts to merchants.
Non-Functional Requirements
The Set Up
Defining the Core Entities
API or System Interface
High-Level Design
1) Merchants should be able to initiate payment requests
2) Users should be able to pay for products with credit/debit cards.
3) The system should provide status updates for payments
Potential Deep Dives
1) The system should be highly secure
2) The system should guarantee durability and auditability with no transaction data ever being lost, even in case of failures.
3) The system should guarantee transaction safety and financial integrity despite the inherently asynchronous nature of external payment networks
4) The system should be scalable to handle high transaction volume (10,000+ TPS)
Servers
Kafka
Database
Bonus Deep Dives
1) How can we expand the design to support Webhooks?
What is Expected at Each Level?
Mid-level
Senior
Staff+
Purchase Premium to Keep Reading
Unlock this article and so much more with Hello Interview Premium
Currently up to 25% off
Hello Interview Premium
On This Page
Understanding the Problem
Functional Requirements
Non-Functional Requirements
The Set Up
Defining the Core Entities
API or System Interface
High-Level Design
1) Merchants should be able to initiate payment requests
2) Users should be able to pay for products with credit/debit cards.
3) The system should provide status updates for payments
Potential Deep Dives
1) The system should be highly secure
2) The system should guarantee durability and auditability with no transaction data ever being lost, even in case of failures.
3) The system should guarantee transaction safety and financial integrity despite the inherently asynchronous nature of external payment networks
4) The system should be scalable to handle high transaction volume (10,000+ TPS)
Bonus Deep Dives
1) How can we expand the design to support Webhooks?
What is Expected at Each Level?
Mid-level
Senior
Staff+