Bizzly
Operations

Recovering failed payments automatically

Around 9% of recurring subscription payments fail on the first attempt (Recurly Subscription Benchmark Report). How you handle these failures determines whether they become recovered revenue or involuntary churn. This page covers the causes, the recovery sequence, and the numbers.

Why payments fail and when
Smart retry timing explained
Dunning email sequence strategy
~9% of payments fail first attempt
Smart retry recovers ~24%
Expired cards are predictable and preventable
Based on Recurly benchmark data

Quick Answer

Around 9% of recurring subscription payments fail on first attempt. Left unhandled, each failure becomes involuntary churn. With automated retries over 3–7 days and timed dunning emails, a significant share recovers before the client notices. A well-configured dunning sequence eliminates the need for any manual payment follow-up.

Around 9% of recurring payments fail on the first attempt. Left unhandled, each failure becomes a cancelled subscription. Handled correctly, a significant share is recovered automatically before the client even notices. This page covers why payments fail, how the recovery sequence works, and what a well-configured dunning setup looks like for a service business.

Why subscription payments fail

Subscription payment failures fall into two broad categories: card-based failures and bank account failures. Each has different causes and different recovery approaches.

Card-based failures

  • Card expired: The most preventable failure. Stripe can request card updates proactively before expiry. Addressing expiry before the billing date eliminates this failure type entirely.
  • Insufficient funds: The most common failure on first-of-month billing dates. Retrying 3 to 5 days later when funds have replenished recovers a portion of these.
  • Bank fraud block: A bank flags the recurring charge as suspicious. The client needs to confirm authorisation with their bank. These require a client action and cannot be resolved by retry alone.
  • Card reported lost or stolen: Requires a full card update. Cannot be retried.

Direct debit failures

  • Account closed: The client has switched banks. Requires a new direct debit mandate setup.
  • Mandate cancelled: The client cancelled the direct debit directly at their bank. Usually deliberate; treat as an explicit cancellation unless the client re-establishes the mandate quickly.
  • Insufficient funds: Same as card. Retry in 3 to 5 days.

How Bizzly recovers failed payments

Bizzly runs two recovery layers in parallel when a subscription payment fails.

Layer 1: Stripe Smart Retry

When a payment fails, Stripe automatically schedules a retry a few days later. Bizzly includes that retry date in the failure email sent to the subscriber, so they know exactly when the next attempt is and can update their card before it happens.

Layer 2: Bizzly dunning cycle

Alongside Stripe's retry, Bizzly runs an escalating email sequence triggered daily by a scheduled job. Each message includes a direct link to the Stripe-hosted invoice page where the subscriber can update their card or pay the outstanding amount immediately.

Day 0Immediate email: Sent by webhook the moment the failure is detected. Contains the next Stripe retry date and a direct payment update link.
Day 3First reminder: "We wanted to remind you that your recent payment was unsuccessful." Friendly tone. Same payment link.
Day 7Urgent reminder: "Action required: update your payment within 7 days to avoid interruption." Subscriber website enters grace period (limited features).
Day 14Final notice: "Your subscription will be cancelled in 24 hours." Subscriber website suspended.
Day 15Cancelled: Subscription cancelled. Subscriber site set to inactive. Cancellation email sent with option to reactivate.

The data: what recovery looks like

Recurly's Subscription Benchmark Report found that approximately 9% of recurring subscription payments fail on the first attempt. With an automated dunning sequence, approximately 24% of those failed payments are eventually recovered. Without automated retry and communication, the recovery rate is significantly lower, as clients who do not receive a prompt update request are less likely to proactively fix the issue.

For a business with 50 subscribers at £80/month (£4,000 MRR), a 9% first-attempt failure rate means approximately £360 in at-risk revenue each billing cycle. Recovering 24% of that with automated dunning saves approximately £86/month compared to doing nothing. The cumulative effect over a year is over £1,000 in retained revenue that would otherwise be lost as involuntary churn.

Failed payments: common questions

Reduce involuntary churn with automated payment recovery

Bizzly includes smart retry logic and automated dunning sequences for all Stripe subscription payments. 14-day free trial.

14-day free trial
Cancel anytime
Setup in minutes
Failed Subscription Payments: Recovery and Dunning Guide | Bizzly