What is an idempotency key in payments?

An idempotency key is a unique value a client attaches to a payment request so that, if the same request is sent more than once, the server processes it only a single time. Networks are unreliable: a request can time out after the payment actually succeeded, and a naive retry would charge the customer twice. With an idempotency key, the server recognizes the repeat, returns the original result, and does not move money again. It turns a risky 'did that go through?' retry into a safe one. This is foundational to reliable payments engineering — any system that initiates transfers should make creation idempotent. While idempotency keys live mostly in the engineering layer, the outcome users feel is simple: no accidental double payments, even when the connection drops at the worst moment.

Why retries are dangerous without it

If a payment request succeeds but the response is lost, the client doesn't know the outcome. Retrying without protection can duplicate the charge. The idempotency key lets the server say 'I already did this one' and return the same result instead of executing again.

How it's used in practice

The client generates a key (often a UUID) per logical operation and sends it with the request. The server stores the key with the result; subsequent requests with the same key short-circuit to that stored result. The key should be unique per intended action, not reused across different payments.