Recipe
Stripe Webhooks to Slack: Failed Payments, Disputes and Large Orders
Stripe will email you about some of this and show you all of it in the Dashboard. What it will not do is put the three events your team needs to react to in the channel where they already are, worded the way you would word them.
17 November 2026 · 3 min read
What you will end up with
One webhook URL registered at Stripe, with three small rules on it:
- A failed invoice payment posts the customer, the amount and a link to the invoice.
- A new dispute posts the reason and the evidence deadline.
- A completed checkout above a threshold posts a short celebration.
A free URL allows 3 automations, which is exactly this.
Step 1: a Slack incoming webhook
Create a Slack app at api.slack.com, enable Incoming Webhooks, add one to your channel and copy the URL. It starts with https://hooks.slack.com/services/. Anyone holding that URL can post to the channel, so treat it as a secret.
Step 2: point Stripe at a webhook URL
- Create a webhook.stream URL.
- In the Stripe Dashboard, open Developers → Webhooks and add an endpoint with that URL. Start in a sandbox or test mode.
- Select only the events you need:
invoice.payment_failed,charge.dispute.createdandcheckout.session.completed. - Trigger one of each so you have real samples to build against. The Stripe CLI is the quick way:
stripe trigger invoice.payment_failed
stripe trigger charge.dispute.created
stripe trigger checkout.session.completedStep 3: the three automations
For each one, select the matching request in the inspector, open Automations, choose Notify Slack and paste the Slack URL as the destination.
Failed payments
| Field | Operator | Value |
|---|---|---|
body.type | equals | invoice.payment_failed |
{
"text": ":warning: *Payment failed* for {{body.data.object.customer_email | default: \"a customer with no email\"}}\nAmount due: {{body.data.object.amount_due}} {{body.data.object.currency | upper}} (smallest currency unit)\nAttempt {{body.data.object.attempt_count}} · <{{body.data.object.hosted_invoice_url}}|Open invoice>"
}New disputes
| Field | Operator | Value |
|---|---|---|
body.type | equals | charge.dispute.created |
{
"text": ":rotating_light: *New dispute* · reason: {{body.data.object.reason}}\nAmount: {{body.data.object.amount}} {{body.data.object.currency | upper}} (smallest currency unit)\nEvidence due: {{body.data.object.evidence_details.due_by | iso}}\n<https://dashboard.stripe.com/payments/{{body.data.object.charge}}|Open the payment>"
}The iso filter turns Stripe's Unix timestamp into a readable date.
Large checkouts
| Field | Operator | Value |
|---|---|---|
body.type | equals | checkout.session.completed |
body.data.object.amount_total | is greater than | 50000 |
body.livemode | equals | true |
{
"text": ":tada: *{{body.data.object.customer_details.email | default: \"Someone\"}}* just paid {{body.data.object.amount_total}} {{body.data.object.currency | upper}}"
}The threshold is the reason to filter here and not at Stripe. Stripe lets you choose which event types to send, but not "only when the amount is over 500.00". The last condition keeps test-mode events out of the channel once you go live.
Step 4: test, then save
With a sample request selected, the editor shows the exact JSON that would be sent. Press Send test to post that one message to Slack. When all three read well, save. Each request's Deliveries tab then shows what was sent and what Slack answered.
Things worth knowing
- Amounts are in the smallest currency unit. Stripe sends
4900for 49.00. Templates do not do arithmetic, so the message shows 4900. Label it, as above, or rely on the invoice link for the formatted figure. - Stripe gets its answer immediately. The URL acknowledges at the edge before any automation runs, so a slow Slack never causes Stripe to retry.
- Deliveries are not retried. If Slack is unreachable for a moment, that message is missed. The request itself is still in the inspector with the failed attempt logged against it. Use this for awareness, not as your record of payments.
- Automations do not check the Stripe signature. Signature verification in the inspector is something you do by hand, in your browser. The webhook URL is long and unguessable, but keep it private, and do not let a chat message trigger anything irreversible.
- Captured payloads are readable by anyone with the dashboard link. Subscribing only to the three events you need keeps what is stored to a minimum.
Variations
- Cancelled subscriptions: filter on
customer.subscription.deleted. - A different channel per event: each automation has its own destination, so disputes can go to finance and large orders to sales.
- Discord or Telegram instead: the same conditions work with those presets; only the message format changes. See webhook to Slack or Discord.
For what Stripe sends and how its signature works, see the Stripe webhook guide.
Build it against a real event
Create a URL, register it in a Stripe sandbox and trigger a failed payment. You will have the first message in Slack in a few minutes.
Keep reading
Webhook filtering
Filter webhooks by event type, amount, branch, header or path before they reach a channel or an API. How conditions work, ten patterns worth copying, and how to express OR.
ReadA lighter alternative to Zapier for webhooks
If your automation is one step long (a webhook arrives, a request goes out), you do not need a workflow platform. What a lightweight webhook relay does, where it stops, and how to choose.
Read