Duplicate Request

Overview

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. 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. In operational terms, this flow should remain connected to Payment Retry , because its upstream decision and downstream outcome must be interpreted together. 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.

Duplicate Request should remain distinct from Payment Retry and Duplicate Payment, because each can represent a different stage, record, control, or financial outcome.

The final control should feed Duplicate Payment , preserve the original evidence, and document any correction, override, or manual action. Important failure modes include duplicate or delayed events, wrong destinations or currencies, stale instructions, unavailable providers, unsupported retries, and customer-facing status that differs from authoritative records.

Deduplication scope, retention period, key ownership, payload comparison, and response behavior should be explicit. For merchants, developers, finance teams, and payment operators, a well-designed implementation means that retries and redeliveries remain safe while legitimate new instructions are still accepted and every business effect retains one stable identity.