Stripe notifications: the dispute email is the one you can't miss
Stripe gives you 7 to 21 days to answer a dispute. Which Stripe notifications to keep, which to switch off, and where each email and push setting lives.
A Stripe dispute comes with a deadline, and it is short. Stripe's own docs say you have a limited window to respond, "usually 7 to 21 days, depending on the card network," and that if you miss it "you automatically lose the dispute and can't retrieve the disputed funds." Of all the Stripe notifications you can switch on, that is the one that costs money when it sits unread.
If you'd rather Stripe's dispute email rang your phone, the email route works on an iPhone; the Stripe app's push alerts there need a Bluetooth relay.
Does Stripe notify you of disputes?
Yes, in four places. Stripe's dispute page lists your email address, the Dashboard, a charge.dispute.created event if your integration listens for events, and a push notification from the mobile app if you're subscribed. Disputes are also on the default list of emails that each team member can turn on or off, and that per-person part matters more than it sounds.
Two details from the same page change how fast you should move.
Some disputes start as inquiries, a pre-dispute stage that typically comes up when the cardholder doesn't recognise a charge. Stripe says answering at that stage can stop a formal dispute and saves "time, fees, and your rating with the card networks." If it escalates anyway, you respond again.
And you get one shot. "You've only one opportunity to submit your response," Stripe writes, and once it's sent you can't edit it or add files. So the deadline isn't really 7 to 21 days to reply. It's 7 to 21 days to dig out the invoice, the customer emails, your refund policy and whatever proves the work was delivered. Then you combine them into files under Stripe's 4.5 MB limit and reply. For a SaaS founder that proof is often usage records. For a freelancer it's the contract and the message where the client said the work looked great.
Countering isn't free either. Stripe charges a dispute countered fee on top of the dispute received fee and returns the countered fee only if you win. The bank can take up to 3 months to decide, and Stripe emails you when it does. If you also take PayPal, its disputes run on a different clock, covered in PayPal notifications.
Does Stripe send a failed payment notification?
To your customer, yes, if you turn it on. To you, it depends on what your account offers, and this is where people get mixed up.
The setting most people find first is Send emails when card payments fail, on the revenue recovery emails page. Stripe is clear about who receives it: it "automatically sends an email to your customer after each failed payment" so they can update their card. Good for subscriptions. It does nothing to tell you that a $2,000 annual renewal just bounced.
Stripe's published list of emails it sends to you covers successful payments, disputes, payments flagged as risky by Stripe or a Radar rule, application fees from connected accounts, mentions in notes, invoices paid with the wrong amount and failed webhook deliveries. Failed payments aren't on that list. Stripe also says the full list lives in your own Communication preferences, so look there before deciding anything. If it isn't offered, there are two routes. Stripe Workflows starts from a trigger and can email a team member (Stripe's example emails someone when a payment over $1,000 succeeds), so check whether a failure trigger is available on your account. Or a developer can catch the failure with a webhook, covered in the developer note below.
Stripe payout notifications
A payout that lands doesn't need an alarm. Your bank will tell you. A payout that fails is different. If your bank can't process a payout, Stripe's payouts FAQ says you may get an email with the subject line "Action required to resume payouts from your Stripe balance". For a closed bank account, it can take up to 5 business days for the money to come back to Stripe. Fix the bank details in the Dashboard when that email arrives, not when you notice rent hasn't cleared.
On the phone, Stripe lists "deposited transfers" among the app's push notification types.
Should you get an email for every successful payment?
No. Turn it off, at least for yourself.
Successful payment emails are the noisy ones, and the noise has a cost that never shows on an invoice. Get forty "payment received" emails a week from Stripe and your brain files Stripe as good news that can wait. Then the dispute email arrives from Stripe and gets the same half-second glance, on the same busy Tuesday, and slides under the next three receipts. Every successful payment email trains you to ignore Stripe's emails, including the one with a deadline on it. If you want to know what came in today, the Dashboard home charts and the app's daily summary push do that job without touching your inbox.
How do I turn on Stripe email notifications?
In the Dashboard, open your Personal details settings and find Communication preferences. Stripe applies these per user, so each teammate sets their own, and anyone can opt in or out of any default notification. Turning disputes on for yourself does nothing for your co-founder's inbox. If two of you can answer a dispute, both of you should check.
| Event | Email to you | Stripe app push | Where to change it |
|---|---|---|---|
| Dispute opened | Yes, on the default list | Yes, disputed payments | Communication preferences, and the app's notification settings |
| Failed payment | Not on Stripe's published list | Not among the listed types | Check Communication preferences, then Workflows or a webhook |
| Failed payout | Yes, the Action required email | Not among the listed types | Update bank details in the Dashboard |
| Payout arrived | Not on Stripe's published list | Yes, deposited transfers | The app's notification settings |
| Successful payment | Yes, on the default list | Yes, new payments | Communication preferences (worth turning off) |
For the app, tap your merchant icon at the top left of any screen to open Account and Settings, go to Global settings, then Notification settings, and use the toggle for each merchant account. Then allow notifications for Stripe in your phone's own Settings, because Stripe says push won't work without that. The app's push types are daily summary, new payments, new customers, disputed payments and deposited transfers.
A note for developers
If you'd rather build your own alerts, Stripe webhooks are the tool. You register a public HTTPS endpoint (in the Webhooks tab in Workbench, or through the API), choose the event types, and Stripe pushes each event to you as JSON in real time. Start with charge.dispute.created and payment_intent.payment_failed. Verify the Stripe-Signature header, return a 2xx quickly, and expect duplicates and events out of order. In live mode Stripe retries a failed delivery for up to three days, and a failed webhook delivery is itself one of the things Stripe can email you about. Leave that email on, because the week your alert endpoint quietly breaks is the week you'd otherwise learn about a dispute from your balance.
Can a Stripe dispute email call me?
Stripe's notification emails can go to Gmail, and that's where our app, OLL.E, picks them up. You type a watch as a sentence. When a dispute opens, or an email about a failed payment over your amount comes in, it calls you and sends a summary of the email, and it can forward the email to your co-founder, whose own Stripe settings might be off. That part works on iPhone with nothing extra. If you rely on the Stripe app's push instead, Android phones can be watched directly and an iPhone needs the PinG keyring.
It sees the email Stripe sends you, nothing else: no refunds, no evidence uploads, no access to the money. Because of that, a failed-payment watch needs a failed-payment email to exist first, from your preferences, a workflow or your own webhook code.
One more reason to watch the inbox rather than trust the settings: Stripe's email preferences belong to each person, not the account, so your co-founder can be getting every dispute email while you get none, or the other way round. OLL.E closes that gap from your own Gmail. It calls you when a dispute email lands, sends a short summary, and forwards the email to whoever pulls the evidence together, so the person with the receipts hears about it the same day. On iPhone the Gmail watch works fully; the Stripe app's alerts there need PinG. You can start free; the paid plan is $19.99 a month once you outgrow four watches.
Questions people ask
How do I turn on Stripe email notifications?
In the Stripe Dashboard, open Personal details and go to Communication preferences, then switch on the emails you want. The settings are per user, so every teammate who should hear about disputes has to turn them on in their own account.
Does Stripe notify you of disputes?
Yes. Stripe notifies you by email, in the Dashboard, with a charge.dispute.created event if your integration listens for events, and with a push notification from the Stripe app if you're subscribed. Dispute emails are on the default list each team member can turn on or off.
How long do I have to respond to a Stripe dispute?
Usually 7 to 21 days, depending on the card network, according to Stripe. If you don't respond before the deadline you lose the dispute automatically, and you only get one chance to submit evidence, so gather everything before you reply.
Can Stripe text me?
Not for disputes, going by Stripe's own docs. Its dispute page lists email, the Dashboard, a webhook event and a push notification from the Stripe mobile app, and text messages aren't among them.