Stripe alerts for course creators: launches, refunds, and payment plans

Stripe alerts for course creators cover two different jobs. During launch week, every sale should show up in Slack so the team can watch the cart fill. In the weeks after, the same channel should flag refunds inside your guarantee window and payment plan installments that fail. This guide sets up both with Stripe events that ChargeBell posts to Slack.

Why Stripe alerts for course creators belong in Slack

Launch revenue arrives in bursts. Sales jump when the cart opens to your email list, again before the early-bird price ends, and again in the last hours before the cart closes. Then the cart closes and sales stop.

Refreshing the Stripe dashboard during those bursts means you see totals, not people. Slack is where you and any launch helpers are already talking, so each sale can land there with the buyer's email and amount. Other ways to set this up are compared in how to get Stripe payment notifications in Slack.

A raw feed of every Stripe webhook is unreadable during a launch. General automation tools hand you the raw fields and leave the wording and filtering to you, as covered in how to avoid noisy Stripe notifications. A course creator needs a handful of alerts, each tied to a launch moment.

Five course moments and the Stripe events behind them

Each moment below lists the Stripe event and what ChargeBell does with it.

• A sale. ChargeBell alerts on payment_intent.succeeded. It ignores checkout.session.completed, so if enrollment runs off Checkout completion, watch that event elsewhere. Fee and net appear only when Stripe returns them and you chose net display.
• A first-time buyer. ChargeBell works this out from payment history, not from customer.created. The first-time customer alert is off by default, so turn it on before a launch.
• A refund. Fires on charge.refunded, including partial refunds, and on refund.created. A refund count after a launch tells you whether buyers think the course delivered.
• A missed installment. ChargeBell alerts on payment_intent.payment_failed when an installment attempt fails. Also watch invoice.payment_failed in Stripe, because an invoice can fail with no failed PaymentIntent. Check your course platform's access rules for unpaid plans.
• A launch spike. There is no separate alert for this. It is the launch channel filling up at cart open, at the early-bird deadline, and at cart close.

Post each launch sale to a Slack channel

A launch channel shows each supported payment as it happens, with the customer and amount. Fee and net depend on Stripe data and your net display setting. To confirm which course the buyer bought and whether they are enrolled, open the Stripe record or your course platform.

This sample uses fake customer data and the gross amount layout. A first-time buyer gets the first-time customer alert in place of this one, not both. Check enrollment in your course platform before you send a welcome. Connection steps are in how to get Stripe payment notifications in Slack.

Track refunds through the guarantee window

A refund lowers what you collected. Whether Stripe returns the processing fee depends on the payment method, your region, and your Stripe terms, so check Stripe pricing for your account.

Refunds usually come after the launch. With a 30 or 60 day guarantee, a buyer who stops watching the lessons can still ask for money back weeks later. If you only look at launch week revenue, you miss refunds that arrive in weeks three to eight.

A refund channel makes each refund visible to the team. Three refunds in one week that mention the same module point at a content fix. Setup is in Stripe refund alerts in Slack. ChargeBell has read-only access, so it cannot issue or reverse a refund. Stripe stays the source of truth.

Catch failed payment plan installments

Higher-priced courses often sell on a payment plan of three or four monthly charges. In Stripe, a plan like this usually runs as a subscription that ends after the last installment. When an installment fails and Stripe's retries also fail, your Billing settings decide whether Stripe cancels the subscription or marks it unpaid. Many course platforms keep the student's access open unless you change it, so you can end up delivering the course without collecting the rest.

Stripe's `invoice.payment_failed` event is the invoice-level warning, and it covers invoices with no stored payment method. ChargeBell does not map it. ChargeBell's payment failed alert comes from payment_intent.payment_failed and is critical, so it skips quiet hours and can mention the channel. Keep an invoice-level monitor in Stripe or another tool for the cases with no PaymentIntent.

This sample shows only the fields ChargeBell sends. Before you contact the student, open the invoice in Stripe and check the retry schedule and payment link. If a later retry succeeds, ChargeBell posts a separate payment recovered alert. Change access in your course platform only after you confirm the subscription status. The full process is in the failed payment playbook.

Recommended alert settings for a course launch

Change the channel names to match your workspace.

Set the minimum amount filter to Any during a launch so a $27 order bump still posts. ChargeBell sends one alert per payment, so a first-time buyer's purchase does not post twice. Leave quiet hours on. Sales from 2 a.m. wait until morning, while failed payments and disputes are critical and arrive right away.

Why not build this in Zapier?

You can connect Stripe to Slack with a general automation tool, and that makes sense if you already run many workflows there. For a launch, each event (sale, first-time buyer, refund, failed installment) is usually its own Zap. You write each message format by hand. Zapier bills per task, so your biggest sales day is also your biggest Zapier day.

ChargeBell ships its alert types already worded, with fee and net when available, channel routing, and digests. A general tool can cover invoice and Checkout events that ChargeBell does not map, if you build the steps. Read ChargeBell vs Zapier and when to replace a Zapier Stripe alert workflow before switching.

Set it up before your next cart opens

Setup takes a few minutes with no code. Connect Stripe with read-only OAuth, add the Slack app, pick your channels, turn on the alerts above, and send a test alert. The Stripe Slack integration page walks through each step. ChargeBell reads payment events but cannot move money or change anything in Stripe. Disconnecting stops new alerts, and stored history follows the retention policy. Do it the day before the cart opens so the first real sale shows up where you expect it.