Payment System Architecture: Business Background, Process Decomposition, Sequence Design, and Structural Design

1. Business Background

In most business systems, payment‑related functions are inevitable, and inexperienced developers often find the detailed settlement logic stressful because any minor issue can cause reconciliation errors, leading to costly manual interventions.

Errors in payment flows can result in high time costs for fixing processes and balancing erroneous data, potentially causing chaotic accounting that requires manual handling.

2. Payment Business

2.1 Process Decomposition

Complex business should be broken into modules, each managed separately, then linked to form a complete solution.

The typical transaction scenario can be divided into four modules:

Account Management: clear management of user funds such as available balance, frozen amount, and statements.

Transaction Ledger: records of all fund movements, including recharge, withdrawal, and refunds.

Payment Integration: handling third‑party payment requests and logging messages.

Order Structure: managing order models, split strategies, and product specifications.

Although real‑world details are more complex, the overall thinking remains consistent; design sequence diagrams for each module and plan node interactions.

2.2 Process Sequence

Sequence diagrams help analyze how nodes collaborate, typically divided into three core stages: pre‑payment, payment integration, and post‑payment.

Pre‑payment: build order model, validate inventory, freeze funds, generate transaction record, status set to pending.

Payment Integration: after successful model initialization, construct third‑party request, initiate payment, record request parameters, await notification.

Post‑payment: based on payment result, update business model; if successful, update transaction records, release frozen funds, adjust order and inventory.

3. Structural Design

Based on the analysis and sequence diagrams, a basic structural design can be drafted:

Account Management: core dimensions – account amount, available balance, frozen amount.

Transaction Records: store user actions; may contain multiple transaction details (e.g., shopping cart orders).

Transaction Details: split from orders, allowing funds to be allocated to different merchants.

Payment Integration: record request parameters and third‑party callback messages.

Order Records: support multiple sub‑orders with various split strategies (warehouse, merchant, category, etc.).

Order Details: manage each sub‑order’s product, specifications, buyer/seller, price, quantity, amount.

Even this simple design reveals the inherent complexity of payment systems, which multiplies further when coupons, discounts, or other promotional rules are added.

4. Associated Business

Beyond core payment logic, typical e‑commerce scenarios involve product management, inventory, logistics, and coupon rules that intertwine with payment flows.

Product Management

Product Entity: maintain product attributes, specifications, and pricing tiers.

Warehouse Management: after order split, verify stock, freeze inventory, and handle post‑payment shipping.

Coupon Rules

Coupon Entity: design various discount mechanisms (full‑reduction, percentage, tiered pricing, validity periods).

Distribution Rules: support marketing activities, user lifecycle management, and channel conversion.

5. Practical Summary

Business Model: clear understanding and modular decomposition of core nodes, with corresponding sequence and data structures.

Transaction Management: commonly use TCC (Try‑Confirm‑Cancel) pattern for reliable transactions.

Locking & Retry: lock order identifiers after payment success to avoid duplicate processing from retries.

Fund Settlement: ensure precise calculations to avoid precision loss; each transaction must be verifiable.

Process Maintenance: provide visual workflow tools and manual maintenance mechanisms to reduce errors.

Complex business scenarios require iterative refinement, but mastering core logic and systematic decomposition simplifies implementation from analysis to innovation.