Google Play's Fee Overhaul: Billing Choice, Quality Rate Cards, and What Comes Due in Q4

Google Play's billing choice program is live, two new quality-tier rate cards (Games Level Up and Apps Experience) take effect September 30, and alternative billing transaction reporting kicks in October 1. Here's what subscription app developers need to understand before Q4.

Google Play's monetization structure is changing faster in 2026 than at any point since the App Store antitrust era began. The Billing Choice Program went live June 30, letting US developers offer third-party payment options alongside Google Play Billing. Two quality-performance rate card programs — Games Level Up and Apps Experience — take effect September 30. And for any developer already enrolled in alternative billing or external content links, transaction reporting becomes mandatory October 1. If you haven't stress-tested your unit economics against these changes, the next 60 days are the time to do it.

The Billing Choice Program: What Went Live on June 30

Google's Billing Choice Program — a direct outcome of the Epic Games antitrust settlement — allows developers serving US users to offer alternative payment methods inside or alongside their app. There are two flavours:

• External content links: a persistent in-app link directing users to purchase on your website. The user completes checkout in a browser and returns to the app.
• Alternative billing: a third-party payment processor integrated into the in-app purchase flow itself (e.g. a Stripe or PayPal sheet).

The critical detail most write-ups bury: Google's service fee applies to both routes. The rate is lower than standard Play Billing, but it is not zero. And starting October 1, every transaction processed through these channels — new purchases, renewals, upgrades, and refunds — must be reported back to Google via the Play Developer API. Failure to report is a compliance risk that could cost you program eligibility.

For indie apps without an existing payments backend, the operational overhead of the Billing Choice Program may not yet be worth it. For apps already processing web subscriptions or running a cross-platform RevenueCat setup, the maths are worth running.

The New Quality Rate Cards: Games Level Up and Apps Experience

Starting September 30, 2026, Google is introducing two new rate card programs for apps that meet specific quality benchmarks:

Auto-renewing subscriptions remain at 10% regardless of program tier. The reduced rates apply above the $1M annual revenue threshold — for qualifying transactions only.

What "quality benchmarks" actually means

According to Google's program documentation, eligibility is assessed against Android quality signals: strong Android Vitals scores (low crash rate, low ANR rate), high Play Store ratings, implementation of recommended Play features (Play Integrity API, Adaptive layouts for large screens, Play Asset Delivery), and demonstrated investment in the Android platform. Exact scoring is evaluated per-app through Play Console — Google hasn't published a fixed threshold checklist.

The implicit message is clear: Google is financially rewarding apps that treat Android as a first-class platform rather than a port. If your Android Vitals dashboard shows warning-level crash or ANR rates, fix those before September 30 — that's your most direct lever toward eligibility.

What this means if you earn under $1M on Play

For most indie developers and small studios, the headline is less impactful than it sounds. Google's small business programme (in place since 2021) already gives you a 15% rate on your first $1M in annual Play revenue. The quality rate cards mostly benefit apps and studios operating above that threshold. Subscriptions at 10% are unchanged for everyone.

That said, the direction is worth noting: Google is explicitly tying fee economics to platform quality scores. Future expansions of these programmes — or equivalent signals affecting search ranking — could reach smaller developers over time. Starting to track your Android Vitals baseline now costs nothing.

The October 1 Reporting Deadline You Shouldn't Miss

If you're enrolled in the Billing Choice Program and processing any alternative billing transactions, mark October 1 in your calendar. As of that date, Google requires transaction reporting for all events: new purchases, renewals, upgrades, refunds. Every event goes through the Google Play Developer API's transaction reporting endpoint.

This is non-trivial engineering. You need to capture the transaction event from your payment provider, map it to the correct Play product SKU, call the Google API within the required window, and handle retries. RevenueCat has published an integration guide if you're on their platform. For custom implementations, the Android developer documentation covers the backend integration pattern.

If you're managing subscription pricing across many markets, AppsOps's purchasing power parity tool can help you model how regional price points interact with your effective platform fee — especially relevant as these fee tiers start shifting your blended cost of revenue. And if you want deeper context on how the iOS/Android revenue split is evolving this year, the AppsOps Insights blog has covered the cross-platform economics in detail.

Sources and further reading

• Android Developers Blog — Expanded billing choice and lower fees on Google Play
• Play Console Help — Understanding Google Play's lower service fees & policy announcements
• RevenueCat — Understanding Google Play's Billing Choice (integration guide)
• Android Developers — Backend integration for monetization outside Google Play Billing