Since August 3, Google Play chargeback costs have shifted onto developers, and here's what each dispute now takes from you

Google Play quietly changed who pays for chargebacks, and it did it in a help-center article, not a keynote. For orders placed on or after August 3, 2026, Google Play chargeback costs are shared with the developer, which in plain terms means you now pay the money back plus a bank fee every time a customer disputes a Play purchase through their card issuer. Google absorbed all of this before. It does not anymore. Here is exactly what shifted, what a single dispute takes out of your account, and the one 24-hour window where you get to push back.

What Google changed, and where it showed up

The change is small in wording and large in effect. Google Play's help center added a page titled updates to refund protection and chargeback cost responsibility, and the operative line is one sentence: for orders placed on or after August 3, 2026, Google Play and the developer share the cost of a chargeback. There was no launch event and no email blast to match the size of the shift. It landed as a dated policy note in the Play Console help center, next to a reminder that Google prevented US$3.4B of fraud in 2025.

Before this, a chargeback on a Play purchase was Google's problem. A customer disputed a charge with their bank, the bank pulled the money, and Google carried the loss. Under the new policy the loss routes to you for the part of the order you were paid, and it arrives with a fee on top.

Who pays what now

What a single chargeback now takes out of your account

The headline number is not the purchase price. It is the purchase price plus a fixed fee, and on small purchases the fee is the larger half. Card networks charge a flat chargeback fee per dispute regardless of the order size, and industry reporting puts it at $15 to $25 for a typical Play dispute. Google does not set that fee and does not disclose a figure of its own, so treat any exact number as the card network's, not Google's.

Take a $9.99 in-app purchase. Assume Play's service fee is 30 percent, so Google took about $3.00 and you received about $6.99. If that order is charged back, you pay back the $6.99 you received and you pay the chargeback fee. At $20 that is $26.99 gone on a single $9.99 sale, before you count what you already spent serving the purchase. Google keeps covering its $3.00 service fee, which is the shared part, but it does not come close to covering your side.

And the fee is only the visible loss. You almost always spent real money serving that purchase before the dispute arrived. The generated output cost GPU minutes. The API calls cost per-token charges you were billed for. Stored files cost storage you are still paying to hold. If the purchase funded a payout to a creator, that money already left. A chargeback claws back the sale and adds a fee, and none of the spend behind the sale comes back with it.

The one window where you get to fight back

Google shipped a pressure valve alongside the cost shift, and it is the only leverage you have. When a customer initiates a chargeback that needs your input, Google Play sends a real-time developer notification called PendingRefundReviewNotification. From the moment it arrives you have 24 hours to respond by calling the orders.reviewrefund method on the Google Play Developer API. Miss the window and Google decides without your evidence.

What Google lets you send

The reviewrefund call is not a free-text appeal. You submit a refund preference and structured usage evidence: the order delivery state and the item consumption status for the purchase. In plain terms, you are telling Google whether the customer already received and used what they bought. Google folds that into its own decision and, where the evidence supports it, contests the chargeback with the bank on your behalf.

The 24-hour clock is the Google Play analog of Apple's 12-hour CONSUMPTION_REQUEST window. Both stores give you a short, fixed timer to hand over evidence, and both decide without you if the timer runs out. The difference now is the stakes on the Play side. On Google, letting the timer expire can mean paying the purchase back plus the bank fee, not just losing a case you were never going to influence.

A chargeback is not a refund, and the difference decides who pays

It is easy to lump every money-back event together, but Google Play treats them differently, and only some of them ever route a cost or a question to you. Knowing which is which tells you where this new policy actually bites.

The flows that never ask you

• Google Play's 48-hour self-service refund, where a customer taps refund in the store within two days of buying, is decided by Google under its own policy. You get no input, and these are refunds handled by Google, not the bank chargebacks the August 3 change is about.
• Support-initiated refunds and Google-granted goodwill refunds are also Google's call. You are told they happened through the Voided Purchases API, but you do not approve them.
• An unacknowledged purchase auto-refunds at around 72 hours. That is a gap on your side, not a dispute, and the fix is to acknowledge purchases on time, not to contest anything.

The flow that now costs you

A chargeback is different in kind. The customer skips the store and disputes the charge with their bank. The bank pulls the money and, historically, charged a fee for doing so. That is the flow the August 3 policy moves onto you, and it is the flow the reviewrefund window is built to contest. Everything else on the list is decided above your head and always was.

What this means for your dispute pipeline

The practical response is not a heroic one. It is plumbing. The developers who come out of this cheaply are the ones who can answer, automatically and within 24 hours, a single question: did this customer receive and use what they paid for. If your systems can produce delivery state and consumption status on demand, you can feed reviewrefund and let Google contest the weak disputes. If they cannot, every chargeback is an uncontested loss plus a fee.

Wire the notification, not a person

A 24-hour window is not a human workflow. Route PendingRefundReviewNotification into an automated handler that gathers the evidence and calls reviewrefund without waiting for someone to read an inbox. A dispute that lands on a Friday night still expires on Saturday.

Record consumption at the moment it happens

The evidence Google wants, delivery and consumption, is only convincing if it was already recorded when the dispute arrives. Log what each purchase granted and whether it was used at the time it is used, not reconstructed later. The reviewrefund call is only as strong as the telemetry sitting behind it.