Architecture and Core Components of the Big Member Transaction System

In the era of digital transformation, efficient operation and innovation of online businesses rely on robust technical support. A transaction system serves as the critical hub connecting users and services, and its maturity determines business competitiveness.

The Big Member transaction system is a modular platform that combines efficiency, flexibility, and stability. It is built with independent yet tightly coordinated modules such as transaction, order, signing, product, and settlement, enabling rapid response to business changes.

System Architecture Overview

The system adopts a modular design, decomposing complex transaction flows into core modules. It is tailored for virtual‑item business scenarios, differing from traditional e‑commerce transaction systems.

Core Process Deep Dive

The core process starts when a user places an order. The order links payment, fulfillment, refund, and other stages, interacting with product, payment, marketing, and settlement services to ensure smooth execution and data security.

Key Technical Components

1. Business Identity Management

Each business receives a unique ID that persists throughout the order‑payment‑settlement chain, ensuring data isolation and precise tracking.

2. Payment Hub Configuration

Supports flexible selection and prioritization of payment channels, as well as management of payment protocol templates for rapid front‑end adaptation.

3. Risk Control

Implements proactive defenses (e.g., blacklists) and intelligent interception (e.g., malicious refunds) to block abnormal transactions.

Order Service

Handles transaction orchestration, business data management, and data security. It maintains the full order lifecycle via a state‑machine, supports timeout cancellation, automatic confirmation, real‑time queries, and distributed transactions. It also provides hierarchical circuit‑breaker mechanisms and automated reconciliation.

Order Lifecycle

Order creation

User payment

Order fulfillment

Order completion

Refund processing

Order closure (payment failure, timeout, user cancellation)

Signing Service

Manages subscription‑type contracts (e.g., monthly charging), providing contract creation, renewal, deduction, and termination capabilities. It ensures idempotent contract handling and data consistency with upstream order and payment systems.

Product System

Defines “product” as the transaction entity (SKU) and groups SKUs into SPUs. It offers product information display, configuration, pricing, inventory support, marketing activity integration, and custom rules for virtual goods.

Settlement System

After transaction completion, the settlement subsystem distributes revenue to partners. It consists of a clearing component that splits transaction amounts according to predefined ratios, and a settlement component that aggregates cleared data per period and transfers funds.

Front‑End Unified Revenue Payment SDK

Provides a full‑process payment SDK that creates orders, invokes payment channel APIs, polls results, and handles exceptions. It includes a headless UI component library for product display, quantity selection, channel selection, agreement confirmation, and payment buttons. The SDK can be used as a ready‑made panel or customized via modular plugins.

Business Integration

New activity‑type businesses can be integrated with zero development effort by configuring the SDK. Existing businesses undergo compatibility assessment, interface scanning, data model mapping, and front‑end panel adaptation.

Consistency, Stability, and Reliability

Ensures data integrity through database transactions, distributed locks, idempotent design, automated reconciliation, timeout compensation tasks, and tiered rate‑limiting.

Future Outlook

Continuous architecture optimization, exploration of innovative business models, and building an open, collaborative transaction ecosystem.