Dunning for Seal Subscriptions merchants: recovering failed payments
Seal Subscriptions has earned its reputation as a merchant-friendly subscription app, and it ships the dunning essentials: failed renewal charges can be retried on a schedule, and subscribers can be emailed about the failure with a link to fix their payment method. But "it retries" is not the same as "you're recovering everything you could." This guide covers what the built-in handling does, where it stops being your ally, and what to check in your own admin this week.
What Seal's built-in handling covers
- Automatic retries. Failed charges can be reattempted a configurable number of times with configurable spacing. Exact ranges depend on your own settings — treat your Seal admin as the source of truth.
- Customer notifications. Payment-failure emails can go out automatically, including a prompt to update the card on file.
- Exhaustion behavior. When the last retry fails, the subscription ends up paused or cancelled depending on configuration. This single setting decides whether a fixable failure becomes permanent churn — check which yours does.
Where the gaps are for you as the merchant
- The conversation skips you. Retries and reminder emails run between the app and your customer. Unless you go looking, a renewal that quietly fails — and quietly exhausts its retries — surfaces only as a smaller payout weeks later.
- One cadence, every decline. A fixed retry schedule treats an expired card (no retry will ever save it) the same as an insufficient-funds decline (a retry timed after payday often saves it). Our guide on why subscription payments fail breaks down why the failure reason should pick the treatment.
- No running dollar total. There's no ledger that says "failures cost you $X this month, retries recovered $Y." Without the number, dunning settings get configured once and never revisited — and the leak stays invisible.
Five settings to review this week
- Retry count and spacing — do the attempts spread across enough days to catch a payday or a bank-side hold expiring?
- Exhaustion behavior — pause is usually safer than cancel; a paused subscriber can come back, a cancelled one rarely does.
- Failure emails — is the payment-failure notification turned on at all, and does the update link work on a phone?
- Merchant visibility — does anyone on your team learn about a failed renewal the day it happens?
- A monthly failure review — even a manual export of failed and cancelled subscriptions beats not looking.
Where Moorly fits: Moorly sits alongside your subscription app — no migration, no checkout changes, and your existing setup keeps running exactly as it does now. It surfaces failed renewals on your side of the wall — Moorly takes Seal's billing-attempt webhooks and also polls as a backstop, so a missed delivery still gets picked up — emails you a weekly recovery summary, and (only when you turn actions on) works each failure by its reason while staying out of the way of the app's own retries. It starts read-only. Join the early-access list →
Moorly is an independent product by Velun Labs and is not affiliated with Seal Subscriptions. Seal feature details change — always confirm against your own admin.