Resources

Paddle Dunning: The Complete Guide

If you bill on Paddle, you already have dunning — the question is whether it's a system you control or a set of defaults running inside someone else's platform. Paddle Billing ships a real native stack: automatic payment retries, and — through Paddle Retain, the recovery toolkit formerly offered as ProfitWell Retain — Payment Recovery with optimized retry timing, recovery emails, in-app prompts, and optional SMS. What it doesn't run is the full recovery playbook under your control: a decline-code-specific schedule as the organizing system, outreach you author per day under your brand, cancel deflection included in the same product and price, and one recovery view across every platform you bill on. This guide explains where Paddle's native dunning stops, what a dedicated recovery layer adds, and how to decide whether the gap is worth paying for.

What "Paddle dunning" actually is, out of the box

Dunning is everything that happens after a subscription payment fails: retrying the charge, telling the customer, getting a working card on file, and deciding when to stop. In Paddle, those jobs are split across three native pieces:

• Paddle Billing's automatic retries — when a payment fails for an automatically-collected subscription, the subscription moves to past due and Paddle retries the payment. Paddle's developer documentation is explicit about the baseline: if you use Paddle Billing without Retain, failed payments are retried up to seven times over a 30-day window before they're canceled.
• Payment Recovery, part of Paddle Retain — Retain's dunning layer, now accessible from the Paddle Billing dashboard. By default it also works over a 30-day period, and only for automatically-collected subscriptions; manually-collected subscriptions that go past due get no Retain action. It combines optimized retry logic, whitelabeled email outreach, and no-login payment method update forms, and at the end of the window it can pause or cancel the subscription for you.
• Tactical Retries and recovery notifications — Tactical Retries is Retain's timing layer: Paddle says it weighs payment method type, customer location, and more than fifteen other factors to retry at the moment most likely to succeed. Around the retries sit the prompts — recovery emails, in-app notifications delivered through Paddle.js when a customer is in your app or on your site, and SMS messages you can turn on through Paddle's setup process.

Around those sit two Retain features worth naming: proactive prompts that flag a card about to expire while the customer is in your app, and cancellation flows and term optimization — save offers at the cancel moment and prompts toward longer plans. Paddle's own update notes those two pieces have historically been hosted in ProfitWell, with Payment Recovery and Retain settings brought into the Billing dashboard first. One structural fact shapes everything else: Paddle is your merchant of record — the seller of record for the transaction, with tax, compliance, and the payment itself sitting with Paddle — and any recovery layer works alongside that relationship rather than replacing it.

Where native Paddle dunning stops

None of the above is a criticism of the machinery. It's a description of its shape — and the shape has edges:

• The timing algorithm is the system. Retain's native logic is organized around retrying at the best moment — Tactical Retries choosing when, based on signals across Paddle's network. But a failed payment is not always a timing problem. A replaced card, a closed account, a customer who never saw the email: those need a different play per decline cause, run as one coordinated sequence of retries and messages you can inspect and adjust. In native Paddle dunning, the decline cause informs Paddle's algorithm; it does not become a playbook you own. Paddle also handles the recovery email content — you can preview the messages, but you do not author one per day of your own sequence.
• Outreach follows Paddle's cadence, not yours. Retain sends up to four payment recovery emails, on its own schedule, plus in-app prompts where Paddle.js is installed and SMS if you complete its setup. That is a fixed program, not a sequence you design: no per-day branded email you control, and no voice step for the high-value account that never opens email.
• Cancel deflection is a separate Retain surface. The subscriber who clicks cancel while a payment problem is unresolved meets Retain's cancellation flows — a different part of the toolkit, with its own setup, historically managed outside the Billing dashboard in ProfitWell. Dunning and deflection are two halves of the same retention problem; in Paddle's catalog they are separate flows.
• It only sees Paddle. If you also bill anywhere else — a Stripe product line, a Shopify storefront — Retain's recovery view ends at Paddle's border, and so does its reporting. That is the trade built into a merchant-of-record platform: the recovery is deep inside Paddle and silent everywhere else.
• Attribution is recovery-rate centric. Native reporting tells you what Retain recovered and at what rate. It is not built to separate "recovered by anyone's efforts while a system was active" from "recovered because of a specific message or attempt" — the split you need to judge any recovery tool honestly, including this one.

What a dedicated recovery layer adds on Paddle

Swipe Again connects to Paddle and runs the recovery system as one sequence, coordinated with Paddle's native retries so the same customer is never worked by two competing schedules. Paddle stays your merchant of record and your billing system — subscriptions, invoices, taxes, and charges stay exactly where they are:

• A decline-code playbook, not a retry setting. Each failure is routed by its code: up to six attempts over roughly sixteen days for the declines that clear with timing (payday-aware for insufficient funds), a dedicated day 1 / 3 / 7 cadence for expired cards, and no blind retries at all for hard declines like lost or stolen cards — those go straight to asking the customer for a new card.
• Outreach beyond a fixed cadence. Branded email you control per day of the sequence, SMS on day 1 and day 7, and voice calls reserved for high-value accounts — every message carrying a secure, hosted card-update page under your brand.
• Cancel deflection in the same product. Reason-matched save offers — discount, pause, downgrade — presented at the cancel moment and applied to the subscription automatically. No second surface to configure, no separate pricing model.
• Backfill on connect. Connecting pulls in your last 90 days of failed payments, so recovery starts on the backlog already in your account, not just tomorrow's failures.
• One dashboard across platforms. If Paddle is one of several places you bill, every recovered dollar lands in the same view, split into Total Recovered and Directly Recovered, and attributed to the attempt or message that won it.

One decision has to be made explicitly before any of this runs: which system owns retries. Layering a second retry schedule over Paddle's without coordination is how customers get double-charged attempts and contradictory emails. Our engine coordinates with the native schedule rather than stacking on it — the same rule we'd tell you to apply to any tool you evaluate here, including ours. How that coordination decision works in practice is covered in our guide to subscription dunning software.

What it costs, and what the pricing models do at scale

Paddle's pricing is all-inclusive transaction pricing, and Paddle presents Retain as Billing's built-in toolkit at no extra cost for Billing users — there is no separate Retain list price on Paddle's pricing page. Outside that bundle, Paddle describes Retain's model as performance-based, priced around what it recovers rather than as a published flat rate you can model in advance. Swipe Again is one flat price — $179/month, or $1,799/year — with dunning and cancel deflection in the same plan and no percentage of recovered revenue, ever. The full breakdown is on the pricing page. The model difference matters more than the entry number: performance pricing scales with recovered revenue, while a flat fee stays where it started. Run any model at 3× your current failure volume before you sign — the math is in our best dunning software comparison and our review of failed payment recovery software.

And the flat fee carries the guarantee: recover $179 in your first 30 days, guaranteed — or Swipe Again is free the next 30 days. Recovered revenue means every failed payment collected while Swipe Again is active, from any recovery source, as defined in Section 3 of our Terms. How we count: how Swipe Again counts recovered revenue

Frequently asked questions

Should I turn off Paddle's native retries or Retain Payment Recovery?

You don't have to choose on day one. Swipe Again coordinates with Paddle's native retries so schedules never collide; many merchants simplify to one schedule once they've seen the attribution. What you should never do is run two uncoordinated retry engines on the same failure.

Does Swipe Again replace Paddle Billing or the merchant-of-record relationship?

No. Paddle remains your merchant of record and billing system of record — subscriptions, invoices, tax handling, and charges stay there. Swipe Again is the recovery layer that works the failures Paddle surfaces: retries, outreach, card updates, and cancel deflection.

How is this different from Paddle Retain?

Retain is a built-in toolkit centered on optimized retry timing and Paddle-managed messaging. Swipe Again runs the whole recovery system around the retry — a decline-code playbook you can inspect, email, SMS, and voice outreach you control per day, a hosted card-update page under your brand, and cancel deflection in the same plan — and reports total recovered versus directly recovered, separately. They answer different questions: "when should this charge be retried?" versus "what does it take to get this subscriber paying again?"

What about Retain's cancellation flows?

Retain's cancellation flows are Paddle's native option, and if cancel flows inside Paddle are your only gap, they are the place to start. Swipe Again includes cancel deflection — discount, pause, and downgrade offers applied automatically — in the same flat price as dunning, so the comparison that matters is the total cost and control of both halves together, not either piece alone.

The short version

Paddle's native dunning is a capable built-in stack: automatic retries in Billing, and Retain's Payment Recovery with tactical timing, emails, and in-app prompts on top. It is not a recovery system you control: the play doesn't reorganize around the decline code in a playbook you own, outreach runs on Paddle's cadence and copy, cancel deflection is a separate flow, and the view ends at Paddle's border. If your unrecovered gap is bigger than $179 a month, a dedicated layer closes it — and a 14-day trial on your own backlog will prove it. For the full recovery playbook, see our complete guide to recovering failed payments.