Comprehensive Overview of Payment System Architecture and Core Processes

Payment systems act as a bridge between consumers, merchants, and financial institutions, managing payment data, invoking third‑party payment interfaces, recording transaction details, and handling reconciliation. They evolve from isolated, tightly coupled applications to decoupled services supporting both internal and external business needs.

Key functional modules:

Application Management – supports multiple business systems.

Merchant Management – onboarding and documentation.

Channel Management – supports WeChat, Alipay, UnionPay, JD Pay, etc.

Account Management – shared and proprietary channel accounts.

Payment Transaction – pre‑order generation and refund services.

Reconciliation Management – automatic matching of transaction data with third‑party channels (typically T+1).

Clearing Management – calculates merchant receivables and system revenue.

Settlement Management – transfers funds to merchant accounts.

Core processes:

Payment flow: user initiates payment → e‑commerce gateway forwards order → user selects bank/channel → bank processes and returns result → platform notifies merchant and updates order status.

Refund flow: user requests refund → merchant validates → payment platform verifies order status, balances, and signatures → funds are deducted from merchant’s available account and returned via bank or proxy channel.

Reconciliation: includes both information‑flow matching (transaction records) and fund‑flow matching (settlement amounts) between the payment system and banks, handling discrepancies such as missing or extra records.

Settlement: automated clearing rules settle funds to merchants, support detailed fee and billing configurations, and provide data for finance, operations, and management analytics.

Design highlights:

Gateway front‑end abstracts channel differences, providing a unified API to business systems.

Routing selects optimal channels based on fees, availability, and risk.

Risk assessment evaluates transactions and may block, require enhanced verification, or allow passage.

Asynchronous notifications decouple long‑running channel calls from the main thread.

Order generation persists transaction data, with high‑traffic scenarios requiring careful DB write optimization.

Transaction logging records each operation, with MQ‑driven downstream accounting, analytics, and distributed‑transaction handling.

Payment routing and multi‑channel integration ensure resilience and scalability, supporting third‑party, UnionPay, direct bank connections, and mobile‑specific channels.

In summary, a payment system is a complex, evolving backend service that must handle diverse business flows, ensure data consistency, provide robust monitoring, and continuously adapt to changing requirements and external channel dependencies.