Payout Callback

Overview

A payout callback is an asynchronous server-to-server notification reporting a change in an outbound transfer’s processing or settlement status. Delivery success also does not prove that downstream accounting finished. The provider sends callback events for states such as accepted, processing, completed, failed, canceled, or rejected according to its lifecycle. A forged event can falsely mark a payout completed, while an old failure can regress a newer success. Receivers should authenticate callbacks, validate payout identity, amount, asset, network, and allowed state transition, then persist and deduplicate atomically. Status endpoints, transaction evidence, replay, and reconciliation should resolve missing or uncertain events. The merchant uses them to update withdrawal records, notify recipients, and support reconciliation. Callbacks may repeat, arrive late, or be delivered out of sequence. A Payout Callback handler should acknowledge only after durable receipt when the provider’s retry contract depends on the response. Recovery for Payout Callback should combine replay controls with an authoritative status check rather than trusting delivery history alone. Business actions triggered by Payout Callback should be idempotent and should verify the current object state before fulfillment or accounting updates.

Monitoring for Payout Callback should track delivery age, signature failures, duplicate rate, retry exhaustion, and unresolved business events.

Replay of Payout Callback should preserve original identifiers and timestamps so historical processing cannot masquerade as a new event.

For Payout Callback, the event identifier, signature result, delivery attempt, and resulting business state should remain connected throughout processing.

A receiver should treat transport acknowledgement and successful downstream processing as separate states for Payout Callback.