The charge.dispute.created event fires when a cardholder charges back a payment — and the clock to respond starts immediately. Here's how ChargeBell turns it into a CRITICAL Slack alert so nobody finds out too late.
A Stripe dispute alert in Slack is a message posted the instant a cardholder charges back a payment. ChargeBell listens for Stripe's charge.dispute.created event and posts a plain-English, CRITICAL alert — with the amount, the reason, and the customer — so nobody discovers the chargeback days after the deadline to respond has already passed.
charge.dispute.created fires when a cardholder formally disputes a payment — either by filing a chargeback directly with their bank, or when an earlier inquiry escalates into a formal dispute. It's an asynchronous event that lands outside your normal payment flow, so unless something surfaces it, it's easy to miss entirely. For a real chargeback it usually arrives with a needs_response status: the ball is in your court.
The moment the dispute is created, Stripe withdraws the disputed amount plus the dispute fee from your balance — before anyone has reviewed anything. The money is already gone. That, combined with a hard deadline, is what makes this the single most time-sensitive event in Stripe.
Every dispute carries a deadline set by the card network, exposed on the dispute object as evidence_details.due_by. Submit your evidence before that date and you get a chance to win. Miss it and the cardholder wins automatically — there is no appeal for a missed deadline. The response window is typically 7–21 days depending on the card network and region, but the only number that matters is the one Stripe gives you. ChargeBell's job is to make sure you know the dispute exists in time to open Stripe and act on it.
evidence_details.due_by and the dispute is lost with no way to reopen it.The clock starts the moment this event fires
Response windows vary by card network and region (often 7–21 days), so don't treat any single number as universal. Stripe's evidence_details.due_by is the source of truth for the exact deadline — ChargeBell's part is getting the alert to Slack fast enough that you have time to act.
A raw webhook payload helps no one under time pressure. A good dispute alert answers, at a glance: how much, why, and who — and makes unmistakably clear that this one is urgent. ChargeBell computes the plain-English version and flags it CRITICAL so the response window doesn't slip by unnoticed.
🚨 CRITICAL — New Stripe dispute opened
$249.00 disputed · reason: fraudulent · jordan@example.com
Respond in Stripe before the deadline or it's lost automatically
fraudulent, product_not_received)needs_response on a new chargeback)It's one alert, not a countdown
ChargeBell sends a single notification the moment the dispute opens so your team can act right away. It doesn't track the deadline or send reminders — responding to the dispute, and the exact due date, live in the Stripe Dashboard, where Stripe stays the source of truth.
The dispute_created alert is marked CRITICAL by default. Because the urgency is inherent to the event — a hard deadline and money already withdrawn — a CRITICAL alert bypasses quiet hours and can add an @channel prefix so it reaches the whole team even at 2am. A win landing while everyone's asleep can wait until morning; a dispute deadline can't. Route these to a channel like #disputes or #founders where the right people will see them.
Connect Stripe
One-click, read-only OAuth via Stripe Connect. ChargeBell can see dispute events and can never move money or touch the dispute itself.
Connect Slack and pick a channel
Add the app and choose where disputes should post — a dedicated #disputes channel keeps them visible.
Enable the dispute created alert
It's on by default and marked CRITICAL, so it bypasses quiet hours and can @channel. Leave the defaults on for maximum coverage.
Send a test alert
Confirm the message looks right and reaches the right people before a real dispute ever lands.
Want the full playbook? See how to send Stripe dispute alerts to Slack for the complete setup, and how to build a payment incident workflow in Slack to turn alerts into a repeatable response.
Key takeaways
charge.dispute.created fires the moment a cardholder charges back a payment, and the money is withdrawn immediately.evidence_details.due_by — miss it and the dispute is lost automatically.Connect Stripe and Slack, enable the dispute alert, and send a test. Free plan, no card needed.
charge.dispute.created. It's sent when a cardholder formally disputes a charge — either by filing a chargeback with their bank or when an earlier inquiry escalates. ChargeBell listens for it and posts a CRITICAL Slack alert.
In the Stripe Dashboard. Every dispute carries a network-set deadline on Stripe's evidence_details.due_by field — submit your evidence before it or the dispute is lost automatically. ChargeBell's role is to alert you the moment the dispute opens so you have time to open Stripe and respond.
No. ChargeBell sends one CRITICAL alert the moment the dispute opens. It does not track the deadline, send countdowns, or repeat reminders — you respond in the Stripe Dashboard, and Stripe stays the source of truth.
Yes. The dispute alert is CRITICAL, so it bypasses quiet hours and can add an @channel prefix. A dispute carries a hard deadline and the money is already withdrawn, so it can't wait until morning.
No. ChargeBell connects with official read-only OAuth. It can see dispute events to build alerts, but it can never move money, submit evidence, or change anything in your Stripe account — including the dispute itself.