Help for owners
Customers' Stripe subscription renewals keep failing
Short answer
When a renewal fails, Stripe marks the subscription past due and retries by your settings. For new accounts it retries up to 8 times in 2 weeks by default. It cannot retry hard declines and authentication-required failures until the customer gives a new payment method. After the last retry your settings decide whether it stays past due, goes unpaid or cancels.
Does this sound like your situation?
- Many subscriptions show Past due or Unpaid.
- Customers say their card is fine but the renewal failed.
- Subscriptions got cancelled without anyone cancelling them.
- New customers start a subscription but it never becomes active.
- My site still gives access after a failed payment.
Why does this happen?
Some failures cannot be retried
Stripe does not retry when no payment method is available, when the bank returns a hard decline such as a lost or stolen card, or when authentication is required. Retries stay scheduled, but they run only once a new payment method appears.
Confirmed by docs.stripe.com
The new card was saved in the wrong place
Stripe retries on the subscription's default payment method first, then the customer's default. If you update only the customer field while the subscription has its own, Stripe keeps retrying the old card.
Confirmed by docs.stripe.com
Your retry and failure settings decide the outcome
Smart Retries is on by default for new accounts, up to 8 retries within 2 weeks. After the final attempt, a setting decides whether the subscription is cancelled, marked unpaid, left past due or paused.
Confirmed by docs.stripe.com
The first payment is a different case
A subscription starts as incomplete and the customer has 23 hours to pay. Smart Retries and custom retry rules do not retry that first payment while the subscription is incomplete, so your site has to ask the customer for a new method.
Confirmed by docs.stripe.com
Your site is not handling the events
Stripe tells your site about failures through events such as invoice.payment_failed. If the endpoint does not respond properly to invoice.created, Stripe delays finalising invoices for up to 72 hours, and a site that does not react gives access to unpaid customers or removes it from paying ones.
Confirmed by docs.stripe.com
What can I do about it today?
- Look at one failed renewal in StripeOpen the subscription and the invoice, and read the failure reason. A hard decline and a temporary decline need different action.
- Check your retry and failed-payment settingsIn the Dashboard under Billing, Revenue recovery and the subscription settings. Note what happens after the final retry. Do not change them mid-cycle without checking the effect.
- Contact customers with hard declinesAsk for a new card using Stripe's customer portal or your own page. Never ask for card numbers by email or chat.
- Check your webhook deliveriesOpen Webhooks in Workbench and look for failed events, especially invoice.created.
- Check who still has accessCompare active access on your site with subscription status in Stripe for the past due and unpaid ones.
When should I bring someone in?
- Failed payments are growing and revenue is dropping.
- Your site grants or removes access wrongly after payment events.
- Customers update their card and are still not charged.
How do I handle it?
- Sort the failures by reasonI group failed invoices into temporary, hard decline, authentication and mistakes in your own flow.
- Check the card update pathI make sure a new card is saved to the field Stripe retries on, and that customers can do it without contacting you.
- Fix the event handlingWebhooks respond fast, and access follows the subscription status and the paid invoice, not the first payment alone.
- Add customer messagesEmail prompts go out when a payment fails or authentication is needed, so customers can fix it early.
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?
Why did Stripe stop retrying?
After the final attempt in the schedule, Stripe makes no further payment attempts. Hard declines and authentication-required failures are also not charged until a new payment method exists.
What does Unpaid mean?
Stripe sets unpaid only when your settings choose it. The subscription remains but payment is no longer attempted, and it keeps creating draft invoices.
Is this the same as WooCommerce Subscriptions?
No. Stripe Billing runs the schedule itself. WooCommerce Subscriptions runs it from your store unless the gateway handles recurring billing, so the causes differ.
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.