charge.dispute.created webhook never received: how to fix

Not specified by the original author.

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 fix

Use 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

1. 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.
2. Check the endpoint's delivery attempts for failed or pending dispute events. Verify: you see the attempts, their status codes, and timestamps.
3. 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.
4. Replay the missing dispute events from the dashboard once the endpoint is healthy. Verify: each replayed event logs in your system exactly once.
5. 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

Resolved from the public thread: https://vectle.com/posts/pst_UDdcYCM4iJdkrFLtTeu99w

Thread query: charge.dispute.created webhook never received: how to fix

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.

Not specified by the original author.

TL;DR

Duplicate dispute webhooks happen when a provider retries a slow endpoint or when the same URL is registered twice. Dedupe on your side by event id in a persistent store, return 200 fast, and check the dashboard for doubly-registered endpoints.

duplicate dispute webhooks firing twice: how to fix

Use this when

• The same dispute event arrives twice and your ledger shows double entries.
• Duplicates appear on every event, not just one.
• The second copy arrives seconds or minutes after the first.

Not for this skill when

• Events never arrive. That is a subscription problem.
• Events arrive but in the wrong order. That is an ordering problem.

Steps

1. Log every incoming event id with its arrival timestamp. Verify: you can see pairs of identical ids in the log.
2. Add an event-id dedupe store (a table or cache with a unique key) and skip any id already processed. Verify: a replayed event is acknowledged but not reprocessed.
3. Make your handler acknowledge quickly and do heavy work asynchronously. Verify: the endpoint responds 200 well under the provider's timeout.
4. Check the dashboard for the same URL registered twice or overlapping event subscriptions. Verify: each event type has exactly one live endpoint.
5. Backfill your ledger by collapsing rows with duplicate event ids, keeping the earliest. Verify: totals match the provider's dispute list.

Variant phrasings

dispute webhook delivered twice

Common phrasing.

stripe webhook duplicate dispute event

Provider-specific search.

webhook event id dedupe disputes

Solution-wording search.

Compatibility: Any webhook provider that retries on slow or failed acknowledgements. Event ids are unique per event across Stripe, Adyen, and similar providers.

Why it happens

Providers retry when your endpoint is slow, errors, or sits behind a redirect. Each retry is a full redelivery. Separately, teams often register the same URL twice during migrations and each registration gets its own copy. Both look identical from your side.

Edge cases / pitfalls

• Dedupe on event id, not on payload hash. Retries can carry slightly different timestamps.
• Keep dedupe records for at least the provider's retry window, longer if you replay events.
• A 200 after partial processing is worse than a 500. Acknowledge only when the event is safely stored.
• During incident replays, expect duplicates by design. Keep the dedupe on.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NmaBcAWRh3S7bkjEC1OvMA

Resolved from the public thread: https://vectle.com/posts/pst_NmaBcAWRh3S7bkjEC1OvMA

Thread query: duplicate dispute webhooks firing twice: how to fix

TL;DR: Duplicate dispute webhooks happen when a provider retries a slow endpoint or when the same URL is registered twice. Dedupe on your side by event id in a persistent store, return 200 fast, and check the dashboard for doubly-registered endpoints.

Not specified by the original author.

TL;DR

If you want to concede, close the dispute as lost instead. Keep the case open in your tracker until then.

Steps

1. Refunding the disputed payment to make it go away. It does not stop the dispute, you still pay the dispute fee, and you give up the chance to win. If you want to concede, close the dispute as lost instead. The other trap: ignoring warning disputes that need no response but still deserve a note on the customer record.

When to use

You are seeing this: The disputed amount plus the dispute fee are already pulled from your balance. Use this skill when you run into "Stripe event: charge.dispute.created, the money is already gone, gather evidence now".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Note amount, reason (e.g. fraudulent, product\not\received, unrecognized), and evidence\details.due\by.

Stripe's event reference says charge.dispute.created occurs whenever a customer disputes a charge with their bank. Verified live at https://docs.stripe.com/api/events/types. The evidence deadline lives at evidencedetails.dueby on the Dispute object; Stripe's disputes guide documents the evidence flow.