← Blog

Dunning Management: How to Get a Failed Subscription Payment Paid

Dunning management for subscriptions: what to tell customers before and after a failed renewal, when to cut access, and how to tell recovery is working.

Dunning management is how a subscription business gets a failed or overdue payment paid. It covers four jobs: charging again at the right moments, telling the customer, giving them a quick way to fix their payment details, and deciding what happens to their access while all that runs.

A note on the word. In accounts receivable, dunning also means chasing customers for unpaid invoices. That's the sense behind questions about dunning in collections or in SAP. This guide is about the subscription meaning: a renewal on a saved card or bank account that didn't go through.

The retry side has its own guide. Payment Retries: Which Declines to Retry, When, and How Many Times sets out the schedule and the limits FloPay runs, so we won't repeat them here. This guide covers the rest of the loop, and how FloPay handles each part.

The loop, end to end

Each moment around a renewal has a job, and someone has to own it:

MomentWhat should happenWho does it with FloPay
Before the chargeRemind the customer that a charge is comingFloPay sends the email, if you switch it on
The renewal failsDecide whether to retry, set the card aside or check what happenedFloPay
While retries runTell the customer, and give them a link to fix their payment detailsFloPay sends the emails, if you switch them on
AccessKeep it, close it or restore itYour product, on FloPay's events
AfterwardsSee what was recovered, and what the emails brought backFloPay reports it, you read it

The sections below take these one at a time.

Before the payment fails

Some failures start before the charge: a customer forgets about a yearly plan, or a trial rolls into its first paid charge without them noticing. FloPay can send two reminders before a charge:

Each one also fires a webhook (subscription.renewal_upcoming or subscription.trial_will_end), even when the email is switched off, so you can send your own message instead. The settings are in the emails guide.

Here's what FloPay doesn't do before a charge today: it doesn't email customers about cards that are about to expire, and it doesn't run an automatic card updater. At the charge itself, a stale saved-card token is refreshed once from the vault before the next saved method is tried. The recurring billing software guide explains how that works.

When the renewal fails

The first decision isn't about messages. It's whether the failure can clear on a later attempt. A card reported stolen won't; insufficient funds might. Payment Retries sorts every failed renewal into three outcomes and gives the schedule for each plan. If you're looking at a single decline right now, Payment Was Declined is the faster read.

What matters for dunning is that everything else follows those retries. While they run, the subscription is past due. Your customer messages and your access rules should key off that same recovery campaign, not run on clocks of their own.

Telling the customer: three emails on the campaign's clock

FloPay sends three failed-renewal emails, each with its own switch:

  1. First failure: when a renewal fails for the first time.
  2. Retry failed: after each failed retry.
  3. Final notice: when the retries run out.

There's no separate email calendar. The emails go out on the recovery campaign's own rounds, so a customer hears about a failed retry when it fails.

Each email carries a button to your hosted manage page, where the customer signs in with a one-time code and updates their payment details. The customer fixes it themselves, and you build nothing. The next retry looks up their saved methods again, so a card they update mid-campaign can pay the renewal, as Payment Retries describes.

A failed monthly renewal on a timeline: the first-failure email goes out when the renewal is declined, a retry-failed email after each failed retry, and the final notice when the last retry fails and the subscription expires

The emails follow the campaign's own rounds. There's no separate email calendar to keep in step.

You can switch each email on or off, and rewrite it as your own template: save a draft, preview it, send a test, then publish. New merchants start with all three on. Existing merchants start with the retry and final emails off until they review them, so check your switches before you count on them. The emails guide has the switches, the templates and the variables each email offers.

When to cut access

FloPay never cuts a subscriber's access itself. Access lives in your own product, driven by FloPay's webhook events. Our advice is simple: a failed payment is not a reason to cut access.

A past-due subscription is still being worked. Cutting access on the first failure takes the service away from a customer whose card may clear on the next retry, or who is about to update it from the first email.

The same rule covers a charge whose outcome is unknown. FloPay holds that campaign for review and sends no expiry event while it's reviewed, so access stays on until there's an answer. The full event order is in the subscriptions guide.

Subscription states and what to do with access: active, past due and under review keep access, renewed keeps or restores it, and only expired closes it

FloPay sends the event. Your product decides access, and only expiry closes it.

How to tell it's working

Three places in FloPay show whether dunning is paying off:

Each week, compare the recovered count and revenue with your rebill totals. Then check the email log for failed-renewal emails that bounced or were suppressed. A customer who never gets the email can't update their card.

We don't publish a recovery rate yet, so you won't find one here.

What stays with you

FloPay runs the retries and sends the emails. A few things stay with you:

Choosing dunning management software

If you're comparing tools, start by running one failed renewal through each in a sandbox, as our recurring billing software guide describes. Then add three questions for the customer side:

The short version

See how FloPay recovers failed renewals, read the emails guide, or visit FloPay.