Google Play's October Billing-Reporting Requirement Is Now Live

As of October 1, 2026, Google Play requires developers using alternative billing or external content links to report every qualifying transaction — or risk losing program eligibility. Here's what's in scope, what the fees look like, and how to stay compliant.

If your Android app links users to an outside payment flow — or processes purchases through a non-Google billing system — the rules changed again on October 1, 2026. Google's new fee-reporting requirement for its External Content Links and Alternative Billing programs is now live in the US, and staying enrolled means staying compliant. Here's what you actually need to do.

What Changed on October 1

Google's settlement with Epic Games reshaped Play Store economics starting June 30, 2026: the flat 30% commission dropped to a tiered structure, and developers gained the right to use alternative billing systems and link users outside the app. What wasn't immediate: the obligation to report those external transactions back to Google.

That obligation kicked in October 1. If your app is enrolled in either the External Content Links program (in-app buttons or banners directing users to your web shop) or the Alternative Billing program (processing purchases through a non-Google system), you must now:

• Report every qualifying transaction — new purchases, renewals, upgrades, downgrades, and refunds — via the Play Developer API
• Pay Google the applicable service fee on that reported revenue

Google notified enrolled developers on July 22, 2026, giving roughly ten weeks to instrument reporting pipelines. If you haven't done that yet, you're already several days past the deadline.

The Fee Structure at a Glance

The fees are significantly lower than the old 30% take, but they're real and non-trivial depending on your scale:

The 10% subscription rate compares favorably to Apple's post-year-one 15% — a real advantage for subscription-heavy apps if you maintain Google Play Billing Library 8 compliance alongside your external billing option. Worth revisiting the fee tier math you modeled in June now that the reporting obligation is live.

What's In Scope — and What Isn't

This is where the details matter most. These programs cover two surfaces: purchases made inside your app through a non-Google billing system, and links that originate inside your app and drive a user to an outside checkout. The key boundary is where the user journey begins.

What falls outside the programs — and therefore outside the reporting requirements:

• Web traffic to your shop that didn't start in-app (organic SEO, paid ads, creator links)
• Email campaigns, Discord messages, and push notifications
• Promo codes on physical packaging or QR codes in marketing materials
• Direct web subscriptions from users who visited your site independently

This distinction matters for how you structure purchasing power parity pricing on your web shop. If a user in an emerging market navigates to your web checkout via email or social — not via an in-app link — their transaction is not reportable under these programs. Design your user flows accordingly.

What Happens If You Don't Report

Google has been explicit: accurate and timely reporting is a condition of program eligibility. Under-reporting or late reporting puts your enrollment at risk, which could mean Google revokes your access to alternative billing or external content links — forcing a reversion to Google Play Billing at the standard tiered rate.

It's not yet clear how aggressively Google will audit compliance in these early weeks. The pattern from Apple's StoreKit enforcement history suggests the first months tend to be educational rather than punitive — but that's no reason to wait. Reports suggest Google's Play Developer API already exposes the relevant transaction-reporting endpoints, and Play Console Help documents the payload schema.

A Practical Compliance Checklist

1. Confirm your app is enrolled in the correct program(s) in Play Console
2. Instrument reporting calls for every qualifying event: purchase, renewal, upgrade, downgrade, refund
3. Validate with sandbox transactions before pushing to production
4. Build a reconciliation step: your backend revenue logs vs. what you've reported to Google
5. Review your monetization architecture — the fee differential between subscriptions (10%) and one-time IAP (20%) may make a PPP-tiered subscription more attractive than a la carte purchases in growth markets

Sources and Further Reading

• Google Play Console Help — Developer Program Policies
• Stash.gg — Google's October 1 External Link Fees: What Changes and What Developers Still Don't Know
• TechCrunch — Google settles with Epic Games, drops Play Store commissions
• Pocket Gamer Biz — Google Play expands billing options and lowers fees for developers