Payment System Architecture Overview and Core Components

Payment is the core domain of any transaction‑driven company; this article outlines a typical payment system architecture, dividing it into a transaction core that links business scenarios with underlying payment mechanisms and a payment core that abstracts various payment operations.

1. Payment System Overview

Core System Interaction

Business Map

2. Core System Analysis

Transaction Core

Transaction core connects the company's business systems with the underlying payment infrastructure, allowing business systems to focus on domain logic without dealing with payment details.

Transaction Core

Basic Transaction Type Abstraction

Multi‑table Aggregation & Order Association

Payment Core

Payment core abstracts multiple payment types into 充值 , 提现 , 退款 , 转账 and integrates various payment tools, handling orchestration and rule configuration.

Payment Core Overview

Payment Behavior Orchestration

The goal is to achieve plugin‑style development and configurable payment rules.

Exception Handling

Handles duplicate payments, partial payments, amount mismatches, and other abnormal scenarios.

Channel Gateway

Fund Accounting

3. Service Governance

Unified Platform Context

After defining system boundaries and business modeling, the platform is split into dozens of services; a unique business identifier is propagated across the entire payment flow to prevent information loss.

Data Consistency Governance

Large payment companies often adopt strict distributed‑transaction solutions; the article discusses alternatives such as CAS checks, idempotency, compensation, and reconciliation.

CAS Check

Idempotency & Compensation

Reconciliation

Near‑real‑time Reconciliation

DB Sharding

Asynchrony

Asynchronous design improves stability and execution efficiency of the payment flow.

Message Asynchrony

External Payment Call Asynchrony

Asynchronous Parallelism

Accounting Asynchrony

Hot Account Separate Handling

Accounting Transaction Splitting

4. Production Practice

Performance Stress Testing

Build stress models that simulate real scenarios, write results to a shadow database, and monitor system stability and capacity.

Stability Governance

Core Link Separation

Service Dependency Degradation