No heads-up on the first attempt, but there is on the second-to-last
You'll decide which payment retries in your payment processor happen silently and which one comes with a heads-up to the customer before the last attempt, with the notice text ready to use.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
You charge a card for a subscription, the charge fails, and you've got several retries scheduled in your payment processor (Stripe Billing, for example, set up separately). There's one decision that really shows on the outside: every time the card fails, do you tell the customer, or do you let the processor keep trying on its own?
If you send an alert on every attempt, you end up firing off three or four emails over an issue that probably clears up on its own. If you never alert at all, one day the customer finds the service down with no warning at all. Both approaches cost you customers, just in different ways.
The first failure isn't news
Most charges that fail the first time sort themselves out without anyone lifting a finger: a daily limit that resets overnight, a bank hiccup, a balance that's just a little tight that week. If you send an email every time this happens, you're warning people about something that's about to fix itself on the next scheduled attempt.
Worse still, a notice on the first failure sounds like an alarm. The customer reads "we couldn't charge you" and assumes something's wrong with their account or your business, when often the second attempt, a few days later, goes through without anyone ever knowing there was a hiccup.
That's why the first attempt, and any attempts in between if your schedule has more than two, run quietly. Your payment processor charges the card; if it fails, it retries on the date you set, and the customer doesn't hear a thing as long as there's still time for it to resolve itself.
The notice goes out before the last attempt, not on it
If you wait to notify until the last attempt has already run out, the notice comes too late: there's no scheduled date left where a new card could be charged. The customer reads that their service has been cut off, and their only option is to email you directly to get it reactivated, something a good number of them won't bother doing.
The moment a notice actually does its job is the second-to-last attempt: the one right before the final one. Say your schedule is day 0, day 3, day 6, and day 9. The day 6 attempt is the second-to-last, and that's when the email goes out. The customer still has the full three days before the day 9 attempt to log in and update their card. If you wait until day 9 to notify them, there's no day 12 on the schedule: the email can only say the service has already been cut off.
That email doesn't send itself: you send it, with a reminder set for the day of the second-to-last attempt, or your payment processor schedules it if it lets you set up an alert for failed charges. And like any email that depends on being opened and not landing in spam, yours works better coming from your own domain than from a free account.
- An email every time the processor retries, even when the failure is temporary
- Many customers stop reading them after the second one
- Can trigger voluntary cancellations out of fear of a problem that doesn't exist
- Silence while there's still time for the automatic retry to fix it on its own
- A single email, the one that actually matters, with plenty of days to act
- The customer connects that notice with something real, not background noise
Which one I'd pick: Send one notice, right when the second-to-last attempt fails, leaving the remaining days until the last attempt for the customer to react. Every other attempt stays quiet.
- Decided which attempts stay silent and which one gets a notice
- The notice fires when the second-to-last attempt fails, not the last one
- Ready-to-use base text for the notice email
- Coming up in the next lesson: exactly what the notice says depending on which attempt you're on