What happens if RedChurn goes down?

Your app keeps working normally. Cancel flows, paywalls, and billing through your provider are unaffected. If our servers are unreachable, users simply won't see a retention message. Nothing breaks.

Can RedChurn break my app or billing?

No. RedChurn is read-only on your billing stack. We listen to webhooks from RevenueCat, Superwall, Polar, and other providers, then send retention emails and/or in-app messages at the right moment. We never modify your products, prices, subscriptions, or store configuration.

Which billing providers does RedChurn support?

RevenueCat (email + in-app), Superwall (email), and Polar (email) are live today. Connect via webhooks in a few minutes: paste your RedChurn webhook URL and secret into your provider dashboard. Stripe and more integrations are on the roadmap.

Do I need to change my paywall or pricing?

No. RedChurn sits on top of your existing setup. Keep your products, paywalls, and pricing as they are. We add recovery and retention flows on top of what you already ship.

How long does setup take?

Connect your billing provider in about 5 minutes. Email flows can go live the same day once Resend is connected, no app release required. The in-app SDK is one line and usually ships in your next store release.

Can I use email only, in-app only, or both?

Yes, per flow. Use email-only if you want recovery and win-back without touching the app yet. Use in-app-only for native cancel screens and dunning on the next open. Most teams enable both so email reaches users who do not open the app and in-app catches them inside the product.

What does the SDK weigh?

Less than 200 KB on iOS and Android. We obsess over bundle size because we know mobile teams do too.

How does pricing work?

Starter is free up to 50 active subscribers and includes analytics plus churn recovery on one app. As you grow, pricing scales with your active subscriber count — pick Starter or Growth on the slider. Every plan includes the Red Center, billing recovery, cancel saves, win-back, and in-app retention. Pay yearly and get 2 months free.

Is the beta open right now?

Yes. Sign up today, connect your billing provider, and start recovering MRR. You get the full dashboard, all three flows, and a direct line to the team while we polish for public launch.

Événements billing issue RevenueCat

L’événement BILLING_ISSUE est votre signal le plus précoce qu’un paiement d’abonné a échoué. Voici comment réagir avant la fin de la période de grâce.

Ce qui déclenche BILLING_ISSUE

RevenueCat envoie BILLING_ISSUE quand Apple ou Google signale un problème de facturation sur un abonnement actif. Refus temporaires, cartes expirées et fonds insuffisants remontent ici avant l’expiration complète de l’abonnement.

C’est le bon moment pour démarrer le dunning — pas après EXPIRATION quand l’abonné est déjà parti.

Brancher le webhook

Dans RedChurn, chaque app reçoit une URL webhook HTTPS unique et un en-tête d’autorisation. Collez les deux dans RevenueCat sous Project → Integrations → Webhooks.

Activez BILLING_ISSUE, CANCELLATION, EXPIRATION et RENEWAL pour que les trois flux de rétention et le suivi des résultats restent exacts.

Automatiser la réponse

Configurez la récupération des paiements une fois dans le tableau de bord : e-mail à l’heure zéro, bannière in-app à la prochaine ouverture, relance le jour trois. RedChurn exécute la séquence pour chaque billing issue sans export manuel.