Dunning

Dunning is the automated process of recovering revenue from failed subscription payments. It encompasses Smart Retries|retry logic, customer communications (email, SMS), in-app payment walls, and Card Account Updater|card updater services. Dunning is distinct from collections in that the customer has not chosen to cancel — the failure is involuntary, meaning the subscription business loses a customer who still wants the product. This category of loss is called Involuntary Churn.

Scale of the problem

Failed subscription payments were expected to cost businesses more than $129 billion in lost revenue in 2025 (as-of 2025, Recurly/Slicker; Recurly press release; note: widely re-cited across vendor sources — original primary derivation not confirmed independently). (as-of 2025-09-28)
Involuntary Churn accounts for 20–40% of total subscription churn across subscription businesses (Chargebee blog, 2024-08-09; Slicker, 2025-09-28).
Subscription businesses lose an average of 9% of MRR to failed payments monthly, based on Baremetrics data across 148 businesses using their Recover product (Baremetrics, updated 2026-06-02). (as-of 2026-06-02)
As much as 10% of recurring revenue is at risk from payment failures — expired cards, network downtime, insufficient funds (Chargebee product page).
Approximately 6% of all card payments fail on first attempt (Chargebee blog, 2024-05-14). (as-of 2024-05-14)

The $129B figure (Slicker, 2025-09-28) and the 20–40% involuntary churn share (Chargebee, 2024-08-09) are 2024–2025 datapoints. No newer cross-industry benchmark was found as of this run.

Decline code taxonomy

Not all payment failures are equal. Decline Codes determine whether and how a payment can be retried.

Hard vs soft declines

Soft declines (insufficient funds, do not honour, credit limit exceeded) are retryable — the card is valid but the transaction failed due to temporary conditions (Churnkey State of Retention 2025; Chargebee product page).
Hard declines (stolen card, invalid card number, business closure) must not be retried — card issuers penalise merchants who attempt to retry hard declines (Churnkey, 2025).

Breakdown by cause (two methodologies disagree)

Churnkey (2025, 6 million failed payments across 1,000+ companies, $3B subscription revenue): insufficient funds = 42.3%; "Highest Risk Level" = 9.7%; "Transaction Not Allowed" = 8.5%; "Do Not Honor" = 8.1%; expired card = only 1.2%. Source: https://churnkey.co/reports/state-of-retention-2025

Slicker (2025-09-28, citing Recurly metrics): insufficient funds = 35%; expired card = 28%; changed card information = 22%; technical/gateway issues = 15%. Source: https://www.slickerhq.com/resources/blog/2025-involuntary-churn-benchmarks-b2c-subscription-brands

Churnkey uses raw issuer decline codes; Slicker appears to apply a higher-level classification that groups "changed card information" and "expired card" together — the taxonomies are not directly comparable.

Geographic variation (Churnkey 2024 data)

"Insufficient funds" as share of declines by country: Australia 81.4%; UK 66%; Germany 62%; US 50.1%; India 4.8%. India is dominated by "Transaction Not Allowed" at 62.2%, attributed to Reserve Bank of India subscription authentication policies (Churnkey State of Retention 2025; 2024 data). (as-of 2025-stale-risk)

Geographic decline data is from Churnkey's 2024 dataset. RBI subscription rules and UK/EU regulatory environments may have shifted.

Network retry rules (card scheme limits)

Card networks impose hard limits on retry attempts. Exceeding them incurs financial penalties.

Mastercard: maximum 35 retry attempts within 30 days. From January 2025, Mastercard raised its retry fee to $0.50 per transaction after 35 retries within 30 days (Checkout.com blog, ~2024-published, pre-January 2025 content). (as-of 2025-01)
Visa: maximum 15 retry attempts within 30 days. Exceeding these limits can incur fines as high as $15,000 (Churnkey State of Retention 2025).

Retry fee and fine figures are from 2024–2025 sources. Card network rules change; verify against current Mastercard and Visa operating regulations before relying on these figures.

Recovery rates

Industry benchmarks

Industry median recovery rate: 47.6% (Baremetrics, 2026; dataset size not specified). (as-of 2026-06-02)
90% of recovered transactions occur within the first 10 days of a failed payment — quality of early-window decisions determines the majority of outcomes (Recurly blog).
Optimised retry strategies improved recovery from ~53% to 71% without replacing any billing infrastructure (Recurly blog).
Top-performing subscription businesses reach 70–85% by layering multiple tactics: smart retries + Card Account Updater + email + SMS (Slicker, 2025-09-28). (as-of 2025-09-28)

By involuntary churn vertical (Slicker 2025, citing Recurly)

Monthly involuntary churn median by vertical: streaming/entertainment 2.1%; fitness/wellness 1.9%; ecommerce subscriptions 1.7%; SaaS/professional tools 1.3%. (as-of 2025-09-28)

Vertical benchmarks are Slicker's synthesis of Recurly data, published 2025-09-28. No 2026 cross-vertical benchmark was found.

By ARPC band

Monthly involuntary churn median: $5–15/month = 1.8%; $15–50/month = 1.5%; $50–100/month = 1.2%; $100+/month = 0.8%. At-risk threshold ≈ 2× median (Slicker, 2025, citing Recurly). (as-of 2025-09-28)

Smart retry technology

Smart Retries are ML-driven systems that predict the optimal timing and conditions for retrying a failed payment, replacing fixed retry schedules.

Stripe Smart Retries

Uses an AutoML ensemble trained on 500+ attributes across billions of transactions — customer, business, payment, seasonality, and billing signals; uses Sentence Transformers for multimodal (text + numerical) embeddings (Stripe engineering blog, 2024-01-23). (as-of 2024-01-23)
Considers time-dependent signals including how many devices have presented a given payment method in recent hours, and optimal local-time patterns (e.g. debit cards in certain countries succeed slightly more at 12:01 AM local time) (Stripe docs, undated).
Default policy: retry up to 8 times within 2 weeks; configurable from 1 week to 2 months (Stripe docs).
Stripe's own claim: 55% of failed payments recovered on average; $8.2 billion recovered across the platform in 2025. (as-of 2025)

Stripe (Stripe Docs, undated): 55% of failed payments recovered on average across Stripe Billing.

Third-party audit (Redux Payments, analysis of 200+ Stripe Billing B2C accounts representing $500M+ failed-payment volume): actual recovery rate consistently lands at 25–35%. Source: https://www.reduxpayments.com/blog/stripe-smart-retries-explained

The discrepancy may reflect different customer mixes (B2B vs B2C), different denominators (gross failed vs retry-eligible failed), or Stripe's inclusion of card updater recoveries in the headline figure.

Case studies (Stripe, 2024-01-23, stale-risk): Deliveroo recovered £100M+ using Smart Retries + card account updater + Adaptive Acceptance in one year; Retool recovered $600K+; Stripe claims $9 revenue recovered per $1 spent on Billing. (as-of 2024-01-23)

Stripe case study figures are from a 2024 blog post. Check current Stripe case study library for updated figures.

Practitioners (r/SaaS, 2026-06): "Stripe's smart retries in 2026 are reportedly recovering 45–50% of failed payments automatically before any email dunning — up from 30–35% two years ago. When we add our own email sequence on top we get to about 62%." (as-of 2026-06)

Adyen Auto Rescue

Part of Adyen's RevenueAccelerate suite. Uses ML to identify optimal days and times for retrying declined shopper-not-present transactions (subscriptions). Since implementing ML for auto retries in July 2021, Adyen reports a 300% increase in recovered payments (Adyen Knowledge Hub, undated). (as-of undated)

The 300% figure is anchored to a 2021 baseline and is on an undated page — recency uncertain.

Pinterest case study: 4% improvement in recovery rate on retried transactions using Adyen Auto Rescue, with expectation of reaching 10% (Adyen Knowledge Hub, undated).

Checkout.com Smart Dunning Retries

Analyses customer location, payment amount, issuing bank, and historical customer behaviour to schedule retries at optimal times for merchant-initiated transactions (MIT). Checkout.com reports rescuing 20% of payments entered into their dunning mechanism (Checkout.com docs and blog, undated). (as-of undated)

Chargebee Revive

Reads historical funding patterns and schedules retries for when funds are typically available — paydays, salary cycles, start of month — replacing fixed schedules with a per-transaction model using 200+ signals (Chargebee product page, undated). Supports up to 12 retries with up to 5 user-defined retry days; dunning emails run separately from retries to avoid customer spamming.

Recurly Intelligent Retries

AI/ML model drawing on 2,000+ merchants' data. Reported to have recovered $1.3 billion in otherwise-lost revenue, with 55.4% of merchants decreasing overall churn rates (Recurly product page, 2025). Q2 2025 release expanded smart retry logic to all direct debit methods (ACH, SEPA, BACS, BECS) and introduced AI-driven retries tailored for Shopify merchants (Recurly blog, Q2 2025). Fall 2025 release launched Recurly Compass — an AI subscription strategist powered by 15+ years of proprietary data capable of detecting involuntary churn anomalies (Recurly blog, 2025-10-16). (as-of 2025-10-16)

Card account updater

Card Account Updater services push updated card details directly from card networks to merchants before a payment attempt fails.

Silently recovers 15–20% of cards that would otherwise fail, before the payment is even attempted (r/SaaS, 2026-06, 71 upvotes on comment; Chargebee via Slicker, 2025). (as-of 2026-06)
The updater shows in Stripe dashboard as "cards automatically updated" — many merchants are unaware it is running (r/SaaS, 2026-06).
Findmypast case study: Account Updater + Recurly dunning campaigns contributed to measurable reduction in payment failure rate — previously zero visibility into why failures occurred (Recurly case study, 2023, stale-risk).

Findmypast and AllTrails case studies (Recurly, 2023) are pre-2024. Recurly's platform has evolved significantly since then.

Pre-dunning

Pre-dunning is proactive outreach before a payment fails — typically card expiry notifications sent 30–45 days before expiry.

Emailing customers 30–45 days before card expiry reduced payment failure rate by 18–22% before failures ever reached the dunning flow. "By the time a payment fails, you're already behind." (r/SaaS, 2024-09, 124 upvotes, stale-risk) (as-of 2024-09)

Pre-dunning effectiveness claim is from a 2024-09 thread — included because it is the only quantified pre-dunning practitioner report found and nothing newer covers the same ground.

Findmypast found that offering more payment methods at checkout achieved a 5% increase in payment conversions and a 19% increase in mobile registrations — reducing involuntary failure upstream (Recurly case study, 2023, stale-risk).

Dunning email sequences

Timing

First dunning email should arrive within 24 hours of payment failure (Baremetrics, 2026-06-02).
Sending the first email within 15 minutes of failure drove a 12% uplift in recovery from that email alone — "you catch people while they're thinking about it" (r/SaaS, 2026-06, 58 upvotes). (as-of 2026-06)
Optimal send window: Tuesday–Thursday, 9–11am local time; weekends should be avoided for early-cadence emails (Baremetrics, 2026-06-02).

Sequence length

Baremetrics Recover (2026): 7 emails over 27–30 days — Day 0, 3, 7, 10, 13, 20, 27. Day 13 described as "the most important email" — it lands before the typical Day-15 access cutoff (Baremetrics, 2026-06-02). (as-of 2026-06-02)
4-email Klaviyo sequence for Shopify/ReCharge (2025): Day 0, 2, 5, 8 → 34% recovery rate. Recommended to route through transactional email IP (Postmark/SendGrid) rather than marketing IP — deliverability improved from 89% to 97% after switch (r/shopify, 2025-04, 89 upvotes). (as-of 2025-04)
A 4–6 attempt retry schedule over 14–30 days generally produces the best recovery rates (Slicker, 2025-09-28).

Subject line copy

A/B test across ~50k sends (r/shopify, 2025-04, 44 upvotes): "Payment failed" = 18% open rate; "Action required: [Brand] subscription" = 24%; "We couldn't charge your card" = 31%; "Quick question about your [Brand] subscription" = 38%. Softest framing performed best. (as-of 2025-04)

Subject line A/B test is from 2025-04. Included as the only quantified dunning copywriting data available.

Channel mix

SMS vs email: SMS open rates typically 90–94% vs 20–34% for email; businesses using SMS alongside email report 15–20% higher recovery (Slicker, 2025-09-28; r/SaaS, 2026-06, 28 upvotes). (as-of 2025-09-28)
SMS compliance: TCPA in the US requires explicit SMS consent; practitioners recommend SMS as touch 3 or 4 only, never first, and only for opted-in subscribers (r/SaaS, 2026-06).
Mobile-first card update experience: 78% of dunning emails are opened on mobile (r/shopify, 2025-01, via Churnkey data). A mobile-friendly, login-free card update page drove recovery from 22% to 41% — credited for "roughly 60% of our improvement" in a multi-tactic programme (r/shopify, 2025-01, 112 upvotes). (as-of 2025-01)

Mobile-first and SMS recovery uplifts are 2024–2025 data. Included as no 2026 data covers the same angles.

LTV/tenure segmentation

Personal founder email at Day 5 for 6+ month or high-LTV subscribers achieved 61% recovery vs 34% on standard automated flow (r/shopify, 2025-04, 72 upvotes). (as-of 2025-04)
Customers who fail payment in their first 3 months churn 3x the rate of long-tenure customers — dunning effort should be disproportionately targeted at long-tenure subscribers (r/shopify, 2025-04).

Pause option

Including a "pause" option alongside the card update CTA in later dunning emails recovered an additional 8% of subscribers who would otherwise have churned — particularly useful where temporary financial stress causes the payment failure (r/shopify, 2025-04, 51 upvotes). (as-of 2025-04)

Deliverability

Dunning emails should route through a transactional email IP (Postmark, SendGrid), not the marketing IP — deliverability improved from 89% to 97% in one case study (r/shopify, 2025-04). (as-of 2025-04)

B2B-specific complexity

Generic dunning tools do not handle B2B well — the person who originally paid is often not the correct contact for card updates; a separate finance contact capture workflow may be necessary (r/SaaS, 2026-06, 64 upvotes; echoed in multiple 2024–2025 threads).

Platform landscape (as-of 2026-06)

Platform	Dunning capability	Practitioner sentiment
Stripe Billing (direct)	Smart Retries ML, card updater, 8-retry/2-week default, highly configurable	Recommended at any scale; Recovery settings "widely underutilised" (r/SaaS, 2025-02)
Recurly	Intelligent Retries ML, direct debit coverage, Compass AI (Fall 2025)	Preferred for subscription-first operations; AllTrails <1% involuntary churn
Chargebee	Revive (200+ signal ML), hard/soft decline routing, 12-retry limit	Positioning as full-stack subscription management
Checkout.com Smart Dunning	ML-scheduled retries for MIT, 20% rescue claim	European processor; less practitioner data available
Adyen Auto Rescue	ML retry timing, part of RevenueAccelerate	Enterprise-grade; Pinterest 4% uplift case study
Shopify native	Basic — 3 emails, standard retry schedule, limited customisation	"Adequate under 500 subscribers" (r/shopify, 2026-06, 38 upvotes); not recommended for scale
Skio	Best in Shopify ecosystem by practitioner consensus	"Best dunning tools in the Shopify ecosystem right now" (r/shopify, 2026-06, 45 upvotes)
ReCharge + Stripe	Inherits Stripe Smart Retries and card updater when Stripe is gateway	Confusion in community about what is inherited vs native
Churnkey	Precision Retries, email/SMS/failed payment wall, Billing Contact API	Worth it at $50k+ ARR; below that, Stripe default + own email is sufficient (r/SaaS, 2025-04)
Baremetrics Recover	7-email over 27-30 day sequence; 82% of users see ROI within month 1	Self-reported vendor data; n=148 businesses

Practitioners' consensus for Shopify DTC: decouple the subscription platform from the dunning comms layer — use Klaviyo (or equivalent) for dunning emails rather than the subscription platform's native email (r/shopify, 2026-06).

Platform capability comparisons are from 2025–2026 sources. Shopify, ReCharge, and Skio capabilities evolve frequently.

AI/ML scepticism

Practitioners in 2026 are sceptical of "AI dunning" vendor claims: "Most 'AI dunning' claims from vendors I've seen are marketing." The most credible ML application cited is merchant-level retry timing prediction — "almost nobody is doing it at the merchant level." (r/SaaS, 2026-06, 43 upvotes on post)

Contradictions

Custom retry logic vs native Stripe (ROI by ARR scale): One practitioner built custom retry logic and reached 58% recovery, arguing it was worth the engineering investment (r/SaaS, 2025-02, 67 upvotes). Another argues custom dunning ROI is low below $5M ARR — "save the engineering time for product" (r/SaaS, 2025-02, 48 upvotes). ARR scale appears to be the deciding factor, but no cross-company data exists to validate the threshold.

Stripe Billing direct vs ReCharge + Stripe: One operator reports recovery improving from 31% to 47% after switching to Stripe Billing direct (r/ecommerce, 2025-01, 73 upvotes). A commenter argues that using ReCharge with Stripe as the payment gateway already inherits Stripe's smart retries and card updater (r/ecommerce, 2025-01, 44 upvotes). A third voice concedes Stripe Billing direct is better but notes it requires engineering resources most DTC brands lack (r/ecommerce, 2025-01, 31 upvotes).

Key terms

Term	Meaning
Involuntary Churn	Subscription cancellation caused by payment failure rather than deliberate customer decision
Smart Retries	ML-driven retry scheduling that predicts optimal time/conditions for a retry attempt
Card Account Updater	Card network service that pushes updated card details to merchants before failure
Hard decline	Issuer decline that should never be retried (stolen card, closed account)
Soft decline	Issuer decline that may be retried after a delay (insufficient funds, do not honour)
Pre-dunning	Proactive outreach before a payment fails — typically card expiry notifications
Decline Codes	Issuer/network codes that classify the reason for a payment failure

Gaps in current coverage

SCA/PSD2 impact on European dunning: Under 3D Secure 2 (3DS2) and Strong Customer Authentication, retry eligibility for European recurring transactions is constrained — not covered in any source found for this run. Significant gap for UNIQLO Europe context.
BNPL failed instalment recovery: No sources found on dunning mechanics for buy-now-pay-later failed instalments (Klarna, Afterpay, etc.).
Fashion/apparel subscription-specific failure patterns: All quantified data covers SaaS or generic subscription boxes; fashion replenishment and DTC apparel subscription have different debit-card prevalence and ARPC profiles.
Enterprise retail at scale: Practitioner signal is almost entirely small/mid-market; no large-scale fashion retail (replenishment programmes, membership) dunning operations data found.