Designing a Unified Payment Settlement Platform: Blueprint, Challenges, and Lessons
This article recounts how a product manager defined and implemented a unified payment settlement middle‑platform, identified core system problems, proposed five central hubs, and illustrated the architecture with diagrams to guide future financial solutions.
01. Make Everyone See
The product manager’s mission is to solve problems using a product as a tool, always returning to the enterprise’s scenario to deliver the optimal solution.
When the author joined a company as the product lead for the payment settlement middle‑platform, the senior director asked for a complete blueprint and an internal presentation. At that time the organization had no clear middle‑platform strategy, so the presentation needed to define the future vision.
First, the author collected product and business information from the team and stakeholders, learning about past, present challenges, pain points, and future expectations. After a week of discussion, the current state of the settlement business and the responsibilities of the middle‑platform were summarized (see diagram below).
The analysis revealed five major problems:
System construction is fragmented
Severe business coupling
Weak product configurability
Poor data accuracy
Low service abstraction
To address these, the author proposed five central hubs:
Unified Clearing Center
Unified Accounting Center
Unified Account Center
Unified Settlement Center
Unified Reconciliation Center
Beyond the core middle‑platform services, these hubs will provide comprehensive financial solutions such as wallet services, merchant settlement, B‑merchant settlement, insurance settlement, employee exit settlement, guarantee fund, and commission fund solutions, extending the middle‑platform’s reach into the business front‑end.
02. One Diagram Determines Destiny
The author created a single diagram that captures both the business layer and the account layer of the unified account center.
The diagram consists of two parts:
Business Layer
Describes the scenarios the unified account middle‑platform serves and the user groups involved, including wallet business, financial processing, balance payment at cash registers, corporate settlement platforms, and the account console.
Account Layer
Divided into three tiers:
Basic Capability Layer: Core account functions such as entity management, account management, balance management, transaction handling, and ledger management.
Service Layer: Exposes services like entity changes, account opening, and information queries to both internal and external systems.
Solution Layer: Packages the services into ready‑to‑use financial solutions (e.g., settlement schemes, corporate settlement, enterprise payment channels).
This service‑oriented approach makes capabilities visible, selectable, composable, and customizable for users.
03. Make Yourself Irreplaceable
Over the next three years, the department will continue to build on these five centers, standardizing, configuring, and abstracting services to a high degree of perfection.
When the author eventually leaves, the goal is to have completed all planned constructions, with the demand dropping to just two tickets per quarter while still achieving top performance.
The key insight is that understanding the past clarifies the present and illuminates the future; with a clear vision, a single diagram can drive decisive action.
Chen Tian Universe
Chen Tian Universe, payment architect specializing in domestic payments, global cross‑border clearing, core banking, and digital payment scenarios. Notable works: “Ten‑Thousand‑Word: Fundamentals of International Payment Clearing”, “35,000‑Word: Core Payment Systems”, “19,000‑Word: Payment Clearing Ecosystem”, “88 Diagrams: Connecting Payment Clearing”, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
