---
title: "Discussion on \"Idempotency Keys: The Small Design Choice That Saves Incident Reviews\" | Hashnode"
description: "Discussion on \"Idempotency Keys: The Small Design Choice That Saves Incident Reviews\". A payment endpoint retried once at the wrong moment can cost more than the outage that caused the retry.\nWe learned that the hard way last year, and the fix was not a new service. It was one header an"
url: "https://hashnode.com/posts/idempotency-keys-the-small-design-choice-that-saves-incident-reviews/6ae184c8e954bbcefe8e7bc1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Idempotency Keys: The Small Design Choice That Saves Incident Reviews](https://distributed-notes.hashnode.dev/idempotency-keys-the-small-design-choice-that-saves-incident-reviews?utm_source=hashnode&utm_medium=feed)

A payment endpoint retried once at the wrong moment can cost more than the outage that caused the retry. We learned that the hard way last year, and the fix was not a new service. It was one header an

Oct 28 · 2 min read · distributed-notes.hashnode.dev  
Read the article

-   [#backend](https://hashnode.com/tag/backend)
-   [#distributed-systems](https://hashnode.com/tag/distributed-systems)
-   [#api](https://hashnode.com/tag/api)

## Written by

[Tobias Lang](https://hashnode.com/@tobiaslang)

@tobiaslang · Vienna, Austria

  
[View profile](https://hashnode.com/@tobiaslang)

Writing about distributed systems, databases and the trade-offs behind production incidents.

Backend engineer in Vienna working on services that have to stay correct when the network lies. I write about distributed systems, database trade-offs, and the incident reviews that taught me the most. Most of my notes start from a production bug and end with a smaller architecture.

## Responses 2

Markdown supported · ⌘↵ to post

[Noah Bennett](https://hashnode.com/@hhnh4g7udvs)

[Oct 28](https://hashnode.com/posts/idempotency-keys-the-small-design-choice-that-saves-incident-reviews/6ae184c8e954bbcefe8e7bc1/comment/6ae185e4ed3f693a112be294)

Hashing the body is the step people forget, and it hides the bug you want to see.

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 28](https://hashnode.com/posts/idempotency-keys-the-small-design-choice-that-saves-incident-reviews/6ae184c8e954bbcefe8e7bc1/comment/6ae1c22ff32e7834fff9013e)

The subway retry example makes the expiry choice concrete. What response do you return when the same key arrives with a different request body?
