Dunning for Seal Subscriptions merchants: recovering failed payments

Moorly guides · Updated August 2026 · 6 min read

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 options depend on your plan and settings version — treat your own 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

1. 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.
2. 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.
3. 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

1. Retry count and spacing — do the attempts spread across enough days to catch a payday or a bank-side hold expiring?
2. Exhaustion behavior — pause is usually safer than cancel; a paused subscriber can come back, a cancelled one rarely does.
3. Failure emails — is the card-update request sent promptly for hard declines, and does the update link work on a phone?
4. Merchant visibility — does anyone on your team learn about a failed renewal the day it happens?
5. A monthly failure review — even a manual export of failed and cancelled subscriptions beats not looking.

Moorly is an independent product by Velun Labs and is not affiliated with Seal Subscriptions s.r.o. Seal feature details vary by plan and version — always confirm against your own admin.