Failed payment recovery sequence: what are the steps, and what recovery rate is normal?
Home › Articles › Seam 07: Close to Payment › Failed payment recovery sequence
Updated 2026-11-01
A failed payment recovery sequence is the scheduled set of card retries and messages, each with a named owner, that runs from a declined payment until it is collected or written off. Stripe Smart Retries alone recovered 51% of failed payments in an average 5.5 days (Churnkey, 14 Nov 2025). Jon Weberg builds it for Seam 07: payment collection.
- A failed payment recovery sequence runs from the decline to collection or write off, with a named owner at each step.
- Insufficient funds caused 40.56% of failed payments in Churnkey's data; card errors such as incorrect number caused 4.69% (Churnkey, 14 Nov 2025).
- Stripe Smart Retries alone recovered 51% in an average 5.5 days; adding Churnkey retries recovered 55% in 4.8 days.
- Retries, a failed payment wall and dunning together recovered 70% of detected involuntary churn in Churnkey's data.
- Each dunning email recovered between 2.8% (the first) and 1.5% (the fifth).
- The sequence ends with a call on day 7 from the person the buyer already knows.
Three names on the processor's failed tab are buyers you remember from the closing call, and since insufficient funds sits behind 40.56% of declines, most are waiting for pay day, so you earned those installments, didn't you?
What is a failed payment recovery sequence?
A failed payment recovery sequence is the schedule of retries and messages that runs from a declined payment to collected cash. Default retries alone bring back about 51% of failed payments.
A declined installment is a sale still in progress, so how many declined last month, and how many of those buyers heard from a person within a day?
What should happen on each day after a card declines?
Message the buyer within minutes, retry on days 1, 3, 5 and 7, and call on day 7. Day 14 carries the final notice.
| Day | Retry | Message | Sender | Channel |
|---|---|---|---|---|
| 0 | No | Decline notice with the card update link | Collection owner | |
| 1 | Yes | None | Processor | None |
| 3 | Yes | Second email with the link | Collection owner | |
| 5 | Yes | Short text with the link | Collection owner | Text |
| 7 | Yes | Call | Closer on a first payment, collection owner after | Phone |
| 14 | No | Final notice with a stated final date | Collection owner |
Every row stops when the payment clears. Who on your team calls on day 7, and does the buyer know their name?
Why did the payment fail?
Insufficient funds causes 40.56% of failed payments, so most retries should land after pay days, not hours later. Churnkey (14 November 2025) counted 5.4 million failed payments across 25 million subscriptions in one year.
| Decline reason | Share | Retry? | Route to |
|---|---|---|---|
| Insufficient funds | 40.56% | Yes, on schedule | Retries, then the day 7 call |
| Transaction not allowed | 8.83% | No | Buyer, new payment method |
| Highest risk level | 7.99% | No | Collection owner |
| Do not honor | 7.56% | Yes, on schedule | Retries, then the day 7 call |
| Previously declined, do not retry | 6.44% | No | Collection owner |
| Incorrect number | 4.69% | No | Buyer, card update link |
| Expired card | 1.14% | No | Buyer, card update link |
If 40.56% of declines are an empty account, how many of your retries landed before your buyers' next pay day?
Which declines should you never retry?
Do not retry codes that say do not retry, lost card or stolen card; route them to a person for a new payment method. In Churnkey's data, previously declined do not retry was 6.44%, pickup card 0.94%, lost card 0.78% and stolen card 0.72%.
Which of your declines carried a do not retry code, and who asked those buyers for a new card?
What should each recovery message say?
Each message names what was bought, states the amount and date, and gives one link to update the card.
Day 0:
Hi [first name], your [amount] payment for [program] on [date] did not go through. It happens; here is a secure link to update your card: [update link].
Day 3:
Hi [first name], we tried your [program] payment of [amount] again and it is still open. One click fixes it: [update link].
Day 5 text:
[first name], [closer] here. Your [program] payment is still open. Update it here: [update link]
Day 14:
Hi [first name], your [amount] payment for [program] is still open. Please update your card by [date] so your place stays active: [update link].
Help with a payment reads as service to a buyer two days from pay day, so what does your first message say that your fifth does not?
How many dunning emails are worth sending?
Five emails each added between 1.5% and 2.8% recovery in Churnkey's data, with opens falling from 55.8% to 20.6%. By email: 2.8%, 1.9%, 1.7%, 1.5% and 1.5%.
Who should own a failed installment on a high ticket sale?
The closer owns the first payment and the day 7 call; one named collection owner owns everything after.
Your buyer said yes to the closer's voice, so the day 7 call from that voice is a favour, and a buyer whose card declined has not decided to leave, has she? Where cash flow is the obstacle on the next sale, the payment structure rung moves the dates before any card is charged.
What recovery rate should you expect?
Expect about half of failed payments back from default retries alone and up to 70% when retries, a payment wall and dunning run together.
| Setup | Recovered | Average days | Source |
|---|---|---|---|
| Stripe Smart Retries only | 51% | 5.5 | Churnkey, Nov 2025 |
| Churnkey retries plus Stripe | 55% | 4.8 | Churnkey, Nov 2025 |
| Retries, payment wall and dunning | 70% of detected involuntary churn | Not stated | Churnkey, Nov 2025 |
Churnkey sells retention software, its data is mostly software subscriptions, and no benchmark for high ticket installments was found, so if default retries stop near 51%, what is the other half of last month's declined amount?
How much of churn is failed payments?
Failed payments caused 15% of churn for order values of $1,000 to $10,000 and 24% above $10,000 in Stripe data reported by Churnkey. The share was 26% in business services and 24% in education.
If failed payments are 15% of churn at your order value, how many of last year's lost clients never decided to leave? Those who decided belong to winning back a customer who cancelled and to Seam 09: churn early warning.
What does an AI employee do in the recovery sequence?
An AI employee sends the day 0 message within minutes, logs every retry and reply, routes non retryable codes to a person and reports the recovery rate every Friday.
Tuesday at 9:12 am a $2,000 installment declines on insufficient funds, the day 0 email leaves at 9:13, and Friday after pay day the buyer taps the link and the log reads collected, while the AI employee never changes a price or waives a fee, so on Friday, who reports your recovery rate, and to whom?
Why does a declined card go unowned after the sale?
Sales books the win and moves on, and finance inherits a receivable nobody asked it to defend. The Thirteen Seams files it as Seam 07, Close to Payment.
"The card declined, they'll sort it out" is how the revenue seam between sales and finance sounds, and nobody on your team owns day two, do they? Tax Strategists of America collected $471,000 in new cash in 13 business days, because money that arrives the day of the yes never becomes a receivable, and Jon Weberg, Fractional President of a $70,000,000 a year business still running on the CRM he built, runs every lead, call and payment through one record where a decline is a task with an owner. Next month's Friday report then shows every declined installment with a status and a name. The install sets that up on your processor, from $30,000 for one seam, guaranteed at triple the fee, conditioned on proper tracking and reporting being in place.
- Click Book My AI Seam Architect Install (about 30 seconds).
- Choose a time and export last quarter's failed payments with decline codes (about 10 seconds).
- Confirm, and on the 45 minute call your unrecovered amount is priced and the sequence is mapped to your processor.
Questions about failed payment recovery sequences?
Is a failed payment usually the customer's fault?
Usually not. Four in five failed subscription payments are not the customer's fault, according to a survey of 200 executives (PYMNTS and Flex Pay, 2 May 2023). Write every message as help fixing a payment, not as a warning.
Should you pause a client's access when a payment fails?
Pause only after the day 7 call and a stated final date. A buyer in the middle of a program who loses access on day 1 often cancels instead of paying, a risk covered in Seam 08: onboarding handoff.
Should you text as well as email after a decline?
Yes. Churnkey's published data covers retries and email, with no SMS recovery figures (Nov 2025), so measure your own text recovery rate against email for four weeks.
When should you write off a failed payment?
After the day 14 final notice and one call that reached voicemail or the buyer. Record the reason so the next deal's deposit or payment terms change.
Does a deposit reduce failed payments?
A deposit collects part of the price while the buyer is still on the call, so less of the total rides on later cards. The pillar covers deposits in full.
How fast should the first message go after a decline?
Within minutes, while the buyer still remembers the purchase. An AI employee can send it the moment the processor reports the decline.
Jon Weberg is the founder of Profitalize and the originator of The Thirteen Seams, a revenue diagnostic that finds the money a company loses in the handoffs between its teams. About Jon Weberg
