Design and Architecture of a Scalable Payment System

Hello, I am a senior architect. Payment is the core of any transaction‑oriented company, and the overall payment system can be viewed as two major subsystems: the transaction core and the payment core. The transaction core connects business scenarios with underlying payment mechanisms, while the payment core handles interactions with payment tools, reconciliation, and settlement.

1. Payment System Overview

Core System Interaction

Business Map

2. Core System Analysis

Transaction Core

The transaction core links the company's business systems with the underlying payment infrastructure, allowing business logic to focus on domain concerns without dealing with payment details.

Transaction Core

Basic Transaction Type Abstraction

Multi‑Table Aggregation & Order Association

Payment Core

The payment core abstracts multiple payment types into 充值 , 提现 , 退款 , 转账 and integrates various payment tools, orchestrating payment commands.

Payment Core Overview

Payment Behavior Orchestration

Its goal is to achieve plugin‑based development and configurable payment rules, enabling flexible development.

Exception Handling

Exception handling covers duplicate payments, partial payments, amount mismatches, and other error scenarios.

Channel Gateway

Fund Accounting

3. Service Governance

Unified Platform Context

After defining system boundaries and business modeling, the payment platform is split into dozens of services. A unique business identifier is propagated across all services to ensure business information is not lost during inter‑service communication.

Data Consistency Governance

Large payment companies adopt strict distributed‑transaction solutions, sacrificing development efficiency for data stability. For businesses that avoid distributed transactions, strategies such as CAS validation, idempotency, and compensation are discussed.

CAS Validation

Idempotency & Exception Compensation

Reconciliation

Near Real‑time Reconciliation

DB Sharding

Asynchronization

Payment is the core link of the transaction chain; to balance stability and execution efficiency, asynchronous processing is employed.

Message Asynchronization

External Payment Call Asynchronization

External payments often require obtaining a pre‑payment credential from third‑party services, which can cause long response times and block the entire payment flow.

Asynchronous Parallelization

Fund Accounting Asynchronization

Hot Account Accounting Isolation

Accounting Transaction Splitting

4. Production Practices

Performance Stress Testing

Build stress‑test models that simulate real scenarios; test data is written to a shadow database to avoid impacting normal business. Both single‑machine performance and centralized link performance are considered to identify system stability and capacity bottlenecks.

Stability Governance

Core Link Separation

Service Dependency Degradation