Skip to main content

Trends, tech news, and tool comparisons.

How to handle failed payments in a SaaS (Stripe setup)

· 7 min read
Dealpuffin
Proof points and live coupons for early adopters

To handle failed payments in a SaaS, let your billing provider retry the charge on a schedule, email the customer a link to update their card, and decide in advance when access ends if the invoice stays unpaid. With Stripe Billing, the first two are dashboard settings and the third is one dropdown plus a webhook handler in your app.

This guide covers that setup for Stripe, based on Stripe's documentation read on 13 November 2026. The same three decisions apply to Paddle, Polar and others, though the settings are named differently.

Why failed payments deserve an afternoon​

A failed renewal is not a cancellation. The customer usually still wants the product: the card expired, the bank declined a charge it did not recognize, or the balance was short that day. If nothing happens next, the subscription ends anyway, and you lose a customer who never decided to leave. Early on, when you have 30 customers, losing three this way is a visible dent.

You do not need a recovery vendor for this. The defaults in Stripe cover most of it, as long as you check that they are on and wire up your own access rules.

The setup, step by step​

  1. Confirm Smart Retries are on. Stripe says it enables Smart Retries by default for new accounts. You find the setting under Billing, then Revenue recovery, then Retries. The default configuration is up to 8 retries within 2 weeks.
  2. Choose the retry window. You can set the policy to 1 week, 2 weeks, 3 weeks, 1 month or 2 months. A longer window gives a customer more time to fix a card, and it also means more days of unpaid service if you keep access on. Pick the window first, then decide what access looks like during it.
  3. Turn on the failed-payment email. In the revenue recovery email settings, enable "Send emails when card payments fail". Stripe then emails the customer after each failed payment with a link to update their payment method.
  4. Turn on expiring-card emails. Stripe sends an email one month before the default card on file expires. This catches the most predictable cause of failure before it happens.
  5. Choose what happens after the last retry. The options are to cancel the subscription, mark it unpaid, leave it past due, or pause it if it is eligible. Each is explained below.
  6. Listen for invoice.payment_failed. Stripe sends this webhook for each failed attempt. Use it to flag the account in your own database and show an in-app banner.
  7. Test the flow before real customers hit it. Stripe lets you test failed payment notifications in the dashboard, and our guide to testing Stripe webhooks locally covers the webhook side.

Sources: Stripe: Automate payment retries and Stripe: Automate customer emails.

What each end state means​

When retries are used up, Stripe moves the subscription according to your settings. According to Stripe's subscription lifecycle documentation, the states behave like this:

SettingSubscription statusInvoicesBest for
Cancelcanceled, a terminal stateCollection disabledSimple products where a new signup is fine
Mark unpaidunpaidKeep generating as drafts, no payment attemptsKeeping the record so the customer can come back and settle
Leave past duepast_dueKeep generating and charging per retry settingsProducts where you want to keep trying and decide access yourself
Pausepaused, if eligibleNo new invoices until resumedCustomers you expect to return

Stripe's own guidance on unpaid is to revoke access to your product, because payment was already attempted and retried while the subscription was past_due. During past_due, Stripe notes it might retry but that the status does not promise another attempt.

A rule we suggest: leave access on while the subscription is past_due and retries are running, show a banner, and cut access when it becomes unpaid or canceled. That keeps the grace period equal to your retry window, so it is a single number you chose on purpose.

Write the access rule in one place​

Your app needs one function that answers "can this account use the product right now?" Feed it the subscription status from Stripe, not your own guess. A minimal version:

function hasAccess(status) {
// trialing and active are in good standing; past_due is the grace period
return ["trialing", "active", "past_due"].includes(status);
}

Keep this check on the server. Update the stored status from webhooks, since Stripe tells you to monitor status changes to detect transitions to past_due or unpaid. If you also give discounts, remember that a coupon does not change any of this; see how to offer an annual discount in Stripe for the billing side.

Write a failed-payment email that gets a card updated​

Stripe's default email works. If you send your own, keep it short and specific. State that the renewal payment failed, the amount, the date access will pause, and one button that opens the page where the card can be updated. Stripe's emails link either to a Stripe-hosted page or to your own subscription page, and you choose which. Stripe notes that the hosted link stops working once the subscription becomes canceled, incomplete_expired or unpaid, so do not send a stale link after that point.

Skip the blame and the threats. "This sometimes happens when a card expires or a bank blocks a charge" is accurate and calm.

Cases people forget​

  • The first payment fails. For a new subscription, Stripe says Smart Retries and custom rules do not retry the initial payment while the subscription is incomplete. Your checkout must collect a working payment method, and the customer has 23 hours to pay before the subscription becomes incomplete_expired.
  • Bank debits. Direct debit methods retry under separate settings. For example, Stripe lists ACH Direct Debit as retryable for insufficient funds, with up to 2 retries over 40 days.
  • Which payment method gets retried. If you update the card, update the field where the previous payment failed. Stripe's example is a subscription with its own default_payment_method: if you only change the customer's default, Stripe keeps retrying the subscription's card.
  • Free trials without a card. If you let people start without a card, decide what happens at the trial end. Stripe can pause the subscription if there is no payment method, which beats a failed charge.

If you are still choosing plans, how to price a SaaS product at the early stage is the place to start.

A weekly check​

Once a week, open the list of past_due subscriptions. If an account has been there for days, reach out personally with a short note. At early-stage volumes, a human message from the founder will often fix a card faster than a fourth automated retry. Write down what you find: expired cards, bank blocks, or customers who simply did not want to continue.

Frequently asked questions​

How long should I keep retrying a failed payment?​

Stripe's default for new accounts is up to 8 retries within 2 weeks, and you can set the window from 1 week to 2 months. Two weeks is a reasonable starting point; shorten or lengthen it once you see how many customers recover late.

Should I cut access as soon as a payment fails?​

Most founders do not. A past-due subscription is still in the retry process, and an immediate cutoff turns a fixable card problem into an angry customer. Stripe advises revoking access when the status becomes unpaid, so that is a safer line.

Do I need a separate dunning tool?​

Not at the start. Stripe's built-in retries and customer emails handle the basics, and Stripe says it manages retry logic, dunning and status transitions for subscriptions. Look at specialist tools once failed payments are a measurable share of your revenue.

What if the customer cancels after a failed payment?​

Treat it as a normal cancellation and ask why. If the card was the only issue, offer to restart the subscription with a working payment method.