A failed payment doesn't mean a customer wants to leave
Decide how many retries and reminders you send after a failed payment, and how many days of grace you give before cutting off service, then set it up in your payment gateway.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
The expired-card notice doesn't always arrive in time, and when it doesn't, here's what happens. It's the 15th and a customer's monthly charge fails. They haven't written, haven't called, haven't said a word. Do you cut off access that same night, send an email asking them to pay manually, or wait and see if next month sorts itself out?
The most expensive reaction is treating that failure like it's the customer's decision. Often it isn't: a failed payment can mean the bank blocked the charge that day, a spending limit got maxed out by another purchase, or an expired card hasn't been updated yet. What you're deciding today isn't whether the customer is staying. It's what happens between the moment the payment fails and the moment you actually know if they've left: how many times it retries on its own, what email they get in the meantime, and how many days you give them before cutting things off.
Why a payment fails (and why it's often not a goodbye)
A recurring charge can fail for a lot of reasons, and several of them have nothing to do with 'I don't want to pay you anymore.' Maybe there just wasn't enough in the account that particular day, the card expired, the bank flagged the charge as suspicious, or the card hit its spending limit.
All four of those can sort themselves out in a few days without the customer wanting to leave: the paycheck lands, the new card arrives and gets updated, the bank lets the charge through on a later try, or the customer raises the limit from their banking app without you having to do a thing. Your job isn't to convince anyone to stay. It's not letting go while the problem works itself out.
The retry schedule: how many times and when
Several of those reasons resolve themselves with a few days and a reminder, without you having to do anything else. That's what the retry schedule is for: it's not a list of tasks for you, it's a sequence you set up once in your payment gateway and that runs on its own. You set it up there, in Stripe Billing, for example, which you sign up for and configure separately, not in Yodai, which doesn't charge subscription fees or retry payments for you. In the gateway, you choose how many times it retries and how many days between attempts, whether the customer gets an email after each failed charge, and what happens to the subscription if it never goes through.
- 1Day 0: immediate alert
As soon as the payment fails, your gateway sends an automatic email letting the customer know the card didn't go through. It doesn't sound like a cancellation notice, it sounds like check this. - 2Day 3: first retry
The gateway tries the charge again on its own. If the issue's already been resolved by then, the payment goes through and that's the end of the story, no action needed from the customer. - 3Day 7: second retry and second alert
Another charge attempt, plus a more direct email that spells out what happens, and on exactly what date, if the card isn't updated. - 4Day 10: decision time
If it still hasn't gone through, that's when you act: pause or cut off access. But if you choose not to cancel it once the retries run out, the subscription stays alive, ready to charge again as soon as the card works.
Cut off right away, or give it a few days
The ten-day grace period isn't just being nice. It's a calculated bet: it costs you less to give a little extra service to someone who was going to pay anyway, than to lose someone who just had an expired card and would've paid within three days if you'd given them the chance.
- You stop giving service without collecting a single extra day of payment
- You lose customers who just had an expired card and would've paid within three days
- To continue, the customer has to sign up again like a brand-new customer, and they might not come back
- You recover the charges that failed for something temporary, without the customer having to start over
- You give a few days of service before you've actually been paid
- You need the retry schedule set up in your gateway, not reviewed customer by customer
Which one to pick: Give it some slack if your cost of serving those extra days is low: a membership, digital content, an appointment already on the books. Cut off sooner if every day without payment really costs you, like a physical product or a session with someone in front of you. There, you shorten the grace period to the first retry, without leaving access in between.
- The retry schedule, with its dates set (day 0, day 3, day 7, and day 10), ready to set up in your payment gateway.
- The notice email for when a charge fails, written before you ever need it.
- The grace period you've decided on: how many days of service you give before cutting off access, based on what each extra day actually costs you.
- What's still open is what happens when the customer asks to cancel on their own, not when a charge simply fails. That's what you'll decide in the next lesson.
Three cases to decide
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. A customer has had their charge fail on day 3 for two months straight, always due to insufficient funds. The third month comes around and it fails again. Do you apply the same retry schedule as the first time?
Not quite. A failure that repeats on the same day of the cycle, three months in a row, isn't a one-off incident anymore. It's a pattern. The automatic schedule keeps running, but on top of that, you reach out to them directly to suggest changing the billing date or the card on file, instead of counting on the bank to sort it out again.
2. You sell monthly boxes of a physical product, and a customer's charge fails on day 1. Do you ship the box anyway while the ten-day retry period runs?
Don't ship it until the charge goes through. The retry period is meant to avoid abruptly cutting off digital access, but a physical shipment is a cost you won't get back if the customer never ends up paying. In that case, shorten the grace period to the first failed retry on day 3, not the full ten days.
3. The day 7 email uses the same soft wording as the day 0 one: "it's usually an expired card, nothing serious." Do you leave it as is?
No. If the second notice sounds just like the first, the customer won't notice the deadline is closing in and won't update their card. The day 7 email needs to state the exact date access gets cut off if the issue isn't resolved, so the urgency shows up in the wording, not just in a schedule they can't see.
Retries, reminders, and a cutoff date take care of the customer whose card fails without them choosing it. The one who messages you to cancel isn't failing because of a card, and you don't treat that one the same way.
NextCancel now, cancel at the end, or pause: canceling has three ways out