Replace DTC Dunning Failures: 3 Recovery Workflows 2026

Subscription revenue is only as reliable as your payment recovery system. Most DTC brands treat failed payments as an inevitable cost of doing business — a certain churn percentage per month that the finance team quietly writes off. That assumption is expensive.

Shopify Plus merchant GMV growth: 19% YoY according to the Shopify Plus 2024 Merchant Report (2024), driven largely by brands that retained more of the subscribers they already had rather than endlessly acquiring new ones. Payment recovery is the most overlooked retention lever in the DTC stack.

This post is a workflow recipe for automating the full dunning cycle — from the moment Stripe fires a invoice.payment_failed event through the final re-engagement SMS — using Recharge, Stripe, and Klaviyo in combination. Each of the 3 workflows below has a named trigger, a defined action sequence, and a measurable output.

TL;DR

Automated DTC dunning replaces the manual process of chasing failed subscription payments with a time-sequenced retry and outreach system. Done well, it recovers 20–40% of otherwise-lost subscribers. The three workflows are: (1) smart card retry sequencing, (2) customer-facing update campaigns, and (3) at-risk winback before hard churn.

Who This Is For

This guide is written for DTC brand operators running subscription products on Shopify Plus or similar platforms with at least $500K ARR in recurring revenue, 500+ active subscribers, and a working Recharge + Klaviyo stack.

Red flags: Skip this if you have fewer than 200 active subscribers (the audience segments are too small to sequence meaningfully), if you haven't set up a Recharge billing plan beyond the default retry logic, or if your average order value is under $25 (the margin math on recovery outreach changes significantly).

The Economics of Failed Payments

According to Baymard Institute's 2025 abandonment study, payment failure is the second-highest reason US consumers don't complete online checkout — and that friction pattern carries into subscription billing cycles. A card that expired at checkout will also fail on next billing day.

The cost compounds quickly. A subscription brand at $1.2M ARR losing 3% of active subscribers per month to involuntary churn — that is, churn caused by payment failures rather than active cancellations — loses roughly $36K monthly in recoverable revenue before a single dissatisfied customer has clicked "cancel." According to eMarketer's 2025 US retail ecommerce forecast, subscription commerce is growing faster than one-time purchase models, which means every churn percentage point represents more absolute dollars than it did three years ago.

The fix is not a better cancellation flow. It is a dunning automation that catches the failure at the payment event, retries intelligently, and contacts the customer with exactly the right message at exactly the right time.

Common Mistakes in DTC Dunning

Before the workflows, here is what most brands get wrong:

• Retrying too fast. Three retries in 24 hours trains card networks to flag the merchant. Space retries by 3–5 day intervals.

• Generic "update your payment" emails. These feel transactional and cold. Personalized subject lines referencing the specific product they're about to lose perform measurably better.

• Giving up after email. SMS open rates on dunning messages exceed 80%. If Klaviyo email day 1 doesn't convert, an SMS on day 4 frequently does.

• No account updater enrollment. Both Stripe and Recharge support automatic card updates when a bank issues a replacement card. Not enrolling in this program means avoidable failures.

• Treating all failed payments the same. A hard decline (card reported stolen) should not trigger the same retry as a soft decline (insufficient funds on billing day).

Workflow 1: Smart Retry Sequencing via Recharge + Stripe

The first and highest-leverage intervention happens before any customer communication: intelligent retry scheduling.

How It Triggers

When Stripe fires a invoice.payment_failed event, Recharge's dunning settings determine the next attempt. The default Recharge configuration retries on days 3, 5, and 7. That is reasonable but not optimal for all failure types.

Better approach:

HVAC note for ecommerce brands: the same principle that makes field service dispatch smarter — routing by context rather than by default — applies here. The decline code contains the routing signal. Read it.

Recovery Rate Benchmarks by Retry Configuration

Workflow 2: Customer-Facing Payment Update Campaign (Klaviyo)

The retry logic runs in the background. In parallel, a Klaviyo flow addresses the customer directly.

Sequence Architecture

Day 0 (failure event): Klaviyo receives the customer.payment_failed event from Recharge via webhook. An email fires within 2 hours with a subject line referencing the specific subscription product (not just "your payment failed"). The email body surfaces the exact product image, next skip/pause option, and a single prominent button to update the card.

Day 4: If no card update has been logged, a second email goes out. This one introduces social proof — "8,000 subscribers renewed this month" — and restates what they lose if the subscription lapses.

Day 7 (if still unresolved): An SMS via Klaviyo's native SMS channel fires a single message under 160 characters. Open rates on this step routinely exceed 80% across DTC brands, according to industry SMS benchmarking by Attentive's 2024 Mobile Commerce Report.

Day 12 (final): A "we saved your spot" email fires, combining urgency (offer expires in 48 hours) with a one-click reactivation link routed through Recharge's hosted payment page.

What Lands in the Operator's Hands

After 12 days, the Klaviyo dashboard shows a segment of "recovered" subscribers who updated their card and whose next Stripe charge succeeded. A second segment of "hard churned" subscribers feeds into a winback email list for Workflow 3. No manual follow-up needed; the segmentation happens automatically as Klaviyo receives Recharge event webhooks.

US Tech Automations connects the Recharge event stream to Klaviyo, enriches each event with subscriber lifetime value and at-risk score, and routes high-LTV subscribers into a premium-touch recovery branch where an AI agent drafts a personalized outreach referencing their order history. A subscriber who has placed 14 orders over 18 months gets a different recovery message than one on month 2. The orchestration layer handles that branching logic without requiring a Klaviyo flow per segment.

Worked Example: A $2.4M ARR Supplement Brand

A supplement DTC brand at $2.4M ARR runs 4,200 active subscribers at an average subscription value of $48/month. Their baseline involuntary churn rate is 3.2%, generating roughly 134 failed payment events per month. With the default Recharge retry config and a single generic "update your card" email, they recover about 22% of those — 29 subscribers per month, or ~$1,400 MRR saved.

After mapping each invoice.payment_failed event by Stripe's decline_code field and routing expired-card failures through account updater before any retry, their effective immediate recovery on that cohort jumps. The Klaviyo 4-touch sequence (day 0 email, day 4 email, day 7 SMS, day 12 final) runs automatically on the 78% of failures not caught by retry alone. Net recovery moves from 22% to 41% — an additional 25 subscribers per month, or roughly $14,400 additional ARR annually from the same payment failure volume.

Workflow 3: Pre-Churn Winback Before the Subscription Lapses

The most underused dunning workflow does not target already-failed payments. It targets subscribers whose cards are about to fail.

Predictive Signals

Three signals predict imminent payment failure with reasonable accuracy:

• Card expiration date within 60 days (Stripe surfaces this via card.expiry_month / card.expiry_year)

• 2+ consecutive logins without any activity or order on a subscription account

• NPS score below 6 from a post-purchase survey (fed into Klaviyo as a custom property)

The Workflow

When any of the above signals fire, a proactive Klaviyo flow sends a card-refresh prompt — not framed as a payment failure warning, but as "keep your subscription uninterrupted" language. The conversion rate on proactive card update requests (when a card hasn't failed yet) is consistently 15–25 percentage points higher than on post-failure recovery messages, according to subscription analytics published by ProfitWell's 2024 Subscription Benchmarks.

Subscribers who update before the billing date never hit the dunning sequence at all — their next charge processes cleanly. This is the highest-ROI dunning action a DTC brand can take.

Comparison: Recharge vs. Stripe vs. Klaviyo Native Dunning

Stripe's Smart Retry feature uses machine learning to pick retry timing based on success probability signals from Stripe's payment network. According to Stripe's published benchmarks, Smart Retry recovers 11–17% more failed payments compared to fixed-interval schedules. Enabling it in Stripe Billing settings costs nothing additional and requires no code change in Recharge.

Recovery rate with Smart Retry alone: 11–17% lift according to Stripe's 2024 billing documentation (2024).

When NOT to Use US Tech Automations

If your DTC brand is under $300K ARR, a dedicated orchestration layer is likely over-engineered. Recharge's native dunning + a Klaviyo flow manually built on their 3-step template will cover 80% of the recovery value for a fraction of the cost.

If you operate a single one-time-purchase product and subscriptions represent less than 15% of revenue, the ROI math on investing in dunning orchestration doesn't close. Address your higher-volume revenue stream first.

If your entire billing stack is Shopify Payments with no Recharge subscription module, the webhook architecture described here does not apply directly — you would need a different integration approach.

Glossary

Dunning: The process of communicating with customers whose payments have failed in order to recover the outstanding amount and retain their subscription.

Soft decline: A payment failure that can be resolved with a retry — typically due to insufficient funds, temporary network issues, or a bank flag that clears after a waiting period.

Hard decline: A permanent payment failure where the card cannot be charged regardless of retry timing — stolen cards, closed accounts, or fraud blocks.

Account updater: A network service (Visa Account Updater, Mastercard Automatic Billing Updater) that refreshes expired or replaced card numbers automatically before the next billing attempt.

Involuntary churn: Subscriber loss caused by payment failure rather than an active cancellation decision.

invoice.payment_failed: Stripe's webhook event that fires when a subscription charge attempt fails, containing the decline_code that identifies the failure type.

LTV (Lifetime Value): Total revenue a subscriber generates across their active subscription period — the key metric for prioritizing recovery spend.

Key Takeaways

• Automated dunning recovers 38–55% of failed subscription payments when retry, account updater, and multi-touch outreach are combined.

• Intelligent retry routing by Stripe decline_code outperforms fixed-interval schedules by 10–17 percentage points.

• Proactive pre-failure card update campaigns convert 15–25 points higher than post-failure recovery messages.

• SMS outreach on day 7 of the dunning sequence achieves 80%+ open rates, making it the highest-conversion single touch.

• US Tech Automations enriches Recharge event data with subscriber LTV to route high-value accounts into a personalized recovery branch automatically.

• Shopify Plus merchant GMV growth: 19% YoY according to the Shopify Plus 2024 Merchant Report (2024) — retention, not just acquisition, drives that number.

See the playbook.

Frequently Asked Questions

How long should a DTC dunning sequence run before marking a subscriber as churned?

Most brands run dunning for 14–21 days. Beyond day 21, recovery rates drop below 5% and continued messaging risks deliverability reputation. At day 21, mark the subscriber as involuntarily churned and move them to a winback campaign rather than continued dunning.

Does Recharge's native dunning replace the need for a Klaviyo flow?

No. Recharge's built-in dunning handles retry scheduling and sends a basic system email. Klaviyo adds multi-touch sequencing, SMS, personalization, and segmentation by LTV or subscription tenure. They solve different parts of the problem.

What is the single highest-ROI change for brands with basic dunning already in place?

Enrolling in Stripe's account updater service. This catches expired and replaced cards automatically before the billing attempt fails, eliminating the most recoverable failure type (expired cards) before they ever enter the dunning sequence.

Can the Klaviyo flow be triggered directly by a Stripe event, or does it require Recharge?

Klaviyo can receive Stripe events directly via a webhook integration without Recharge as an intermediary. If you use Stripe Billing for subscriptions without Recharge, the invoice.payment_failed event can trigger a Klaviyo flow natively.

How should brands handle subscribers who fail payment but are also considered flight risks (low NPS, low engagement)?

These subscribers should receive a shortened dunning sequence (7 days vs. 21) with a value-reinforcement email early in the sequence rather than just a payment update request. Recovery rates on low-engagement subscribers are lower, so reducing the time spent chasing them before routing to winback is operationally efficient.

What metrics should a DTC brand track to know if dunning automation is working?

Track involuntary churn rate (failed-payment churn as a % of total active subscribers), dunning recovery rate (recovered / total failed), and MRR recovered per month. Compare these to the 30-day baseline before automation was implemented.

Is SMS dunning compliant with TCPA for US subscribers?

Yes, if the subscriber opted into SMS communications at the time of subscription. Pre-existing SMS opt-in consent covers transactional billing messages. If you add SMS to a dunning flow, confirm that your opt-in capture at checkout includes explicit SMS consent language — this is a standard Klaviyo setup step.

Dunning ROI: Recovery Value at Different ARR Levels

Understanding the financial upside of improved dunning performance helps prioritize the investment. According to ProfitWell's 2024 Subscription Benchmarks, the median involuntary churn rate across B2C subscription brands is 2.8–3.5% of MRR per month — nearly all of which is recoverable with the right automation stack.

At $2.4M ARR, a 20-point recovery rate improvement recovers $14,400 in annual ARR that would otherwise be permanently lost — without acquiring a single new subscriber.

Take Action

The workflows described here — smart retry sequencing, multi-touch Klaviyo outreach, and pre-failure card update campaigns — are implementable in a weekend if your Recharge and Klaviyo stacks are already configured.

For brands managing multiple subscription product lines or high subscriber volumes, the branching logic by LTV and decline type that separates a 22% recovery rate from a 42% one is where orchestration becomes essential. US Tech Automations connects your Recharge event stream, enriches it with subscriber data, and routes each failed payment into the right recovery branch automatically.

Explore the pricing options to see which plan fits your current subscriber volume.

See the full automation stack at ustechautomations.com to connect Recharge, Stripe, and Klaviyo in a single orchestrated pipeline.

Related Resources

• Automate Shopify and ShipBob 3PL inventory sync — keep inventory and subscription fulfillment in sync alongside payment recovery

• Automate DTC bookkeeping with Shopify and QuickBooks — reconcile recovered revenue automatically in your accounting system

• Automate DTC supplier purchase orders on Shopify — close the loop between subscriber retention and supply chain planning