On Google Play, about 31% of subscription cancellations are billing failures. On the App Store, about 14%. RedChurn detects billing issues from RevenueCat and runs recovery on email, inside your app, or both.
Payment failed
user_8a3f · $9.99
Recovery email sent
From your domain
In-app dunning shown
Tap to update card
Retry 2
Card updated by user
Payment recovered
+$9.99 saved
RevenueCat tracks how often churn is a failed payment, not a user quitting. Most teams never split the two.
Involuntary churn happens when a subscriber wants to stay but their payment fails. Expired cards, insufficient funds, bank blocks. The subscription lapses even though they never tapped cancel.
App Store and Play Store retry on their own schedule. Most apps never follow up with an email from their domain or a prompt inside the app. The grace period ends and MRR drops silently.
31%
Play cancellations from billing errors
Involuntary churn, not users leaving
RevenueCat State of Subscription Apps 2026
14%
App Store cancellations from billing errors
Payment errors on iOS subscriptions
RevenueCat State of Subscription Apps 2026
2
Channels per flow
Email, in-app, or both from one dashboard
RedChurn
Billing recovery starts when RevenueCat reports a billing issue. RedChurn picks up the event through your webhook and launches the sequence you configured in the dashboard.
Payment failed
user_8a3f · $9.99
Recovery email sent
From your domain
In-app dunning shown
Tap to update card
Retry 2
Card updated by user
Payment recovered
+$9.99 saved
Default sequence
Payment fails, RevenueCat sends BILLING_ISSUE
Recovery email from your domain
In-app dunning on next app open
Second retry after card update
Payment recovered, MRR saved
CompleteYou control timing, copy, and channel mix. Email only, in-app only, or both stacked together.
Start with email only if you have not shipped the SDK yet. Connect Resend, verify your domain, and enable billing recovery under Scenarios → Email. No app release required.
Add in-app dunning when the React Native SDK is installed. BillingRecoveryBanner shows on the next open with a one-tap path to update the payment method.
From your domain via Resend
In-app
Native screens on next open
Both
Stack channels per flow
Everything runs from app.redchurn.io after RevenueCat is connected. No engineering time needed to change copy or timing once the webhook is live.
Scenarios → Email → Billing recovery: steps, subjects, send timing
Scenarios → In-app → Billing recovery: banner copy, CTA, appearance
Toggle email, in-app, or both per flow independently
Billing recovery view: recovered MRR, channel attribution, events
Connect RevenueCat first. Paste the RedChurn webhook URL and authorization secret in your RevenueCat project.
Enable billing recovery on email, add the SDK when you want in-app dunning, and track recovered MRR in your dashboard.
RedChurn reads subscription events and sends retention messages. It does not replace your billing provider, paywall, or user accounts.
We ingest webhooks from RevenueCat, Superwall, Polar, and other providers. We never change your products, prices, or subscriptions.
Cancel saves use Apple and Google native flows. No guideline workarounds.
Email sends from your domain via Resend. Push uses your FCM and APNs credentials.
Optional SDK under 200 KB. Disconnect anytime. Your paywall and billing keep running.
Connect your billing provider, open your Red Center, and turn on save flows. Starter is free up to 50 active subscribers — pricing scales as you grow.
Already have an account? Log in