Inside the Core of Payment Systems: Architecture, Governance, and Performance

1. Payment System Overview

Core System Interaction

Business Map

2. Core System Analysis

Transaction Core

Transaction core links business systems with underlying payment, allowing business logic to focus on domain without worrying about payment details.

Transaction Core

Basic Transaction Type Abstraction

Multi-table Aggregation & Order Association

Payment Core

Payment core abstracts multiple payment types into Recharge, Withdrawal, Refund, Transfer, and integrates various payment tools while orchestrating payment commands.

Payment Core Overview

Payment Behavior Orchestration

Its goal is to achieve Plugin‑style development and Configurable payment rules for flexible development.

Exception Handling

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

Channel Gateway

Fund Accounting

3. Service Governance

Platform Unified Context

After defining system boundaries and business modeling, the payment platform is split into dozens of services; a unified context identifier is passed throughout to preserve business information across services.

Data Consistency Governance

Large payment companies adopt strict data consistency solutions, often using distributed transactions at the cost of development efficiency; alternatives for businesses without such transactions are discussed.

CAS Validation

Idempotency & Exception Compensation

Reconciliation

Near‑real‑time Reconciliation

DB Sharding

Asynchrony

Asynchrony balances payment system stability and execution efficiency.

Message Asynchrony

External Payment Call Asynchrony

External payments often require interaction with third‑party services to obtain pre‑payment credentials, which can cause long response times and block the payment chain.

Therefore, credential acquisition can be split via a front‑gate service that obtains internal credentials and asynchronously calls third parties.

Asynchronous Parallelism

Fund Accounting Asynchrony

Hot Account Billing Separate Handling

Accounting Transaction Segmentation

4. Production Practices

Performance Stress Testing

Build stress models simulating real scenarios; store test data in shadow databases without affecting normal business; consider both single‑machine performance and centralized link capacity to assess system stability and capacity ratios.

Stability Governance

Core Link Separation

Service Dependency Degradation

Source: www.cnblogs.com/wintersun/