Delayed Webhook

Definition

A Delayed Webhook is an event notification that reaches the receiver later than the delivery time expected by the sender or the business workflow.

Overview

Contents Hide

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

Context and purpose

It is not the same as a failed webhook because the event may eventually arrive successfully, and it is not proof that the underlying payment action was delayed. The main risks include premature fulfillment decisions, stale customer status, duplicate recovery work, out-of-order processing, and false incident escalation. Delay can occur before dispatch, in a retry queue, across the network, or inside the receiving system. In production, teams should define ownership and apply event timestamps, delivery-attempt timestamps, queue-age monitoring, idempotent consumers, status-query fallback, and service-level thresholds. A Delayed Webhook handler should acknowledge only after durable receipt when the provider’s retry contract depends on the response. Useful measures include end-to-end webhook latency, queue age, delayed-event rate, p95 delivery time, and status-query fallback volume. Delayed Webhook is closely connected to Failed Webhook, Webhook Event Log , and Out-of-Order Payment Event .

How it works

A delayed webhook is a legitimate event notification arriving later than its underlying state change or later than another event. Networks, retries, outages and queue backlogs can change delivery order.

Practical checks and failure points

Reconcile using authoritative event versions or fresh resource queries; track delivery lag and persist message IDs.

Duplicate Callback · Refund Callback

Example

A refund completes at noon, but the completion event reaches the merchant at 12:20 after a newer status event. The consumer must not blindly roll the refund state backward.

Comparison

Delay concerns timing of delivery; duplication concerns repeated delivery of the same event.

Key Takeaway