Rechurn + Paddle
Paddle (Merchant of Record). Limited integration potential because Paddle's MoR model handles dunning differently than direct gateways.
Setup
- 1On the roadmap with caveats — Paddle's MoR model means dunning is partially handled by Paddle directly
- 2Best fit: complementary tooling for save offers and post-recovery analytics
Features
- Planned: Failed-payment notification ingestion
- Planned: Save offer flow on Paddle's customer-facing pages
Notes
If you're on Paddle, evaluate Paddle Retain first — it's free at lower volumes and tightly integrated. Rechurn's value is highest on Stripe and Stripe-like direct gateways.
Want to see what this looks like on your Stripe?
Paddle integration is in progress — sign up for the audit on Stripe to see how Rechurn performs, and we'll let you know when Paddle is ready.
Frequently asked questions
Is the Paddle integration live?+
Paddle is on the roadmap. Vote it up by joining the waitlist; we prioritize by request volume.
Does Rechurn replace Paddle?+
No. Rechurn sits alongside Paddle. Your billing platform stays the source of truth — Rechurn handles the recovery automation on top.
What data does Rechurn need from Paddle?+
Subscriptions, customers, invoices, and failed-payment events. We fetch via OAuth or API key with the minimum scope necessary. Tokens are encrypted at rest with AES-256-GCM.
Can I migrate to Rechurn from another dunning tool?+
Yes. Disconnect the old tool's webhooks, connect Rechurn, done. We don't touch your subscription data — just the dunning automation.
What does setup typically look like?+
On the roadmap with caveats — Paddle's MoR model means dunning is partially handled by Paddle directly → Best fit: complementary tooling for save offers and post-recovery analytics