Documentation
Everything you need to connect RedChurn to your mobile app and run billing recovery, cancel saves, and win back on email, inside your app, or both.
What RedChurn does
RedChurn is a retention layer for mobile subscription apps. It connects to your billing provider (RevenueCat, Polar, and more) and runs automated flows when a payment fails, a subscriber taps cancel, or someone has already churned.
You can start with email only (through your Resend domain) and add in-app flows later with the SDK. Each flow toggles independently from the dashboard.
How it fits your stack
Your billing provider remains the source of truth for entitlements and billing. RedChurn reads webhook events and optionally registers subscribers through the SDK. Your paywall, purchase flow, and store billing stay unchanged.
If RedChurn is unavailable, your app keeps working normally. The SDK is fail-safe: no crashes, no blocked cancellations.
- Billing provider webhooks trigger email and in-app flows
- React Native and Swift SDKs show native UI for cancel saves, dunning, and win back
- Dashboard controls copy, offers, timing, and channel mix
- Changes propagate to apps within 60 seconds without a release
Quick start
Most teams connect in this order: add a webhook from RevenueCat or Polar, connect Resend for email, configure a billing recovery sequence, then install the SDK (React Native or Swift) when ready for in-app flows.
Pick the setup guide for your billing provider and Resend, then move to the React Native or Swift SDK doc when you are ready for in-app flows.