Navigating the Chargeback Landscape: A Framework for Game Studios Against Google Play's Shifting Liability

Google Play Chargebacks Are Moving Onto the Studio P&L

*For payments and compliance leads: Google Play’s August 2026 rule turns chargebacks into a studio cost. The answer is not better policy prose. It is evidence, captured before the dispute arrives.*

## TL;DR

– After August 3, 2026, Google Play and developers share chargeback costs on eligible disputes [[Google Play Help]]. – The developer cost is not just the purchase price. It is the purchase price minus Play’s service fee, plus the bank chargeback fee [[Google Play Help]]. – Google’s optional Review Refund flow gives studios a short response window, typically about 24 hours, so evidence has to exist before the dispute lands [[Android Developers]]. – A small-ticket IAP can become a fixed-cost event if the chargeback fee is high. That is a margin problem, not a policy problem [[PiunikaWeb]]. – Tebex matters on the D2C side because it operates as Merchant of Record there, which changes where chargeback liability sits.

The refund button still looks the same. The accounting behind it does not.

A Google Play chargeback is a bank reversal of a player purchase. Until now, most studios could treat that as Google’s problem. For orders placed after August 3, 2026, it becomes partly yours [[Google Play Help]].

This is not a payments footnote. It is a cost center opening on your operational surface area, and it scales with volume rather than intent.

The system changed. The tooling has to change with it.

## What is the TL;DR on Google Play chargebacks?

Start with the split. After August 3, 2026, a disputed Play transaction leaves the developer paying the purchase price minus Play’s service fee, plus the bank chargeback fee. Google still covers the service fee portion [[Google Play Help]].

That is not a fee increase. It is a liability transfer.

A fee can be modeled from volume. Transferred liability is messier. It moves with fraud rates, dispute behavior, and the speed of your response process.

## Who owns Google Play chargebacks after August 3, 2026?

On Play, the liability rule is now set by Google. For orders placed after August 3, 2026, developers share chargeback costs on disputed transactions [[Google Play Help]]. If a player reports an unauthorized charge, Google says the player can often resolve it fastest by contacting the developer first [[Google Play Help]].

Ownership also splits by channel. In direct-to-consumer sales, the merchant of record owns the dispute. That is the practical significance of Tebex. For game D2C, Tebex acts as MoR, so chargeback liability on those direct transactions sits with Tebex rather than with the studio.

Liability you understand is liability you can price and defend.

## What do Google Play chargebacks do to your unit economics?

Run it at the level of one order.

A player buys a $9.99 item. The transaction is charged back. The studio loses the purchase price minus the Play service fee, and then takes the bank chargeback fee, which has reportedly reached $100 per case [[PiunikaWeb]].

So the chargeback is not really a reversal of a $9.99 sale. It is a fixed-cost event attached to a low-value transaction.

That is the asymmetry. In small-ticket IAP, the loss is not the item. The loss is the process.

Google says it prevented US$3.4B in fraud and abuse in 2025 [[Google Play Help]]. That matters. The platform is still absorbing and filtering a vast amount of bad activity. But the new rule changes the economics of the residue. The fraud that gets through, the friendly fraud that looks legitimate, the edge case that used to be external, these now have a direct route into the developer P&L.

This moves chargebacks out of the payments back office.

They become part of margin planning, payout forecasting, reconciliation, support, and entitlement management.

## How do you build a Google Play chargeback evidence workflow that scales?

The operational mistake is to treat chargebacks as tickets.

They are not tickets. They are timed state changes.

The useful model is simple:

notification, evidence pull, API response, entitlement decision

On Google Play, the trigger is a `PendingRefundReviewNotification`, delivered as a real-time developer notification. From there, the clock matters. Developers respond through the Review Refund API, usually within roughly 24 hours, with a refund preference and purchase-usage evidence [[Android Developers]]. If the evidence has to be assembled manually after the notification arrives, the process is already too slow.

Then there is the second loop. Server-side, the Voided Purchases API lets you detect refunds and chargebacks and revoke entitlements to prevent repeat abuse [[Google Play Console]].

The evidence system has to know five things before the dispute exists:

– Was the order delivered? – Was the item consumed? – Is the entitlement active, revoked, or pending? – What are the timestamps for purchase, delivery, and first use? – Do webhooks feed one reconciliation source of truth?

That last point is the real control. If finance, support, commerce, and game services each have a different version of the transaction, the studio does not have evidence. It has fragments.

If you cannot reconcile it, you cannot dispute it.

This is why the D2C pattern matters. Tebex already runs this discipline on direct sales: webhook-driven transaction records, entitlement tracking, and timestamps captured at the moment of sale rather than reconstructed after the fact. Google Play’s new process does not make that kind of evidence useful. It makes it time-critical.

## Where should Google Play chargeback liability live versus D2C?

Not all chargeback exposure is a platform rule. Some of it is a channel-design choice.

The important point is that these are not interchangeable.

Google Play liability sharing is policy. You can build better evidence systems around it, but you cannot negotiate the core allocation. After August 2026, the Play channel has a fixed chargeback rule, and the studio’s lever is readiness.

D2C is different. In direct sales, the merchant of record determines where the liability sits. If Tebex is the Merchant of Record, Tebex is the merchant on those transactions, takes on the chargeback liability for that channel, and runs the dispute and evidence process. That does not reduce the studio’s Play exposure. It reduces the amount of revenue for which the studio is personally carrying dispute liability.

Treat competitors fairly here: Xsolla and Paddle also operate MoR models. The question is not “who is best?” The question is: “What does my contract actually assign, per channel?”

## Verified quotes needed

– One attributable quote from a recognized payments analyst or fraud researcher on rising dispute costs and small-ticket asymmetry. This should come from a public, linkable source. – One attributable quote from a Tebex executive on how Merchant of Record shifts chargeback liability on D2C. This should come from a Tebex-approved public source.

## What are the key Google Play chargebacks FAQ answers?

**Who pays Google Play chargeback fees in 2026?** For orders placed after August 3, 2026, Google Play and developers share chargeback costs. The developer pays the purchase price minus Play’s service fee, plus the financial-institution chargeback fee, while Google continues to cover the service fee portion [[Google Play Help]]. Historically Google absorbed most of this, so the shift is a genuine liability transfer rather than a simple rate change. Payments leads should model the fixed bank fee separately from the ticket price, especially for low-value IAP where a fee reportedly reaching $100 can exceed the sale many times over [[PiunikaWeb]].

**What Google Play API helps dispute chargebacks?** Google provides an optional Review Refund flow. When a `PendingRefundReviewNotification` real-time developer notification arrives, the developer responds through the Review Refund API with a refund preference and purchase-usage evidence. The window is short, typically about 24 hours [[Android Developers]]. The Voided Purchases API then lets you detect refunds and chargebacks server-side and revoke entitlements to limit repeat abuse [[Google Play Console]]. The workflow is mechanical. Notification, evidence, API response, access decision. Manual review only works if the data is already wired.

**How do developers prove a Google Play purchase was consumed?** You prove consumption with transaction-level evidence captured when the purchase happens: delivery state, consumption state, entitlement status, and timestamps for purchase, delivery, and first use. Google’s Review Refund flow expects purchase-usage evidence inside the response window, so rebuilding the record after a dispute lands is too slow [[Android Developers]]. The durable fix is one reconciliation source fed by webhooks. Tebex applies that discipline on D2C through webhook-driven records and entitlement tracking, creating the trail before any dispute exists.

**Can a Merchant of Record reduce chargeback liability?** Yes, on the channels where the MoR is the merchant. Tebex operates as Merchant of Record for game D2C sales, so Tebex absorbs chargeback liability on those transactions and runs the dispute and evidence workflow itself [[Tebex]]. That shifts part of your revenue’s dispute exposure off your books. The qualifier matters: this applies to your direct channel, not to Google Play. Play liability sharing is fixed by Google’s policy. The practical strategy is to reduce the surface area you own where you can, and stay evidence-ready where you cannot.

## What is the bottom line on Google Play chargebacks?

The liability moved. The question is whether your evidence workflow moved with it.

Build the state machine before August 2026: notification, evidence pull, API response inside 24 hours, and entitlement revocation. Otherwise, you pay the difference per dispute. On Play, the lever is readiness. Off Play, the lever is where liability lives. Tebex as Merchant of Record lets studios move a slice of revenue, and the chargeback risk attached to it, off their own books.

Decide now. After August 3, every missing workflow gets priced one dispute at a time.

## SOURCE PACK