How to Recover Declined Recurring Payments
To recover declined recurring payments, sort every decline by its response code, retry only the soft declines on a spaced schedule, and route hard declines straight to the customer for a new payment method. Pair that with automatic card updating and a short, clear dunning sequence, and most of the revenue you are losing to failed renewals becomes recoverable.
Key takeaways
- Decline codes tell you what to do: soft declines (like insufficient funds) are worth retrying, hard declines (like lost, stolen, or closed accounts) are not.
- Retries are not free. Each attempt can carry a per-authorization fee, and card brands limit reattempts and can charge for exceeding those limits.
- Account updater services and network tokens fix many expired and reissued cards before the renewal ever fails.
- Dunning works best with a no-login update link, a short grace period, and a backup payment option such as ACH.
- Late recoveries of charges the customer forgot about can turn into chargebacks, so send a clear receipt and descriptor on every recovered payment.
Start with the decline code, not the retry
Every declined authorization comes back with a response code from the issuing bank. That code is the single most useful piece of data you have, and many subscription businesses never look at it. Pull a decline report from your gateway and group the last 90 days of failed renewals by code before you change anything else.
Soft declines mean the card may work later. Common examples are 51 (insufficient funds), 05 (do not honor, a generic refusal), 91 or 96 (issuer or system unavailable), and 65 (activity limit exceeded). These are where retries earn their keep.
Hard declines mean the card will not work no matter how many times you try. Examples include 41 (lost card), 43 (stolen card), 14 (invalid account number), 54 (expired card), and codes indicating the cardholder revoked authorization for recurring charges. Mastercard also returns merchant advice codes alongside some declines; a code meaning 'new account information available' tells you to fetch updated card details, and one meaning 'do not try again' tells you to stop. Hard declines go straight to customer outreach, not the retry queue.
A practical split for most subscription businesses: soft declines feed an automated retry schedule, expired and reissued cards feed account updater, and everything else triggers a request for a new payment method.
Retries are not free: the mistake most guides make
Most articles on this topic treat retries as a free lever: if one attempt fails, try again daily until it works. That advice costs money and can get you flagged. Each authorization attempt, approved or declined, can carry a per-item authorization fee from your processor and network fees from the card brand. Interchange is only paid on transactions that settle, but authorization-level fees apply to every attempt.
More importantly, the card brands have rules limiting how many times you can reattempt the same declined card within a set period, and they can assess fees per transaction for exceeding them. Retrying a hard decline even once can count against you. The exact limits differ by brand and are revised periodically, so ask your processor for the current numbers and configure your billing system to stay under them.
A sensible soft-decline schedule uses a small number of attempts spread over one to two weeks rather than daily hammering. For insufficient funds, timing attempts a few days apart, and near common pay cycles such as the 1st, the 15th, or a Friday, is a reasonable starting point to test against your own data. For 'issuer unavailable' style codes, a retry within hours often makes sense because the problem was temporary on the bank's side.
Make sure every renewal and retry is sent with the correct stored-credential and merchant-initiated transaction indicators, referencing the original customer-initiated transaction. Issuers use these flags to recognize a legitimate recurring charge, and missing them can cause avoidable declines.
Fix the card before the renewal fails
Expired and reissued cards are the most preventable source of failed renewals. Visa Account Updater and Mastercard Automatic Billing Updater let your processor check stored cards against issuer records and pull new expiration dates or card numbers when a card is replaced. Running updater checks a few days before each billing date catches changes before they cause a decline.
Network tokens go a step further. Instead of storing the raw card number, you store a token issued by the card network that stays valid when the underlying card is reissued, so the customer's subscription keeps working without any update on their side. Ask your processor or gateway whether network tokenization is available on your account and whether it applies to cards already on file.
For cards an updater cannot fix, send a pre-dunning email about two weeks before a known expiration date. A simple 'your card on file expires this month, update it here' message is the cheapest recovery you will ever make, because nothing has failed yet.
Run your own numbers
See how much subscription revenue slips away to declined cards each year and how much better recovery could win back.
Open the free Failed Payment Revenue Loss Calculator Book a 15-minute callDunning that actually gets cards updated
When a hard decline hits or soft retries run out, the customer has to act, and your job is to make that take under a minute. Send a direct link to a hosted update page that does not require a password reset. Every extra step loses people who were perfectly happy to keep paying.
Keep the sequence short and specific: a same-day notice that the payment did not go through, a reminder a few days later, and a final notice before access changes. Name the plan, the amount, and the date service will pause. SMS alongside email helps for businesses where customers rarely check the inbox tied to their account.
Decide your grace-period policy deliberately. Keeping access live for several days while you recover the payment avoids punishing customers for a bank issue, while pausing rather than canceling the account makes reactivation a single click. Offer a second payment method too; for B2B and higher-ticket subscriptions, an ACH or eCheck option on the update page sidesteps card expirations and credit limits entirely.
Worked example: what a better recovery rate is worth
Here is a made-up but realistic example. A subscription box company has 2,000 subscribers at $40 per month, or $80,000 in monthly recurring revenue. Assume 6% of renewals decline in a given month. That is 120 failed payments worth $4,800. If the company currently recovers 30% of them, it gets back $1,440 and loses $3,360 a month, about $40,320 a year.
Now assume better decline-code routing, account updater, and a tighter dunning sequence lift recovery to 55%. The company recovers $2,640 and loses $2,160 a month, about $25,920 a year. The improvement is roughly $14,400 a year, and that understates it, because a subscriber who churns this month also takes every future month with them.
The cost side is small by comparison. Using our tool's estimated assumptions for eCommerce (about 1.95% average interchange plus a 0.20% markup and a $0.10 per-transaction fee), a recovered $40 payment costs roughly $0.96 to process. Even four authorization attempts on each of the 120 declines at $0.10 apiece would be about $48. The real risk is not the fee on smart retries; it is brand fees and wasted attempts from retrying hard declines. Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting.
To run these numbers with your own subscriber count, price, decline rate, and current recovery rate, use our free Failed Payment Revenue Loss Calculator at https://touchsuite.com/tools/failed-payment-revenue-loss-calculator. It shows how much subscription revenue slips away to declined cards each year and how much a better recovery rate could win back.
Recover the payment without creating a chargeback
A payment recovered ten days late can surprise the customer, especially if they assumed the subscription lapsed. Surprised customers dispute charges. Send a receipt immediately on every recovered payment, and make sure your billing descriptor clearly shows your business name and, ideally, a support phone number or URL.
Watch your dispute rate after you tighten recovery. If chargebacks on recovered payments climb, shorten the retry window or require the customer to confirm before charging a payment that failed long ago. Rising disputes can lead a processor to review your account and, in some cases, apply a reserve or hold funds, which ties up the very cash you were trying to recover.
Finally, honor cancellations and revocations instantly. If a customer cancels or their bank returns a code indicating authorization was revoked, remove the card from every retry queue right away. Charging after a cancellation is one of the fastest ways to turn a recovery program into a dispute problem.
Frequently asked questions
How many times should I retry a declined recurring payment?
Only retry soft declines, and use a small number of attempts spread over one to two weeks rather than daily. Card brands limit reattempts on the same card and can charge fees for exceeding those limits, which vary by brand and change over time, so get the current limits from your processor and set your billing system below them. Never retry hard declines like lost, stolen, or closed accounts.
What is the difference between a soft decline and a hard decline?
A soft decline means the card may be approved later, such as insufficient funds, a generic 'do not honor,' or a temporary issuer outage. A hard decline means the card will not work again, such as a lost or stolen card, an invalid account number, or a revoked authorization. Soft declines go into a retry schedule; hard declines need the customer to provide a new payment method.
Does account updater fix every expired card?
No. Account updater only works when the issuing bank participates and reports the new card details, so some cards will still fail. Combine it with network tokens where available and a pre-dunning email before known expiration dates to catch the rest.
Do I pay processing fees on declined retry attempts?
You do not pay interchange on a declined attempt because nothing settles, but many accounts are charged a per-authorization fee and card network fees on every attempt, approved or not. Check your statement for authorization fees and any excessive reattempt fees to see what each retry costs you.
Should I offer ACH as a backup for failed card renewals?
For many subscription and B2B businesses, yes. Bank account payments are not affected by card expirations or credit limits, so offering ACH or eCheck on your payment update page gives customers a second way to stay subscribed. If you want help setting up retries, account updater, or ACH alongside cards, talk to a payments specialist at https://touchsuite.com/contact.
How we put this together
The decline response codes referenced here (such as 05, 14, 41, 43, 51, 54, and 91) come from the ISO 8583 messaging standard used across the card networks, and merchant advice codes are returned by Mastercard on certain declines; account updater and network token services are offered by the card brands through processors and gateways. The worked example uses made-up figures for illustration, and the processing cost uses the estimated assumptions in TouchSuite's tools (eCommerce average interchange of 1.95%, a 0.20% markup, and a $0.10 per-transaction fee), which are estimates only and not TouchSuite pricing. Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting. On your own statement, check whether you are billed per authorization attempt, whether any card brand reattempt or excessive retry fees appear, and whether account updater is listed as a service. Card brand retry limits and stored-credential rules are revised periodically, so confirm the current versions with your processor before changing your retry logic.
Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting.