Webhook notifications can arrive more than once or out of order. A system that assumes a single, perfectly timed delivery can make duplicate changes.

The decision to make

Use the provider's documented verification method and store a stable event identifier. Separate receipt from successful processing.

Practical checklist

  • Validate the event before changing records.
  • Track processing status and retries.
  • Reconcile important state with the source system.

An illustrative example

A subscription event repeated after a timeout should not grant an extra entitlement or create a duplicate invoice entry.

Your next step

Design the consumer around repeatable processing and inspect failed events instead of treating receipt as completion.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.