How to Set Up Subscriptions on Google Play (Developer Guide)

Most Android developers set up Google Play subscriptions once and assume the hard part is done.

It isn’t. Billing lifecycle management, grace period configuration, proration modes, and RTDN handling all sit between a working subscription and one that actually retains revenue.

This guide covers everything: how the auto-renewing subscription system works, how base plans and offers are structured, how failed payments are recovered, what the service fee structure looks like, and how to integrate billing correctly on both the client and server side.

What Are Google Play Subscriptions?

Google Play subscriptions are recurring billing products sold through the Google Play Store, charged automatically on a defined billing cycle. Users pay on a weekly, monthly, or annual basis, and access continues as long as the subscription stays active.

They are distinct from one-time in-app purchases. A subscription persists until a user or developer actively cancels it, making the billing relationship ongoing rather than transactional.

Over 95% of Google Play revenue comes from free-to-install apps monetizing through in-app purchases and subscriptions rather than upfront payments (sqmagazine, 2025). That figure makes subscriptions one of the most significant revenue mechanisms on the platform.

Android app monetization has shifted heavily toward this model. Streaming platforms, productivity tools, fitness apps, and news publishers all rely on the auto-renewing subscription flow as their primary income source within the Play ecosystem.

The mobile application development process for subscription-based apps requires planning well beyond the feature set. Billing states, entitlement logic, and payment recovery all need dedicated implementation before an app ships.

Subscriptions are available to Android apps, games, and digital content platforms. Developers configure them via Google Play Console using a layered system of subscription products, base plans, and offers introduced in May 2022.

How Do Google Play Subscriptions Work?

A purchase triggers an initial billing event. Renewal happens automatically at the end of each billing period, and the user retains access without any action on their part.

Google Play’s subscription lifecycle covers 6 distinct states a subscription can move through: active, in grace period, on account hold, paused, canceled, and expired.

Non-gaming app revenue from in-app purchases grew 28.2% year-over-year to $19.2 billion in Q4 2024, nearly matching gaming app revenue (accio.com, 2025). Much of that growth is driven by recurring subscription billing rather than one-time purchases.

Grace Period and Account Hold

Grace period is the window after a failed renewal payment where the user keeps full access while Google retries the charge.

Account hold starts if the grace period ends without payment recovery. Access is suspended, but Google continues retrying. As of December 2025, the default account hold duration is auto-calculated as 60 days minus whatever grace period the developer configured (Google Play Console Help, 2025).

Google’s own internal data shows developers who use both grace period and account hold see more than a 3x increase in decline recovery rate, from 10% to 33% (Android Developers Blog, 2019). That gap is almost entirely configuration, not code.

Truecaller’s implementation of RTDN-triggered messaging alongside these recovery features recovered 40% of at-risk subscribers, up from 15% before the changes (RevenueCat, 2026).

Pause, Cancel, and Restore States

Cancellation stops future renewals but access continues through the end of the current billing period. The subscription only expires when that period ends.

• Pause: Users can suspend billing for 1 week to 3 months (developer must enable this; annual plans cannot be paused)
• Cancel: Stops auto-renewal; access persists until period ends
• Restore: Canceled but not yet expired subscriptions can be restored without a new purchase token
• Resubscribe: Expired subscriptions require a new purchase; a new token is issued

Annual subscribers who churn are notably hard to recover. RevenueCat’s 2026 data shows only 5% of lapsed annual subscribers return within a year, compared to 20% for monthly. Preventing the initial loss is far more valuable than winning them back.

What Are Base Plans and Offers in Google Play Subscriptions?

In May 2022, Google restructured how subscriptions are defined. The old model required a separate subscription SKU for each combination of billing period, price, and promotion. The new model separates “what the subscription provides” from “how it’s sold.”

A single subscription product now supports multiple base plans and multiple offers, each configurable independently (Google Play Console Help, 2022).

Base Plan Configuration

A base plan sets the default price, billing period, and renewal behavior. Developers can create multiple base plans per subscription, for example a monthly and an annual variant, each with its own pricing.

3 base plan types are available: auto-renewing (charges each period automatically), prepaid (no auto-renewal; user tops up to extend), and installments (fixed monthly payments over a committed period, currently available in Brazil, France, Italy, and Spain).

As of August 2023, all new apps were required to use Play Billing Library version 5 or newer, and existing app updates followed by November 2023 (adapty.io, 2023). Older integrations using the deprecated querySkuDetailsAsync() method no longer receive updates.

Offer Types: Free Trials, Intro Prices, and Developer Offers

Offers layer on top of base plans and are only shown to users who meet the eligibility criteria the developer sets.

• Free trial: Zero-cost access for a defined period before billing starts
• Introductory price: Reduced rate for a set number of billing cycles
• Developer-determined offer: Custom eligibility logic set by the developer using offer tags

Eligibility options cover 3 scenarios: users who never had this specific subscription, users who never had any subscription in the app, and users upgrading from a lower-tier or shorter-period plan.

What Subscription Features Can Developers Configure?

Google Play gives developers granular control over how subscriptions behave. Most of this configuration happens in Play Console before the subscription goes live, not in the app code itself.

Proration Modes for Plan Changes

When a user switches between base plans mid-cycle, Google applies one of 5 proration modes that determine how credit is calculated and when the new billing period starts.

Developers specify proration mode in the BillingFlowParams when launching the billing flow in-app. Getting this wrong means users either get charged incorrectly or lose access unexpectedly during the plan switch.

Prepaid vs. Auto-Renewing Plans

Auto-renewing plans are the default. They charge the user each period without requiring any action, and access continues indefinitely until cancellation.

Prepaid plans work differently. The user pays for a fixed period upfront, and when that period ends, access stops unless they top up. No automatic charge occurs.

Prepaid plans suit markets where users are reluctant to commit to recurring billing or where payment methods make auto-renewal unreliable. They also give users a stronger sense of control, which can reduce cancellation anxiety. Regional pricing is set per country, and Google auto-converts prices across 20+ buyer currencies.

How Does Google Play Billing Handle Failed Payments?

Involuntary cancellations from failed payments account for over a third of all subscription cancellations on Google Play (Android Developers Blog, 2019). This is the single largest recoverable churn category on the platform.

Google does not immediately cancel a subscription when a payment fails. Instead, it activates a structured recovery sequence with 2 phases: the grace period, then account hold.

Payment Retry Logic

Grace period timing by billing type:

• Weekly subscriptions: 3 days
• Monthly and annual subscriptions: up to 7 days (configurable)
• Maximum grace period: 30 days (developer-configured)

During the grace period, the subscription remains active. The user keeps full access. Google retries the charge internally while also sending email prompts to fix the payment method.

If the grace period ends without recovery, account hold begins. Access is suspended but the subscription has not expired. The user can restore by fixing their payment method at any point during account hold.

Starting December 1, 2025, Google changed the default account hold duration from a fixed 30 days to an auto-calculated value of 60 days minus the grace period duration (Google Play Console Help, 2025). The total recovery window is now capped at 60 days.

Real-Time Developer Notifications During Failure

Developers receive state-change events via Real-Time Developer Notifications (RTDN) through Google Cloud Pub/Sub the moment a subscription enters grace period or account hold.

The relevant notification types are SUBSCRIPTIONINGRACEPERIOD and SUBSCRIPTIONONHOLD. Without server-side RTDN handling, apps relying only on queryPurchasesAsync() will show grace period subscriptions as active, which they are, but miss the signal to prompt the user to fix their payment.

The In-App Messaging API provides an easier path. Call it on app launch and Google will show a built-in snackbar to users in grace period or account hold, prompting them to fix their payment without any custom UI work. It fires once per day while the payment issue persists.

What Is Google Play’s Subscription Revenue Share?

Google Play generated over $50 billion in revenue in 2024, with subscriptions and in-app purchases making up the majority of that figure (scaleupally.io, 2025).

As of January 1, 2022, all subscription transactions on Google Play are subject to a flat 15% service fee, regardless of developer size or how long the subscriber has been active (RevenueCat docs, 2022). The old model charged 30% in year one and dropped to 15% after 12 months, but churn made the 15% tier effectively inaccessible for most developers.

Fee Structure by Developer Size

99% of developers subject to a service fee qualify for 15% or less (Google Play Console Help). That leaves a small group of larger publishers paying 30% once they exceed the $1 million threshold in a calendar year.

The fee breakdown works like this:

• Subscriptions: flat 15% across all billing periods
• Non-subscription in-app purchases: 15% for the first $1M annually, 30% above that
• Alternative billing (User Choice Billing): service fee reduced by 4% in eligible regions
• 97% of developers distribute apps on Google Play at no charge (Google Play Console Help)

For context: Apple’s App Store charges 15% after the first 12 months of a subscription, with 30% in year one unless the developer qualifies for the Small Business Program. Google’s flat 15% subscription rate, active since 2022, removes that first-year penalty entirely.

Media Experience Program

Developers offering qualifying media content (audiobooks, music, video) can participate in the Play Media Experience Program, which provides additional commercial terms.

Google has also introduced the Apps Experience Program and a revamped Games Level Up Program offering 15% on new installs for developers who meet specific integration and quality requirements (Google Play Console Help, 2026). These programs are part of broader fee structure changes rolling out from June 2026 across the US, UK, and EEA.

The practical advice for most developers building Android development projects with subscription models: the 15% rate is the baseline assumption. Planning app pricing models around that rate is accurate for most commercial scenarios.

How Are Google Play Subscriptions Managed by Users?

Users manage their subscriptions at play.google.com/store/account/subscriptions or inside the Google Play app under “Payments and subscriptions.” Both surfaces show all active, paused, and recently canceled subscriptions tied to the Google Account.

Google sends renewal reminder emails 7 days before annual subscription charges. For monthly subscriptions, no advance notification is required, though payment failure prompts are sent immediately when a charge declines.

Available Subscriber Actions

What users can do from the subscription management page:

• Cancel a subscription (access continues to period end)
• Pause billing for 1 week to 3 months, if the developer has enabled this
• Switch to a different plan if the developer offers multiple base plans
• Update their payment method
• Request a refund within 48 hours of a charge via Google’s self-service flow

After 48 hours, refund requests go through Google support rather than the self-service tool. Google’s standard policy for subscriptions is to refund charges within 48 hours if the user hasn’t used the subscription content, though exceptions exist.

One notable gap compared to Apple: Google Play does not support family sharing for subscriptions natively. Each Google Account requires its own subscription. Apple’s family sharing works across up to 6 family members for a single subscription purchase. For developers building apps where household sharing is part of the value proposition, this difference matters and affects how iOS development and Android approaches diverge at the product level.

How to Cancel and What Happens After

Cancellation does not immediately end access. The subscription moves to a “canceled” state, but the user retains access through the end of the current billing period.

Once the period ends, the subscription expires. At that point, if the developer has enabled resubscription, the user can repurchase from within the app or from the Play Store listing. A new purchase token is issued on resubscription. The original token from the canceled subscription is no longer valid.

For developers tracking subscriber state, this distinction between “canceled” and “expired” matters. Canceled subscriptions still show as active in queryPurchasesAsync(). Only expired subscriptions are fully removed from that response. Handling the app lifecycle around these transitions requires server-side subscription state management, not just client-side purchase checks.

What Are the Google Play Subscription Policy Requirements for Developers?

Google enforces strict disclosure requirements for any app offering a subscription. Developers must not mislead users about the services or content a subscription provides (Google Play Console Help).

As of August 2025, all new apps and app updates must use Play Billing Library version 7 or newer, which directly affects how subscriptions, refunds, and payment flows are handled (knowband.com, 2025).

Mandatory Disclosure Rules

Before a user completes a subscription purchase, the app must clearly disclose:

• The price and billing period
• What content or features the subscription provides
• How to cancel
• What happens at the end of a free trial (including the exact charge amount)

Subscription names must accurately reflect the offer. Naming a subscription “Free Trial” is a direct policy violation, even if a trial is included.

Developers can add up to 4 benefit descriptions of 40 characters each when setting up a subscription in Play Console. Google recommends populating these because they reduce user confusion and churn (Google Play Console Help).

Prohibited Subscription Practices

Apps that lock access to features that are native to the device behind a subscription are rejected. Gating the camera, contacts, or basic OS functions is prohibited.

Policy violations that result in app removal:

• Misleading benefit descriptions
• Subscription names that imply a price or trial when the user is not eligible
• Failing to provide a clear cancellation path within the app
• Obscuring the renewal price after a discounted introductory period

Google’s review process for subscriptions has tightened since 2024. New apps now go through a mandatory 2-week testing period with at least 20 real users before a public launch is permitted (scaleupally.io, 2025). For subscription apps, this window also serves as a functional check on billing flows.

Price Change Notification Requirements

For opt-in price increases, Google notifies existing subscribers and requires them to agree before the new price takes effect.

Opt-out price increases follow a different path. Google notifies users in advance, and if no action is taken, the new price applies at the next renewal. The notification window is a minimum of 30 days in most regions and 60 days in others, depending on country-specific rules (Google Play Console Help).

How Do Real-Time Developer Notifications Work for Subscriptions?

RTDN is Google Play’s push channel for subscription lifecycle events. Instead of polling the Play Developer API repeatedly, Google pushes a Pub/Sub message to your server the moment a subscription changes state (Android Developers, 2026).

Truecaller’s implementation of RTDN-triggered messaging recovered approximately 40% of at-risk subscribers compared to 15% before the changes (Google Codelabs, 2026). The delta is almost entirely explained by response speed.

Setting Up the Pub/Sub Pipeline

RTDN runs on Google Cloud Pub/Sub. Setup requires 3 steps before any notification reaches your server.

Required configuration:

• Create a Pub/Sub topic in Google Cloud Console
• Grant the service account google-play-developer-notifications@system.gserviceaccount.com the role of Pub/Sub Publisher
• Link the topic to your app in Google Play Console under Monetization Setup

Google recommends push delivery over pull for most apps. Pull subscriptions optimize for high-volume message processing but add latency that defeats the purpose of real-time subscription recovery (Android Developers, 2026).

One critical point: RTDNs are notification-only. The payload tells you that a state changed; it does not tell you the complete current state. After receiving an RTDN, you must call purchases.subscriptionsv2.get on the Play Developer API to get the full subscription record.

Subscription Notification Types

Google sends 11 distinct SubscriptionNotification types that cover every state transition in the billing lifecycle.

Apps without RTDN handling fall back to polling queryPurchasesAsync(), which misses the grace period signal entirely. Users in grace period show as “active” in that API, so the billing failure goes undetected until expiry.

How Does Google Play Handle Subscription Upgrades and Downgrades?

When a user switches between base plans mid-cycle, Google does not simply swap the plan. It calculates how much of the current period was used, applies credit based on the chosen proration mode, and determines when the new billing period starts.

Developers specify proration mode in BillingFlowParams at the moment the purchase flow launches. Getting the wrong mode means users either get charged immediately when they expected no charge, or they keep the old price longer than intended.

Upgrade vs. Downgrade Logic

Upgrade path (e.g., monthly to annual, basic to premium):

• Immediate access to new plan features is standard
• IMMEDIATEANDCHARGEPRORATEDPRICE charges the difference immediately
• New billing period starts from the upgrade date

Downgrade path (e.g., annual to monthly, premium to basic):

• DEFERRED mode is the typical choice; the switch happens at next renewal
• User keeps higher-tier access through the paid period
• No immediate charge or credit; clean handoff at renewal

Proration Credit Calculation

Google calculates prorated credit automatically under modes that involve immediate plan switches. The credit is based on the remaining days in the current period multiplied by the daily rate of the existing plan.

This is straightforward in theory. The practical problem is when developers mix proration modes across upgrade and downgrade paths without testing them against real purchase tokens. Spotify, for example, built its plan-switching flow with A/B testing on upgrade vs. DEFERRED downgrade treatment specifically to observe churn impact before settling on defaults.

For cross-platform app development teams supporting both Android and iOS, the proration models differ enough that the logic needs separate handling per platform. Apple does not use proration modes in the same way; iOS upgrades always charge immediately with credit applied.

What Metrics Track Google Play Subscription Performance?

Play Console surfaces subscription data across 4 primary report types: subscription overview, retention, cancellations and recovery, and cohort analysis. Each answers a different operational question.

The Apple App Store generated $103.4 billion in 2024 compared to Google Play’s $46.7 billion (hubifi.com, 2025). That 2.2x revenue gap, despite Android commanding 71.44% of global mobile OS market share (tekrevol.com, 2025), makes subscription retention metrics especially worth tracking closely on the Android side.

Core Subscription Metrics in Play Console

Active subscriptions: subscriptions active for at least 1 day in the selected period, including free trials.

New subscriptions: first-time activations in the period. Broken out by base plan and offer if you switch to those report views.

Churned subscriptions: split into voluntary (user action) and involuntary (payment failure). Involuntary churn accounts for over a third of all cancellations (Android Developers Blog, 2019), so the split matters operationally.

Recovery rate: percentage of subscribers who entered grace period or account hold and then recovered. This is the direct output of how well your billing recovery configuration is working.

Cohort and Retention Reports

Google I/O 2025 announced new subscription capabilities in Play Console focused on reducing checkout friction and churn (Android Developers Blog, 2025).

The retention report lets developers compare 2 subscription cohorts across conversion and retention rates. You can filter by subscription, base plan, offer, country, and acquisition date range. The “Retention by billing period” chart shows how many billing cycles each cohort stays active, which is the clearest proxy for subscriber lifetime value.

The cancellation report breaks down top reasons for churn as percentages by default. Reasons include: user-initiated cancellation, payment failure, price change rejection, and developer-initiated cancellation. Switching to absolute values in the display settings shows raw subscriber counts rather than percentages, which is more useful for smaller subscriber bases where percentages mask the actual numbers.

How Do Google Play Subscriptions Compare to Apple App Store Subscriptions?

Android holds roughly 71.44% of global mobile OS market share, while iOS holds about 27.89% (tekrevol.com, 2025). Despite that install base advantage, the App Store generates more than double the subscription revenue.

iOS users spend an average of $1.08 per user on apps, compared to $0.43 for Android users (pravaahconsulting.com, 2026). For subscription-based mobile application development, both platforms are worth supporting, but the monetization dynamics differ significantly.

Revenue Share Differences

Google’s flat 15% subscription rate since January 2022 is a genuine advantage over Apple’s structure. An iOS subscriber in month one generates 30% less revenue to the developer than the same subscriber on Android, assuming neither platform qualifies for a small business program.

Apple’s Small Business Program does reduce this to 15% from day one for developers earning under $1M annually. At that scale, the rates converge. Above $1M, Apple charges 15% after 12 months; Google charges 15% from the first dollar of every subscription.

Recovery and Churn Tools

Apple’s App Store handles billing retry automatically for all auto-renewable subscriptions. Since iOS 16.4, Apple shows a Billing Problem Message to users without any API call on the developer’s part (RevenueCat, 2026).

Google requires more active configuration. The In-App Messaging API, grace period settings, and account hold duration all need to be deliberately configured. The upside: Google gives developers a total 60-day recovery window, significantly longer than Apple’s 28-day maximum billing grace period.

For custom app development teams supporting both platforms, Apple’s automated recovery is simpler to set up but leaves less control. Google’s system takes more work but recovers more revenue when configured correctly, as Truecaller’s 40% recovery rate demonstrates.

What Is Google Play’s User Choice Billing for Subscriptions?

User Choice Billing (UCB) lets developers offer an alternative payment system alongside Google Play Billing. Users choose which system to pay through at the point of purchase.

The Digital Markets Act, enforced since March 2024, requires Google to allow alternative billing options for users in the European Economic Area. As of August 2025, Google updated its EEA conditions following direct pressure from the European Commission (asoworld.com, 2025).

Where UCB Is Available and What It Costs

UCB is available in the following regions: the EEA, UK, US (following Epic v. Google rulings in late 2025), Australia, Brazil, Indonesia, Japan, and South Africa, among others (Google Play Console Help).

Fee structure under UCB:

• Transactions through Google Play Billing: standard service fee applies
• Transactions through the alternative system: service fee reduced by 4%
• In the EEA specifically, an EEA-only billing option carries a 3% reduction instead

Developers participating in UCB must use the alternative billing APIs to report transactions. Manual self-reporting ended as of March 13, 2024 (Google Play Console Help). All transactions must be reported within 24 hours of payment authorization.

Regulatory Context and Business Impact

The EU can fine companies up to 10% of global annual revenue for DMA violations, a potential fine in the billions for Google (gadgethacks.com, 2025). That regulatory pressure explains both the timing of UCB expansion and the relatively modest fee reductions offered.

The honest assessment from developers testing UCB: the 4% reduction rarely offsets the additional integration work for most subscription apps. The larger commercial case for alternative billing is external webshops, where developers in some regions can now redirect users outside the app for purchases entirely, bypassing platform fees on those transactions.

For most subscription apps, Google Play Billing remains the default path. The API integration cost of UCB only makes financial sense above a certain subscription volume, and the user experience friction of presenting 2 payment options at checkout carries its own conversion risk.

How Do Developers Integrate Google Play Subscriptions in an App?

Integration requires 4 components working together: the Play Billing Library on the client, a server-side backend, the Google Play Developer API for purchase verification, and RTDN for real-time state sync.

Skipping server-side verification is the most common integration mistake. Local receipt validation alone is insufficient. A subscription status must always be verified against Google’s API, not just the client-side purchase result.

Client-Side Integration with BillingClient

All new apps and updates must use Play Billing Library version 7 or newer as of August 2025 (knowband.com, 2025).

The client-side flow follows 4 steps in sequence:

• Connect: initialize BillingClient and establish a connection to Google Play
• Query: call queryProductDetailsAsync() to retrieve available subscription products, base plans, and eligible offers
• Launch: call launchBillingFlow() with BillingFlowParams specifying the offer token and proration mode
• Handle result: implement onPurchasesUpdated() to process the purchase outcome and send the purchase token to your server

The offer token is the specific identifier for the combination of base plan and offer the user selected. Passing the wrong offer token results in the user being charged for a different plan than intended, with no easy recovery path.

Server-Side Purchase Verification

After the client receives a successful purchase, the purchase token goes to your backend. Your backend calls the purchases.subscriptionsv2.get endpoint on the Google Play Developer API to retrieve the authoritative subscription state before granting access.

The response includes the subscription state, expiry time, payment state, and any active offers. Only after confirming the subscription is in SUBSCRIPTIONSTATEACTIVE should your server grant entitlement to the user.

Testing uses Google Play’s license testing accounts and Play Billing Lab’s Subscription State Transition feature. These let developers simulate payment declines, grace period entry, and account hold without processing real charges. Testing the full failure-and-recovery path before shipping is the part most teams skip, and it’s exactly where production bugs surface.

For teams building complex billing systems, the full back-end development work includes idempotency handling on RTDN messages (Google sends duplicates regularly), state machine logic for all 6 subscription states, and reconciliation against the Developer API on every RTDN event. Teams that underestimate this part typically discover the gaps through production incidents rather than QA.

The software development process for subscription-based Android apps consistently underestimates billing integration time. A rough benchmark from developers who have shipped subscription systems: client-side billing takes a day or two; server-side lifecycle management with proper RTDN handling and state reconciliation takes one to two weeks.

FAQ on Google Play Subscriptions

What is a Google Play subscription?

A Google Play subscription is a recurring billing product sold through the Play Store. It charges users automatically on a defined cycle (weekly, monthly, or annual) and stays active until canceled by the user, developer, or Google’s billing system.

How do I cancel a Google Play subscription?

Go to play.google.com/store/account/subscriptions or open the Google Play app, tap “Payments and subscriptions,” select the subscription, and tap Cancel. Access continues until the current billing period ends.

What happens if my Google Play payment fails?

Google activates a grace period first, keeping access active while retrying the charge. If payment isn’t recovered, account hold begins and access is suspended. The total recovery window is up to 60 days before the subscription expires.

Can I get a refund on a Google Play subscription?

Yes, within 48 hours of a charge via Google’s self-service refund tool. After that, requests go through Google support. Refunds are not guaranteed and depend on whether the subscription content was accessed.

How do I manage my Google Play subscriptions?

Visit play.google.com/store/account/subscriptions or use the Google Play app under “Payments and subscriptions.” From there you can cancel, pause, switch plans, or update your payment method.

What is the Google Play service fee for subscriptions?

Google charges a flat 15% service fee on all auto-renewing subscription transactions, regardless of developer size or subscription duration. This has been the standard rate since January 1, 2022, replacing the old 30% first-year rate.

What is a base plan in Google Play subscriptions?

A base plan defines the billing period, renewal type, and price for a subscription. A single subscription product can have multiple base plans, for example monthly and annual variants, each priced and configured independently in Play Console.

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

During the grace period, the user keeps full access while Google retries a failed payment. Account hold starts after the grace period ends without recovery. Access is suspended during account hold, but the subscription hasn’t expired yet.

Do Google Play subscriptions support family sharing?

No. Unlike Apple’s App Store, Google Play does not support native family sharing for in-app subscriptions. Each Google Account requires its own subscription purchase. Google Play Pass is a separate service that does support family sharing for up to 6 members.

What is User Choice Billing on Google Play?

User Choice Billing lets developers offer an alternative payment system alongside Google Play Billing in eligible regions, including the EEA, UK, and US. Developers pay a 4% reduced service fee on transactions processed through the alternative system.

Conclusion

This conclusion is for an article presenting Google Play subscriptions as a complete billing system, not just a checkout step.

The recurring billing lifecycle, from auto-renewing base plans and introductory offers to involuntary churn recovery through grace periods and account hold, requires deliberate configuration at every stage.

Revenue share, proration modes, RTDN handling, and the purchases.subscriptionsv2 API all connect directly to how much subscription revenue your app actually keeps.

User Choice Billing and DMA compliance are reshaping the landscape across the EEA and beyond.

The developers who treat subscription lifecycle management as a core engineering concern, not an afterthought, consistently recover more failed payments and retain more subscribers long-term.

• Author
• Recent Posts

Bogdan Sandu

Bogdan Sandu specializes in web design, focusing on creating user-friendly websites, and innovative UI kits.

Many of his resources are available on various design marketplaces and for free on Codepen.

Over the years, he's worked with a range of clients and contributed to design publications like Design Your Way, Designmodo, WebDesignerDepot, WPDean, Speckyboy, and Slider Revolution among others.

Latest posts by Bogdan Sandu (see all)

• How to Set Up Subscriptions on Google Play (Developer Guide) - July 12, 2026
• Why Work With a CMS Development Company for a Secure and Scalable Website? - July 12, 2026
• ADB Commands Cheat Sheet - July 11, 2026