Webhook reconciliation

Webhooks provide timely notification but are not a complete reconciliation mechanism. A receiver can be unavailable beyond the retry window, and your application can fail after acknowledging an event.

Recovery strategy

Run a scheduled process that:

1. lists payouts updated within an overlapping time window;
2. compares each payout's current state with your stored state;
3. retrieves unresolved payouts individually;
4. repairs missing or stale local records; and
5. joins terminal payouts to the funding account statement.

Use an overlap between runs so records near a time boundary are reconsidered. The process must be idempotent.

Identifier roles

• Event id de-duplicates a webhook delivery.
• payoutId identifies the Axiym payout across events and reads.
• clientReference joins the payout to your business record.
• accountId identifies the partner-owned funding account affected by the payment.
• Related resource IDs join account statement entries to payouts.

Do not use event arrival as the sole proof that a payout completed. Treat the current payout resource and posted account movements as the reconciliation evidence.

See Reconcile payouts for the full business and ledger workflow.