Duplicate Request
Pronunciation: DOO-plih-kit rih-KWEST
Definition
A duplicate request is a repeated command or message that represents a previously submitted business action, regardless of whether it arrived through an API, queue, file, user interface, or webhook. Duplicate request is the general concept. Duplicate API request is the HTTP or API-specific form, and a duplicate financial object describes the resulting business effect rather than the repeated input.
Overview
Meaning and scope
A duplicate request is a repeated command or message that represents a previously submitted business action, regardless of whether it arrived through an API, queue, file, user interface, or webhook. Duplicate request is the general concept. Duplicate API request is the HTTP or API-specific form, and a duplicate financial object describes the resulting business effect rather than the repeated input.
Mechanism and operation
A duplicate request is a repeated command that represents an already submitted business action, regardless of whether the underlying transport generated a fresh message identifier. Retries can happen when a client times out after the server processed a payout or invoice creation. HTTP request IDs alone may not show that two requests have the same commercial intent. Systems therefore use stable idempotency keys, order IDs or operation records and compare important parameters before deciding whether to return an earlier result or reject a conflicting retry. Shared persistence and atomic state transitions prevent two workers from executing the same financial side effect concurrently.
Practical payment example
A mobile client repeats an invoice request after a timeout, and the server recognizes it as the original business action.
Operational checks
Store original operation identity, parameters, creation time, status and committed result; test timeouts, concurrency, retention expiry and conflicting payload reuse. It either returns the prior outcome, ignores the repeated delivery, or raises a conflict when the same identity is reused with different instructions. The receiving component compares a stable request identity, payload, business reference, and processing history. The system also needs durable storage so restarts and failover do not erase the evidence used to recognize an earlier request. These records support API Security and let an operator reproduce the result from authoritative evidence rather than relying on a dashboard snapshot or a provider’s latest status alone.
Distinctions and limits
A duplicated request may lead to one or many external effects depending on protection; it is distinct from receiving the same event twice.
Related reading
Related definitions: Payment Retry, Duplicate Payment.
Example
A mobile client repeats an invoice request after a timeout, and the server recognizes it as the original business action.
Comparison
It either returns the prior outcome, ignores the repeated delivery, or raises a conflict when the same identity is reused with different instructions. The system also needs durable storage so restarts and failover do not erase the evidence used to recognize an earlier request.
Key Takeaway
Duplicate Request is useful only when its scope, evidence, state transitions, financial effect, and exception handling are defined precisely; otherwise similar events can be mistaken for the same payment outcome.
Sources
- The Idempotency-Key HTTP Header Field — Internet Engineering Task Force (2026-08-03)
- HTTP Semantics, RFC 9110 — RFC Editor (2026-08-03)
- Monitoring distributed systems — Google SRE (2026-08-03)