Verify first
Validate the event signature and expected timestamp data with the secret assigned to the endpoint before processing the payload.
Expect retries
Delivery may be retried when a merchant endpoint is unavailable or does not acknowledge successfully. Store processed event IDs or use another idempotency strategy so repeated delivery does not duplicate side effects.
Respond quickly
Acknowledge a valid event promptly. Move slower fulfillment, email, ERP, inventory, or analytics work into your own durable processing path when practical.
Do not broaden merchant scope
A webhook consumer should act only on the merchant scope represented by its authenticated endpoint configuration and event.