How to Send Stripe Dispute Alerts to Slack

A Stripe dispute is the one payment event where inaction alone costs you money. The moment a customer disputes a charge, a hard countdown starts — typically 7 to 21 days — and if you miss it, you automatically lose the funds without anyone even reviewing your case. Sending Stripe dispute alerts to Slack in real time is how you make sure a human sees that clock the moment it starts, not when you next happen to open the Stripe Dashboard.

What actually happens when a charge is disputed

When a cardholder disputes a payment with their bank, Stripe fires the charge.dispute.created webhook event and notifies you across the Dashboard, email, webhooks, and the API. Stripe immediately pulls the disputed amount out of your available balance and holds it pending the outcome. You don't get to opt out of that hold — the money is gone from your balance until the dispute resolves.

In the US, Stripe also charges a non-refundable $15 dispute fee the instant the dispute is filed — regardless of the amount, and regardless of whether the dispute is legitimate. Since June 17, 2025, there is a second fee too: a $15 dispute countered fee that applies only if you choose to submit evidence and fight the chargeback. That one is refunded if you win. So contesting a single US dispute puts up to $30 in fees at stake on top of the disputed amount itself.

The Dispute object carries the field that matters most: evidence_details.due_by, a Unix timestamp for your response deadline. That deadline is the whole reason speed matters — everything after this section is about getting a human to it in time.

The deadline is real, and you only get one shot

The evidence-submission window is typically 7 to 21 days after the dispute is initiated, depending on the card network. Miss it and you lose automatically — Stripe won't even review evidence submitted late. There is no appeal for a missed deadline; the funds are simply not recoverable.

It gets stricter: you get one submission. Once you submit evidence you cannot amend it, add files, or send more information — the case is final. That's why preparation before the deadline matters as much as the deadline itself. Rushing a half-assembled response the hour before it's due is often worse than a calm response sent on day three.

• One evidence submission, no edits — assemble everything before you click submit.
• Max 4.5 MB combined file size, and Mastercard caps evidence at 19 combined pages.
• One file per evidence type — combine multi-file evidence into a single multi-page PDF.
• No audio, no video, no external or download links — Stripe won't accept them.
• 150,000 characters total across all text evidence fields submitted via the API.

After you submit, the dispute status flips to under_review, and the issuing bank takes roughly 60 to 75 days to decide. The full lifecycle from initiation to final outcome is usually 2 to 3 months — but your part of it, the part you control, is that first short window. The alert exists to protect that window.

The odds are why speed matters

Merchant win rates on disputes are low — around 30% on average for most merchants, rising into the mid-40s in some industries and transaction sizes. Roughly 73.6% of disputes turn into full chargebacks, and US chargeback volume is projected to reach about 146 million cases worth $15.3 billion by 2026. A fast, well-prepared response won't win every dispute, but a slow or missed one loses every time.

There's a quieter reason speed matters that most guides skip. When customers reach out to the merchant before their bank, merchants resolve about 44% of cases just by answering a question and another 31% by issuing a refund — only about 25% still escalate. Being the first to see a dispute (or the frustration that precedes one) in Slack means a quick human reply can preempt the chargeback entirely. That's the same logic behind treating refunds as a signal worth watching, not just a number.

How to send Stripe dispute alerts to Slack with ChargeBell

ChargeBell connects Stripe to Slack and sends plain-English alerts for the events that matter, disputes included. There's nothing to build — no webhook handler, no message template, no deadline math. You connect two things and pick what you want to hear about.

1. 1

   Connect Stripe

   One-click, read-only OAuth. ChargeBell can see dispute events to alert you, but it can never move money or touch a dispute in Stripe. Stripe stays the source of truth.

2. 2

   Connect Slack

   Add the app and pick a channel. ChargeBell only posts to channels you choose — send disputes to #founders or #billing where the right people will see them.

3. 3

   Keep the Charge disputed alert on

   The dispute_created alert is on by default. You can route it to its own channel so a chargeback never gets buried under routine payment pings.

4. 4

   Send a test alert

   Confirm the setup works before a real dispute lands. You'll get your first alert before your coffee cools — no code, no settings to learn.

In ChargeBell the Charge disputed alert is flagged critical. That's not cosmetic: a critical alert prefixes the Slack message with @channel and bypasses quiet hours, so a dispute reaches your team at 2 a.m. even when every routine alert is politely held until morning. The alert itself carries the Respond by date pulled straight from Stripe, so the deadline is on the message the moment it lands — no one has to open Stripe to find out how long they've got.

What a dispute alert looks like in Slack

The point of the message is that you can act on it without opening Stripe first. It leads with the amount, the reason, and the deadline — the three things that decide whether you fight and how fast you have to move.

How to respond to a dispute in Stripe

The alert gets you to Stripe in time; Stripe is where you actually respond. ChargeBell is read-only and never touches the dispute — you'll always counter inside your own Stripe Dashboard. Here's the flow.

1. 1

   Open the Dispute details page

   From the alert, click through to the disputed charge in Stripe and open its Dispute details page.

2. 2

   Decide whether to counter

   Weigh the disputed amount against the fees and your odds. If it's a low-value charge and a weak case, accepting may cost you less than the $15 countered fee. If you're fighting, click Counter dispute.

3. 3

   Explain the error and set the product type

   Tell Stripe why the dispute is incorrect and specify the product type (physical, digital, service, etc.) so the right evidence fields appear.

4. 4

   Assemble your evidence

   Stripe auto-populates what it can — shipping details, refund policy, customer info, product background. Add proof of delivery, receipts, and communication logs. Combine multi-file evidence into one PDF and stay under 4.5 MB.

5. 5

   Check the box and submit

   Confirm the acknowledgment box and submit. Remember: one submission, no edits. The status flips to under_review, and Stripe notifies you of the outcome by email and the charge.dispute.closed event.

ChargeBell vs building the alert yourself

You can absolutely wire up dispute alerts without ChargeBell. Stripe's own Workflows for Slack app and Zapier both handle New Dispute → Slack and are worth knowing. The honest counterpoint: if you only want a single plain dispute ping and already run one of those, it's enough. The difference is in the dispute-specific defaults — critical severity, quiet-hours bypass, @channel, and a plain-English message with the amount, reason, and Respond-by date up front — that you'd otherwise assemble and maintain by hand.

If disputes are one small part of a wider automation need, a general tool may fit — see the fuller breakdown in ChargeBell vs Zapier. If you want a whole system for reacting to payment problems in Slack, disputes included, read how to build a payment incident workflow in Slack. And if you're still deciding which events warrant an alert at all, what Stripe events should a founder monitor is the place to start.