When a membership payment fails, most billing software sends an automated email and retries the card a few times — then gives up and writes it off. Real recovery means a person follows up: updating expired cards, calling the member, and when it comes to it, working directly with banks and card networks to recover the money. That human step is the difference between writing off lost revenue and actually getting it back.
That’s the short answer. The rest of this post is the long one — because the gap between “the software retried it” and “we got the money back” is the entire reason a company like ours exists, and it’s worth understanding before you choose who handles your billing.
We’re Member Solutions. We’ve been doing billing for businesses with recurring payments since 1991 — 35 years, 11,000+ businesses. So yes, we have a horse in this race. But the mechanics below are just true, regardless of who you pick. If you understand them, you’ll make a better decision either way.
The moment a payment fails: what software does vs. what a team does
A failed payment isn’t a single event. It’s the start of a fork.
Here’s the moment: it’s Tuesday, your billing run goes out, and a member’s card declines. Maybe it expired. Maybe the bank flagged it. Maybe the account was closed and a new card was issued and nobody told you. The money you were counting on this month didn’t arrive.
What software does next: It logs the decline. It sends the member an automated email (“your payment didn’t go through, please update your card”). It schedules a retry — often on a tuned interval, because retry timing genuinely matters. It may retry two or three more times over the following days. If a retry catches the charge, great — that one’s recovered automatically, and modern retry logic recovers a real share of declines this way. If the retries don’t catch it, the software’s job is essentially done. It waits for the member to log in and fix the card themselves.
What a team does next: Everything the software does — and then the part the software can’t. When the retries fail and the member goes quiet, a person picks it up. They find out why the payment actually declined, get the corrected information, and follow up directly until the payment is recovered or the account is genuinely resolved.
The first fork costs you nothing extra and recovers the easy ones. The second fork is where the stubborn money lives — and it doesn’t recover itself.
The automated-retry ceiling (why dunning emails plateau)
“Dunning” is the industry word for the automated email-and-retry sequence that fires when a payment fails. It’s a real tool and it works — up to a point. Understanding where it plateaus is the whole game.
Automated retries are excellent at recovering declines caused by temporary conditions: an insufficient-funds decline that clears once the member’s paycheck lands, a momentary bank-side hold, a network hiccup. Retry on a smart schedule and a meaningful chunk of those resolve on their own. No human required. This is genuinely good technology and every serious billing system should do it. We do.
But retries hit a ceiling, and the ceiling is structural, not a tuning problem:
- An expired card will decline on every retry. Retrying a dead card a fifth time doesn’t make it less dead. The card number has to change, and only the member or someone working on their behalf can make that happen.
- A closed account will decline on every retry. Same problem. The money is behind a door the software can’t open.
- A dunning email only works if the member reads it and acts. Plenty don’t. The email lands in spam, or gets ignored, or the member means to fix it and forgets. The automation did its job perfectly and still recovered nothing, because recovery depended on someone else taking an action they never took.
- A chargeback isn’t a decline at all — it’s the member’s bank pulling money back out after the charge succeeded. No retry logic touches it. Someone has to file a dispute, with evidence, inside a deadline.
So dunning plateaus. It clears the recoverable-by-retry layer fast, then flattens — because everything underneath that layer requires a human action the software cannot perform. If your only recovery tool is automation, the accounts in that bottom layer get written off. Quietly, every month. (If you want to see how far you can push the automated side before that plateau, our breakdown of professional payment reminder email templates covers the messaging that does the most work.)
What human recovery actually involves
Here’s the part no software company can write truthfully, because it’s labor, not code. This is what our billing specialists actually do when the automation runs out of road.
They call the bank. A decline code like “do not honor” tells you almost nothing on its own. A specialist gets on the phone with the issuing bank or the processor and finds out what actually happened: card reported lost, account closed, a fraud hold that needs lifting, a daily limit that was hit. You can’t act on a decline until you know its real cause, and the real cause usually isn’t in the decline code.
They update expired and reissued cards. When a card expires or is reissued, the number changes. Card networks run account-updater services that can supply the new credentials, and a person works that process — querying the updater, validating the new card, getting the membership back on a card that will actually charge. The automated email asks the member to do this. The recovery team does it.
They dispute chargebacks. When a member’s bank reverses a charge, you have a short window to respond and a specific format the bank will accept. A specialist assembles the evidence — the signed agreement, the usage record, the terms the member accepted — and files the dispute representment on your behalf, before the deadline. Miss the window and the money is gone for good. This is paperwork, deadlines, and bank procedure. It is not something an app does.
They call the member. Not an email — a phone call. A trained person, calling professionally on your behalf, so you’re not the one having an awkward “your payment bounced” conversation with someone who trains at your school or shops at your business three times a week. They sort out the new card or the new arrangement, and the relationship stays intact.
They handle the paperwork. Updated authorization forms, payment-plan arrangements for a member who’s behind but wants to stay, the documentation that makes the next charge succeed instead of bouncing again. Tedious, unglamorous, and exactly the work that turns a write-off back into revenue.
None of that is software. All of it is what “recovery” means once you get past the retry. It’s the work we built the company around — and it’s why we describe ourselves as a revenue-recovery service, not a billing app.
Recovery rates: the numbers, honestly
You’ll see big recovery percentages thrown around in this industry. We’re going to be careful here, because careful is the only honest way to talk about it.
What we can tell you straight: across our book, clients recover up to 19% more revenue from their delinquent accounts once a human recovery layer is working those accounts — compared to where they were before. That’s a real, measured figure from our own client base, and the word up to is doing honest work in that sentence: it’s a ceiling some clients hit, not a floor everyone clears. Your number depends on your mix of declines, your average ticket, and how stale your delinquent accounts already are when we start.
What we won’t do is invent a tidier stat. We’re not going to tell you “we recover X% of all failed payments,” because that number varies enormously by business and any single figure would be misleading. The 19%-more figure is the one we stand behind.
And the honest framing on why it’s not higher or lower: some failed payments are genuinely unrecoverable. A member who’s moved, gone bankrupt, or truly decided to leave is not a recovery case — chasing them harder just wastes effort and goodwill. Good recovery isn’t about squeezing every account to zero. It’s about reliably catching the large share that are recoverable but that automation alone leaves on the table. That’s the gap the 19% lives in.
What “automated recovery” really means on competitor platforms
Let’s be fair, because the alternative isn’t a strawman — it’s a legitimate model that works for a lot of businesses.
When a competitor platform says it does “automated recovery” or “smart retries” or “payment recovery,” here’s what that genuinely means, stated without spin: tuned retry logic that re-attempts declined charges on a schedule, automated dunning emails that prompt the member, and member self-service tools that let the member update their own card. Some platforms publish strong collection-rate figures behind this model, and those figures are believable. For businesses whose declines are mostly the recoverable-by-retry kind — and many are — this gets you most of the way there with very little coordination on your end. That’s a real advantage, and we won’t pretend otherwise. (We lay this out platform-by-platform in our Member Solutions vs ASF Payment Solutions comparison, where the recovery model is the deciding difference.)
Here’s the precise place that model stops, said plainly: it depends on the member acting. Automated recovery’s hard-decline path is “the member needs to log in and fix it.” When the member doesn’t — and on stale, stubborn accounts, many don’t — the automation has done everything it can, and the account waits. The platform isn’t failing; it’s doing exactly what it’s designed to do. It just isn’t designed to pick up the phone.
The difference between “automated recovery” and “human recovery” isn’t whether retries happen — everyone runs retries. It’s what happens after the retries don’t work. One model waits on the member. The other puts a person on it.
Why this is the whole reason Member Solutions exists
Most billing companies started as software companies and added a support team. We came at it from the other direction. We started as a billing service — people doing the recovery work — and built software around it. That ordering is the whole story.
It’s why, when a retry fails at your business, the next thing that happens is a trained specialist calling a bank, not an email sitting unread in a member’s inbox. It’s why chargeback disputes get filed before the deadline instead of quietly expiring. It’s why you can run your business instead of chasing declined cards.
We’re PCI-DSS Level 1 — the highest level of payment-security compliance — because we handle sensitive payment data for 11,000+ businesses every day, and the recovery work means our people are in that data constantly. We publish our price: $99/month, with transaction fees per transaction, and the recovery team included in that monthly fee, not sold as an add-on. We’ll tell you the number before you sit through a demo.
If automated retries and member self-service already keep your involuntary churn low, you may not need us — and we’d rather say that than oversell you. But if you’ve got a stack of failed payments quietly draining revenue every month — expired cards on members who’ve gone quiet, chargebacks nobody’s disputed, declines nobody’s diagnosed — that stack is exactly what our team works by hand. That’s the difference between writing the revenue off and getting it back.
If that’s the problem you’re trying to solve, the fastest way to see what’s recoverable in your own book is a free billing assessment — we’ll look at your actual situation and tell you straight.
