Rc Payment Recovery

RevenueCat/ai-toolkit/revenuecat-play-billing/skills/rc-payment-recovery

by RevenueCatccfc038185ec457b2ac9077f3bbf1ba947a44dbbApache-2.0; see LICENSEListed Oct 9, 2026Updated Oct 9, 2026

Use this skill when handling failed renewals on Android with RevenueCat. Covers how Grace Period and Account Hold are reflected in CustomerInfo automatically, when to prompt the user, and how to trigger Google's in app messaging via showInAppMessages.

AI-generated overview

Guides Android developers handling failed RevenueCat subscription renewals through grace period, account hold, and recovery.

What it does
Explains how Google Play failed renewals surface in RevenueCat CustomerInfo, covering grace period, account hold, and recovery states. Describes the billingIssueDetectedAt and isActive signals, when to prompt users, and how to trigger Google's in-app messages via showInAppMessagesIfNeeded. Includes Kotlin snippets for default behavior, manual triggers, custom grace-period UI, and opening the management URL, plus verification steps.
When to use it
Use when building or debugging Android subscription flows with RevenueCat and you need to handle failed renewals. Also useful when deciding whether to rely on Google's default in-app message or build custom billing-issue UI.
Requirements
Requires the RevenueCat Android SDK and Google Play Billing in an Android app. No scripts ship with the skill; it is instructions and code snippets only. Backend webhook handling requires a server endpoint for BILLING_ISSUE events.

Payment Recovery

Failed renewals on Google Play move a subscription through two states: grace period (user keeps access while Google retries the card) and account hold (access revoked until the user fixes the payment method). With RevenueCat, both states land in CustomerInfo automatically, and Google's in app message shows by default.

Phase 1: Understand

Three things happen when a renewal fails:

StateAccessHow RevenueCat surfaces itUser sees
Grace periodRetainedentitlement.isActive == true and billingIssueDetectedAt != nullGoogle in app snackbar by default
Account holdRevokedentitlement.isActive == false and billingIssueDetectedAt != nullGoogle in app snackbar by default
RecoveredRetainedbillingIssueDetectedAt == nullNothing

Two signals matter in the SDK:

  • EntitlementInfo.billingIssueDetectedAt is non null from the moment Google reports a billing problem until the user resolves it.
  • EntitlementInfo.isActive tells you whether they still have access.

On the backend, a BILLING_ISSUE webhook fires once per transition. You do not decode RTDNs.

Phase 2: Plan

Before you write app code, decide what you actually need. Most apps need none.

Ask:

  1. Do you want the default Google in app message? If yes, do nothing. The SDK calls showInAppMessagesIfNeeded on BillingClient connect.
  2. Do you want your own banner or dialog? If yes, read billingIssueDetectedAt from CustomerInfo and branch on isActive.
  3. Do you want to gate the message to specific screens? If yes, disable the automatic call and invoke showInAppMessagesIfNeeded(activity) yourself.
  4. Do you need a server side flag (for example, to send a recovery email)? If yes, handle the BILLING_ISSUE webhook. No app code required.

If you only want the default behavior, stop here.

Phase 3: Execute

Default (recommended)

Leave automatic in app messages on. This is the default:

kotlin
PurchasesConfiguration.Builder(context, apiKey)    .showInAppMessagesAutomatically(true)    .build()

Manual trigger

Disable the automatic call and show the message from your chosen activity:

kotlin
PurchasesConfiguration.Builder(context, apiKey)    .showInAppMessagesAutomatically(false)    .build()
Purchases.sharedInstance.showInAppMessagesIfNeeded(activity)

Your own UI during grace period

Read the entitlement and branch on both flags:

kotlin
val entitlement = customerInfo.entitlements["pro_access"]when {    entitlement == null || !entitlement.isActive ->        showSubscribeScreen()    entitlement.billingIssueDetectedAt != null && entitlement.isActive ->        showGracePeriodWarning()    entitlement.billingIssueDetectedAt != null && !entitlement.isActive ->        showAccountHoldScreen()    else ->        showPremiumContent()}

Send the user to fix payment

CustomerInfo.managementURL points to the Google Play subscription page:

kotlin
customerInfo.managementURL?.let { url ->    startActivity(Intent(Intent.ACTION_VIEW, url))}

Phase 4: Verify

Test each transition:

  • Use a Google Play test card that declines renewals to push a subscription into grace period.
  • Confirm entitlement.billingIssueDetectedAt becomes non null and isActive stays true.
  • Wait for account hold and confirm isActive flips to false while billingIssueDetectedAt remains non null.
  • Update the payment method and confirm billingIssueDetectedAt returns to null.
  • On backend, confirm a BILLING_ISSUE webhook fires on the first transition.

References

Source and attribution

Source:RevenueCat/ai-toolkitinrevenuecat-play-billing/skills/rc-payment-recoveryat commitccfc038

License: Apache-2.0; see LICENSE

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal