Overview and Core Architecture of a Payment System

Payment is the core domain of any transaction-oriented company, and this article outlines the typical architecture of a payment system that applies to most scenarios.

The system can be divided into two major subsystems: the transaction core, which connects business scenarios to the underlying payment mechanisms, and the payment core, which abstracts various payment types— 充值, 提现, 退款, 转账 —and integrates multiple payment tools.

The transaction core includes basic transaction type abstraction, multi‑table aggregation, and order association, providing a unified way for business services to invoke payment functions without dealing with low‑level details.

The payment core focuses on abstracting payment behaviors, enabling plugin‑style development and configurable payment rules, which allows flexible extension and customization of payment flows.

Service governance is achieved through a unified context that propagates a unique business identifier across dozens of micro‑services, ensuring data consistency via CAS checks, idempotency, compensation mechanisms, and both batch and near‑real‑time reconciliation.

Asynchronous processing is employed to improve stability and efficiency, including message‑level async, external payment async, and parallel execution of payment‑related tasks, while performance testing, stability governance, core link separation, and service degradation strategies are applied in production practice.

The article concludes with an invitation to join a technical learning group for further discussion and knowledge sharing.