Google Play is ending its longstanding practice of absorbing chargeback losses on behalf of developers. Starting later in 2026, when a player disputes a Play Store purchase with their bank, the developer, not Google, will cover the transaction cost plus the card network's chargeback fee, which is typically $15-$25 per dispute. On top of that, Google's liability is limited to refunding its own service fee. The change was quietly posted on the official Google support page back in early May, without any wider announcements. Apple has been operating this way as standard; however, this is a meaningful change for Android developers who have felt protected by Google’s billing environment.

What's changing, in a nutshell

Until now, Google absorbed chargeback losses entirely. Developers got a notification, and that was the end of it. Under the new model, though, the cost shifts to developers, but Google will still contest chargebacks under the new Review Refund API, which launches in July of this year. Here's how the two models compare:

## What does the Review Refund Fund API actually mean? The Review Refund API, launching in July 2026, is labeled optional, but in reality, it is the only option available if publishers want Google to contest disputes on their behalf. Opting in allows you to share transaction-level data such as delivery status, item consumption, and order state, enabling Google to build a case against illegitimate chargebacks on their behalf. Although Google doesn’t publish exact figures on illegitimate chargebacks, Chargeflow estimates that around 70% of disputes in the digital goods and gaming space are categorized as ‘friendly fraud’. Friendly fraud happens when a real player buys something, then disputes the charge with their bank for a refund, but in the end, they keep the digital goods and pocket the money. Google's fraud prevention tools (which blocked $3.4 billion in abuse in 2025) aren't designed to catch that pattern, plus friendly fraud sits in a grey zone that automated systems struggle with. And now, Google is making it the developer's problem.

What this means for you

The headline cost is the chargeback fee, but that's not where most of the damage lands. Google used to absorb the full disputed transaction. Now you do, minus Google's service fee, plus a bank chargeback fee that can reach $100 per case. The Review Refund API is your only way to fight back, and it only works if your data is in order. Industry-wide chargeback win rates sit around 12% without a dedicated dispute infrastructure (Chargeflow). Studios that can submit clean transaction logs, consumption telemetry, and delivery confirmation will win more. Studios that can't will lose most contested cases by default. Your refund policy is now a margin lever. A player who gets a quick in-app refund costs you the sale. A player who skips support and files a bank dispute costs you the sale, the fee, and the staff time to contest. Generous, fast in-app refunds aren't just a customer experience question. They are how you keep your dispute ratio below the 0.9% threshold that triggers card network penalties.

What you should do before July

Google's new API is your only mechanism for contesting disputes, so the groundwork needs to happen now. These are the four things worth prioritizing before the policy takes effect:

• Check your current dispute rate. If you don't have a clean number, get one. You need a baseline before costs start landing.
• Map your data sources. The Review Refund API needs transaction-level evidence delivery state, consumption data, and session activity. Figure out where that data lives and how to connect it.
• Review your refund policy. A player who can easily get a refund through your support channel is far less likely to file a bank dispute. A refund costs you the sale. A chargeback costs you the sale plus fees.
• Plan for the API now. July is the deadline. Build submission workflows and test them before they go live, not after you've already lost winnable disputes.

The bigger picture for D2C

This policy change applies specifically to Play Store transactions, but it's part of a broader shift that's been underway since the Epic v. Google settlement reduced Google's platform fee from 30% to 20% in the US. As Google pulls back on both fees and chargeback protection, the economics of keeping all your revenue inside platform billing continue to change. For studios already selling direct-to-consumer through a Merchant of Record like Xsolla, chargeback liability on those transactions is handled by the MoR, not the studio. That's always been part of the model, but moments like this make the distinction more concrete. When platform protections disappear, owning your commerce infrastructure matters. If you want to talk through how a Merchant of Record handles dispute liability in practice or how to build your D2C strategy, get in touch.