How JD Pay Reinvented Its Business Architecture to Scale with Rapid FinTech Growth

Why Business Architecture Transformation Is Needed

Internet payment volumes in China doubled from 11 trillion yuan in 2015 to 22 trillion yuan in 2018, with transaction counts growing at a similar pace. The high‑frequency, low‑value nature of online payments creates both opportunities and challenges, requiring systems that scale with transaction volume rather than monetary value.

Business products have evolved from simple card‑acquiring and fee calculation to complex offerings that include banking, insurance, securities, and funds. This diversification demands rapid development cycles, seamless user experiences, and robust quality assurance.

JD Pay’s “small treasury” model illustrates the complexity of fund‑flow processes, where immediate redemption, receivable accounting, and reporting must be handled efficiently while maintaining high development productivity in a competitive market.

What Business Architecture Transformation Means

When existing system architecture cannot meet business needs, incremental manual adjustments are insufficient. Transformation is evaluated against three criteria: cost reduction, increased development efficiency, and support for business growth.

Pain Points of Business Architecture Transformation

1. Broad impact: changes to core infrastructure affect all downstream services. 2. Long cycles: parallel operation of old and new systems increases operational difficulty and cost. 3. Seamless migration: 24/7 payment services require online, zero‑downtime switches.

A vivid analogy compares system migration to changing tires on a highway—any delay can be fatal for a payment service.

Challenges of System Migration

Ensuring smooth transition requires designing compatibility from the start and guaranteeing data consistency, idempotency, and accurate financial accounting during the cut‑over.

Example: the transition from first‑generation to second‑generation payment systems in central banks.

JD Pay’s Architecture Practice

Initially, JD Pay patched legacy systems to meet new business demands. Starting in 2013‑2014, a new business architecture was designed, decoupling and encapsulating legacy services into a unified platform.

The transformation focused on core services, migrating upper‑layer applications within two years.

Goals of the New Platform Architecture

1. Abstract and encapsulate common services (account, membership, accounting, transaction) to reduce product complexity and duplicate development. 2. Achieve high stability and scalability, providing a secure, reliable foundation that balances the “speed” of internet finance with the “stability” required by the payment industry. 3. Deliver a complete data view by consolidating core enterprise data, supporting big‑data analytics for future growth.

Implementation Steps

1. Switch the acquiring business from the old system to the new platform, using gray‑scale deployment and iterative roll‑outs over six months. 2. Migrate member transactions (personal, corporate, mobile) to the new platform, integrating payment products across portals. 3. Transition the accounting system, ensuring data consistency, zero‑downtime fund settlement, and full end‑to‑end verification.

Results After System Switch

Business outcomes: unified customer account system, reengineered processes, stable core platform, rapid response to new demands, comprehensive fund accounting, and full data visibility.

System stability: increased transaction success rate, support for peak daily transactions exceeding ten million, handling billions of member accounts, 99.99% service availability, and zero scheduled downtime for core services.

Key Takeaways and Recommendations

Common pitfalls include treating architecture change as mere technical upgrade, reinventing the wheel without preserving legacy interfaces, and neglecting compatibility, leading to service disruption and financial loss.

Recommendations: maintain continuous architecture governance, plan phased migrations early, address both current and future needs, ensure seamless transition to preserve business continuity, and choose the most suitable architecture rather than seeking a perfect one.