Teams that move to Paddle often describe the decision in one relieved sentence: taxes and payments are handled. Both true, and both incomplete in a way that only becomes visible at the first failed renewal. A merchant of record absorbs the legal and tax surface of the transaction. The renewal still fails for the ordinary human reasons — cards expire, banks get cautious, subscribers miss email — and when it does, the recovery work lands in a shape the MoR model dictates, which is not the shape most teams picture during the migration demo.
What changes, concretely
The retry machinery is the platform's, tuned to the platform's whole portfolio rather than to your subscriber base. That is a reasonable default and a real constraint at the same time: your failure mix — annual plans with VAT invoices, say, or a base concentrated in a few issuing countries — is a rounding error in the portfolio the schedule was averaged over.
The customer relationship, meanwhile, remains entirely yours. A subscriber whose payment failed does not experience a platform; they experience your product going quiet. The emails they get, the grace they perceive, the moment they understand what happened — a practical account of dunning on Paddle separates which of those levers the MoR holds and which ones never left your desk.
Where the leverage actually sits
You cannot out-retry the platform, and trying produces the worst outcome: duplicate pressure on the same subscriber from two systems that cannot see each other. The leverage sits around the platform's sequence instead — in the warning subscribers get before a known-risk renewal, in the annual-plan pre-renewal notice that arrives while an invoice query can still be answered, in the winback path for accounts the platform sequence already closed.
Annual plans deserve special attention on this stack, because an annual failure is twelve months of revenue riding on one attempt window, and the pre-renewal conversation (new card on file? billing contact changed? invoice details still right?) is almost free compared to the recovery conversation after the lapse.
The support inbox is your early-warning system
On a merchant-of-record stack, your own support queue often learns about a dunning problem before any dashboard does. The tickets are phrased as confusion, not billing: a subscriber locked out mid-project, an annual customer holding an invoice in one currency and a charge attempt in another, a finance contact at a small company asking why the renewal paperwork does not match the quote. Each of those is a recovery opportunity with a human already attached — the highest-converting segment in all of dunning, because the subscriber has done the hardest part themselves by raising a hand. Teams that route these tickets to a generic queue with a two-day SLA routinely discover, months later, that their most recoverable failures were answered politely and lost anyway. The operational fix is small: a billing-aware tag, a same-day path, and a support macro that treats a locked-out subscriber as a renewal in progress rather than a complaint. It is also a useful diagnostic — if your MoR's reporting and your inbox disagree about how many renewals are failing, believe the inbox first and reconcile later.
The honest framing
A merchant of record is a trade: you exchange control over the payment machinery for freedom from its compliance surface. Good trades are made with open eyes. The teams that recover well on Paddle are the ones who mapped, before migrating, exactly which parts of dunning they were handing over and which parts were coming with them — because the second list is longer than the demo suggests.
Platform-by-platform recovery notes live at Swipe Again, built for the seams between billing platforms and the subscribers behind them.
Top comments (0)