0 views collected around this technical thread.
The article details NetEase Games' challenges in payment‑environment risk control and explains how they transformed a T+1 batch workflow into a fully real‑time risk‑control system with Apache Flink, describing the platform architecture, data modeling, session windows, joins, and future development plans.
The article explains why popular mobile payment platforms like WeChat and Alipay use six‑digit numeric passwords, discussing brute‑force attack complexity, the rapid growth of computing power, human short‑term memory limits, and additional authentication layers that together make six‑digit passwords a practical balance of security and usability.
The article explains the functional and non‑functional requirements, common pitfalls, and detailed architecture—including real‑time, near‑real‑time, and batch engines, rule and penalty centers, and CEP technology—of a payment risk control system aimed at detecting and mitigating fraud while maintaining performance and flexibility.