Overview of Payment System Evolution, Architecture, and Practices

Payment is a core capability of e‑commerce platforms. Understanding the payment domain helps order‑related engineers grasp the upstream and downstream flows, the four‑stream model of e‑commerce, and the design patterns that ensure fund safety and process reliability.

1. History and Evolution – From the early ticket‑house and money‑shop institutions, through the manual inter‑bank (pre‑1989) and electronic inter‑bank stages (1989‑2005), to the modernized payment system (2005‑present). Key milestones include the establishment of the national clearing centre, the electronic inter‑bank system (EIS), and the shift to real‑time settlement.

2. Basic Concepts – Core notions of a payment system, common payment forms such as platform payment, online‑bank payment, quick payment, protocol (direct‑debit) payment, virtual‑currency payment, balance payment, and credit payment.

3. System Overview – The overall architecture consists of third‑party payment channels (e.g., WeChat, Alipay) and aggregated payment systems that hide channel differences. The typical payment flow starts at the gateway, proceeds through security checks, redirects to a checkout page, and finally invokes bank or third‑party APIs.

4. Interfaces – Typical APIs include payment, transaction‑close, transaction‑query, refund, and statement‑download. Each API follows a clear request‑response pattern and supports asynchronous notification (Notify_URL) and result redirection (Return_URL).

5. Funds and Information Flow & Settlement – Detailed description of how funds move from the user’s bank card through the network clearing platform (网联) to the third‑party and finally to the merchant’s account. Settlement can be real‑time or periodic, involving billing, aggregation, verification, and final fund transfer.

6. Security and Risk Control – Accuracy (information completeness, timing) and compliance (two‑level clearing, regulatory rules). Mechanisms such as idempotency keys, retry queues, maximum‑effort notifications, and monitoring ensure robustness.

7. Two‑Level Clearing (二清) – Explains fund‑level and information‑level two‑clearing issues, associated risks (fund misappropriation, regulatory violations), and common solutions: obtaining a payment licence or integrating a third‑party two‑clearing service. Example of a marketplace using a third‑party’s two‑clearing product for settlement and commission distribution.

8. Order‑Payment Interaction – Interaction patterns between order and payment domains, handling of 0‑amount orders, design of payment‑order expiration times to avoid mismatched lifecycles, and the importance of synchronizing order and payment timeouts.

9. Summary – A solid understanding of payment system history, architecture, flow, and risk‑control techniques equips order engineers to design reliable e‑commerce transactions and to adopt proven industry practices.