Inside a Payment Platform: How Transaction and Payment Cores Interact

Payment System Overview

Payments are the core of any transaction‑based company. A typical payment platform can be divided into two major subsystems: the transaction core , which links business scenarios to the underlying payment mechanisms, and the payment core , which handles integration with payment tools, reconciliation, and settlement.

Core System Analysis

Transaction Core

The transaction core connects business systems with the underlying payment layer, allowing business services to focus on domain logic without dealing with payment details.

Basic Transaction Type Abstraction

Multi‑Table Aggregation & Order Association

Payment Core

The payment core abstracts four payment forms— Recharge, Withdrawal, Refund, and Transfer —and integrates multiple payment tools, orchestrating payment commands.

Payment Core Overview

Payment Behavior Orchestration

Designed for plug‑in development and configurable payment rules, enabling flexible extension of payment logic.

Exception Handling

Handles duplicate payments, partial payments, amount mismatches, and other error scenarios.

Channel Gateway

Fund Accounting

Service Governance

Unified Platform Context

After defining system boundaries and splitting business models, the platform consists of dozens of services. A unique business identifier is propagated across all services to prevent information loss.

Data Consistency Governance

Large payment companies often use heavyweight distributed transactions to guarantee consistency, sacrificing development speed. For services that avoid distributed transactions, alternative strategies include:

CAS validation

Idempotency and compensating actions

Reconciliation (batch and near‑real‑time)

CAS Validation

Idempotency & Compensation

Reconciliation

Near‑Real‑Time Reconciliation

Production Practices

Performance Stress Testing

Build stress‑test models that simulate real‑world traffic, write test data to shadow databases to avoid affecting production, and evaluate both single‑node and centralized link performance.

Stability Governance

Core Link Separation

Service Dependency Degradation

Overall, the architecture emphasizes modular design, strong data‑consistency mechanisms, asynchronous processing, and robust operational practices.