How a Modular Transaction System Drives Scalable Membership Services

System Overview

The large‑membership transaction platform is implemented as a collection of independent micro‑services: transaction , order , signing , product , and clearing‑settlement . Each service owns its own data store, exposes standardized REST/gRPC interfaces, and can be built, deployed and scaled separately, which yields high efficiency, flexibility and maintainability.

Core Process

Order creation triggers a state‑machine driven workflow: CREATE → PAY → FULFILL → COMPLETE / REFUND → CLOSE. The order service publishes domain events (e.g., OrderCreated, PaymentSucceeded) that downstream services (payment, product, clearing) consume to advance the transaction.

Architecture Diagram

Core Flow Example

The end‑to‑end flow proceeds through order creation, payment, fulfillment, and finally order completion or refund, each step handled by a dedicated service.

Configuration Highlights

Business Identity Management : Assigns a unique business ID that travels with the order, payment and settlement pipelines, guaranteeing data isolation and traceability.

Payment Hub : Supports dynamic selection and prioritisation of multiple payment channels and configurable payment‑protocol templates.

Risk Control : Implements black‑list filtering and intelligent interception (e.g., malicious refund detection) to block abnormal transactions.

Order Service

Workflow Orchestration : Implements a finite‑state machine with rules for timeout cancellation, auto‑confirmation and manual closure. State transitions are driven by events.

Business Data Management : Provides real‑time order queries and metric aggregation; uses distributed transactions to keep order‑related data consistent.

Transaction Data Security : Guarantees ACID properties via database transactions, applies tiered circuit‑breaker isolation, and runs automated reconciliation to protect funds.

Event‑Driven Engine : Publishes order events to a message broker and subscribes to external events (payment, fulfillment) for fine‑grained state updates.

Signing Service

Subscription Management : Handles recurring contracts (e.g., monthly charging) and exposes pluggable renewal/deduction hooks.

Renewal & Payment Flow : On signing order creation, a contract is created in the payment centre and its lifecycle is synchronised with order status.

Extensible Design : Abstracts signing and deduction interfaces so any subscription business can inject its own logic.

Data Consistency : Enforces idempotent contract operations and reconciles contract data with order and payment systems.

Product System

Information Management : Stores product attributes, images, specifications; supports SKU/SPU concepts for virtual goods.

Transaction Support : Supplies accurate price and inventory data to order, payment and clearing modules, ensuring transaction validity.

Marketing Integration : Allows configuration of discounts, bundles and other promotional activities.

Custom Configuration : Handles special rules for virtual items, custom attribute bindings and bespoke clearing/settlement settings.

Clearing‑Settlement System

After a transaction completes, the clearing module splits revenue according to configured ratios and writes the result to a clearing ledger. The settlement module aggregates cleared amounts per partner, applies settlement cycles (daily, SPU‑level) and triggers fund transfers.

Consistency & Stability Measures

Database Transaction Control : Uses ACID‑compliant transactions for multi‑table operations.

Distributed Lock Mechanism : Prevents concurrent conflicts in high‑concurrency order processing.

Idempotency Design : Guarantees that repeated requests (e.g., payment retries) produce the same outcome.

Automated Reconciliation : Periodically verifies order and payment data to detect and resolve inconsistencies.

Compensation Tasks : Executes fallback actions such as refunding users when downstream fulfillment fails.

Tiered Rate Limiting : Applies isolation per payment scenario to protect the system under traffic spikes.

Outlook

Future work focuses on incremental architecture optimisation, support for new business models and extending the platform into an open ecosystem that can integrate upstream and downstream partners for shared value creation.