Failed-Payment Emails Going Nowhere? Verify Your Stripe Customer Emails

Stripe's recovery emails only work if the customer's email works. When a card fails, Stripe can email the customer a link to fix it, but a mistyped gmial.com or a work address from a job they left means the email never lands, the retries run out, and the subscription lapses without the customer knowing. Export your customers, verify the addresses, and fix the invalid ones on active subscriptions before the next renewal run.

Sources, read 2 November 2026: Stripe's docs on automating customer emails (failed payment, expiring card, trial ending, renewal reminders, 60-day email logs) and sending customer emails (additional To and CC recipients, Dashboard only).

Which Stripe emails depend on the address

Email	When Stripe sends it
Failed payment	After each failed subscription payment, with a link to update the payment method
Expiring card	One month before the default card expires
Trial ending	Seven days before a free trial ends
Renewal reminder	Before renewal, for subscriptions that charge automatically
Unpaid invoice reminders	On your schedule, for invoices sent for manual payment

All of these go to the customer's email or the billing recipients set on the customer. None of them can reach a mailbox that doesn't exist.

How bad addresses get onto paying customers

• Typos at checkout. The buyer types the address once; nothing checks the domain.
• Duplicates. Stripe doesn't deduplicate customers by email, so one person can have several customer records, some with an old address.
• Job changes. A B2B subscription bought on a work address keeps billing after the buyer leaves. The card still works; the address doesn't. See the email verified as valid but the person left.
• Shared inboxes that close. billing@ aliases get removed during IT clean-ups.

Step by step

1. Export customers. In the Stripe Dashboard, open Customers, press Export and keep Email, Created, Total Spend, Delinquent and subscription status.
2. Merge duplicates. Upload unified_customers.csv to Stripe customers to email list. Records with the same email become one row, with spend added up and delinquent status kept. It runs in your browser.
3. Verify the emails on the verify page.
4. Fix invalid addresses on active subscriptions first. Those are the ones whose next failed payment email will vanish. Contact them through your app (in-app banner, account page) and ask them to update their email.
5. Add a second recipient on B2B accounts. In the customer's Details, untick "Same as account email" and add an accounts-payable address in CC. Stripe's docs say this is Dashboard only.
6. Check the email logs on the Customers page for anything already failing; Stripe keeps 60 days.
7. Check at signup from now on. A server-side check before you create the Stripe customer catches the typo while the buyer is still there; real-time verification on signup forms covers timeouts and when not to block.

What not to do

Don't delete or block customers whose result is risky or unknown. Catch-all company domains accept every address, so a single mailbox can't be confirmed, and many Microsoft consumer mailboxes (outlook.com, hotmail.com) don't answer mailbox checks reliably. Those customers are probably fine. Spend your effort on the invalid ones, and on delinquent customers whose address is also invalid; that pair is the likeliest silent churn.

Where SimpleVerifier fits

Verify your customer export on the verify page; the first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off, and includes API calls for checking at signup. See pricing and the API docs.