Stripe notifications in a Slack channel

Paste a Slack incoming webhook, add one endpoint in Stripe, and every payment, failed card and cancellation lands in your channel as one readable message.

Loading…

Getting the webhook address of your Slack channel

1. Open api.slack.com/apps and create an app "from scratch" in your workspace. Any name will do, for instance "Stripe".
2. In the app, open Incoming Webhooks and switch the feature on.
3. Click Add New Webhook to Workspace, choose the channel, and allow.
4. Copy the webhook URL. It starts with https://hooks.slack.com/services/. Paste it above.

One webhook posts to one channel. For a second channel (say, failed payments in #billing-alerts and everything else in #sales), add a second webhook, create a second connection here, and give each its own rules.

Then, on the Stripe side

1. After connecting, you get an endpoint address. In your Stripe dashboard, under Developers → Webhooks, add it as an endpoint. Test mode is a good place to start.
2. Select the events you care about. The dashboard of your connection lists ten that cover payments, failures, subscriptions, refunds and disputes.
3. Copy the signing secret Stripe shows for the endpoint (it starts with whsec_) and paste it in the dashboard. Events are verified from then on.

What you get

• Only genuine events. The Stripe signature is checked before anything is sent. How the five checks work.
• One message per payment, even though Stripe emits several events for it, and never the same event twice.
• Your rules: kinds of events, a minimum amount, test mode on or off.
• A daily summary at the hour you choose, and a journal of every event with what was done about it.

Questions

Do I have to install a Slack app from the directory?

No. You create an incoming webhook in your own workspace, which takes a minute, and paste its address here. Nothing is installed from the Slack directory and no permission on your workspace is granted to anyone.

Can I send failed payments to another channel?

Yes. Create one incoming webhook per channel and one connection per webhook, then switch on only "Failed payments" in the rules of the second one. Both connections can use the same Stripe events.

Why not a Zap?

A Zap forwards each event as it comes: a single payment can produce three messages, and a retried event produces another. Here a payment is announced once, the signature is checked, and a journal tells you what happened to every event.