Dunning for Multi-Channel DTC: Thresholds and Failure Modes

Core Dunning Mechanics

Dunning begins the moment a payment fails. The failure triggers a state change in the subscription system - the customer is no longer active, but not yet churned. This window typically lasts 3 - 14 days depending on business model and payment processor rules.

The primary goal is to get the customer to update their payment method or resolve the underlying issue (insufficient funds, expired card, fraud block). Secondary goal is to maintain relationship and reduce involuntary churn.

Most Shopify stores using Stripe, PayPal, or Adyen can access native dunning tools, but these are baseline only. Multi-channel dunning requires orchestration across email, SMS, and sometimes direct outreach.

Retry Schedule and Thresholds

A standard retry schedule spans 3 - 5 attempts over 7 - 10 days. Each retry should be spaced 2 - 3 days apart to allow time for customer action (card replacement, account funding).

Threshold for escalation to manual review: if a customer has 2+ failed retries and has not updated payment method, flag for SMS or direct outreach. Threshold for cancellation: 3+ failed retries with no customer interaction over 10+ days indicates true churn risk.

Day 0 - 1: Automatic retry (processor-level, often silent)
Day 2 - 3: First customer-facing email (neutral tone, update payment method link)
Day 4 - 5: SMS reminder (if opted in) or second email
Day 7: Final email or SMS with urgency messaging
Day 10+: Cancellation or manual intervention decision

Multi-Channel Execution

Email alone recovers 20 - 35% of failed payments. Adding SMS increases recovery to 40 - 55%. In-app messaging (for app-based DTC) or push notifications add another 5 - 10%.

Channel sequencing matters. Email first (lowest friction, highest open rate for existing customers). SMS second (higher urgency, shorter window). Social or direct outreach only for high-LTV customers or repeat failures.

Personalization thresholds: include subscription value, renewal date, and specific reason for failure (if available from processor). Avoid generic 'payment failed' messaging - customers need clarity on next step.

Email: Clear subject line with 'Action Required' or 'Update Payment'. Include one-click update link. Test 2 - 3 variants (urgency vs. reassurance tone).
SMS: Keep under 160 characters. Include link to update payment. Only send to opted-in segments.
In-app or push: Show banner or modal on login. Direct to payment update screen.
Social: Retarget cart abandoners and failed-payment cohorts on Facebook/Instagram with update payment CTA (for high-LTV only).

Common Failure Modes

Failure mode 1: Retry logic too aggressive. Retrying every 24 hours exhausts processor limits and triggers fraud blocks. Result: customers locked out, recovery rate drops to 5 - 10%.

Failure mode 2: No payment method update flow. Dunning emails sent but no easy way to update card. Customers abandon instead of retry. Recovery rate stays under 20%.

Failure mode 3: Silent retries only. Processor retries happen but customer never receives notification. They assume subscription is active, then discover churn weeks later. Reactivation is harder than prevention.

Failure mode 4: Over-reliance on email. Unsubscribe rates spike if dunning emails are too frequent or poorly timed. SMS and in-app messaging are higher-intent channels for payment recovery.

Data and Monitoring

Track dunning metrics separately from general churn. Define: failed payment rate (% of renewal attempts that fail), recovery rate (% of failed payments recovered), and dunning-driven churn (% of cancellations that occurred during dunning window).

Benchmark: healthy DTC brands recover 40 - 60% of failed payments. Brands under 30% recovery typically have execution gaps (weak email, no SMS, poor payment update UX).

Monitor by cohort: new customers vs. repeat, high-LTV vs. low-LTV, and by payment method (card vs. ACH vs. PayPal). Failure rates and recovery rates vary significantly.

Failed Payment Rate = (Failed payments / Total renewal attempts) × 100. Target: < 3% for healthy processor relationships.
Recovery Rate = (Recovered payments / Failed payments) × 100. Target: 40 - 60%.
Dunning-driven churn = (Cancellations during dunning window / Total cancellations) × 100. Target: < 20% (rest should be voluntary or other reasons).

Payment Method Update UX

The update flow is the conversion funnel of dunning. If customers can't update payment method in < 2 minutes, recovery fails.

Shopify Billing and Stripe Billing both provide hosted payment update pages. Use these instead of custom forms - they handle tokenization and PCI compliance. Link directly from email and SMS.

For high-LTV customers, offer phone-based payment update or account manager outreach. Cost per recovery is worth it if LTV > $500.

One-click link from email to payment update page (no login required if using secure token).
Mobile-optimized form (Shopify Billing and Stripe Billing are mobile-first).
Post-update confirmation email or SMS.
Retry payment within 24 hours of update (don't wait for next scheduled renewal).

Processor and Compliance Constraints

Payment processors have dunning rules. Stripe allows 3 - 4 retries over 7 days before flagging account. PayPal has similar limits. Exceeding these can result in account review or suspension.

TCPA and CAN-SPAM rules apply to SMS and email dunning. Ensure SMS is sent only to opted-in customers. Email must include unsubscribe link (even for transactional dunning, best practice is to include it).

PCI compliance: never store full card numbers. Use processor-hosted payment update pages or tokenized forms only.

Questions

FAQ

What's the difference between dunning and churn prevention?

Dunning is reactive - it addresses failed payments after they occur. Churn prevention is proactive - it addresses voluntary cancellation before it happens (e.g., win-back campaigns, product improvements). Dunning is a subset of retention strategy focused on involuntary churn.

Should we retry failed payments automatically or wait for customer action?

Both. Processors automatically retry once or twice within 24 - 48 hours. After that, customer action (payment method update) is required. Retrying without customer update just generates more declines. Focus dunning effort on getting customers to update payment method, then retry once.

How do we handle customers who ignore all dunning attempts?

After 3+ failed retries and 10+ days with no customer interaction, mark as churned. For high-LTV customers (> $500 LTV), escalate to manual outreach (phone, email from founder/CEO). For lower LTV, accept churn and focus on reactivation campaigns 30 - 60 days later.

Can we use dunning to upsell or cross-sell?

No. Dunning is a recovery mechanism, not a sales opportunity. Mixing dunning with upsell messaging confuses the customer and tanks recovery rates. Keep dunning focused on payment update only. Upsell and cross-sell in separate campaigns to active, healthy customers.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo