Rc Payment Recovery

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

作者 RevenueCatccfc038185ec457b2ac9077f3bbf1ba947a44dbbApache-2.0; see LICENSE收录于 2026年10月9日更新于 2026年10月9日

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 生成的概览

指导 Android 开发者处理 RevenueCat 订阅续费失败,涵盖宽限期、账户冻结与恢复状态。

功能
说明 Google Play 续费失败如何在 RevenueCat CustomerInfo 中体现,涵盖宽限期、账户冻结和恢复三种状态。介绍 billingIssueDetectedAt 与 isActive 两个信号、何时提示用户,以及如何通过 showInAppMessagesIfNeeded 触发 Google 应用内消息。提供 Kotlin 代码片段,包括默认行为、手动触发、自定义宽限期界面和打开管理链接,并附验证步骤。
适用场景
适用于使用 RevenueCat 构建或调试 Android 订阅流程、需要处理续费失败的场景。也适合在决定使用 Google 默认应用内消息还是自建账单问题界面时参考。
运行要求
需要 Android 应用中的 RevenueCat Android SDK 和 Google Play Billing。该技能不附带脚本,仅包含说明和代码片段。后端 webhook 处理需要服务器端点接收 BILLING_ISSUE 事件。

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

来源与署名

来源:RevenueCat/ai-toolkit位于revenuecat-play-billing/skills/rc-payment-recovery提交ccfc038

许可证: Apache-2.0; see LICENSE

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架