Stripe alerts for paid communities: joins, failed renewals, cancellations

Stripe alerts for paid communities put three subscription events in front of the people who run the community. A new member joins, and someone welcomes them. A renewal fails, and someone helps them fix their card. A member cancels, and someone asks why. If you run a paid Discord, Circle, or membership site on Stripe subscriptions, this guide routes each event to a Slack channel your team reads.

Why paid communities lose members they could have kept

Joins, failed renewals, and cancellations each need a different reply, and each loses value the longer it waits. Use your own retention cohorts as the benchmark. Count how many members who joined in a month are still paying after one, three, and twelve months. Published churn rates for communities vary too much by price, audience, and billing cycle to predict yours.

A failed renewal is often not a decision to leave. Cards expire, banks decline charges, and some invoices have no payment method on file. Count failed invoices and later recoveries in Stripe to learn how many members you lose this way.

Stripe Billing can retry eligible failed payments, and a person can help a member update their card. Your recovery rate depends on the decline reason, the payment method, your retry settings, and your outreach. The alert assigns an owner early. Stripe holds the invoice and retry status.

Which Stripe events match each community moment

Each moment is a documented Stripe subscription event. The order matters. A failed payment arrives while you can still help. A cancellation arrives after the member has already left.

• New member joined. customer.subscription.created drives ChargeBell's new subscriber alert. checkout.session.completed is a separate Stripe event, and ChargeBell does not map it.
• Renewal charge failed. payment_intent.payment_failed drives ChargeBell's critical payment failed alert. Watch invoice.payment_failed separately in Stripe, including invoices that fail with no PaymentIntent.
• Member canceled. customer.subscription.deleted means the subscription ended. It is your cue for a personal win-back note.
• Renewal paid. invoice.paid means a recurring charge went through. ChargeBell's invoice paid alert is off by default.

A Checkout completion and a new subscription are separate events. Use the subscription alert to start onboarding, then confirm paid status and access in Stripe and your community platform. What happens after a failed invoice depends on your Stripe Billing retry and subscription settings. See Stripe's subscription webhook guide and how to monitor Stripe subscriptions in Slack.

Post new members to a team channel

A new subscriber alert is a prompt to welcome the member. Have one person check the member's tier and access in the community platform, then add them to the right space or cohort. Compare first-month activity and renewals with and without the welcome to see whether it helps.

This sample uses ChargeBell's new subscriber layout. The MRR line appears when Stripe data allows it. The welcome is your team's reply in the thread, not something ChargeBell adds. For one-off products such as event tickets, see Stripe payment notifications in Slack.

Catch failed renewals while the member can be saved

Stripe Billing's retries depend on your account settings and the decline reason. When ChargeBell posts a failed payment, open Stripe and check the invoice, the retry schedule, and the payment method. If an invoice failed with no PaymentIntent, your separate invoice monitor has to start the same follow-up.

ChargeBell marks payment failed as a critical alert. It skips quiet hours and can start with @channel, because a renewal has a deadline and a routine payment does not. Send it to a channel your community manager reads, such as #renewals. What a good failed payment message includes is covered in Stripe failed payment alerts in Slack.

Use a cancellation alert to ask what changed

A cancellation alert is a cue to find out why the member left. Check in Stripe whether access ends now or at the end of the period. Offer a pause or a cheaper tier only if your community has one and the member wants it. Track your own win-back rate before you count on one.

ChargeBell shows the MRR change when it can calculate it. Check the end date in Stripe before you change community access, and have one person own the follow-up.

How to set up Stripe alerts for paid communities in Slack

Turn on only the alerts that someone will act on. This setup works for most communities as is, using the Stripe Slack integration.

1. 1

   Connect Stripe read-only

   ChargeBell uses Stripe Connect OAuth. It reads subscription events and cannot move money, cancel a member, or change anything in your account.

2. 2

   Turn on three alerts

   New subscriber, payment failed, and subscription canceled. These cover a join, a renewal at risk, and a member who left.

3. 3

   Pick a channel for each

   Send new subscribers to #community-wins, failed payments to #renewals, and cancellations to #saves.

4. 4

   Keep payment failed critical

   Let it skip quiet hours and mention @channel. A renewal you can still save should not wait until morning.

5. 5

   Add the digests

   The daily and weekly digests sum up new members, cancellations, and MRR movement, so you can see the trend as well as each event.

Why not build this yourself?

A custom webhook handler or automation tool can cover events ChargeBell does not map, including invoice.payment_failed. You then own signature checks, message wording, retries, and routing. ChargeBell handles wording and delivery for the events it supports.

ChargeBell's alerts include the customer, subscription MRR or fee and net when available, channel routing, quiet hours, digests, and delivery retries. Pro is $24 a month or $240 a year, and Free covers 50 real-time alerts a month. If you need invoice-level failures or a destination other than Slack, compare custom webhook code and Zapier.