For most of this year, Google Play's US alternative billing and external content links programs ran on an honor system: the fee schedule was published, developers could enroll, but nothing was actually being charged or reported. That changed on October 1, 2026. Developers enrolled in either program are now required to report every qualifying transaction and download through the Play Console and pay the applicable Play service fee on it — the first time this specific obligation has actually been enforced rather than just announced. It's been picked up across developer compliance trackers and Android-focused blogs this week, and it's already generating the kind of confusion that tends to follow when a fee becomes real: several widely shared posts can't even agree on where Google documented the date, and the underlying fee structure itself is still being litigated. If you run an Android app that collects payments outside standard Play Billing, this is the Google Play alternative billing fees story worth actually understanding this week, not filing away as background noise.
What actually changed on October 1
Two separate US programs are affected. The external content links program lets an app point users to a web page to buy digital content or download a separate app, outside Google Play's own checkout. The alternative billing program lets a developer process payment inside the app using their own billing system instead of Google Play Billing. Both existed well before this month — what's new is the obligation attached to using them: as of October 1, every developer enrolled in either program must start reporting transactions and successful downloads through Play Console, and paying the Play service fee that applies to them.
Until now, Google had published what it intended to charge but hadn't actually turned reporting or billing on. That gap is why some developers treated enrollment as close to free — the fee existed on paper, not on an invoice. This week's enforcement closes that gap, and it does so retroactively from October 1 forward rather than giving a grace period, which is exactly the kind of detail that gets lost between the official Play Console Help pages and the blog posts summarizing them.
The fee math: what skipping Google's billing actually saves
This enforcement sits on top of a bigger fee restructuring Google rolled out starting June 30, 2026 as part of its post-Epic Games settlement changes in the US, UK, and EEA. The headline numbers: a flat 10% Play service fee on an app's first $1 million in annual revenue, rising to 20% on new installs or 25% on existing installs above that threshold. Separately, a 5% billing fee applies only when a transaction actually runs through Google Play's own billing system in those three regions.
That second number is the whole pitch for alternative billing and external links — skip Play Billing, skip the 5% billing fee. But the service fee still applies either way, and now it's actually being collected and reported on both paths. Run the real comparison and the margin is thinner than the pitch implies: a developer under the $1M threshold saves 5 percentage points by routing around Play Billing, then immediately owes their own payment processor 2.5–3.5% in card-processing fees, on top of building and maintaining the reporting pipeline Google now requires. For a lot of apps, the net savings is a couple of points of revenue — real, but nowhere near the 30% figure most developers still associate with Play Store fees from memory.
Why the developer confusion around this deadline is itself the story
What's made this week's enforcement a genuine talking point rather than a routine policy update is that it's landed in a fog of conflicting information. Multiple developer-facing writeups this week flagged that the specific October 1 reporting start date isn't phrased the way they expected on Google's own support pages, and that advisors have been telling smaller publishers to hold off enrolling in either program until the underlying legal picture is more settled — because the fee structure itself is still tied up in the ongoing Epic v. Google litigation, where the court-appointed compliance mechanisms and Epic's own objections to Google's fee design haven't fully resolved. A third-party compliance tracker following this exact milestone flagged it as a critical, zero-grace-period deadline specifically because of how much ambiguity surrounds it.
That combination — a real enforcement date, a genuinely contested legal backdrop, and inconsistent documentation — is why this is spreading through Android developer circles this week in a way a routine fee update wouldn't. It's not that the fee itself is shocking; it's that nobody enrolled seems fully certain what they're on the hook for starting now versus what's still in flux.
The EdTech and subscription angle
This lands directly on the kind of app we build most under D.TEN: institutional subscription and licensing products where margins are already tight and procurement cycles are slow to absorb a fee change mid-contract. A school-licensing app that enrolled in alternative billing specifically to avoid Google's cut now has a real, reportable fee obligation on every transaction, not a theoretical one — and the administrative overhead of reporting through Play Console is a cost in engineering and operations time that rarely gets modeled next to the headline percentage savings.
For subscription apps generally, this is the moment to actually re-run the numbers rather than relying on the pitch that got you to enroll in the first place. Below the $1M threshold, where most independent and early-stage EdTech products sit, the 10% service fee applies regardless of billing path — the only variable is whether you're also paying Google's 5% billing fee or your own processor's card fees, and now, either way, reporting it.
A simple model for comparing the two paths
The right choice depends on your numbers, not on the pitch. Put the real figures for your app side by side.
| Cost or effort | Google Play Billing | Alternative billing or external links |
|---|---|---|
| Play service fee | Applies | Still applies, and is now reported |
| Play billing fee | Applies | Not charged |
| Your payment processor fees | None | Your processor's card fees |
| Reporting to Google | Handled for you | You must report qualifying transactions |
| Refunds, proration and receipts | Handled by Play | Your system, or your processor's |
| Engineering and support time | Low | Ongoing, and easy to underestimate |
A checklist before you stay enrolled
- I have confirmed my enrollment status in Play Console.
- Reporting for transactions and downloads is wired up and tested.
- I have modelled the real cost of both paths, including my processor's fees and engineering time.
- Refund, proration and tax handling are defined for the alternative path.
- My pricing logic reads fee percentages from configuration, not hardcoded values.
- Someone owns this decision and will revisit it when the rules change.
What we'd actually recommend
Start by checking your own Play Console enrollment status directly rather than trusting a secondhand summary of the deadline — the authoritative pages are Google's own Play Console Help answers on the US policy update, external content links enrollment, and alternative billing for US developers. If you're enrolled in either program, confirm you have reporting actually wired up for transactions and downloads completed on or after October 1; this isn't a feature you can retroactively backfill cleanly later.
Run the full comparison before deciding whether to stay enrolled: service fee, your own processor's take, and the engineering time to build and maintain Play Console reporting, against simply taking the 5% billing fee hit and letting Google handle billing and reporting for you. For a lot of smaller apps, the operational simplicity of standard Play Billing is worth more than the percentage points saved by going around it.
And don't treat today's fee percentages as fixed. They exist inside an antitrust settlement that's still being contested, which means the numbers you build your pricing model around this month are a reasonable current best guess, not a permanent constant — keep the fee assumptions in your billing logic configurable rather than hardcoded, because this is very unlikely to be the last adjustment Google makes here.
Frequently asked questions
Sources

Written by
Hamza Fazal
Founder, DEESU
Muhammad Hamza Fazal is the Founder of DEESU. An Android and full-stack web developer and digital marketer based in Islamabad, he founded DEESU in May 2022 and leads its engineering operations, product strategy, and client software delivery.
More from HamzaNeed help with this?
