What’s the Core Architecture Behind Modern Payment Systems?

The kernel is the underlying framework of any system; it stays stable while remaining flexible as the environment changes.

It is not static—it continuously absorbs new knowledge, grows, and evolves together with us.

Below are the abstracted kernels I have distilled over the past years, each reshaping the past, present, and future of product development.

Kernel 1: Understanding Payment from a Business Perspective

Payment is essentially about recording transactions, moving funds, and aligning business logic with accounting.

Kernel 2: Payment Organizational Layers

Payment is a societal layered collaboration, not the responsibility of a single entity.

Kernel 3: Information Flow and Capital Flow

Information and capital flow are driven by communication between different accounts across organizations.

Kernel 4: Enterprise Payment – Aligning Business and Money

For an enterprise, business determines payment; understanding the business is more important than the technical implementation.

Kernel 5: Three‑Party Payment Product Framework

Three‑party payment is a hallmark of the payment era, with a unique structure that shapes modern payment products.

Kernel 6: Settlement Enables Collaboration

Settlement institutions are crucial for routing payment information and funds to the ultimate layer – the central bank.

Kernel 7: Transaction Process

Every transaction follows a process that intertwines business flow and system flow.

Kernel 8: Transaction and Order Interdependence

Transactions complete orders; orders link payment, logistics, and settlement.

Kernel 9: Cashier System – Managing Money In and Out

Cashier systems come in various types for users, merchants, and staff, each supporting different business scenarios.

Kernel 10: Payment Processing Core

The cashier opens the payment request; the payment system then handles the entire processing flow.

Kernel 11: Document Core – Understanding Relationships

Documents link across layers; a three‑layer document model clarifies forward and reverse flows.

Kernel 12: Reverse Payment Flow

Reverse scenarios involve multiple systems and organizations, illustrating the full refund lifecycle.

Kernel 13: Settlement Positioning

Settlement sits at the core of the financial middle‑office, defining its responsibilities.

Kernel 14: Calculation Core

Accurate calculation is the starting point for settlement.

Kernel 15: Settlement System Architecture

The settlement system orchestrates calculation, distribution, and reconciliation.

Kernel 16: Money Distribution System

After calculation, distributing money to the right parties is the ultimate goal.

Kernel 17: Middle‑Office Settlement

Three years of experience distilled into a middle‑office settlement model.

Kernel 18: Billing Core

Payment providers incur various billing scenarios, from merchant fees to channel costs.

Kernel 19: Account System Fundamentals

Accounts are more than ledgers; they embody fund attributes and regulatory policies.

Kernel 20: Wallet Three‑Layer Model

A wallet is a three‑layer product that integrates multiple system capabilities.

Kernel 21: Reconciliation – God‑View

A high‑level abstraction of reconciliation scenarios provides a universal perspective.

Kernel 22: Reconciliation Processing Core

The reconciliation engine executes the matching and settlement logic.

Kernel 23: Reconciliation Data Core

Data flows from acquisition to parsing and storage, forming the backbone of reconciliation.

Kernel 24: Compliance Payment Process

Even without a license, enterprises can achieve compliant payment by following a clear flow.

Kernel 25: Two‑Clearance Global View

Payment involves many participants, systems, and processes; a global diagram captures this complexity.

Kernel 26: Allocation Function

Allocation systems coordinate multiple functions to move funds between accounts.

Kernel 27: Business‑Finance Integration

The model links business operations with financial reporting, achieving seamless integration.

Kernel 28: Tax and Invoice from Business Layer

Tax and invoicing are addressed within the business system context.

Kernel 29: Abstract Five‑Point Model

An abstract model connects information systems to business‑finance outcomes, forming a five‑point framework.

Each kernel continues to evolve, and together we become stronger.