Dunning and Failed Payment Recovery

This package adds dunning to a custom or Laravel billing system: when a recurring payment fails, it retries on a schedule you set, emails the customer a secure link to update their card, gives a grace period, then suspends the service and reactivates it the moment payment succeeds. It is for subscription, hosting and service businesses that lose customers to expired cards rather than to cancellations.

Stripe Smart Retries or your own rules?

If you bill only through Stripe Billing, its built-in retries and emails may be enough, and the Stripe subscription setup packages configure them. This build is for billing that runs in your own system, across PayPal, Square, Authorize.Net or several gateways, or where suspension has to reach your app, server or network.

The sequence, step by step

• Before renewal, customers with a card about to expire get a notice to update it.
• On failure, the decline reason is read from the gateway. Business treats soft declines, such as insufficient funds, differently from hard ones, such as a closed account, which are not retried.
• The card-update link opens the gateway's hosted page, so no card number passes through your system.
• After the grace period the service is suspended, not deleted; payment restores it automatically.

Business also offers a pause or a cheaper plan before cancellation, and sends a weekly report of recovered, pending and lost revenue. Premium covers up to three gateways, uses the card account updater where your gateway offers it, and adds a task queue so staff can call high-value accounts personally.

Honest limits

Some customers will not pay however polite the emails are. Card networks also restrict retries on some decline codes, so the schedule follows those limits. Email and SMS sending costs are paid to your providers.