Inside a Modern Payment System: Core Architecture, Governance, and Production Practices

Payment System Overview

Payment is the core domain of many companies because it handles the transaction flow. A typical payment platform consists of two major subsystems: the transaction core , which links business systems to underlying payment mechanisms, and the payment core , which abstracts various payment operations.

Core System Analysis

Transaction Core

The transaction core connects business scenarios with the underlying payment infrastructure, allowing business services to focus on their own logic without dealing with payment details.

Basic Transaction Type Abstraction

Multi‑Table Aggregation & Order Association

Payment Core

The payment core abstracts multiple payment types into four main forms: 充值 (recharge), 提现 (withdrawal), 退款 (refund), and 转账 (transfer). It also integrates various payment tools and orchestrates payment commands.

Payment Behavior Orchestration

Designed for plug‑in development and configurable payment rules, enabling flexible extension of payment behaviours.

Exception Handling

Handles scenarios such as duplicate payments, partial payments, amount mismatches, and other anomalies.

Channel Gateways

Fund Accounting

Service Governance

Unified Platform Context

After defining system boundaries and modeling business domains, the platform is split into dozens of services. A unique business identifier is propagated across all services to prevent loss of context.

Data Consistency Governance

Large payment companies often use heavyweight distributed transactions to guarantee data stability, sacrificing development speed. For services that avoid distributed transactions, alternative strategies are employed:

CAS Validation – optimistic locking to prevent lost updates.

Idempotency & Compensation – ensure repeatable requests do not cause side effects and provide compensating actions for failures.

Reconciliation – periodic comparison of internal records with external channel data.

Near‑Real‑Time Reconciliation – stream‑based matching to detect mismatches quickly.

Production Practices

Performance Stress Testing

Build stress‑test models that simulate real‑world traffic, write test data to shadow databases to avoid affecting production, and evaluate both single‑node performance and centralized link capacity.

Stability Management

Core Link Separation

Service Degradation

Asynchronous Processing

Payment is a critical link; to improve stability and throughput the system adopts asynchronous designs for message handling, external payment calls, and fund accounting.