Every hosting business loses revenue to failed payments. Cards expire, balances run out, banks decline, processors hiccup. The difference between a healthy and an unhealthy subscription business often comes down to one thing: what happens in the days after a payment fails. That process is called dunning, and getting it right can recover 60–80% of would-be lost revenue without any new customer acquisition. This guide shows hosting providers how to build a dunning system that recovers the most money with the least friction.
What Is Dunning, Really?
Dunning is the structured process of communicating with customers whose payments have failed and attempting to recover those payments. It is part technology (retries, payment updates), part communication (emails, in-app notifications), and part business policy (when to suspend, when to write off). Done well, dunning feels like a helpful nudge. Done poorly, it feels like harassment — or worse, the customer never realizes there was a problem until their service is gone.
The Anatomy of a Failed Payment
Not all failures are equal. Knowing the failure reason determines the right response.
- Soft declines — insufficient funds, temporary processor errors, suspected fraud holds. These often clear on retry.
- Hard declines — expired card, closed account, lost/stolen card. Retrying is pointless; the customer must update their payment method.
- Issuer-specific — some banks decline subscription charges if the cardholder has not whitelisted them. A good dunning email gives the customer the language to call their bank with.
Your billing platform should classify the response code on every failure and route it to the appropriate workflow. Treating every failure the same is the most common mistake in dunning.
Smart Retry Strategy
Retrying a failed payment is the single most effective recovery action, but only when done thoughtfully.
Retry cadence
A proven cadence for most hosting providers is something like: retry on day 1, day 3, day 5, and day 7, then stop. Daily retries can flag your merchant account as aggressive and raise decline rates over time. The exact spacing should be informed by your data — track recovery rate by retry day and tune accordingly.
Time-of-day matters
Many issuers approve more transactions during business hours in the cardholder’s timezone. Schedule retries for mid-morning local time when possible.
Stop conditions
Always honor a hard decline immediately. There is no point retrying an expired card, and doing so can erode customer trust if they see the attempts on their statement.
Network tokens
If your processor supports network tokens, use them. Tokens automatically update when a card is reissued, eliminating a large chunk of involuntary churn before dunning ever starts.
Pre-Dunning: Catch Failures Before They Happen
The cheapest failure to recover is the one that never happens. Pre-dunning is the practice of reaching out before a payment will fail.
- Email customers 7–14 days before card expiry with a one-click link to update.
- For annual subscriptions, send a renewal preview 30 days out with the upcoming amount.
- Notify customers when their stored card has been flagged as compromised by a network update service.
Hosting providers that implement pre-dunning typically see 30–50% lower involuntary churn on top of whatever their reactive dunning recovers.
Dunning Emails That Actually Work
Email is still the workhorse of dunning. Here is what high-recovery emails have in common.
Subject line
Be specific and helpful, not threatening. “We could not process your payment for [Service]” outperforms “URGENT: Payment Failed” almost every time.
Body
Explain what happened in plain language, what the customer needs to do, and how long they have. Keep it under 150 words. Include a one-click link to the customer portal where they can update payment without logging in through the front door.
Tone
Customers are people. Many failures are mistakes, not malice. A warm, slightly apologetic tone (“Sometimes cards just don’t go through…”) recovers more revenue than a stern reminder.
Cadence
One email per retry is usually enough. Layer in a final escalation 1–2 days before suspension, with a clearer warning of what is about to happen.
Multi-Channel Dunning
Email open rates are not what they used to be. The most effective hosting providers in 2026 layer multiple channels:
- In-app banners visible at every login.
- SMS for high-value accounts where the customer has opted in.
- Account manager outreach for enterprise plans above a revenue threshold.
- Push notifications via the customer portal where supported.
Each channel should respect the customer’s preferences and frequency caps. The goal is to reach the customer where they actually pay attention, not to bombard them.
Suspension and Termination Policy
At some point, retries and emails have not worked, and you must decide what to do with the service. Best practices:
- Define grace periods clearly in your terms of service: e.g., 3 days past due before warnings escalate, 7 days before service suspension, 30 days before termination.
- Suspend, do not terminate. Suspension is recoverable; termination usually is not.
- Preserve customer data through the grace period so reactivation is instant.
- Differentiate by product: a $5 shared hosting account and a $5,000 dedicated server warrant different timelines and different humans involved.
Customer Portal Self-Service
Every step of dunning should funnel toward the customer portal, where they can:
- See exactly which invoice failed and why.
- Update their payment method in seconds.
- Pay the outstanding balance with one click.
- Reactivate suspended services without contacting support.
The fewer steps between a customer realizing there is a problem and the problem being solved, the higher your recovery rate.
Measure, Tune, Repeat
Dunning is not a set-and-forget system. Track these metrics weekly:
- Involuntary churn rate — failed-payment customers who never recovered, as a percentage of total churn.
- Recovery rate by retry day — helps you tune the cadence.
- Recovery rate by failure code — reveals issuer- and processor-specific issues.
- Time to recovery — from first failure to successful charge.
- Email engagement — opens, clicks, and update completions.
Small tuning changes — a different retry day, a softer subject line, an added in-app banner — routinely produce 5–15% improvements in recovery.
Compliance and Sender Reputation
Dunning emails are transactional, but they still need to follow the rules. Include a physical address, an unsubscribe option for marketing follow-ups (not for the dunning itself), and authenticate your domain with SPF, DKIM, and DMARC. Hosting providers with poor email deliverability lose recovery before the first message even reaches the customer.
Dunning in FluxBilling
FluxBilling ships with configurable dunning workflows, smart retry scheduling that respects timezones and weekends, network token support through compatible payment processors, customizable email templates with merge fields, and a customer portal designed to make payment updates a single tap. Combined with pre-dunning notifications and detailed recovery analytics, that lets hosting providers reach the recovery rates that previously required a custom-built billing engine.
The Bottom Line
Failed payments are not a sign that customers want to leave — they are a sign that something small went wrong, and the customer needs help fixing it. A well-designed dunning system treats them that way. Hosting providers who invest in dunning can recover the equivalent of 5–10% of their MRR every year, year after year, without spending a dollar on new customer acquisition. There is no other lever in subscription economics that pays back so consistently.
Want to see automated dunning in action? Explore FluxBilling or start your free trial.
