This article explains the distinction between payment accounts and login credentials, outlines essential design requirements such as transaction, accounting, reconciliation, risk control, and credit needs, and details entity, account, and transaction models for building comprehensive e‑commerce payment systems.
This article presents a comprehensive overview of payment system architecture, detailing the transaction and payment cores, their interactions, service governance, data consistency, asynchronous processing, performance testing, and practical production practices for building robust backend payment platforms.
This article explains the design of a high‑throughput payment reconciliation system that handles daily transaction volumes in the tens of millions, covering architecture, data collection, big‑data processing with Hive and Spark, handling of suspicious records, and integration with a data platform.
The article provides a comprehensive overview of payment‑system clearing and reconciliation, detailing fund inflow/outflow matching, reconciliation center functions, various one‑to‑one, many‑to‑many and one‑to‑many matching rules, data import, error handling, and auxiliary modules such as balance entry and abnormal data recovery.
This article explains the typical order flow in payment systems, identifies external and internal order loss scenarios, and provides concrete measures such as adding a "payment in progress" state, setting timeout queries, ensuring idempotent notifications, and using Redis hashes to avoid duplicate submissions.
This article explains the foundational design of a payment system's account and accounting architecture, covering transaction models, account types, accounting entries, business processes, and the interaction between account, accounting, and settlement systems to ensure accurate financial tracking.
This article explains the purpose, evolution, business logic, architectural design, and key design principles of a payment operations platform, detailing its user groups, system architecture, interaction model, permission management, and security considerations for internal staff in payment companies.
Jeepay is an open‑source, Spring Boot‑based payment platform that supports multiple channels such as WeChat Pay, Alipay, and UnionPay, offering distributed deployment, high concurrency, secure signing, and a modular front‑back separation with comprehensive management and merchant interfaces.
The article explains the functional purpose, early evolution, layered and clustered design, distributed technical architecture, caching, asynchronous checks, heterogeneous storage, payment solutions, and anti‑bot measures of a cloud‑based shopping cart, highlighting stability, performance, elasticity, and fault‑tolerance.
This article outlines the objectives, call flow, architectural design, and potential challenges of a payment center system that unifies transaction, payment, and finance services, detailing its four main modules, data handling, and integration with third‑party payment channels.
This article provides a step‑by‑step guide for integrating Alipay's new transfer interface in a Java Spring application, covering certificate placement, property configuration, Maven dependencies, bean injection, configuration classes, utility services, and related data models with full code examples.
Jeepay is an open‑source payment system for internet businesses that supports multiple channels like WeChat Pay, Alipay and UnionPay, offers a Spring Boot backend with Spring Security, Ant Design Vue frontend, and provides comprehensive documentation, architecture diagrams, and deployment guides.
Jeepay is an enterprise‑grade open‑source payment platform built with Spring Boot, Ant Design Vue and Spring Security, supporting multiple channels such as WeChat Pay, Alipay and UnionPay, and offering distributed deployment, high concurrency, secure transaction signing, and comprehensive operation and merchant modules.
This article explains the purpose, evolution, business logic, design principles, system architecture, permission model, and technical implementation of a payment operation platform that serves internal staff such as developers, testers, product managers, finance, and customer service within a payment company.
Jeepay is an open‑source, multi‑channel payment system for internet companies that combines Spring Boot backend services, Ant Design Vue front‑end, Spring Security permission control, and supports WeChat Pay, Alipay and UnionPay with distributed, high‑concurrency architecture.
This article outlines the objectives, detailed call process, architectural modules, and potential challenges of a payment center system that unifies order, payment, and finance services while ensuring security, scalability, and data support for downstream applications.
The article explains the role, evolution, business logic, user requirements, and design principles of a payment operations platform, detailing its architecture, interaction model, permission system, and technical stack to support internal staff with secure, efficient, and easy‑to‑use services.
This article presents a visual deep‑dive into the core transaction architecture and payment orchestration flow, illustrating each component and their interactions through detailed diagrams that reveal how modern backend systems handle complex payment processes.
This article outlines the objectives, detailed invocation process, architectural design, and anticipated challenges of a payment center system, describing its core modules, data handling, and integration with third‑party payment channels to achieve unified, secure, and scalable transaction services.
The article outlines the objectives, detailed call flow, architectural components, and potential issues of a payment center system, describing how unified order, payment, and financial services are built, integrated with third‑party channels, and managed through modules such as backend, messaging, transaction core, and channel gateway.
This talk explains how JD.com’s payment platform ensures millisecond‑level speed while guaranteeing exact monetary calculations through a modular architecture, fast integration flow, configurable payment methods, multi‑endpoint order lifecycle management, high‑availability design, and comprehensive monitoring.
This article explains the typical payment order flow, identifies external and internal causes of order loss, and provides concrete backend strategies—such as intermediate payment states, timeout queries, idempotent handling, retry mechanisms, and Redis‑based duplicate‑submission protection—to ensure reliable order processing.
The article explains common causes of order loss and duplicate submissions in payment workflows, distinguishes external and internal loss, and provides concrete backend strategies such as intermediate payment states, timeout queries, idempotent handling, retry mechanisms, and Redis‑based deduplication to ensure reliable order processing.
This article explains the typical order‑payment flow, identifies common causes of lost orders—both external and internal—and provides concrete backend techniques such as intermediate payment states, timeout queries, idempotent notifications, and Redis‑based duplicate‑submission prevention to ensure reliable order processing.
This article outlines a simplified order flow involving payment gateways and third‑party channels, identifies external and internal order‑loss scenarios, and proposes practical measures such as intermediate “payment‑in‑progress” states, timeout queries, idempotent handling, retry mechanisms, and Redis‑based duplicate‑submission prevention to ensure reliable order processing.
This article explains the typical payment flow, identifies causes of external and internal order loss, and provides concrete backend strategies—including intermediate payment states, timeout queries, idempotent handling, retry mechanisms, and Redis‑based duplicate‑submission protection—to ensure reliable order processing.
This article explains common causes of order loss and duplicate submissions in payment workflows, and provides practical backend strategies such as intermediate payment states, timeout queries, idempotent handling, retry mechanisms, and Redis‑based deduplication to ensure reliable order processing.
The YunGouOS open‑source payment SDK provides a one‑package solution for integrating WeChat and Alipay payments, offering installation via npm, JavaScript usage examples for synchronous and asynchronous QR code payments, and a list of newly supported interfaces such as WeChat native, face, and refund APIs.
This article provides a concise, single‑file PHP solution for integrating Alipay and WeChat payments, detailing required environment settings, configuration parameters, essential code snippets, and usage instructions to simplify the payment integration process for developers.
This article examines common payment system anomalies such as duplicate charges and order expiration, explains how asynchronous and synchronous payment flows contribute to these issues, and provides both pre‑payment and post‑payment strategies—including UI improvements, return URLs, status checks, and automated refunds—to prevent and resolve them.
The article describes how a Ctrip senior Android engineer uses divide‑and‑conquer, MVP with Clean Architecture, and Jetpack components such as LiveData and ViewModel to break down a highly coupled payment module into reusable view components, improve data flow, and simplify testing and maintenance.
The article explains the concept of idempotency and presents five practical designs—plain processing, JVM lock, pessimistic lock, optimistic lock, and unique‑constraint approaches—illustrated with Alipay recharge callback examples and SQL/Java code to ensure reliable, duplicate‑free payment handling in distributed backend systems.
This article presents visual diagrams that explain the transaction core architecture and the flow of payment orchestration, offering a concise overview of how payment systems are structured and coordinated.
The article details the evolution of MaFengWo's payment center from a basic payment‑refund module (1.0) to a comprehensive, modular platform (2.0), describing its core capabilities, layered architecture, customizable checkout, routing management, monitoring system, and future micro‑service roadmap.
This article presents a comprehensive guide to applying microservice architecture in payment scenarios, covering business modeling, service decomposition, technical platform choices, performance tuning, operational best practices, and troubleshooting techniques to build reliable, scalable, and maintainable payment systems.
The article outlines Meituan Finance’s front‑end availability challenges in its million‑order payment service and presents a disciplined, end‑to‑end approach—standardized release processes, simple fallback designs, automated testing, robust monitoring, and regular fault‑drill simulations—to ensure stable user experiences across diverse client environments.
The article explains the mathematical definition of idempotency, its importance in preventing duplicate operations such as repeated payments or order creation, and presents practical strategies—including unique business IDs, optimistic locking, deduplication tables, distributed locks, token mechanisms, and payment buffering—to achieve reliable idempotent behavior in backend services.
This article describes the L‑Coin virtual currency used by Lianjia, explains the Spring Cloud micro‑service architecture that supports it, outlines the need for precise cost‑source tracing for each transaction, and presents a detailed backend design and technical implementation to achieve reliable, asynchronous cost attribution and refund handling.
The article examines how the rapid growth of mobile and aggregated payments strains traditional IOE‑based payment systems, and outlines a comprehensive distributed transformation strategy that includes vertical service‑oriented splitting, horizontal sharding by data type, and practical approaches to handling distributed transactions, cross‑shard queries, scaling, disaster recovery, and operational monitoring.
This article provides a comprehensive technical guide on developing WeChat Mini Games, covering their definition, runtime architecture, Webview adapter, core capabilities, engine selection, device adaptation, login, caching, open data domain, sharing, payment, performance tuning, version updates, and operational monitoring.
This article walks through a practical transformation of an old payment architecture into a high‑availability microservice ecosystem, covering SOA vs. microservices, DDD‑guided domain boundaries, Dubbo‑based implementation, operational challenges, continuous integration testing, and future plans for multi‑active data centers.
This article details the design of a modular Java payment system that handles payment initiation, refunds, and callback processing by leveraging asynchronous execution with ExecutorService, RabbitMQ, Redis caching, MongoDB for persistence, and MySQL for configuration data, all illustrated with architecture diagrams and code examples.
This article explains the concepts, structures, and accounting rules of third‑party payment account systems, covering user, merchant, and bank relationships, various account types, debit‑credit recording methods, and detailed fund flow scenarios for different transaction operations.
The event showcases three technical talks covering the evolution of Hujiang's storage architecture, the transformation of the Dianrong payment system into a public service, and an introduction to the TiSpark project that integrates TiDB with Spark, highlighting design choices, trade‑offs, and future directions.
This article provides a comprehensive overview of payment system architecture, covering product classifications, module capabilities, typical business flows, reference designs, and real‑world examples from major platforms, while outlining supporting, core, and product layers essential for building robust backend payment services.
This article explains how modern internet companies design payment systems, covering product classifications, module capabilities, typical business processes, and reference architectures to help developers and product teams build secure, scalable payment solutions.
This article outlines the evolution of payment systems, describes a three‑stage architecture model, details the end‑to‑end payment workflow, presents typical industry designs, and provides practical guidance on system, JVM, service, database, call‑chain, and business monitoring using tools like Zabbix, Flume, Kafka and Spark.
This article presents Hong Guangming's detailed overview of Ctrip's payment engine reconstruction, covering the legacy system's challenges, the new split‑service architecture, channel‑specific services, settlement reconciliation, and the multi‑layered strategies employed to achieve high availability and operational stability.
This presentation details Ctrip's payment engine reconstruction, describing the limitations of the legacy system, the new service‑oriented architecture separating payment planning and execution, channel‑specific services, the reconciliation system, and the operational measures taken to achieve high payment availability.
The article describes the high‑availability, high‑concurrency backend architecture of Weibo's paid reading and tipping platform, covering layered design, database sharding, asynchronous processing, monitoring, idempotency, distributed transaction handling, and security measures for a large‑scale internet‑finance system.
This article chronicles Meituan's payment channel gateway evolution—detailing early usable stages, subsequent availability improvements, and the implementation of a flexible, fault‑tolerant architecture that achieved 99.99% API uptime and record‑high transaction throughput.
This article explains how LeTV's payment platform handled a hundred‑fold surge in traffic by redesigning its architecture with database sharding, a custom order‑ID scheme, asynchronous consistency, high‑availability clustering, data tiering, and a coarse‑fine request pipeline to sustain up to 100,000 orders per second.
