Designing Payment System Architecture: Product Classification, Module Functions, and Business Process

In the rapidly changing internet product environment, integrating a payment system is essential for commercial closure, user accumulation, and monetization. Payment systems can be generic gateways (Alipay, WeChat Pay, PayPal) or aggregated solutions, serving various industries.

Product Classification – Payment products are categorized by usage scenarios, including Quick Pay, Online Banking Pay, Protocol (collection) Pay, Platform Pay, Foreign Card Pay, Mobile Bill Pay, Virtual Currency Pay, Account/Balance Pay, Credit Pay, and Agency Pay.

Module Functions – Typical payment product interfaces include signing/termination, payment execution, revocation/refund, contract status query, order status query, pre‑authorization and its cancellation/completion, reconciliation, and balance inquiry.

Business Process – A standard flow consists of parameter validation, payment routing, risk assessment, order generation, channel invocation, order update, message notification, and asynchronous callbacks, each step addressing security, performance, and reliability concerns.

Typical Architecture – Payment systems are usually three‑tiered: a supporting layer (monitoring, logging, SMS, security, reporting), a core layer (payment core and service modules), and a product layer (user‑facing applications for consumers, merchants, and operations).

Real‑world reference architectures from Alipay, JD Finance, Qunar, and Meituan illustrate common components such as accounting subsystems, flexible transaction handling via messaging, and the separation of single‑sided and double‑entry bookkeeping.

Reference Architecture – A generic diagram shows supporting systems (operations monitoring, log analysis, SMS platform, security mechanisms), core payment processing (routing, risk, order management), and product applications tailored to end‑users, merchants, and internal staff.

The article concludes that the described modules and layers form the foundation for designing scalable, secure, and maintainable payment systems, with future posts planned to dive deeper into each component.