1 views collected around this technical thread.
This guide details how to integrate WeChat native payment into a Java backend, covering merchant setup, Spring configuration, QR‑code generation with the official SDK, handling HTTPS callbacks, and implementing front‑end polling using Redis and Bloom filters for reliable membership upgrades.
This article describes how a C++‑based cross‑platform framework and a unified routing mechanism were built for WeChat Pay to eliminate platform‑specific bugs, streamline data flow, improve crash stability, cut code size by nearly 45%, and boost development productivity across iOS and Android.
This article presents a comprehensive design and implementation guide for securing API interfaces by combining HTTPS fundamentals with WeChat Pay encryption techniques, detailing symmetric and asymmetric encryption, hashing, signature verification, key exchange, parameter handling, and backend processing to protect against tampering, replay attacks, and data leakage.
This article describes how WeChat Pay applied chaos engineering to improve system reliability, detailing the business scenario, challenges of controlling fault injection radius, practical solutions, risk assessment, automation, and the resulting business and tool achievements.
To improve the ultra‑high availability of WeChat Pay, the team introduced chaos engineering using multi‑partition isolation, controlled blast radius, automated fault injection, and systematic risk discovery, detailing the design, execution, automation, and results of this reliability‑focused initiative.
WeChat Pay’s team adopted Netflix‑style chaos engineering, building an automated, YAML‑driven fault‑injection platform that isolates experiments in multi‑zone partitions, enabling over 500 safe experiments in 2021‑2022, uncovering critical bugs across core services while maintaining five‑nine availability and zero production incidents.
This article explains how to develop a recharge feature for WeChat Mini Programs using PHP, covering the setup of payment parameters, generating prepay orders, invoking wx.requestPayment, and handling payment callbacks with example code.
This article explains how WeChat Pay solved the fragmented iOS/Android implementations by building a C++‑based cross‑platform framework, introducing UseCase‑driven flow abstraction, a unified routing mechanism, disciplined network request handling, and standardized data passing, resulting in up to 45% code reduction and faster feature delivery.
The article describes how a C++‑based cross‑platform framework was built to unify iOS and Android implementations of WeChat Pay, addressing bugs, scalability, quality assurance, routing, network request management, and data‑flow discipline, ultimately improving development efficiency and user experience.
This article explains the typical order‑payment flow, identifies external and internal causes of lost orders, and provides concrete backend strategies—such as adding a "payment‑in‑progress" state, timeout‑based query retries, idempotent handling, and Redis‑based duplicate‑submission protection—to ensure reliable order processing and avoid duplicate payments.
This article explains the typical order‑payment flow, identifies causes of order loss and duplicate submissions, and provides practical backend strategies such as intermediate payment states, timeout queries, idempotent handling, Redis‑based duplicate checks, and WeChat Pay best practices to ensure reliable order processing.
This article details how a C++‑based cross‑platform framework was designed for WeChat Pay to unify iOS and Android implementations, improve scalability, quality assurance, and developer productivity through use‑case abstraction, a routing mechanism, and refined network and data handling.
This guide explains how to set up a Flask backend on Windows or CentOS, generate the required signatures for WeChat's unified order API, obtain a prepay_id, and call the mini‑program wx.requestPayment interface with the correct parameters for successful payment processing.
WeChat Pay’s team adopted lean, value‑driven development—using TAPD‑enabled value‑stream and agile kanban, small‑batch work, automation, and transparent metrics—to reconcile rapid growth with high‑quality delivery, build consensus across multiple teams, and continuously improve through retrospectives, visual OKR dashboards, and risk‑aware demand decomposition.
The article describes how a C++‑based cross‑platform framework, combined with UseCase abstraction, routing mechanisms, unified network request handling, and strict data‑transfer rules, solved iOS/Android inconsistencies in WeChat Pay, cut code size by 45%, kept crash rates stable, and dramatically improved development efficiency.
This talk explains how WeChat Pay leverages graph algorithms, graph databases, and graph neural networks to combat fraud at massive scale, covering new risk‑control perspectives, the three‑pillar graph computing platform, practical applications, and the team’s innovations in algorithm design and deployment.
This talk presents how WeChat Pay leverages graph computing, including graph databases, engines, and algorithms such as GNN and PageRank, to combat fraud and money‑laundering by shifting from individual feature engineering to network‑level analysis, highlighting platform choices, practical experiences, and technology‑for‑good outcomes.
The article describes how a C++‑based cross‑platform framework and a unified routing mechanism were introduced to solve iOS and Android inconsistencies in WeChat Pay, resulting in fewer bugs, 45% less code, faster feature delivery, and a more reliable data‑flow architecture.
This article explains how to upgrade to WeChat Pay V3 in PHP, covering composer installation, configuration file setup, a table of payment methods, example usage for mini‑program payments, and a full reusable Wechat class with signing, verification, and refund functions.
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.