Failed payments, disputes and cancellations — with the amount, the card, and the actual decline reason — sent to your phone. Stripe logs every one of them. It notifies you about none of them.
Free forever · No credit card · Read-only access — we can never move your money
What It Catches
The charge declined. You get the amount, the card brand and last 4, and the real reason — insufficient funds, expired card, do not honour.
A chargeback landed. You get the amount, the reason code in plain English, and how long you have left to submit evidence.
Someone churned. You get the MRR you just lost and the cancellation reason they gave Stripe.
A recurring charge declined. You get the amount, which retry attempt it was, and the date Stripe will try again.
Full or partial. You get the amount refunded, the card it went back to, and the reason given.
A payment landed above your threshold. Set it anywhere from $10 to $1000 so only the ones worth knowing about reach you.
How It Works
Chrome extension or the iPhone app. No account, no signup, no onboarding call.
Create a restricted key in Stripe with read access to Events. That's the whole setup — there is nothing else to configure.
Chrome sends desktop notifications. The iPhone app pushes to your phone — checked every 30 minutes on Free, every 5 minutes on Pro.
Pricing
Privacy & Security
Stripe Alerts can't charge, refund, or change anything in your account. It reads your event feed and nothing else.
The extension keeps your key in Chrome's local storage and calls Stripe directly. It never reaches our servers.
Push notifications need something watching Stripe while your phone is asleep, so the app sends your restricted key to our backend and it polls Stripe for you. That's the honest trade. If you'd rather no server ever held a key, use the Chrome extension.
Use Stripe's restricted API keys for an extra layer of security.
Straight Answers
Reasonable. So use a restricted key: in Stripe, create one with read access to Events and nothing else. Stripe Alerts physically cannot charge, refund, or move money with it — the permission doesn't exist on the key. You can revoke it from your Stripe dashboard in one click, at any time, and the app stops working immediately. That's the whole security model, and it's the same one we'd want.
Probably, and that's fine — that's the point. Stripe Alerts is designed so you never open it. It sits in the background and pushes you a notification when a payment fails, a dispute opens, or a subscription cancels. If it's doing its job, the only time you'll see it is when something needs you.
Free checks your account every 30 minutes. Pro checks every 5 minutes. Neither is instant — this polls the Stripe API rather than using webhooks, which is exactly why you don't have to install anything into your Stripe account or configure an endpoint. If you need sub-minute alerting, build it on Stripe webhooks directly; that's a different product.
It doesn't do anomaly detection, revenue forecasting, geographic analysis, or dashboards. It doesn't replace Stripe's own reporting. It watches six event types and tells you about them with the detail attached. That's the entire product.
If you already have a Slack alerting pipeline off Stripe webhooks, you don't need this. If you're doing high enough volume that a failed payment is background noise rather than something you'd want to know about, you don't need this either. It's built for people small enough that one failed payment or one dispute genuinely matters.
Free is free forever, no card. Chrome Pro is $15/month, iPhone Pro is $14.99/month through the App Store. Cancel any time — the iPhone subscription from your Apple ID settings, the Chrome one from the billing link in your license email.
Install it once, forget it, and let it tell you when something needs you.
