How to Get Stripe Payment Notifications in Slack

You want a Slack message every time a customer pays you — no dashboard refreshing, no code. There are three free ways to get Stripe payment notifications in Slack: the official Stripe Workflows for Slack app, a DIY webhook you host yourself, or a no-code tool like Zapier. All three work, and all three hand you a bare "you got $X" message. This guide walks through each honestly, then shows the fast path that also tells you the net after fees, who paid, and what it did to your MRR.

What is a Stripe Slack alert?

A Stripe Slack alert is an automatic message posted to a Slack channel when something happens in your Stripe account — most commonly a successful payment, but also failed charges, refunds, disputes, new subscriptions, and payouts. Instead of opening the Stripe Dashboard to see whether you got paid, the payment comes to you where your team already works.

The mechanism is always the same underneath: Stripe emits an event (like payment_intent.succeeded or charge.succeeded), and something has to catch that event, turn it into a readable message, and post it to Slack. The three DIY routes below differ only in *what* catches the event — Stripe's own workflow engine, your own server, or an automation platform. A dedicated tool like ChargeBell is a fourth path that owns the whole chain for you.

3 ways to get Stripe payment notifications in Slack

Every integration guide lands on the same shortlist. Here's what each one is, and where it stops.

1. Native — Stripe Workflows for Slack

Stripe does not have a one-click "ping me on every sale" toggle. Its official option is the Stripe Workflows for Slack app in the Slack Marketplace, built on Stripe Workflows — the no-code automation engine Stripe launched at Sessions 2025. To use it you install the app from the Stripe App Marketplace, click Add to Slack, run /invite @Stripe in the target channel, then build a workflow that fires on an event (like *Payment intent succeeded*) with a Send Slack Notification action.

You write the message with template variables by hand — {Payment intent | Amount received}, {Customer | Name} — and it can deep-link to the Stripe Dashboard. It's first-party, free to install, and real-time. The catch: it's an automation builder aimed at developers and ops. You configure a workflow per event, and it only surfaces raw event fields. No net-after-fees, no MRR, no new-vs-returning context.

2. DIY webhook — your own server

The most flexible route is also the most work. You stand up a web server that receives Stripe webhooks, verifies the signature, reformats the JSON into Slack's block format, and POSTs it to a Slack Incoming Webhook URL. It's fully customizable and free of subscription cost — but it's code plus hosting to maintain, which rules it out for non-technical teams.

There's a subtler cost here too. A raw Stripe webhook payload does not include the processing fee or net amount. To show what actually landed in your account, you have to retrieve the charge, expand its balance_transaction, and compute amount − fee yourself. That's why almost every DIY (and native, and Zapier) alert shows the gross number, not the money you keep.

3. Zapier (or Make, n8n, Pabbly, Relay.app)

No-code automation platforms have ready-made "new Stripe sale → Slack message" templates. You pick a Stripe trigger (*New Payment*) and a Slack action (*Send Channel Message*), and you're posting to Slack without writing code. It's the most popular middle ground, and it can fan out to email or a CRM in the same flow.

The trade-offs are pricing and output. Zapier's free plan is 100 tasks/month with only 2-step Zaps, and every action counts as a task — so a good sales month burns the allowance fast. The paid Professional plan starts at $19.99/month billed annually for 750 tasks and scales up from there, with overage billed at roughly 1.25× your base rate. And the out-of-the-box message is a plain "new sale" with the gross amount and basic fields — no fee-adjusted net, no MRR, no customer enrichment unless you build extra steps (more tasks, more cost). We break the economics down in ChargeBell vs Zapier for Stripe Slack alerts.

Native vs DIY vs Zapier vs a dedicated tool

The fast path: set up Stripe payment notifications in Slack with ChargeBell

ChargeBell is a purpose-built Stripe → Slack alert product. It owns the whole chain — catching events, computing the numbers, formatting the message, and posting to the right channel — so you never touch a webhook, a template variable, or a task limit. Here's the full setup.

1. 1

   Create your account

   Sign up at app.chargebell.com/signup. No card required to start on the free plan (100 alerts/month, last 7 days of history).

2. 2

   Connect Stripe

   One click through official Stripe Connect OAuth — read-only. ChargeBell can see your payment events but can never move money or change anything in your account.

3. 3

   Connect Slack

   Add the ChargeBell app to your workspace and pick a channel. It only posts to channels you choose, with minimal permissions.

4. 4

   Choose which alerts you want

   Toggle the event types that matter — payment received, failed payment, refund, dispute, new subscriber, and more. Sensible defaults are already on, and you can route each type to its own channel.

5. 5

   Send a test alert

   Fire a test message to confirm it lands, then wait for the real thing. You'll get your first alert before your coffee cools.

That's it — no server to host, no per-event workflow to configure, no task meter running in the background. If you want failed charges routed somewhere separate, see how to send failed payment alerts to Slack; to keep the noise down, how to avoid noisy Stripe notifications covers quiet hours and minimum-amount thresholds.

What a good payment alert actually shows

A ping that just says "you got $249" answers the least interesting question. Founders want the numbers that matter: what actually landed after Stripe's cut, whether this is a new customer or a returning one, and what the payment did to recurring revenue. None of that rides along in the raw webhook — it has to be derived. A full breakdown lives in what should a payment alert include.

Here's the difference in practice. A generic tool posts the gross amount and a customer ID. ChargeBell writes the message with the derived numbers already worked out:

Every line there is data a raw event doesn't carry. Net after fees needs the balance-transaction expansion. "Returning customer · 3rd payment" needs history. "MRR impact +$20.75/mo" needs a tool that tracks subscriptions over time. That enrichment — not just ease of setup — is the real reason to reach for a dedicated tool over stitching one together.

Which route should you choose?

• Choose native (Stripe Workflows for Slack) if you're comfortable in an automation builder, want first-party tooling, and are fine writing template variables per event and living with raw fields.
• Choose DIY if you have engineering time to spare and want total control over the message — and you're willing to also fetch the balance transaction to show net.
• Choose Zapier (or Make / n8n) if Stripe → Slack is one small part of a bigger multi-app workflow and you'll use the same platform elsewhere. See when to replace a Zapier Stripe alert workflow for the tipping point.
• Choose ChargeBell if the job is simply "tell my team what's happening in Stripe, clearly, in Slack, without babysitting it" — and you want net, customer, and MRR context for free.