ChaChing AlertsSign in

Built for

Stripe Payment Notifications for App Developers

Hear your side project make money while you are heads-down in the editor. A real-time Stripe payment notification in a browser tab, with no API key in your environment and nothing to install on the machine.

Start freeNo card required · then $4.49/month
Stripe payment notifications for app developers

2 min

Setup

10

Projects

0

API keys

$4.49

Per month

The feedback loop between shipping and getting paid

You push a change on Thursday night. Then you refresh the Stripe dashboard. Then you refresh it again on Friday morning, and once more after lunch, and by the weekend you have stopped looking, which is exactly when the first stranger pays you.

A Stripe payment sound closes that loop. The tab is already open next to your editor and your terminal. When a charge succeeds it rings, the totals move, and you get the one piece of information a dashboard refresh was never going to give you at the right moment: it worked, someone paid, keep going.

No Stripe API key, which is the point for a developer

Every notifier that asks for a secret key is asking for read access to your whole account, stored on someone else's server, in exchange for a sound. That is a poor trade and you already know it, which is why the key sits in a password manager you never quite got around to rotating.

This works the other way round. You create an event destination in your own Stripe dashboard for charge.succeeded and point it at a private endpoint. Stripe talks to us, we cannot talk back. There is no key to leak, nothing to rotate, and revoking access is one delete in a UI you control.

Yes, you could build this in a weekend

You could, and it would be a fun weekend. Here is the honest scope of the weekend, because the demo is an afternoon and the rest is the part that keeps you up.

Swipe the table sideways to see every column.

Building a Stripe payment sound yourself compared with using ChaChing Alerts
What you getChaChing AlertsYour weekend build
Public webhook endpointIncludedHost it, keep it awake
Stripe signature verificationIncludedWrite it, test it
Realtime push to the browserIncludedWebsocket or polling
Browser audio unlock and re-armIncludedAutoplay policy per browser
Duplicate suppressionIncludedOne payment, one sound
Catch up after downtimeIncludedCursor and backfill
Slack and Discord fan-outIncludedRetries and backoff
Multiple Stripe accountsUp to 10More endpoints to manage
Running cost$4.49 a monthHosting plus your weekends

If you want to build it anyway, the setup guide walks through the same webhook plumbing, and you are welcome to steal the approach.

Stripe payment alerts in the channel your project already lives in

Point a webhook at a Slack or Discord channel and every payment posts there as well as ringing in your tab. Amount and currency only, so the channel can stay public to your team without leaking anything about a customer.

Ten projects, one tab

Most developers reading this do not have one Stripe account. They have the SaaS, the client retainer, the little tool that unexpectedly still earns, and a half-abandoned thing that charges four people a month.

Connect up to 10 accounts on the same subscription. Each one keeps its own label and its own webhook, so the payments list tells you which project just paid, and every total can be filtered by currency.

Frequently asked questions

Which Stripe payments trigger the sound?
Any successful charge on a connected account. It does not matter whether the money came from Stripe Checkout, a Payment Link, an invoice, a subscription renewal or your own API call: if the charge succeeds, Stripe sends charge.succeeded and the tab rings.
Does it work with Stripe test mode?
Yes. Register the endpoint from a test mode destination and test payments ring exactly like live ones, which is the fastest way to confirm your integration end to end. Live and test payments are labelled separately so you always know which one you just heard.
Do you verify the webhook signature?
Yes. You paste the signing secret from the destination when you connect, and every incoming event is checked against it before anything is stored or played. An event with a bad signature is rejected, so knowing your endpoint URL is not enough to make your speakers ring.
Can I hear several side projects at once?
Connect up to 10 Stripe accounts on one subscription. Each connection carries its own label, so the payments table tells you which project just got paid without you having to guess from the amount.
What happens to payments that arrive while my laptop is closed?
They are captured server side and the dashboard catches up when you open it again, so the totals stay right. The sound needs an awake browser, which is a physical limit of a browser tab rather than a feature we withheld.

Keep reading

Ship it, then hear it sell.

$4.49/month, unlimited payments, up to 10 Stripe accounts, every sound and every feature on this page.

Or pay $120 once and never pay again. Lifetime access is available until September 30, 2026.

No card required. Your free trial ends 48 hours after your first live payment arrives, or 30 days after signup, whichever comes first. Then subscribe for $4.49/month to continue, or pay once for lifetime access. No automatic charge.