Orchestrating payments for the millions
summary
Concrete numbers and fixes: payment stack runs for 30 million monthly active users and >$30M ARR, an account deletion triggers 3,208 Braintree token errors causing 1,420 failed purchases and ~12 hours outage costing $5–10K plus churn risk. Orchestration uses rule-driven routing, seven-line provider configs, and reactive client loading to cut component bundle size by 70%, add Alipay to lift ARR 3.5x, restore parity in ~30s (build pipeline is the 10‑min bottleneck), and ships as an OSS toolkit called Tenderlane.
AI-written summary · about
chapters (16)
- 0:00Introduction with rubber ducky
- 1:52Raffle for free conference ticket
- 2:33Payment failure incident story
- 5:01Struggles with payments overview
- 8:10Regulation and compliance challenges
- 11:21Reliability and uptime in payments
- 13:03What is payment orchestration
- 14:27Front-end architecture for orchestration
- 16:32Payments as code benefits
- 17:58Case study and financial impact
- 18:40Live demo of payment orchestration
- 20:24Edge cases and payment method nuances
- 22:52Anomaly detection and observability
- 23:54Quick recovery from payment failures
- 24:58Introducing Tenderlane library
- 27:10Raffle winner announcement
related talks
29mMoney Makes Your App Go Round
15mKeynote: The Operating System of Payments, UX and Security in Modern Apps
26mMastering API Platforms for Enhanced Payment Integration
48mPayments: The Next Frontier
51mThe Tie That Binds: Unique Cyber Tools in the Payments Industry
33mFrom 0 to €500 Billion and Beyond, How Adyen Builds for Growth
01h 01mChallenges in building neobank infrastructure
24mCollision 2015 - Taavet Hinrikus, Kathryn Petralia, John Maccllwaine, Katie Benner & Aunkur Arya