Dunning Emails

Dunning emails are automated messages sent to customers following failed subscription or recurring payment attempts, designed to notify them of the issue and prompt corrective action such as updating payment information or authorizing a retry.

Purpose and Business Impact

Dunning emails serve as the primary communication channel for recovering failed recurring payments. When a charge fails due to insufficient funds, expired cards, or other decline reasons, these messages alert customers to the problem before service interruption occurs. Industry data suggests that properly timed dunning campaigns can recover 30-40% of failed payments that would otherwise result in involuntary churn.

The financial impact is significant: for a subscription business processing $1 million in monthly recurring revenue with a typical 9% payment failure rate, effective dunning can recover $27,000-$36,000 monthly that would otherwise be lost.

Timing and Sequence

Dunning email sequences typically follow a structured timeline coordinated with payment retry logic:

Immediate notification (0-24 hours): First email sent immediately or within hours of the initial failure, alerting the customer while the issue is fresh. This message has the highest open rate, typically 35-45%.

Reminder sequence (3-7 days): Follow-up messages sent before subsequent retry attempts, maintaining urgency without overwhelming the customer. Most payment processors including Stripe execute Smart Retries over 2-3 weeks, and dunning emails should align with this schedule.

Final notice (14-21 days): Last communication before subscription cancellation or service suspension, clearly stating consequences and providing a direct path to resolution.

Essential Content Elements

Effective dunning emails contain specific information that drives action:

Clear problem statement: The opening line explicitly states that a payment failed, avoiding ambiguous language like "there's an issue with your account."

Decline reason context: When available from payment processors, including the general category (expired card, insufficient funds, authentication required) helps customers understand the specific action needed. Stripe's decline codes like expired_card, insufficient_funds, or authentication_required can inform email content variations.

Direct resolution path: A prominent call-to-action linking to a secure payment update page, not requiring customers to navigate through account settings independently.

Service continuity information: Explicit statement of when access will be affected, removing uncertainty about grace periods.

Payment method preview: Last four digits of the failed payment method help customers identify which card needs attention, particularly valuable for users with multiple subscriptions.

Technical Integration

Dunning emails are triggered by webhook events from payment processors. Stripe sends invoice.payment_failed webhooks containing the failure details, invoice ID, and customer information needed to generate targeted messages. The charge.failed event provides additional context including the specific decline code.

Modern implementations use conditional logic to vary email content based on:

• Decline code category (hard vs. soft declines)
• Customer lifetime value or subscription tier
• Number of previous failures
• Time remaining before service interruption

Compliance and Tone Considerations

Dunning communications must balance urgency with customer relationship preservation. Failed payments are often legitimate temporary issues—expired cards account for approximately 25% of all declines—not intentional non-payment.

Emails should avoid accusatory language, maintain a helpful tone, and provide customer support access for questions. PCI DSS compliance prohibits including full card numbers or requesting sensitive payment data via email; all payment updates must occur through secure hosted pages.

Subject lines require particular attention: overly aggressive subjects ("URGENT: Account Suspended") may trigger spam filters or damage customer sentiment, while too-subtle subjects ("A note about your account") reduce open rates. Testing shows that straightforward subjects like "Payment update needed for [Service Name]" balance urgency and professionalism effectively.

Integration with Retry Logic

Dunning email timing should coordinate with automated payment retry schedules to avoid confusion. If an email states "we'll retry in 3 days" but the system attempts a charge in 2 days, customer trust erodes. Stripe's Smart Retries follow an adaptive schedule based on decline type and historical success patterns; dunning sequences should either reference this explicitly or provide general timeframes.

Some businesses pause retries after the first attempt until customers update payment information, making dunning emails the sole recovery mechanism. This approach reduces unnecessary decline fees but places full recovery burden on email effectiveness.