Stripe webhook not working: how to diagnose it

Works with Stripe webhook events. When Stripe webhooks “stop working,” it is almost always one of a handful of causes. Stripe’s dashboard records each delivery attempt and the response your endpoint returned (Developers → Webhooks → your endpoint) — start there, then work down this list.

Checklist

1. Endpoint returns 500 — your handler threw. Read the response body Stripe recorded for the failed event. See webhook 500 errors.
2. Timeout — Stripe expects a fast 2xx; if the handler does too much inline, Stripe gives up and retries. Acknowledge first, process asynchronously.
3. Signature failure 400 — the payload failed verification, almost always the raw-body problem. See Stripe signature verification.
4. Wrong events — the event type you expect is not enabled on the endpoint. Check the “Events to send” list in the Stripe dashboard.
5. Disabled endpoint / wrong URL — Stripe disables endpoints after repeated failures. Confirm the URL and that the endpoint is still enabled.

Confirm it in HookWatch

Point the Stripe endpoint URL at your HookWatch endpoint and each delivery — payment_intent.succeeded, invoice.payment_failed, checkout.session.completed — is captured with its request, response, and attempt history. You can see exactly which events failed and why, instead of guessing from a summary. Applied end to end on the Stripe webhooks page.