---
title: "Case: Stripe's idempotency keys"
description: "How Stripe's idempotency keys let a client retry after a lost reply without a second charge: what broke, the decision, and what changed after."
canonical_url: "https://fanout.sh/system/archive/case-stripe-idempotency-keys"
md_url: "https://fanout.sh/system/archive/case-stripe-idempotency-keys.md"
last_updated: "2026-11-11"
access: "pro-preview"
---

# Case: Stripe's idempotency keys

How Stripe's idempotency keys let a client retry after a lost reply without a second charge: what broke, the decision, and what changed after.

- Access: Fanout Pro (public preview)

## The core idea

An idempotency key tells a server which intended operation a request belongs to.

That matters when the server completes work but its reply never reaches the caller: another attempt should recover the result without creating another operation.

## In this lesson

- What they had
- What broke, or would not scale
- The numbers they published
- The decision
- What changed after
- Fundamentals used

## Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.

---
This representation contains public Fanout content only. Protected Pro lessons, account data, billing, checkout, and pricing are not included.

Browse the public content map: https://fanout.sh/sitemap.md
