Google Just Made The Hidden Liability in Your Payment Contract Visible
Why Google's new chargeback policy is a bigger deal than most realize.
Many studio finance leads don't know exactly how much chargeback exposure sits on their books.
Google's 2026 policy change is about to make that a costly oversight.
Key Takeaways
- Google Play's 2026 chargeback policy formally transfers disputed purchase liability from platform to developer, creating a measurable financial exposure most studios have not modeled.
- The actual cost per disputed transaction is not the transaction amount. It is the fee, the defense overhead, and the refund, compounding on every dispute that lands.
- Fragmented payment stacks make this exposure harder to quantify and more expensive to manage when disputes arrive.
- Tebex operates differently: 100% chargeback protection means the liability sits with Tebex, not on the studio's books.
A liability that was always there, now formally yours
For years, mobile platforms absorbed a meaningful portion of payment risk on behalf of developers. Fraud protection, dispute handling, and chargeback liability all sat with Google and Apple. This was not a charity arrangement - they took 30% of every transaction in part to cover that operational cost.
Google's 2026 policy ends that arrangement in a specific and consequential way: developers will now be directly responsible for disputed purchase amounts and the associated chargeback fees. The platform is keeping a high take rate - and effectively widening its own margins - while transferring the financial risk to developers.
For a finance lead, this is not primarily a payments operations problem. It is a liability transfer. Risk that was previously sitting on Google's balance sheet is moving to yours. Most studios haven't modeled what that exposure looks like at their transaction volume - because most are measuring the wrong number entirely.
Understanding the real cost structure
The instinct is to think of chargeback exposure in terms of just the disputed transaction amount. That is the wrong unit of analysis. The actual cost of a disputed transaction has three components, and only one of them is the transaction itself.
These fees and overhead accumulate into a substantial ongoing expense - one that most studios are not currently booking as a liability because, until now, they have not been formally responsible for it.
Why fragmented payment stacks make this harder to contain
Most live-service studios don't run on a single payment system. Platform-native billing, third-party processors, fraud tooling, and manual dispute workflows each solve one problem - and rarely communicate with each other.
When a dispute lands, the evidence required to contest it are often distributed across systems that weren't designed to share data. Transaction records, delivery confirmation, and consumption events all live in different places. Reconstructing a coherent dispute record means pulling manually from each.
That cost doesn't appear in the chargeback fee line. It shows up in staff time, compounded across every dispute your title generates.
The diagnostic question worth asking right now isn't "what is our dispute rate?" It's this: how long does it currently take your team to reconstruct the evidence for a single disputed transaction, and what does that cost at your current volume?
How Tebex structures this differently
The distinction that matters here is not a feature. It's a contract structure.
Tebex operates as a Merchant of Record for all its partners, which means Tebex (not the studio) is the legal entity responsible for managing payment disputes. The chargeback liability sits with Tebex, not on the studio's books. That is a structural consequence of the MoR model, not a premium add-on unlocked at higher volumes.
The specific terms: Tebex provides 100% chargeback protection as a baseline for studio, publisher, and developer partners from the first transaction. That covers the chargeback fee, the cost of mounting a defense, and the full refund to the player if the dispute is lost. The studio's revenue is not touched. And because Tebex accepted the payment and owns the outcome, the studio is not required to provide evidence - Tebex manages the dispute operationally, end to end.
For a finance lead modeling exposure under Google's new policy, the relevant comparison isn't between dispute rates. It's between two contract structures: one where chargeback costs are a variable liability on the studio's books, and one where they aren't.
The finance action items right now
Three steps worth completing before Google's policy takes effect.
1. Model your actual exposure, not your assumed exposure: Pull your last 90 days of disputed transactions on Google Play. Apply a $15-20 fee per dispute. Then model the scenario where 30-40% of those disputes result in failed defenses and the transaction amount is also clawed back. That number - not your dispute rate, not your refund rate - is your real monthly chargeback liability under the new policy. Most studios have never calculated it this way, because until now, Google absorbed enough of that cost to make it invisible.
2. Read your Google Play Developer Distribution Agreement: Specifically, find the clauses covering chargeback responsibility post-2026. Google processes the payment, runs the risk check, and manages the card network relationship. What is changing is that they are removing the chargeback coverage that historically came with that role, while keeping the take rate. The liability moves to you; the margin does not move with it.
3. Ask your D2C provider the direct question: If you operate a web store or direct checkout channel alongside your mobile presence, contact that provider now and get a written answer to three questions: who owns the chargeback fee when a dispute is filed, who manages the defense, and who covers the refund if the defense fails. For studios working with Tebex, the answer to all three is Tebex.
One policy change, a broader signal
The structural shift Google is formalizing in 2026 will not be the last. Platforms that historically absorbed payment complexity are reassigning that cost downstream, and the direction of travel is clear. The finance question worth resolving now (before the first disputed charge posts) is whether your payment infrastructure is already built for it.
FAQ
What exactly is changing in Google Play's chargeback policy?
Later in 2026, Google Play will formally transfer chargeback liability from the platform to developers. The coverage that Google previously absorbed (the fee at filing, the cost of defense, and the refund if the defense fails) becomes the developer's responsibility. Google is also introducing a Review Refund API for submitting transaction-level evidence, but dispute outcomes remain Google's determination.
How does Google's new policy compare to standard Merchant of Record contracts?
Google Play functions as the de facto MoR for in-app transactions, and its 2026 policy brings it in line with the harsher end of standard industry practice. Most MoR providers already pass chargeback costs back to the studio: a fee at filing, a manual evidence requirement, and recovery of the refund if the defense fails. Tebex diverges: 100% chargeback protection applies from the first transaction, across all channels, regardless of volume.
Is Google's policy change an isolated decision or part of a broader trend?
It reflects a broader pattern. As platform margins compress, services that historically absorbed payment complexity are reassigning that cost downstream. Studios planning only for Google's announcement are solving the wrong problem. The more durable question is whether your payment infrastructure is built for a world where platform risk coverage keeps shrinking - and whether the answer is already in your current setup.
What's the right question to ask your payment provider right now?
It's not about dispute rates or fraud tools. It's about contract structure: who owns the liability when a chargeback lands? Ask for a written answer to three things - who pays the fee at filing, who manages the defense, and who covers the refund if the defense fails.
