Key Takeaways
- • Soft vs hard declines — Use the codes or messages your platform exposes to set retry logic and dunning timing.
- • Three levers — Retry logic, dunning, and authorization optimization.
- • Recovery rate — Use the 4 outcomes (Recovered, Churned, Pending, Active Churn Impact) for accurate reporting.
Passive churn isn't real churn—it's recoverable revenue. When a payment fails, the customer didn't cancel. They still want your product. The problem is friction, not intent.
PASSIVE CHURN ≠ REAL CHURN
It's recoverable revenue, not cancellation. For a concise overview of both churn types, see our churn guide; for multi-channel recovery sequences, read dunning best practices.
Understanding Payment Failure Reasons: Soft Decline vs Hard Decline
Payment failure reasons fall into two categories that require different recovery strategies. Soft declines are often temporary (e.g. insufficient funds, temporary holds, or technical/network issues) and can sometimes be resolved with a retry. Hard declines are permanent (e.g. expired card, invalid card, account closed, or “do not honor”) and won’t succeed with a simple retry—the customer usually needs to update their payment method. Your subscription platform or payment processor will show either numeric codes or human-readable messages; use your provider’s documentation to map them to soft vs hard so you can set retry and dunning logic correctly.
Platform Differences: Error Codes vs Messages (and Why They’re Obscured)
What you see in your subscription or Shopify admin is not the same as the raw decline codes from the bank. Each subscription platform normalizes, maps, or rewrites those responses—and some expose numeric error codes (e.g. Ordergroove, Shopify) while others expose only human-readable error messages (e.g. Recharge, Loop, Skio, Stay AI). The underlying bank/processor codes (e.g. ISO 8583 or network-specific codes) are often more granular than what the platform shows you.
Shopify and subscription management software also intentionally obscure some decline reasons. Exposing every precise bank code would let fraudsters run stolen cards through failed charges and learn exactly which codes mean “insufficient funds” vs “invalid card” vs “stolen.” That would make it easier to test which cards are still valid. So platforms often collapse several bank codes into a single generic decline or message, or omit the most sensitive ones. Your retry and dunning logic should be built around the codes or messages your platform actually exposes—and when in doubt, treat ambiguous or generic declines as hard declines and start dunning.
Where to find the codes or messages your platform uses:
- Ordergroove — Error response codes (numeric): Error Response Codes
- Recharge — Decline messages (not codes): Understanding order error messages
- Loop — Payment error messages: Payment errors
- Skio — Payment error messages: Payment errors
- Stay AI — Billing failures and error messages: Using the Billing Failures report
Why Decline Analysis Matters
Most brands never look past “payment failed.” But reviewing the failure reasons your platform provides (codes or messages) reveals patterns that inform retry logic and dunning. A customer with insufficient funds needs different timing than someone with an expired or invalid card.
A well-designed recovery strategy can significantly improve how much failed revenue you recover.
The Three Levers to Recover Payments
1. Payment Retry Strategy Based on Decline Type
Your retry strategy should adapt based on whether the failure is a soft or hard decline (using the codes or messages your platform exposes). One-size-fits-all retry logic leaves money on the table.
Soft declines – adaptive retry strategy
Card network retry limits: Visa, Mastercard, and Amex typically allow a limited number of retry attempts for soft declines before requiring customer intervention (e.g. updating the card). Use that window strategically.
- Insufficient funds (when your platform indicates it): Retry every 2–3 days for multiple attempts. Time retries around common pay dates (e.g. Fridays, 15th and 30th of the month, or early in the day when balances may have updated).
- Technical or network errors: Retry soon (e.g. immediately, then again in 1–2 hours if it fails). These are usually temporary.
- Generic or “do not honor” (when your platform shows it as soft): Can indicate token or auth issues. Retry once, then start dunning if it fails.
- Temporary hold: Retry within 24–48 hours, then every few days if needed.
- Consider waiting to start dunning until you see 2–3 consecutive declines, so you don’t over-contact for one-off glitches.
Hard declines – move to dunning
- Generic or “do not honor” (when your platform treats it as hard): Often card restrictions or account issues. Start dunning right away.
- Expired card: One retry is reasonable, then dunning with clear “update your card” messaging.
- Invalid card, account closed, or similar: No retry; start dunning immediately and offer alternative payment methods where possible.
2. Dunning
Dunning is sending communication to collect payments. Effective dunning connects with customers across multiple touch points: Email, SMS, website notifications, snail mail, and possibly phone calls.
High-quality dunning includes personalized flows based on product and failure type, pre-dunning for expiring cards, transactional email configuration, website banners and popups, simple card update UX, and multi-channel outreach.
3. Authorization Optimization
Other settings and tactics to improve authorization rates:
- Enable Auto-Account Updater: Automatically updates expired or replaced cards
- Encourage Higher-Auth Payment Methods: PayPal typically has better auth rates than credit cards
- Check Your MCC: Merchant Category Code can impact auth rates. Misclassification hurts performance
Platform Tools vs Shop-Specific Optimization
Subscription management platforms (Ordergroove, Recharge, Loop, Skio, and others) ship built-in retry logic, dunning emails, and sometimes store-facing prompts. That gets you most of the way—but those settings are usually one-size-fits-all. Retry schedules, message copy, and when you show a “update your payment method” banner are often the same for every merchant on the platform. Your shop is different: your product, your billing cycle, your customers’ pay patterns, and your brand voice. You can recover more by tuning retries (which days, how many attempts, and for which failure types), dunning communication (tone, channel mix, and timing that fits your audience), and store UX (where and how you ask subscribers to update payment—banners, account pages, checkout—so it feels native to your store instead of a generic prompt). That kind of optimization is shop-specific; the platform gives you the levers, but tuning them for your shop is how you maximize recovery.
How to Calculate Recovery Rate: Accounting for Natural Variance
Recovery rate calculation is more complex than dividing recovered payments by failed payments. You need to account for natural variance and active churn impact.
The 4 Outcomes Framework
Every failed payment results in one of four outcomes. Mapping these in a simple diagram (Recovered → Churned | Pending | Active Churn Impact) helps teams align on definitions and reporting.
The four outcomes:
- Recovered: Payment successfully retried or customer updated card
- Churned: Customer actively cancelled during recovery process
- Pending: Still in recovery window, outcome not yet determined
- Active Churn Impact: Customer would have cancelled anyway (not a recovery failure)
Recovery Rate Formula
True recovery rate excludes pending payments and accounts for active churn:
Recovery Rate = Recovered / (Recovered + Churned + Active Churn Impact)
Exclude pending payments from the calculation until they reach a final outcome.
Understanding Natural Variance in Churn
Natural variance refers to the normal fluctuation in recovery rates due to factors outside your control: seasonal patterns, economic conditions, customer behavior changes. Ignoring natural variance leads to false conclusions about recovery performance.
Perform a Decline Analysis
Most brands never look past “payment failed.” But reviewing the failure reasons your platform exposes is one of the highest-ROI retention steps you can take. Understand why payments fail, improve retry logic, tailor dunning messaging, spot processor issues early, and recover revenue you already earned.