Duplicate Payout

Definition

A duplicate payout occurs when the same intended payout obligation is executed or recorded more than once, creating multiple transfers or credits for one business instruction.

Overview

Contents Hide

Context and purpose
How it works
Practical checks and failure points
Related concepts

Context and purpose

This differs from a duplicate API request because several technical requests can safely resolve to one payout, while one request can also create duplicate payouts if downstream processing is not idempotent. Detection compares payout IDs, beneficiary, amount, asset or currency, business reference, time, and provider transaction identifiers. A reliable payout workflow uses immutable business identifiers, idempotent creation, state transitions, approval controls, and reconciliation against provider and ledger records. When two transfers exist, remediation must preserve both records and document any recovery or offset. These records support Payout Reconciliation 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 Payout should remain distinct from Payout, Payout Reconciliation , and Duplicate Payment , because each can represent a different stage, record, control, or financial outcome.

How it works

A duplicate payout occurs when the same intended obligation is discharged more than once. It can result from repeated jobs, racing workers, weak idempotency or manual recovery.

Practical checks and failure points

Enforce one durable obligation ID, atomic claim of work and approval controls; reconcile outgoing chain transactions to authorized payout records.

Accounting Integration · End-of-Day Settlement

Example

Payroll item W-8 is paid twice after a processing worker crashes between broadcast and saving success. Both on-chain transactions can be valid even though only one was authorized.

Comparison

Two different payout IDs do not necessarily represent two legitimate obligations.

Key Takeaway