How to send Stripe dispute alerts to Slack and meet the evidence deadline

To send Stripe dispute alerts to Slack with ChargeBell, connect Stripe and Slack, turn on the dispute created alert, send it to a channel with an owner, and send a test alert. ChargeBell maps charge.dispute.created, shows the respond-by date when Stripe provides one, and marks the alert critical. It doesn't map charge.dispute.closed, so check the outcome in Stripe. The rest of this guide covers what to do once the alert arrives.

Set up Stripe dispute alerts in Slack

1. 1

   Connect Stripe and Slack

   Approve read-only Stripe access and connect your Slack workspace in ChargeBell.

2. 2

   Turn on and route disputes

   In Alerts, turn on dispute created and pick a channel with a named finance or risk owner. Turn on the critical mention if your team needs it.

3. 3

   Test and check

   Send a ChargeBell test alert and confirm the channel and owner. For a real dispute, open its Stripe link and work from the deadline shown there.

What happens when a charge is disputed

When a cardholder disputes a payment with their bank, Stripe sends charge.dispute.created and takes the disputed amount from your available balance. It holds the funds until the case closes. In a formal dispute, the bank has already credited the cardholder, so the money stays off your balance unless you win.

In the US, Stripe pricing lists a $15 dispute fee that you don't get back if you win. Countering a dispute adds a separate $15 fee, which Stripe returns if you win. Amounts and exceptions depend on region and payment method. We checked these US figures on September 25, 2026.

The Dispute object has the field that matters most, evidence_details.due_by. That's your response deadline, and every step below aims to get a complete response in before it.

The deadline is fixed, and you get one submission

You usually have 7 to 21 days from when the dispute opens, depending on the card network. If you miss the deadline, you lose. Stripe won't review late evidence, and there's no appeal.

You also get one submission. After you submit, you can't edit it, add files, or send more information. Preparation matters as much as speed. A rushed packet sent an hour before the deadline is often weaker than a careful one sent on day three.

• One submission, no edits. Collect everything before you click submit.
• 4.5 MB total file size. Mastercard also limits evidence to 19 pages combined.
• One file per evidence type. Combine several files into one multi-page PDF.
• No audio, video, or links. Stripe won't accept them.
• 150,000 characters. That's the limit across all text evidence fields sent through the API.

The dispute plan, day by day

Most dispute windows run longer than a week. Use the first days to decide and gather evidence, and leave a buffer before the deadline in case a document goes missing.

1. 1

   Within the hour: claim it and note the deadline

   Reply in the alert's Slack thread with the owner's name and the respond-by date. One owner per dispute. Then open the dispute in Stripe and read the reason, such as fraudulent or product_not_received. The reason decides which evidence you need.

2. 2

   Day 1: see if a conversation can fix it

   Stripe suggests asking whether the cardholder will withdraw the dispute if you solve the problem another way, such as store credit or a replacement. Don't refund a disputed charge. The bank already credited the cardholder, so a refund can pay them twice.

3. 3

   Days 1 to 2: decide whether to accept or counter

   Compare the disputed amount with the countered fee and the strength of your evidence. A small charge with a weak case can cost less to accept. Accepting tells the bank you won't contest it. Countering opens the evidence form.

4. 4

   Days 2 to 5: gather evidence for the stated reason

   Collect what proves your side of this claim. That can be proof of delivery or access, receipts, customer messages, your refund policy, and product details. Combine several files per evidence type into one PDF and stay under the size limits.

5. 5

   Well before the deadline: review and submit once

   Have a second person read the packet, then submit in Stripe. Stripe can send charge.dispute.closed when the case ends, but ChargeBell doesn't alert on that event. Track the outcome in Stripe or another integration.

Accept or counter?

No rule fits every case, but four questions help you decide.

• Is the cardholder right? If you didn't deliver, or the charge wasn't authorized, accepting usually costs less than a fight you'll lose.
• Is the amount worth the fee? In the US, countering adds a $15 fee you get back only if you win. On a small charge with thin evidence, that rarely pays.
• Do you have evidence for this reason? A delivery confirmation answers product_not_received. It does nothing for fraudulent.
• Is it a pattern? Several disputes on the same product or customer type point to a problem to fix upstream.

Why a complete response matters

Answer the bank's stated reason with the strongest evidence you have. Check the deadline in Stripe and leave time for a second person to review the packet. A fast response doesn't guarantee a win. A missed deadline means the bank never sees your evidence.

Before a dispute opens, clear support answers and quick refunds can settle real complaints. Once a dispute is open, use Stripe's dispute process and don't issue a second refund. See how to send Stripe refund alerts to Slack.

Who owns a dispute

Send Stripe dispute alerts to the right person

ChargeBell's dispute created alert is critical. It can mention @channel and skips quiet hours. It shows the amount, the reason when Stripe supplies one, and the respond-by date when available. It doesn't send countdown reminders or an alert when the case closes. Give each alert one owner, confirm the deadline in Stripe, and track the outcome there. Send disputes to a channel such as #disputes or #finance.

How to respond to a dispute in Stripe

The alert gets you to Stripe in time, and you respond in Stripe. ChargeBell is read-only and can't touch the dispute. These are the Dashboard steps.

1. 1

   Open the dispute details page

   From the alert, open the disputed charge in Stripe and go to its dispute details page.

2. 2

   Choose Accept dispute or Counter dispute

   Accepting tells the card issuer you won't contest the amount. Countering opens a form that asks for the evidence this dispute type needs.

3. 3

   Explain why the dispute is wrong and set the product type

   Tell Stripe why the dispute is incorrect and pick the product type, such as physical, digital, or service, so the right evidence fields appear.

4. 4

   Add your evidence

   Stripe fills in what it has, such as shipping details, refund policy, customer info, and product details. Add proof of delivery, receipts, and messages. Combine files into one PDF per type and stay under 4.5 MB.

5. 5

   Confirm and submit

   Tick the confirmation box and submit. You get one submission with no edits. The status changes to under_review until the bank decides.

To build one routine for every kind of payment problem, read how to build a payment incident workflow in Slack. To decide which events need an alert at all, start with what Stripe events a founder should monitor.