Stripe's customer.created event just means a record was created — not that anyone paid. Here's the alert that actually matters: a 👋 in Slack the first time someone pays you.
Looking for a Stripe new customer alert in Slack? Here's the honest version: Stripe's customer.created event fires whenever a Customer *record* is created — which is not the same as getting a paying customer. ChargeBell doesn't alert on the raw customer.created event. Instead it sends a 👋 first-time customer alert the moment someone pays you for the very first time — the milestone actually worth celebrating.
In Stripe's own words, customer.created "occurs whenever a new customer is created." It fires every time a Customer object appears in your account — through an API call, a manual entry on the Dashboard's Customers page, or automatically during a checkout or subscription flow. You can even fire one yourself for testing with stripe trigger customer.created from the Stripe CLI.
The key thing to understand: a Customer object is just a record — a name, an email, maybe some metadata. It's a bookkeeping step that has to exist *before* you can bill someone. A customer can sit in your Stripe account with zero payments, no payment method, and no subscription attached.
A customer.created alert sounds appealing until you realize how often it fires on nothing. Because a Customer record can be created via the API, added by hand in the Dashboard, or spun up automatically when Stripe prepares an invoice or subscription, the event says nothing about money. When a subscription needs an upfront payment, Stripe creates the Customer, an Invoice, and a PaymentIntent — but the subscription starts incomplete and only flips to active after that first invoice is actually paid.
So "a new customer exists" and "a customer actually paid" are two different moments. Alerting on customer.created would fill your Slack with empty records and not-yet-paid signups — noise, not signal. ChargeBell is built on the opposite principle: it tells you when money changes hands, in plain English, with the numbers already computed.
The honest answer
ChargeBell has no alert bound to the raw Stripe customer.created event. Its related alert — first-time customer — fires on a customer's first successful payment, not when a Customer record is created.
What founders really want isn't a ping when a record is created — it's the moment someone pays you for the very first time. That's exactly what ChargeBell's first-time customer alert does. When a customer makes their first successful payment, you get a 👋 in Slack that says a real human just became a paying customer.
It's derived from your actual payments: the first time ChargeBell sees a successful payment from a customer, it treats that charge as their first — and it earns the 👋 treatment instead of a plain payment notification.
👋 First payment from Solstice Studio
Mira just paid $49.00
Via your checkout · View in Stripe
A single payment shouldn't trigger three overlapping alerts. ChargeBell uses a supersede chain so each event produces exactly one Slack message. The first-time customer alert takes priority over a plain payment received alert, but it steps aside for payment recovered and large payment on the same charge. The result: one checkout, one clean message.
Connect Stripe
One-click, read-only Stripe Connect OAuth. ChargeBell can see payment events and can never move money or edit anything.
Connect Slack and pick a channel
Add the app and choose where wins should land — a channel like #wins works well.
Turn on the first-time customer alert
It's built into your alert catalog. Flip it on (and route it to the channel you want) so first payments always get the 👋.
Send a test alert
Confirm the message looks right, then wait for your next real first-time payment to roll in.
New to Stripe → Slack alerts? Start with how to get Stripe payment notifications in Slack for the full setup and every option beyond a single alert.
Key takeaways
customer.created means a Customer *record* was created — not that anyone paid.customer.created; it sends a 👋 first-time customer alert on the first successful payment.Connect Stripe and Slack, turn on the first-time customer alert, and get a 👋 the next time someone pays you for the first time. Free plan, no card needed.
No. ChargeBell doesn't alert on the raw customer.created event, because it only means a Customer record was created — not that anyone paid. Its related alert, first-time customer, fires on a customer's first successful payment instead.
Stripe describes it as "occurs whenever a new customer is created." It fires whenever a Customer object appears — via the API, a manual Dashboard entry, or a checkout/subscription flow. It's a bookkeeping event, not a revenue event.
Connect Stripe and Slack, then turn on ChargeBell's first-time customer alert. When someone pays you for the very first time, you get a 👋 message in Slack with their name, the amount, and a link to view them in Stripe.
A Customer can exist with zero payments — Stripe creates the record before billing. A first payment is a separate, later moment: the customer's first successful charge. ChargeBell keys the first-time customer alert off that first payment, not the record.
No. ChargeBell connects with official read-only OAuth. It can see payment events to build alerts, but it can never create customers, move money, or change anything in your Stripe account.