Google Play splits service and billing fees in 2026

For years, Google Play's platform cut was one number. You sold something for a dollar, Google kept a slice, and you booked the rest. That single number actually paid for two different things: the right to be on the store, and the processing of the payment. You never had to think about which was which, because they arrived as one deduction.

On June 30, 2026, that changes. Google Play is separating the service fee from the billing fee and expanding the billing options available to developers. The blended number you have managed around for years is being itemised. This is less an accounting tweak and more a prompt to understand a cost you have been paying blind.

What the split actually is

Think of the old cut as a bundle you could not unbundle. Part of it paid for distribution: store hosting, discovery, getting the game onto the device, fraud protection at the store level. Part of it paid for billing: taking the card, moving the money, handling the payment rails. Both were rolled into one percentage, so there was no decision to make and no line to question.

Separating them does two things. First, it tells you how much of your cut was distribution and how much was payment processing. Second, because billing is now its own priced service, you can in some cases choose to handle billing differently and pay only for what is left. That is what "expanding billing options" means in practice: the payment step becomes a thing you can opt into or replace, rather than a fixed part of being on the store.

The headline percentage may not move much. What moves is your ability to see inside it.

Why this matters even if your total cost barely changes

Plenty of studios will look at the new structure, see roughly the same deduction, and move on. That is a mistake, because the value here is not a discount. It is visibility.

When a cost is a single blended number, you cannot reason about it. You cannot say "payment processing is X and distribution is Y," so you cannot decide whether the payment portion is worth what you pay for it. Once the two are split, you can. You can compare what Google charges to process a payment against what it would cost to process that payment yourself, and you can do it per region, where payment costs vary a lot.

This is the same reason any business itemises its bills. A blended cost hides the decision. An itemised cost surfaces it.

The decision the split forces

The choice that appears on June 30 is straightforward to state and harder to answer: keep Google's billing, or use an alternative billing path now that the billing portion is priced on its own.

Keeping Google billing is the low-effort option. The payment is handled, the trust is built into the store, refunds and disputes flow through a system players already recognise, and you do not take on new operational work. You pay for that convenience, and now you can see exactly what you pay.

Alternative billing is where the apparent savings live, and also where the hidden work lives. If you handle billing yourself or through another provider, you stop paying Google's billing fee, but you inherit everything that fee was quietly covering: payment trust, refunds, chargebacks, tax collection and remittance, and fraud. None of those disappear. They move onto your desk. We have written separately about what it takes to manage chargebacks as a real cost and what linking players to your own store actually changes — both are part of the true price of leaving the platform's billing.

So the decision is not "save the billing fee." It is "is the billing fee less than what it would cost me to do billing well." For a large studio with payments expertise, the answer can be yes. For a small team, the convenience is often worth keeping.

What to instrument before you decide

You cannot answer that question from a spreadsheet of list prices. You need to see your own numbers by component, and most studios are not set up to.

The number that matters is revenue net of fees, broken down two ways: per item sold, and per payment method. Per item, because a low-priced item carries a different effective cost than a high-priced one once fixed processing costs are involved. Per payment method, because the economics of a card payment, a carrier billing charge, and a wallet payment are not the same, and they differ by region.

If you only track gross revenue and a single blended fee, the split gives you nothing to act on. If you track revenue net of fees per item and per method, the split hands you a real decision with real evidence behind it. This is the kind of per-transaction detail that is far easier to capture going forward than to reconstruct after the fact — the moment to start recording it is before June 30, not after you wish you had.

This is also where a platform that already watches every purchase event in real time earns its place. The same stream of player and purchase signals that decides which offer a player sees is exactly the substrate you need to read costs by component. See how that works.

The honest limits

A few things this change does not do.

It does not make the platform cut go away. Distribution still costs what it costs, and for the vast majority of revenue that still flows through the store, you still pay for being there.

It does not make alternative billing free. It makes the billing fee visible and, in some cases, optional. Visible and optional is not the same as cheaper once you count the work.

And it does not change the right answer for everyone. The split is useful precisely because it lets each studio reach a different, evidence-backed conclusion instead of accepting one blended number. A studio shipping in one market with a small team and a studio operating across a dozen regions with a payments team should make different calls — and now they can.

The takeaway is small and concrete. On June 30 a cost you have paid blind becomes a cost you can read. Read it by component, instrument revenue net of fees per item and per method, and decide on evidence rather than on the headline percentage. Talk to us about your game if you want help seeing those numbers clearly.