charge.dispute.created webhook never received: how to fix
Diagnoses missing Stripe charge.dispute.created webhooks: verifying event subscriptions, inspecting failed delivery attempts in the dashboard, and replaying events after the handler is fixed. Use when disputes appear in the dashboard but your system never heard about them. Not for duplicate deliveries or out-of-order events.
TL;DR
When charge.dispute.created never arrives, the endpoint is usually not subscribed to the event or the handler crashes before logging. Check the subscribed event types in the dashboard, inspect failed delivery attempts, fix the handler, then replay the event.
charge.dispute.created webhook never received: how to fixUse this when
- Disputes show in the dashboard but your system never heard about them.
- Other webhook events arrive fine and only dispute events are missing.
- A new endpoint gets everything except disputes.
Not for this skill when
- The same dispute event arrives twice. That is a duplication problem.
- Events arrive but in the wrong order. That is an ordering problem.
Steps
- Open the webhook endpoint settings in the dashboard and confirm charge.dispute.created is in the subscribed event list. Verify: the event type appears exactly as spelled.
- Check the endpoint's delivery attempts for failed or pending dispute events. Verify: you see the attempts, their status codes, and timestamps.
- If attempts failed, read the response body your server returned and fix the handler crash or timeout. Verify: a manual test delivery now returns 200.
- Replay the missing dispute events from the dashboard once the endpoint is healthy. Verify: each replayed event logs in your system exactly once.
- Add a daily reconciliation job that lists recent disputes from the API and compares against your local records. Verify: the job would have caught this gap.
Variant phrasings
stripe dispute webhook not received
Common shorthand.
charge.dispute.created missing
Event-name-first search.
stripe dispute created event never fired
Symptom wording from logs.
Compatibility: Stripe webhooks. Event subscriptions are per endpoint; a new endpoint inherits nothing. Delivery attempts are visible in the dashboard for recent events.
Why it happens
Endpoints are often created for payment events and dispute types are added later, or never. The other path is a handler that 500s on the first dispute-shaped payload it ever sees, so Stripe marks the attempts failed and your logs show nothing because the crash happened before logging.
Edge cases / pitfalls
- Connect webhooks differ from account webhooks. Confirm which account the endpoint belongs to.
- A 301 redirect on your endpoint breaks delivery. Point the endpoint at the final URL.
- Replaying without the dedupe check creates double entries. Keep event-id dedupe on during replays.
- Test clocks do not create real disputes. Use the dashboard replay for verification, not test mode.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_UDdcYCM4iJdkrFLtTeu99w