The CTO Podcast with Fexingo · 2026-07-22 · 6 min
Stripe processes hundreds of billions in payments annually. Every one of those API calls must be idempotent - meaning retries don't double-charge. In this episode, Lucas and Luna unpack how Stripe rebuilt its core API to guarantee exactly-once semantics without sacrificing latency. They walk through the architectural choices: idempotency keys, optimistic locking, and a custom transaction log that handles 50,000 requests per second. They also discuss the hard trade-offs - like when to fail fast versus queue for retry, and how Stripe's engineering culture shaped the solution. If you've ever wondered why your payment API is safe to retry, this episode explains the system design behind it. #Stripe #API #Idempotency #PaymentProcessing #SystemDesign #DistributedSystems #EngineeringCulture #Backend #Reliability #TechLeadership #Business #Technology #FexingoBusiness #BusinessPodcast #CTOPodcast #Architecture #Scale #ExactlyOnce Keep every episode free: buymeacoffee.com/fexingo
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
Trust, stablecoins, and the AI margin squeeze:What McKinsey and QED's fintech report means for banksTearsheet Podcast: Exploring Financial Services Together · on Stripe89 / 100
Fintech Recap: ALT5 Sigma, Increase & Fed Master AccountsFintech Business Podcast · on Stripe86 / 100
The API of the Physical World: Sy Bohy on the Future of Connected HardwareHow I Grew This: Real Stories of Digital Growth · on Stripe81 / 100
Why the Best Fintech Companies Are Staying Private With Sahej Suri, Founder of Blue Dot InvestorsFintech One-On-One · on Stripe81 / 100
#40: FX & Global Payments Insights with Marc Racette CEO of PulseFXFintrepreneur · on Stripe78 / 100
MicroConf Tactics: Start a SaaS From $0 in 2026MicroConf On Air · on Stripe77 / 100
How Datadog Scaled Engineering Without Burning Out82 / 100How Slack Scaled Engineering Without Adding HeadcountHow Atlassian Tamed Technical Debt With Architecture ContractsHow Atlassian Tamed Technical Debt With Architecture ContractsHow GitHub Tamed Merge Conflict Chaos