Stripe webhook event
charge.dispute.created
A customer disputed a charge (a chargeback).
Quick answer
The cardholder's bank opens a dispute.
| Event type | charge.dispute.created |
|---|---|
| Category | Charges & disputes |
| When it fires | The cardholder's bank opens a dispute. |
| Recovery-relevant? | Yes, used in failed-payment recovery |
When it fires
The cardholder's bank opens a dispute.
What to do with it
Submit evidence promptly and consider pausing access; disputes are costly and time-sensitive.
This is a payment-recovery event
charge.dispute.created is part of the failed-payment lifecycle. Handling it well, with retries, branded emails, a card update page, and stop-on-success, is what recovers the ~9% of MRR most SaaS lose to failed payments. See how to recover failed Stripe payments or skip the build with SubRevival.
Stop building webhook handlers
SubRevival consumes the failed-payment events for you and runs the full recovery stack, no endpoint to build, secure, or maintain. 5-minute Stripe OAuth, $19/mo flat.
Start Recovering RevenueFAQ
What does the Stripe charge.dispute.created webhook event mean?
A customer disputed a charge (a chargeback).
When does charge.dispute.created fire?
The cardholder's bank opens a dispute.
What should I do when I receive a charge.dispute.created event?
Submit evidence promptly and consider pausing access; disputes are costly and time-sensitive.
Related events
Source: official Stripe events documentation.