Latest / The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org

How Stripe Rebuilt Its API for Idempotency at Scale
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…
The skinny
The skinny isn't ready yet — notes appear once the transcript is processed.