Card expiring soon
14 days before the renewal date, and once more 3 days before if the card is still the same.
The cheapest failed payment is the one that never happens, and an expiry date tells you it is coming.
Six failed payment emails you can copy today: a heads-up before a card expires, the first notice, a reminder, a final notice, a paused account and a thank you. Each comes with when to send it and why it works.
| When to send it | |
|---|---|
| Card expiring soon | 14 days before renewal |
| First notice after a failed charge | Day 0, when the charge fails |
| Friendly reminder | Day 3 or 4 |
| Final notice before pausing | 3 days before you pause |
| We paused your account | The day you pause |
| Thank you after recovery | The moment it is paid |
Time each email after a retry, so it can say what happened. Stop every email the moment the invoice is paid.
14 days before the renewal date, and once more 3 days before if the card is still the same.
The cheapest failed payment is the one that never happens, and an expiry date tells you it is coming.
The same day, as soon as the charge fails.
Hearing about it straight away, while nothing is switched off, is when fixing it feels smallest.
3 or 4 days after the first failure, once the first retry has also failed.
A second, shorter note catches the people who saw the first one and meant to deal with it later.
3 days before the date you pause or cancel, often 10 to 14 days after the first failure.
A clear date and a clear consequence give people a reason to act now, without a threatening tone.
On the day the account is paused, and not again after it.
Saying what stopped, what is safe and how to come back turns a lockout into an easy return.
As soon as the payment succeeds, whether a retry went through or the customer updated the card.
It closes the loop and tells the customer every reminder has stopped.
Anything in braces is filled in per customer. Map each one to the field your billing tool sends.
Retry schedules and recovery emails come on every plan, with a hosted page where the customer updates the card and pays in one go.
Three or four about a failed charge is plenty: one when it fails, a reminder a few days later, and a final notice before anything changes, then one note if you pause. More than that reads as pressure and teaches people to ignore you. The expiry heads-up and the thank you are extra, and both are welcome.
Space them over one to two weeks rather than retrying every day. Many declines are temporary, such as a limit or funds that arrive with a payday, so a retry a few days later often goes through without the customer doing anything. Time each email to follow a retry, so it can say what happened.
Pausing keeps the customer's data and makes coming back one payment away, which suits most subscriptions. Cancelling is cleaner for low-touch products. Whichever you pick, decide it once as a policy and say it plainly in the final notice.
Yes. yRecurring's emails are editable templates with a preview and a test send, so you can paste these in, adjust the wording to your voice and map the placeholders to the fields yRecurring fills in.
One link, straight to the fix. A page where the customer can update the card and settle the open amount without signing in does more for recovery than any wording.