How to Set Up Stripe Sound Alerts on Your Computer

It helps to know what you are actually assembling, because it explains why no single switch inside Stripe can do this and why some tools in this category ask for far more access than they need.

• An event. Stripe already broadcasts one the instant a charge succeeds. It is called charge.succeeded and it costs nothing to send.
• A destination. A URL you register inside your own dashboard, which Stripe posts that event to. Stripe calls these event destinations, and they are one-way.
• A speaker. A browser tab that has been allowed to play audio, holding an open connection so the sound fires the moment the event arrives.

Stripe hands you the first two for free. It has nothing that does the third, and the third is the hard part: a public endpoint that verifies Stripe's signature, a live connection into the browser, an audio unlock, and a tab that keeps working after the browser tries to put it to sleep.

Sign in with a magic link. There is no password to invent and no card to enter, and the account is free until your first cha-ching, so you hear the thing working before you decide whether it is worth paying for.

Create a connection and the dashboard generates a private endpoint URL for it. Each Stripe account you want to hear gets its own connection and its own URL, up to ten on one subscription, each with a label so you know which business just got paid.

This part happens entirely inside your own Stripe dashboard, so you can see exactly what is being shared and revoke it in one click. Four screens, and the dashboard deep links you past the two that people get lost in.

The moment the first verified event arrives, the connection flips to receiving in your dashboard, so you never have to guess whether it worked.

Open the dashboard and click enable sound once. Pick your sound while you are there. Seven ship with it: a cha-ching, a cash register, a level up, a gong, a vibraphone, a marimba and a coin drop, plus a synthesized fallback, all levelled to the same volume so none is louder than another.

Then leave the tab open and get back to work. The next successful charge in that Stripe account rings within seconds.

This trips people up, so it is worth being exact about. Chrome's autoplay policy allows a page to play audio once the user has interacted with the domain, or on desktop once that site has crossed a threshold of media engagement, or when the site has been installed as an app. Until one of those is true, audio is blocked, and the Web Audio context a page uses to make sound is created in a suspended state that only a user gesture can resume. Safari and Firefox apply their own versions of the same rule.

So the click is not a workaround. It is the browser handing your page permission to make noise, and it only has to happen once per session. On a machine you use every day, browsers generally stop asking.

A tab that must make noise for eight hours runs into a problem that most write-ups on this subject skip: browsers actively work against long-lived background tabs, and pinning a tab does not exempt it. Chrome throttles timers in a hidden tab, can freeze the page outright, and can discard it entirely to reclaim memory, rebuilding it only when you click back.

An audible tab is exempt from all three, which is why arming the sound does more than pick a noise. While sound is on, the page holds an inaudible keep-alive so the browser continues to count the tab as active and leaves it running. If a tab was paused anyway, the dashboard says so and catches up rather than showing a healthy badge over a silent till.

• Make it deterministic in Chrome. Settings, then Performance, then "Always keep these sites active". This is the belt-and-braces step for a machine that must never miss one.
• Pin the tab anyway. It will not stop the browser sleeping it, but it does stop you closing it by accident, and the speaker icon in the title tells you sound is armed.
• Turn off sleep on a counter machine. A sleeping computer cannot play audio. Payments are still recorded and the totals catch up when it wakes.
• Give it a screen of its own. Display mode is built for a second monitor or a shop TV that stays on all day.

Only one, and picking the wrong one is the most common way a home-built version ends up missing sales.

charge.succeeded is the right event for a payment sound. It fires on every successful charge in the account regardless of how the money arrived, so Checkout, Payment Links, subscription renewals, paid invoices and direct API charges all ring.

checkout.session.completed sounds like the obvious choice and is not. It only fires for Checkout sessions, so a subscription renewing next month goes through silently. invoice.paid has the mirror problem: it covers billing and nothing else. payment_intent.succeeded overlaps heavily with charge.succeeded and will double up if you send both.

Two details worth knowing if you are wiring this yourself. Stripe does not guarantee that events arrive in the order they were generated, so anything downstream has to identify duplicates by ID rather than by timestamp. And Stripe explicitly recommends subscribing to only the events your integration needs, rather than sending everything and filtering later.

The honest version, including the free options and the places where something else is the better fit. If you only ever need a record of a payment, Stripe's own email is free and it works.

Competing prices are the cheapest published entry tier for each category as of September 2026 and are worth checking before you decide. Notification platforms in this space start around $20 a month billed annually, and the Mac menu bar apps around $7 a month or a one-time licence. ChaChing Alerts is not affiliated with Stripe.

You can, and it is a genuinely satisfying weekend. It is worth seeing the real scope before you start, because the demo is an afternoon and the parts that make it survive a working week are the rest of it.

• A public HTTPS endpoint on TLS 1.2 or better, since Stripe will not deliver to anything less.
• Signature verification on every request, computed as an HMAC with SHA-256 over the raw body, with a tolerance window so a replayed event is rejected.
• A host that does not sleep, and a handler that returns a 2xx immediately rather than after its own work, or Stripe records a timeout.
• Deduplication by event ID, because endpoints do occasionally receive the same event twice and one sale must not ring twice.
• A live connection into the browser, plus an audio unlock gesture and a strategy for the tab going to sleep behind you.
• A recovery path for the minutes your machine was closed, since Stripe retries for up to three days and those retries all have to land somewhere sensible.

That is the stack running here for $4.49/month. If you want to build it anyway, the overview of how real-time Stripe payment notifications work lays out the same pieces, and the guide to getting a Stripe payment sound covers why Stripe leaves the gap in the first place.

Six things account for almost every report, and each one has a specific tell.

Payments appear in the feed, but nothing makes a noise.

The tab is not armed. Click enable sound once, and check the tab is not muted in the browser and that your system output is not set to a device that is off. Browsers block audio in a tab until someone interacts with the page, so this is the first thing to rule out.

It rang all morning and then went quiet.

The browser paused the tab. Clicking back into it usually rings immediately, which is the giveaway: the payment arrived, the delivery was late. Keeping sound armed prevents this, and Chrome users can make it deterministic under Settings, then Performance, then "Always keep these sites active".

Stripe shows the delivery failed with a 404.

The connection is not verified yet. Until the signing secret is pasted back into ChaChing Alerts, the endpoint deliberately answers unknown callers with a 404 so nobody can probe for live URLs. Finish the last step and Stripe's next retry succeeds.

Stripe shows the delivery failed with a 400 invalid signature.

The secret does not match the destination. The most common cause is pasting the secret from a different endpoint, or a test mode secret onto a live mode destination, since Stripe issues a separate one for each. Reveal the secret on that exact destination and paste it again.

Test payments ring but do not show up in the totals.

That is deliberate. Test mode payments carry a test badge in the feed so you can confirm the wiring works, and they are excluded from revenue totals so your figures stay honest.

A sale landed while the laptop was closed.

The record is safe. Stripe retries a failed delivery for up to three days, and the dashboard reconciles anything it missed the next time you open it. Only the sound is lost, not the payment.

The setup on this page is the same everywhere. What changes is the room, and each of these covers one of them: app developers, solo founders, web shop owners and retail counters. If you want the whole team to hear it rather than one machine, there are Slack and Discord alerts as well.