Help for owners
Subscription payments keep failing and I am losing customers I did not mean to lose
Short answer
Customers who lose their subscription because a card failed did not decide to leave. Stripe retries failed payments automatically, but it does not retry some hard declines, and a retry cannot succeed until the customer supplies a new payment method. Recovery needs retries switched on, a clear email to the customer, and an easy way to update the card.
Does this sound like your situation?
- Subscriptions end with 'payment failed' and the customer never replied or complained.
- Customers say they never knew their card had failed.
- Cancelled subscriptions spike a few weeks after a card batch expires.
- I update the customer's card, but the old card still seems to be charged.
- Nobody on my side looks at the list of past-due subscriptions.
Why does this happen?
Retries are configured, but not for your situation
Stripe's Smart Retries are on by default for new accounts and retry failed payments at times chosen to improve the chance of success. A new account is set to up to 8 retries within 2 weeks by default. You can change the number and the period, or set a custom schedule of up to three retries.
Confirmed by docs.stripe.com
Some failures cannot be retried at all
Stripe does not retry when no payment method is available, when the issuer returns a hard decline code, or when the card is India-issued. For a hard decline the retries stay scheduled, but the payment only runs once you obtain a new payment method.
Confirmed by docs.stripe.com
The new card was saved in the wrong place
Stripe retries using the first available payment method in a set order, starting with the subscription's own default. If the customer's card is updated only on the customer record while the subscription has its own default, retries keep hitting the old card.
Confirmed by docs.stripe.com
When retries run out, your settings decide the outcome
After the last attempt, the subscription is cancelled, marked unpaid, left past due or paused, depending on your setting. After the final attempt Stripe makes no further payment attempts. If nobody chose this setting on purpose, customers may be cancelled that you would have wanted to chase.
Confirmed by docs.stripe.com
Your own system does not hear about the failure
A failed payment is announced by an event the website has to receive. If that is not handled, the customer keeps access or loses it at the wrong time, and nobody sends the reminder.
Technical detail: Stripe webhook: no signatures found matching the expected signature
What can I do about it today?
- Look at the past-due list todayOpen your payment dashboard and list subscriptions that are past due or recently cancelled for payment failure. Note how many there are and how old they are.
- Write to those customers personallyA short, friendly email with a link to update their card works better than waiting. Never ask for card numbers by email or chat.
- Check the retry settingsFind the retries page in your billing settings and confirm retries are on and what happens after the last one.
- Check the customer emailsConfirm that failed-payment and expiring-card emails are switched on and use your business name and a reply address that someone reads.
- Do not delete failed subscriptionsA past-due subscription still has the customer's history and can be recovered. Deleting it loses that.
- Keep notes on the decline reasonsA pattern of one reason, such as expired cards, tells you where to put the effort.
When should I bring someone in?
- Customers update their card but the subscription still shows past due.
- Access to your product does not match the payment state.
- You want reminders, a card-update page and a pause option built into your own app.
How do I handle it?
- Trace one failed subscription end to endI follow a single customer from the failed charge to the email, the retry and the final state, so I can see where the chain breaks.
- Check which card is actually retriedI compare the default payment method on the subscription with the one on the customer record.
- Make failures visible to your systemPayment events are received, checked for authenticity and written to your database, so access and reminders follow the real state.
- Add a clear way to fix the cardA customer-facing page or link for updating the payment method, with messages that say what happened and what to do.
- Report recovered versus lostA simple report shows how many failures were recovered and how many ended in cancellation, so the retry settings can be tuned with evidence.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
How many times will Stripe retry a failed payment?
For new accounts Stripe enables Smart Retries by default, set to up to 8 retries within 2 weeks. You can change this, or use a custom schedule of up to three retries.
Why was my customer cancelled even though retries were on?
Either the issuer returned a hard decline, which cannot be retried without a new payment method, or the retry period ended and your settings cancelled the subscription.
Can I make failed payments less common?
Not completely. Cards expire and banks decline. You can make recovery faster with timely emails and an easy way to update the card.
Does this apply to other payment providers?
The mechanics differ by provider. This page describes Stripe. For others I read their official documentation first.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.