Episode
How Stripe Rebuilt Payment Routing for 99.999% Uptime
- Published
- Jun 15, 2026
- Duration seconds
- 551
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/episodes/how-stripe-rebuilt-payment-routing-for-99-999-uptime/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/how-stripe-rebuilt-payment-routing-for-99-999-uptime.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Stripe's payment infrastructure processes billions of dollars annually, and their routing engine—the system that decides which bank or processor gets each transaction—is a marvel of distributed systems engineering. In this episode, Lucas and Luna explore how Stripe rebuilt its payment routing layer to achieve five-nines uptime, handling failures at the bank level in milliseconds without user impact. They break down the architecture: the state machine that tracks each transaction through six phases, the circuit-breaker pattern that isolates failing processors, and the decision-tree optimization that cut latency by 40 percent. Lucas explains why routing is the hardest problem in payments—more complex than fraud detection or compliance—and how Stripe's design influenced the broader fintech industry. Luna draws parallels to how other critical infrastructure systems, from DNS to CDNs, solve similar reliability problems. A concrete look at what it takes to move money reliably at internet scale. #Stripe #PaymentRouting #DistributedSystems #FiveNines #Fintech #Latency #CircuitBreaker #StateMachines #Reliability #Engineering #Architecture #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #CTOPodcast #TechnicalLeadership #ScalingPayments #SystemDesign Keep every episode free: buymeacoffee.com/fexingo