Beta open·2 mo. free · 3/10 spots

Join
Flow 01Billing recovery

Recover failed payments before they become churn.

Mobile apps lose 4–8% of MRR every month to expired cards and soft declines. Redchurn detects billing issues from RevenueCat and runs recovery on email, inside your app, or both.

  • Email
  • In-app
  • Both

Founding rate · 2 months at $0, then from $49/mo

7 founding beta spots left · 3/10 beta testers

T+0

Payment failed

user_8a3f · $9.99

T+1h

Recovery email sent

From your domain

T+12h

In-app dunning shown

Tap to update card

T+24h

Retry 2

Card updated by user

T+25h

Payment recovered

+$9.99 saved

The problem

Failed payments become churn when nobody follows up

Involuntary churn is the quiet leak most teams never measure separately from voluntary cancels.

  • 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.

4–8%

Involuntary churn rate

Average for mobile subscription apps

RevenueCat State of Subscription Apps

72h

Critical recovery window

Most saves happen before grace period ends

Subscription billing benchmarks

2

Channels per flow

Email, in-app, or both from one dashboard

Redchurn

The workflow

How the workflow runs

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.

Default sequence

  1. T+0

    Payment fails, RevenueCat sends BILLING_ISSUE

  2. T+1h

    Recovery email from your domain

  3. T+12h

    In-app dunning on next app open

  4. T+24h

    Second retry after card update

  5. T+25h

    Payment recovered, MRR saved

    Complete

You control timing, copy, and channel mix. Email only, in-app only, or both stacked together.

Channels

Email, in-app, or both

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.

Resend + your domainReact Native SDK
  • Email

    From your domain via Resend

  • In-app

    Native screens on next open

  • Both

    Stack channels per flow

Dashboard

What you configure in the dashboard

Everything runs from app.redchurn.io after RevenueCat is connected. No engineering time needed to change copy or timing once the webhook is live.

01

Scenarios → Email → Billing recovery: steps, subjects, send timing

02

Scenarios → In-app → Billing recovery: banner copy, CTA, appearance

03

Toggle email, in-app, or both per flow independently

04

Billing recovery view: recovered MRR, channel attribution, events

Get started

Getting started

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.

Founding rate · 2 months at $0, then from $49/mo

7 founding beta spots left · 3/10 beta testers

Beta open

Be first to recover the MRR you're losing.

Three churn-killing flows on email, in-app, or both. Founding rate: 2 months at $0, then from $49/mo. Only 10 spots.

2 months at $0 on every plan

7 founding beta spots left · 3/10 beta testers