معالجة المدفوعات الفاشلة والتحصيل المتأخر

Subscriptions renew automatically, but cards expire, run out of funds, or get blocked. These involuntary failures are a major source of churn.

When a renewal charge fails, Stripe moves the subscription to past_due. The customer still has access while Stripe attempts recovery.

Dunning is the process of retrying failed charges and notifying customers to update their payment method, recovering revenue that would otherwise be lost.

Stripe's Smart Retries use machine learning to pick the best times to re-attempt a charge, instead of fixed intervals.

In Billing settings you choose how many retries to attempt and what happens after the final failure: cancel, mark unpaid, or leave past_due.

The webhook invoice.payment_failed tells you a renewal failed so you can react in your app.

Stripe can automatically send branded emails asking customers to fix their payment method, with a secure link to update the card.

Those emails point to the Customer Portal, where the user can add a new card and immediately retry the open invoice.

After the final retry, decide the consequence: canceled ends the subscription, while unpaid keeps it for later collection. Restrict feature access accordingly.

Track your recovery rate: the share of failed invoices that eventually get paid. Improving it directly grows revenue.

Use card-account-updater and warn customers before cards expire to prevent failures rather than only reacting to them.

You learned to handle failed payments and dunning:

• past_due status and Smart Retries
• invoice.payment_failed webhook handling
• Dunning emails linking to the Customer Portal
• Tracking recovery rate and preventing failures proactively