Comprehensive Overview and Deep Dive of Payment System Architecture

Part One: Payment System Overview

Core System Interaction

Business Map

Part Two: Core System Analysis

Transaction Core

The transaction core links business systems with underlying payment channels, allowing business logic to focus on domain concerns while abstracting payment details.

Transaction Core Overview

Basic Transaction Type Abstraction

Multi‑Table Aggregation & Order Association

Payment Core

The payment core abstracts various payment types into four fundamental operations—recharge, withdrawal, refund, and transfer—while integrating multiple payment tools and orchestrating payment commands.

Payment Core Overview

Payment Behavior Orchestration

Designed for plug‑in development and configurable payment rules, enabling flexible implementation.

Exception Handling

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

Channel Gateway

Fund Accounting

Part Three: Service Governance

Platform Unified 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 prevent information loss.

Data Consistency Governance

Large payment companies often employ heavyweight distributed transactions; the article discusses alternative strategies for businesses that avoid such transactions.

CAS Verification

Idempotency & Compensation

Reconciliation

Near‑Real‑Time Reconciliation

DB Sharding

Asynchronization

To improve stability and throughput, the payment flow is heavily asynchronous.

Message Asynchronization

External Payment Call Asynchronization

By front‑ending a gateway service that obtains third‑party payment credentials asynchronously, the long‑running network call no longer blocks the main payment flow.

Async Parallelism

Fund Accounting Asynchronization

Hot Account Separate Handling

Accounting Transaction Splitting

Part Four: Production Practices

Performance Stress Testing

Build stress‑test models that simulate real scenarios, store test data in shadow databases, and evaluate both single‑machine and centralized link performance to identify stability and capacity limits.

Stability Governance

Core Link Separation

Service Dependency Degradation

Architecture Community Invitation

Join the "Architecture Master" WeChat group for further discussion and knowledge sharing.