Managing subscription lifecycles on Android is one of the most complex aspects of in-app billing implementation. Subscriptions go through numerous states throughout their lifetime, from initial purchase to renewals, grace periods, account holds, pauses, cancellations, and eventual expiration. Each state transition requires specific handling in your app to ensure users receive the correct entitlements, while your backend maintains accurate subscription records. Understanding these lifecycle events is essential for building a robust subscription system that minimizes involuntary churn and provides a seamless user experience.
To make it a little clearer, you will break down the complete Google Play subscription lifecycle in depth. We’ll cover every subscription state and the transitions between them, examine how Real-Time Developer Notifications (RTDN) inform your backend of changes, understand the differences between auto-renewing and prepaid subscriptions, and see how proper lifecycle handling can recover revenue from failed payments. Finally, we’ll look at how RevenueCat simplifies this complexity by abstracting away much of the lifecycle management.
The subscription lifecycle at a glance
Before diving into the details, let’s establish a mental model of how subscriptions flow through different states. A subscription begins with a purchase, enters an active state, and eventually either renews successfully, encounters payment issues, gets canceled, or expires. The complexity arises from the numerous intermediate states and recovery mechanisms that Google Play provides.
Each state has specific implications for user entitlements and requires different handling in your app and backend.
New subscription purchases
When a user purchases a subscription, your app receives a SUBSCRIPTION_PURCHASED notification, and the subscription enters the SUBSCRIPTION_STATE_ACTIVE state. This is the starting point of the lifecycle.
The critical acknowledgment requirement
One of the most important aspects of handling new purchases is acknowledgment. Google Play requires you to acknowledge a subscription purchase within three days of the transaction. If you fail to acknowledge within this window, the user automatically receives a refund, and the subscription is revoked.
The acknowledgment serves as confirmation that you have granted the user access to their purchased content. It’s a safeguard that protects users from situations where a purchase succeeds on Google’s side but fails to register in your app.
Understanding the purchase response
When you query a new subscription purchase using the purchases.subscriptionsv2.get API endpoint, you receive detailed information about the subscription state:
| Field | Value for new purchase |
| subscriptionState | SUBSCRIPTION_STATE_ACTIVE |
| acknowledgementState | ACKNOWLEDGEMENT_STATE_PENDING |
| autoRenewEnabled | true |
| expiryTime | Next renewal date |
The expiryTime field indicates when the current billing period ends and renewal will be attempted. For a monthly subscription purchased on January 15, this would be February 15.
Linking purchases to user accounts
Google Play provides ExternalAccountIdentifiers to help you associate purchases with user accounts in your system. When configuring the billing flow, you can pass your internal user ID:
These identifiers are returned in the purchase response and RTDN notifications, allowing your backend to correctly attribute purchases to user accounts even in edge cases like upgrades, downgrades, or resubscriptions.
Subscription renewals
For