ChargeBell is a Stripe Slack integration that posts payment events to the channels you choose. Each alert shows the amount, the customer, and what you keep after fees.
payment_intent.succeeded
Payment received
ChargeBellAPP
🔔 You got paid: $249.00
You keep $241.48 after fees. Their 4th payment.
Read-only Stripe access
ChargeBell sees payment events and can't move money.
No access to Slack messages
It posts to channels you pick and can't read message history.
About two minutes to connect
Approve Stripe and Slack, pick a channel, send a test.
ChargeBell handles payment_intent.succeeded, payment_intent.payment_failed, invoice.paid, charge.refunded, charge.dispute.created, the customer.subscription events, and payout.paid and payout.failed. Each alert type can go to its own channel.
Successful payments and paid invoices, with the customer and the amount after fees.
See payment alertsFailed payments and new disputes, which need a customer email or dispute evidence.
See failure alertsNew subscriptions, plan changes, cancellations, and recovered payments, with the MRR change.
See subscription alertsRefunds sent to customers, plus payouts that Stripe marks paid or that fail.
See payout alertsStripe webhooks send JSON event objects. A Slack incoming webhook expects a message with a text field. Joining them yourself means running a server that verifies Stripe signatures and formats each event. ChargeBell does that work for you.
{
"type": "payment_intent.succeeded",
"data": { "object": { ... } },
"customer": "cus_R9...",
"amount": 24900
}The data is complete, but a teammate has to decode it.
ChargeBellAPP2:14 PM
🔔 You got paid: $249.00
Jamie at Northloop
Visa ••4242 · Invoice #0382
View in StripeYou don't host a webhook endpoint, build a template, or map fields. The test alert at the end confirms delivery before a real payment arrives.
Stripe's OAuth screen shows the account and the access ChargeBell requests before you approve.
Approve the Slack permissions and pick the channels that get alerts.
Confirm delivery, then route alert types, set minimum amounts, or add quiet hours.
ChargeBell reads payment events from Stripe and posts messages to the Slack channels you selected. It has no other access to either account.
See every permission ChargeBell requestsThe ChargeBell product team wrote this page. We checked the Stripe and Slack claims against the documentation below on July 15, 2026.
Sign up for ChargeBell and approve read-only access to your Stripe account. Then add ChargeBell to your Slack workspace, pick a channel, choose the events you want, and send a test alert. It takes about 2 minutes and needs no code.
Yes. ChargeBell receives the Stripe events and posts a formatted Slack message, so you don't host a webhook endpoint or write a formatter. A Stripe webhook can't post to a Slack incoming webhook directly, because Slack expects a message with a text field and Stripe sends a full event object.
ChargeBell alerts on successful and failed payments, paid invoices, refunds, new disputes, new and canceled subscriptions, plan changes, trials that end in 3 days, and paid or failed payouts. You turn each alert on or off and pick its channel.
No. ChargeBell uses a read-only Stripe OAuth connection. It reads the payment events it needs for alerts. It can't create charges, issue refunds, cancel subscriptions, move funds, or change your Stripe account.
No. ChargeBell doesn't request Slack's message history scopes. Its Slack permissions let it list eligible channels, post alerts as the ChargeBell app, and run its slash command.
A common setup sends successful payments to #revenue, failed payments and disputes to #billing, and subscription changes to #customer-success. ChargeBell routes each alert type separately, so one channel doesn't collect every event.
Approve both accounts, pick a channel, and send a test alert. The Free plan includes 50 alerts a month and needs no card.