Skip to content
AppDues
Log in
Contact salesSign up

Google Play billing error churn: how to recover subscribers lost to payment failures

When a Google Play subscription ends, the default assumption is that the user chose to leave. Payment data says otherwise for a large share of cancellations: the card expired, the balance ran out, or the bank declined a routine charge. Those subscribers wanted to keep paying. This guide separates involuntary churn from real churn, maps the platform recovery windows, and shows how to build a dunning layer around them.

Diagnose billing failures before treating them as churn

A large-scale analysis of subscription app data — spanning more than 115,000 apps and over $16 billion in tracked revenue — put the share of Google Play cancellations caused by involuntary billing errors at 32.3%. The comparable App Store figure was 15.2%. The difference is structural rather than a reflection of platform quality: Apple users commonly have payment methods attached to other Apple services and keep them current, whereas Google Play supports prepaid cards and carrier billing in markets where balances often run dry. If you want to benchmark your own app, look for a published industry report that discloses its sample size and revenue coverage, and compare your billing-error cancellation rate against its platform-level figures rather than assuming the average applies to your audience. Most of these failures are soft declines — expired cards, insufficient funds, generic declines — which are temporary and recoverable through retries and prompts. Industry estimates cited in such reports suggest roughly a quarter to a third of US payment cards are reissued each year, so stale credentials accumulate even among engaged subscribers. Use this decision table to tell the states apart before writing any messaging:

Subscription state map: access, API visibility and billing date

The table below is a reader aid built from the platform behavior described in the guide. It is not a substitute for Google's current developer documentation.

Configure the platform recovery window first

Google provides a total recovery window of 60 days, split between a grace period and an account hold. As of Google's December 2025 policy change, the hold duration is calculated as 60 days minus whatever grace period you configure.

Grace periods are enabled by default on auto-renewing base plans and can run up to 30 days. During grace, Google retries the charge and notifies the user, while queryPurchasesAsync() still reports the subscription as active — so apps that rely on the standard entitlement check need no code change. If payment recovers inside the window, the original billing date is preserved. Google reports a 57% higher recovery rate from renewal declines when grace periods are enabled.

Account hold starts when grace expires. Access stops, the state becomes SUBSCRIPTION_STATE_ON_HOLD, and queryPurchasesAsync() no longer returns the subscription, so the app must check the hold state explicitly to show the right message. Retries continue for the rest of the 60 days. If payment is fixed during hold, access resumes but the billing date resets to the recovery date. Google reports 35% higher decline recovery and 8% lower involuntary churn when hold is added on top of grace; early cohort data showed combined recovery rising from roughly 10% to 33%.

The In-App Messaging API is the cheapest remaining lever: a single BillingClient.showInAppMessages() call with InAppMessageCategoryId.TRANSACTIONAL renders a Google snackbar once per day during grace or hold, linking to the payment fix screen. Google reports a 2x increase in user recovery. Call it on every app launch.

If you use a subscription management platform rather than the raw Play Billing Library, check what it already does for you. Some SDKs, from a given major version, show Google Play's in-app messages automatically and let you turn that off with .showInAppMessagesAutomatically(false) if you prefer to manage it yourself. That is a vendor-specific capability, not a platform default — confirm the behavior of whichever tool you use before assuming it is covered.

Google Play configuration checklist

Work through these three items in the Play Console and your app; the whole set is roughly an hour of work.

  1. Confirm grace periods are enabled on every auto-renewing base plan and set to the longest duration that fits your product, up to 30 days.
  2. Confirm account hold is set to auto-calculated so the combined window reaches the full 60 days.
  3. Add the In-App Messaging API call to your app launch flow.

After changing configuration, watch the billing-issue cohort over the next billing cycle to confirm the effect. Some subscription management platforms already wire this up: grace period and account hold states configured in the Play Console are detected automatically, subscriptions in grace remain "active" in entitlement checks, a BILLING_ISSUE event fires to webhooks and connected integrations when a payment fails, and the Subscription Status chart shows a dedicated "Billing Issue" status so you can see what share of active MRR is at risk. Those are platform-specific behaviors; with a different stack you will need to build the equivalent detection yourself.

Build the dunning layer on top of the platform defaults

Dunning is the practice of contacting users about failed payments and prompting a fix. Platform settings are the floor; the developer-built layer is where incremental recovery comes from.

Push timing matters more than copy. Send the first push on Day 0 when the decline is detected through Real-Time Developer Notifications (RTDN), then follow up on Days 1–3, Day 7 and Day 14. Keep the tone helpful: a message such as "We're having trouble renewing your subscription — tap to update your payment method" outperforms anything alarmist, because the user did nothing wrong.

Match in-app messaging to state. During grace the user still has access, so a non-blocking banner or snackbar fits. During hold, escalate to a modal that explains access is suspended and offers a clear call to action. Google's in-app message covers the once-daily prompt; your pushes reach users who have not opened the app.

RTDN requires Google Cloud Pub/Sub. Handle SUBSCRIPTION_IN_GRACE_PERIOD (type 6), SUBSCRIPTION_ON_HOLD (type 5), SUBSCRIPTION_RECOVERED (type 1) and SUBSCRIPTION_EXPIRED (type 13). After any notification, call purchases.subscriptionsv2.get to fetch the full state, since the notification signals a change without carrying complete details.

Some subscription management platforms get this plumbing pre-built: the BILLING_ISSUE event fires automatically to connected integrations such as Braze, OneSignal, Iterable and Customer.io, and includes grace_period_expiration_at so campaigns know the exact deadline. Without such a platform you own the RTDN pipeline end to end.

Email sequences for users who never open the app

Email reaches subscribers who miss pushes and in-app prompts. A 3–5 message sequence over 14–28 days works well, moving from a friendly heads-up to a risk notice to a final warning. Personalize with the user's name and the specific features they will lose, and make the call-to-action button link directly to the payment update screen.

One caution: pre-dunning emails that warn about upcoming card expirations can backfire. They may prompt users to reconsider the subscription entirely, especially if the app is not top of mind. For active users, an in-app prompt about an expiring card is usually safer than an email.

What recovery looks like at each level of effort

Recovery rates depend on how many of these tools you activate. The figures below are Google's published data and developer case studies as reported in the guide; treat them as a dated reference and check current conditions. - Platform defaults only, with no grace optimization and no developer intervention: roughly 10–15% recovery of failed payments. Most apps sit here. - Optimized grace periods, account holds and the In-App Messaging API, about an hour of configuration: roughly 30–35% recovery on Google Play. Google's data shows grace plus hold triples recovery from baseline, and the In-App Messaging API doubles user recovery on top. - Full dunning stack, adding push, email and deep links: gains compound across channels. In Google's Truecaller case study, RTDN-triggered messaging alongside grace and hold recovered 40% of at-risk subscribers, up from 15% before the changes. A recovered subscriber is worth more than a later win-back. Industry subscription data indicates that a subscriber who survives the first monthly renewal has a 73–82% chance of reaching the third, while only about 20% of monthly subscribers who actually churn return within a year — and just 5% of annual subscribers do. Preventing the loss beats reactivating it. Measure the effect by tracking the billing-error cancellation rate by platform and comparing cohorts before and after extending grace periods. Movement should appear within a single billing cycle. If you use a subscription management platform, its Subscription Retention chart may exclude unresolved grace period transactions, so retention figures reflect subscribers actually recovered — a chart-specific behavior to verify on your own tooling.

Worked example: sizing the recoverable revenue

Take a $1M ARR Android app. If 32.3% of its Google Play cancellations are billing failures, then more than $300K a year is leaving through involuntary churn. Moving from platform defaults (roughly 10–15% recovery) to optimized grace, hold and in-app messaging (roughly 30–35%) recovers a meaningful share of that figure — and the work is configuration, not a product rebuild. The exact result depends on your plan mix, price points and subscriber base, so model it against your own numbers rather than treating the percentages as a forecast.

The Apple side, briefly

App Store involuntary churn runs at less than half the Google Play rate, and more recovery happens automatically. Billing retry is always on for auto-renewable subscriptions, and since iOS 16.4 Apple shows a Billing Problem Message without any API call. The one setting to opt into is the Billing Grace Period in App Store Connect; Apple's own data shows 90% of billing issues resolve within a 28-day window. Beyond that, the Google Play work above is where the larger and more hands-on opportunity sits.

Subscription state map for Google Play billing recovery
StateUser accessReported by queryPurchasesAsync()Billing date after recovery
Grace periodFull accessYes, activeOriginal billing date preserved
Account hold (SUBSCRIPTION_STATE_ON_HOLD)SuspendedNoResets to the recovery date

Behavior described as of the guide's publication; confirm against current Google Play documentation.

Frequently asked questions

What is the difference between a grace period and an account hold?

During grace the subscriber keeps full access while Google retries the charge, and queryPurchasesAsync() still reports the subscription as active. When grace expires, account hold suspends access, the state becomes SUBSCRIPTION_STATE_ON_HOLD, and the subscription stops appearing in queryPurchasesAsync(). If payment recovers during grace, the original billing date is kept; if it recovers during hold, the billing date resets to the recovery date.

How long is the total Google Play recovery window?

60 days. Google calculates the account hold duration as 60 days minus the grace period you configure, so a 30-day grace period leaves 30 days of hold.

Do I need code changes to support grace periods?

No, if your app checks entitlements through the standard API. queryPurchasesAsync() continues to return the subscription as active during grace. Account hold does require an explicit state check so the app can show the right message.

What does the In-App Messaging API actually show?

A Google-rendered snackbar, triggered by BillingClient.showInAppMessages() with InAppMessageCategoryId.TRANSACTIONAL, that appears once per day when a user in grace or hold opens the app. It links directly to the payment fix screen and needs no custom UI.

Should I email users before their card expires?

Be cautious. Pre-dunning emails can prompt users to reconsider the subscription entirely, particularly if the app is not top of mind. For active users, an in-app prompt about an expiring card is usually the safer option.