Dunning Strategy
A step-by-step recipe for configuring Meridian's automated dunning engine to recover failed subscription payments without burning customer goodwill.
1. Trigger Rules
Define when dunning begins. Meridian fires the first retry 24 hours after a payment failure. Subsequent attempts follow an exponential backoff schedule capped at 7 days between tries.
2. Email Cadence
Craft a three-email sequence. Email one is a friendly reminder with a one-click update link. Email two surfaces the invoice. Email three warns of impending access loss. All emails are plain HTML rendered from your Meridian templates.
3. Grace Periods
Keep the license active for 14 days post-failure. Meridian caches an HMAC-signed grace token locally so the user never sees a hard block while billing resolves.
4. Final State
If all retries exhaust, Meridian transitions the license to expired and fires a webhook. You can optionally queue a win-back discount via the SellAuth integration.
Pro tip: Monitor dunning health on the analytics dashboard. A recovery rate above 65% is considered healthy for SaaS.