Idempotent requests¶
Stripe. (2026). Idempotent requests. Stripe API Reference.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Request-Response
- Because a network failure can hide whether a charge request reached Stripe's servers, Stripe supports idempotency keys: the client generates a unique key (typically a UUID) and sends it in the
Idempotency-Keyheader with aPOST.This sourceStripe's own API contract for idempotency - a client-generated unique key, V4 UUIDs suggested, sent in the Idempotency-Key header, accepted on all POST requests. Stripe's own documentation of the retention window, which states that keys may be pruned once they are at least 24 hours old - a floor on retention rather than an exact expiry.
SupportedVerified against the source
- Because a network failure can hide whether a charge request reached Stripe's servers, Stripe supports idempotency keys: the client generates a unique key (typically a UUID) and sends it in the
Mechanisms¶
- Abort-and-Retry After State Mismatch
- The sharpest misuse is retrying a non-idempotent side effect without a dedupe key
This sourceRequires an idempotency key for safely retrying a request after a connection error without performing the same operation twice.
- The sharpest misuse is retrying a non-idempotent side effect without a dedupe key
- Duplicate-Safe Payment Operation
- Reusing one idempotency key across retries of a charge is the standard way payment systems make an uncertain retry safe, and separating authorization from capture gives the workflow a window to catch a duplicate before the money is truly gone.
This sourceDocuments reuse of an idempotency key so a retried request cannot create the same operation twice.
- Reusing one idempotency key across retries of a charge is the standard way payment systems make an uncertain retry safe, and separating authorization from capture gives the workflow a window to catch a duplicate before the money is truly gone.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 3 citations: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:eb1880aa2934 · see in the full table