Soft decline retry: the failed-payment strategy most SaaS companies don't have

Your customer's credit card was declined. The card isn't stolen or frozen. The bank just said no—insufficient funds, daily limit hit, or an expired card the customer forgot to update. That is a soft decline, and it resolves on its own 40-60% of the time if you retry at the right moment. Most SaaS companies don't have a retry strategy. They send the failed-payment email, wait three days, send another email, and then suspend the account. The debtor was planning to pay. Their bank just wouldn't let them at 3 a.m. on a Sunday. Hard declines (fraud, stolen card, lost/stolen report) are a different problem—call the customer. Soft declines are a timing problem.

TL;DR: 15-30% of recurring payment attempts fail on the first try. A structured retry sequence within 3-5 days recovers 40-60% of soft declines. For B2B SaaS on NET terms and invoicing—no recurring card on file—the "retry" is a follow-up sequence with a call trigger at day 7 that resolves 2x faster than email alone. Most companies escalate too late, then wonder why the placement at 90 days no longer recovers.

Soft vs. hard: know the difference before you retry

The decline code the processor returns tells you what kind of problem you have. Insufficient funds, card expired, daily transaction limit exceeded, and temporarily restricted are soft declines—temporary conditions that usually resolve within hours or days. Stolen card, lost card, and fraud detected are hard declines: the customer needs to call their bank and get a new card issued before you can retry. Retrying a hard decline is pointless. Retrying a soft decline in the wrong window—retrying within 15 minutes of the first failure—is nearly as pointless, because the daily limit hasn't reset and the balance hasn't changed. The difference matters because most payment-retry systems send the same email for both, and that email is equally ignored.

What the data says about retry timing

Industry benchmarks on recurring payment recovery are consistent across payment processors and subscription platforms. Of first-attempt failures, 15-30% are soft declines. A retry window of 3-5 days after the initial failure recovers 40-60% of those. A second retry within 7-10 days recovers another 10-15%. Beyond day 14, recovery drops sharply: the card hasn't been updated, the customer has mentally moved on, or the amount has grown with late fees and the bank declines again.

The processor that attempts three retries inside 48 hours and then gives up is the common failure pattern. Three attempts at unhelpful times—all within the same daily-limit window or all on a weekend when the customer isn't checking email—is not a retry strategy. It is noise.

For B2B SaaS on NET terms: the retry is a different problem

Not every SaaS company charges on a recurring card. B2B SaaS with annual or monthly invoicing on NET 30/60/90 terms has no card on file. The invoice was sent, payment was expected, and it didn't arrive. The "retry" is a follow-up sequence—there is no payment gateway to re-submit the charge.

The first past-due notice goes out at day 1. Most companies send 3-4 automated emails over two weeks, then escalate to a human sometime around day 30. That two-week gap is where the recovery opportunity lives. The automated emails are read or ignored depending on who at the debtor company receives them. The person who receives the first past-due notice is rarely the person who approves payment. By day 7, the AP contact who opened the email has filed it. By day 14, it has left their mental queue. The escalation trigger at day 30 catches a debtor who has already decided this month's payment is next month's problem.

What a phone call at day 7 changes

Our data across thousands of B2B SaaS placements shows that a collector's call within 7 days of the first past-due notice resolves accounts 2x faster than email-only follow-up. Not because the call is aggressive—it shouldn't be at day 7. Because the call reaches the person whose job it is to approve payment, and because the acknowledgment moves the invoice out of "I'll get to it" and into an actual queue. An email can be ignored. A voicemail with a name and a direct number is harder to dismiss, and the callback confirms the invoice was seen.

The call at day 7 also surfaces the problems that email never surfaces: the CFO questions the renewal, the implementation was never signed off, the invoice went to a former employee's inbox. Those problems are resolvable at day 7. At day 45, after four automated emails and one internal escalation, they have hardened into a dispute that requires documentation and leverage. The difference between a 23.6-day resolution and a 90-day placement is usually that first conversation.

When automated follow-up is the right call

For low-value monthly subscriptions under $500, a phone call at day 7 costs more in labor than it recovers. The right strategy there is automated: a dunning sequence with 4-5 emails over 14 days, a suspension notice with a clear reinstatement path, and automatic placement at a set threshold. But for annual contracts, mid-market accounts, and any invoice over $2,000—which covers most B2B SaaS AR—the automated sequence is leaving money on the table. The email says "your invoice is overdue." The call says "I'm looking at this account, and I want to understand what happened." One is a system notification. The other is a partnership question.

The escalation trigger that works: day 7 call, day 45 placement

An effective B2B invoice-recovery sequence looks like this:

• Day 1: First past-due notice by email (automated, from the CSM or billing contact).
• Day 4: Second notice, same channel, stronger language—"We need your attention on this."
• Day 7: Phone call from a person who can answer questions about the invoice. Not a collector—a finance or accounts person who sounds like they work for the vendor. The goal is acknowledgment and a payment date, not a threat.
• Day 14: If no acknowledgment after the call, escalate to a third-party soft-notice program. This is when the vendor's relationship risk is highest, and the neutral third party absorbs it.
• Day 45: Full placement with a contingency collection agency. Recovery odds peak here for the pre-90-day window, and the agency carries the escalation from here forward.

What a placement at PCA looks like for a failed-payment problem

If your past-due invoice lands with us, the process is the same as any other commercial placement—free evaluation within one business day, investigation before we contact the debtor, and a specialist who understands that an unpaid SaaS invoice is different from a defaulted equipment lease. Whether the soft decline happened on a card or on a NET-30 invoice that never cleared, the resolution path is the same: find the person who can pay, and give them a reason to make it this month's priority instead of next month's problem. Same contingency pricing—25% on accounts under 12 months past due, 33% over, 40% on second placements. No recovery, no fee.