Stripe dispute alert in Slack (charge.dispute.created)

A Stripe dispute alert in Slack tells your team about a chargeback while there is still time to respond. ChargeBell listens for charge.dispute.created and posts the disputed amount, the reason, and the respond-by date from Stripe. It marks the alert critical, so it posts during quiet hours and adds an @channel mention by default.

What charge.dispute.created means

Stripe sends charge.dispute.created when a customer disputes a charge with their bank. A new chargeback usually has the status needs_response, which means Stripe is waiting for your evidence. An inquiry that the bank later turns into a formal dispute also sends this event.

When a dispute opens, Stripe takes the disputed amount and a dispute fee from your balance. That happens before anyone looks at the case.

Dispute vs chargeback

A chargeback is the bank reversing a card payment at the cardholder's request. Stripe calls this a dispute. An inquiry is an earlier step where the bank asks for information without reversing the money yet. Both appear as Dispute objects in Stripe.

Why a Stripe dispute alert needs to be fast

Each dispute has a deadline set by the card network. Stripe stores it in evidence_details.due_by. If you submit evidence before then, the bank reviews your case. If you miss it, you lose the dispute. The window depends on the card network and country, so use the date Stripe gives you.

• The deadline is fixed. You cannot reopen a dispute after evidence_details.due_by passes.
• The money is already gone. Stripe takes the amount and fee when the dispute opens.
• It is easy to miss. Stripe emails the account, and that inbox may not belong to the person who handles disputes.

What the Slack alert shows

The title reads "A $X charge was disputed." Below it is the reason Stripe reports, such as "fraudulent" or "product not received." A Respond by field shows the evidence deadline in your organization's time zone. A View evidence in Stripe button opens the dispute.

Fields ChargeBell can include

• The disputed amount and currency
• The reason Stripe reports, such as fraudulent or product_not_received
• The respond-by date from evidence_details.due_by
• A View evidence in Stripe button that opens the dispute

Stripe's dispute webhook does not include the customer's name or email, so the alert usually says "a customer." Open the dispute in Stripe to see who it is.

Why ChargeBell marks disputes critical

ChargeBell holds most alerts during quiet hours and posts them as one batch in the morning. Critical alerts skip that hold. Disputes are critical by default, along with failed payments and failed payouts. They also add an @channel mention, which you can turn off in settings. Send disputes to a channel like #disputes or #founders where someone owns the response.

How to set up a Stripe dispute alert in Slack

1. 1

   Connect Stripe

   Approve ChargeBell's read-only Stripe app. It reads dispute events and cannot submit evidence or move money.

2. 2

   Connect Slack and pick a channel

   Add the ChargeBell Slack app and choose where disputes post. A dedicated #disputes channel keeps them visible.

3. 3

   Check the charge disputed alert

   It is on by default and critical, so it posts during quiet hours with an @channel mention.

4. 4

   Send a test alert

   Check that the message reaches the right people before a real dispute arrives.

Related Stripe alerts

• Stripe failed payment alert, another critical alert
• Stripe refund alert for charge.refunded
• Stripe successful payment alert for payment_intent.succeeded