Building a C++ Cross‑Platform Framework for the WeChat Pay Client

Background – WeChat Pay suffered from fragmented iOS and Android implementations, leading to bugs, poor scalability, inconsistent user experience, and a weak quality‑assurance system.

Solution – A C++ cross‑platform framework was built, covering iOS 7.0.4 and Android 7.0.7, reducing the core payment code by about 45% and keeping crash rates stable.

What is software architecture? – Defined as the components of a system and their communication, essentially an MVC/MVVM‑style structure ( MVC, MVVM) for WeChat Pay.

Why architecture is needed – To manage complexity, enable responsibility separation, and improve productivity.

Step 1: Abstract business flow – Introduce UseCase to encapsulate business processes and UIPage for UI, replacing scattered controller logic.

Step 2: Add routing mechanism – A unified router parses a payment‑domain model and triggers actions (open UseCase, launch UI, WebView, mini‑program, etc.). The router data model includes a type and required parameters.

Step 3: Manage network requests – Refactor CGI handling from a singleton to independent command objects ( CGI) with lifecycles bound to UseCases, eliminating one‑to‑many communication bugs.

Step 4: Standardize data passing – Remove shared mutable models, use value‑type data, enforce one‑way injection, and apply the delegate pattern for necessary callbacks, preventing data pollution.

Results – The new architecture unifies flow and special‑case handling, cuts code for new features by up to 83%, improves traceability, and provides a solid foundation for future enhancements.

Conclusion – Good software architecture manages complexity; the presented C++ cross‑platform framework demonstrates how systematic architectural evolution can solve real business problems in mobile payment systems.