Payment System: Survival Guide
summary
A payment platform on Google Cloud built from many microservices with a central orchestrator is presented, including the full transactional flow. The talk analyzes stress failures during Ukrposhta stamp sales (160 TPS real transactions and a 1612 RPS spike from status polling), identifies root causes—missing rate limits, cache and routing misconfiguration, and an overloaded anti-fraud service that was temporarily disabled—and describes the fixes and rebuilds that allowed subsequent sales to succeed.
AI-written summary · about
chapters (11)
- 0:00Payment systems intro
- 4:01Universal payment systems
- 13:58Bank failure processing
- 23:11Payment problems costs
- 23:34Ukrposhta stamp sales case
- 26:27First stamp sale issues
- 32:04Routing errors antifraud
- 36:43Second stamp sale challenges
- 41:47Bank issues Cloudflare
- 44:22Summary
- 46:48Closing Q&A
related talks
24mBuilding Planet-Scale Payment Platforms
39mBuilding a distributed payment system to handle scale
45mE-commerce platform. Core build principles, problems and guidelines.
48mPayments: The Next Frontier
33mOptimizing Bank Operations: Design Patterns, NFR, and GenAI Fusion
33mThe Road to Enable DevOps Within the Payment Industry
22mBlack Friday Brilliance: Managing a Billion Transactions with Tech, and Teamwork
28mRunning MCP Server in Production: Lessons from Razorpay