Guide · 8 min read
Google Play Billing 2026: Lower Fees, Alternative Payments, and the Exact Math for Indie Devs
Google announced its biggest Play Store billing overhaul in a decade: effective June 30, 2026 in the US, UK, and EEA, developers can route purchases through alternative payment processors, link users out to the web for checkout, and — if they stay with Google Play Billing — pay a split service fee plus billing fee instead of a flat commission. The headline rate is 10%. The actual rate most apps will pay is 15%. Here's how to read the new math and what it changes for your monetization model.
The real fee math: 10% service fee plus 5% billing fee equals 15% for most apps
The headline "10% fee" is specifically a 10% service fee — and if you use Google Play Billing to process the transaction, Google charges a separate 5% billing fee on top, bringing your effective rate to 15%. That 15% applies to auto-renewing subscriptions under $1 million in annual revenue, which covers the vast majority of indie apps. The split is intentional: the 5% billing fee is Google's explicit incentive to push developers toward third-party payment infrastructure.
Apps that implement an alternative billing processor — Stripe, Braintree, PayPal, or their own payment gateway — or that redirect users to a web checkout pay only the 10% service fee. Five percentage points saved per transaction is meaningful at scale, but it comes with integration cost, which is what the break-even calculation in a later section addresses.
For context against the old structure: Google previously charged 30% on most transactions in year one of a subscription, dropping to 15% after the subscriber had been active for 12 months. Under the Small Business Program (first $1M of annual revenue), this dropped to 15% immediately. The new 10%/15% structure is a genuine improvement for nearly every subscription app earning under $1 million — particularly for newer apps where the 30% first-year rate was the most painful.
Alternative billing processors: what is supported and what changes in your app
Google now permits three alternative billing paths in addition to Google Play Billing: a third-party payment gateway integrated directly in the app (such as Stripe), a link-out to your own website for checkout, or a hybrid where you present both Google Play Billing and an alternative side-by-side. All three paths require a disclosure to users that the transaction is not processed by Google. The disclosure requirement is non-negotiable — omitting it is a policy violation.
Integration complexity varies sharply depending on your starting point. Adding Stripe to an Android app that previously used only Play Billing requires implementing the Stripe Android SDK, handling webhook events for subscription lifecycle (created, renewed, cancelled, failed), provisioning entitlements server-side, and managing failed payment dunning separately from Google's built-in retry logic. For a solo developer unfamiliar with Stripe's Android integration, a realistic timeline is two to four weeks of focused engineering.
The break-even math is straightforward: switching from Play Billing to alternative billing saves 5% of your annual Google Play subscription revenue. At $30,000/year in subscription revenue, that's $1,500 in annual savings — almost certainly less than the engineering hours to integrate. At $200,000/year, it's $10,000/year — a clear net positive. The threshold where switching pays for itself within 12 months typically falls between $60,000 and $100,000 in annual Play Store subscription revenue, depending on engineering time and your hourly rate.
Link-out to web checkout: highest savings, real conversion tradeoffs
The link-out option — directing users from inside the app to a checkout page on your own domain — is technically the cheapest billing path. You pay the 10% service fee, process the payment with your own gateway, keep the margin on payment infrastructure, and own the customer relationship directly: email address, billing data, and the ability to run win-back campaigns independently of Google.
The catch is conversion friction. In-app purchases benefit from a seamless flow: tap a price, authenticate with fingerprint or face recognition, and return to the app with the purchase active. Web checkout redirects add a browser switch, a form fill, and navigation back into the app — that friction consistently drops conversion rates compared to native in-app purchase flows. How much conversion drops depends on your price point: a $3.99/month subscription may lose more revenue to reduced conversion than the 5% fee savings recover, while a $49/month pro plan is a different calculation entirely.
The use case where link-out works reliably is high-intent, high-ACV purchases — annual plans, lifetime licenses, or team and business tiers where the user has already decided to buy and is specifically comparing options. For impulse-sensitive price points and low-friction subscription trials, in-app purchase flow typically converts better even at a higher fee rate. See the contextual paywall design guide for evidence on which moments in an app flow carry the highest purchase intent.
One-time purchases: 20–25% replaces the old 30% baseline
The new fee structure benefits subscription apps most visibly, but one-time purchase and IAP apps also see rate changes. For non-subscription transactions under $1 million in annual revenue, the service fee drops to 20% for new installs (for apps enrolled in the updated Apps Experience or Play Games Level Up programs) and 25% for existing installs — both down from the previous 30% flat rate.
The program qualification requirement is where many indie developers trip up. The reduced 20% rate is not automatic — it applies only to developers enrolled in Google's quality programs, which have their own benchmarks around app ratings, ANR rates, stability metrics, and policy compliance. Check your Play Console for enrollment status and eligibility before assuming the new rate applies to you. Non-enrolled apps processing one-time IAP outside of a qualifying program may still be on the 30% legacy rate.
If your app's monetization is primarily one-time purchases rather than subscriptions, the free vs paid launch decision now has a better fee floor — worth revisiting if you originally priced against the 30% assumption.
Global rollout timeline: which of your users are already on the new rules
The new billing structure went live in the United States, United Kingdom, and European Economic Area on June 30, 2026. If your app's revenue is primarily from these markets, the new rates are already in effect. Australia follows on September 30, 2026; Japan and Korea on December 31, 2026; the rest of the world by September 30, 2027.
For a typical English-language utility or productivity app, the US and UK likely represent 60–75% of Play Store revenue. Those users are already under the new structure, meaning any billing integration changes you make now apply to your largest markets immediately. You're not waiting for a global rollout to realize most of the benefit.
The phased global rollout means your Play Console revenue dashboard will show different effective rates across geographies until the worldwide cohort unifies in late 2027. Build that into any financial model for your app business — the blended effective rate is somewhere between the new 10%/15% and the old 30% until the transition completes. For the broader context on Play Store structural changes reshaping Android distribution, the Google Play Catalog Access guide covers the parallel development on third-party Android stores emerging from the Epic v. Google ruling.
What to actually do: a decision tree by revenue tier
Under $50K/year in Play Store subscription revenue: change nothing with billing infrastructure. The savings from switching don't justify the integration cost, the existing Play Billing system handles dunning reliably, and your engineering time compounds more in product than in payment plumbing. Revisit when revenue grows — this is a decision you can make without urgency.
Between $50K and $200K/year: evaluate the Stripe integration cost for your specific codebase. If you're already using Stripe on a companion web app, the Android SDK integration is significantly simpler — you're connecting to existing backend infrastructure rather than building new. The 5% savings compound annually; once integrated, you won't touch it again. Get a realistic estimate from the developer who'd do the work before deciding.
Over $200K/year: implementing alternative billing is almost certainly net-positive — the $10,000+ annual savings justify a dedicated sprint. At this revenue level, owning customer email addresses and managing subscription lifecycle directly also carries long-term retention value beyond the immediate fee differential. Pair the billing change with a review of your subscription pricing display — a billing infrastructure migration is a natural moment to tighten the full monetization stack. One deadline that cannot be deprioritized regardless of billing plans: the Android API 36 compliance deadline of August 31, 2026 means you cannot submit any app update until you target API 36 — and a billing migration requires exactly the kind of update that goes through Play Store submission.
New fee floor, same conversion fundamentals
The billing flexibility is real — Google has genuinely reduced fees and opened alternative payment paths for the first time. Whether the savings are material depends on your current revenue run rate more than anything else. For most indie apps earning under $50K/year on Play Store, the change is directionally positive but practically inert: the structure is better, the alternatives exist, and you'll grow into them.
Where the change matters immediately is for mid-stage apps in the $100K–$500K band that deferred a Stripe or direct-billing migration specifically because the old regime made it complex. The new structure makes the business case clear for the first time. While making the billing upgrade, it's also worth refreshing your Play Store listing — update your Play Store feature graphic and screenshots to reflect your current app. Use the editor below to build assets at the correct dimensions.
Update your Play Store listing →
Frequently asked questions
what is the google play service fee in 2026
The Google Play service fee is 10% on auto-renewing subscriptions earning under $1 million/year, effective June 30, 2026 in the US, UK, and EEA. If you use Google Play Billing to process the transaction, a separate 5% billing fee applies — bringing the effective rate to 15%. Apps using an alternative payment processor or web link-out pay only the 10% service fee.
can i use stripe instead of google play billing on android
Yes, as of June 30, 2026 in the US, UK, and EEA. Google now permits alternative payment processors including Stripe, Braintree, and your own gateway. The 10% service fee applies regardless of payment processor — the 5% billing fee only applies when you use Google Play Billing. Integration requires implementing the Stripe Android SDK, server-side entitlement management, and building your own subscription lifecycle handling.
how do i link out to my own website for purchases on android
Include a button in your app's purchase or upgrade flow that opens a URL to your own checkout page in an external browser. Google requires a disclosure that the transaction won't be processed by Google. The 10% service fee still applies, but you avoid the 5% billing fee and process the transaction with your own gateway. Conversion typically drops compared to in-app purchase flows, so this works best for high-ACV or annual-plan purchases where the user is already committed.
does the google play billing change affect my existing subscribers
Yes — the new fee structure applies to all transactions processed after June 30, 2026, including renewals of existing subscriptions. For apps that stay on Google Play Billing, renewal transactions are billed at the new 15% rate (10% service + 5% billing) in qualifying regions from July 1 onward. No action is needed on your part for existing subscriber renewals to benefit from the lower rate.
what is the google play commission rate for revenue over $1 million
For revenue over $1 million annually, the service fee rises to 20% for new installs and 25% for reinstalls or existing subscribers when using Google Play Billing — adding 5% to each brings effective totals to 25% and 30% respectively. Auto-renewing subscriptions over $1 million retain a 20% rate. These are a modest improvement over the previous flat 30%, but the main benefit of the new structure accrues to apps earning under $1 million.