Google Play is making chargebacks your problem starting August 3, here's what changes

Google is about to end one of the quieter perks of selling on Play. Until now, when a customer disputed a charge with their bank instead of asking the store for a refund, Google absorbed the loss and you mostly never heard about it. For orders placed after August 3, 2026, that stops. A lost chargeback comes out of your pocket: the purchase price, minus Play's service fee, plus whatever chargeback fees the bank adds on top. Google's own exposure shrinks to the service fee it already collected.

There was no keynote moment for this. The change sits in a Play Console help article about refund protection, the kind of page you only find once money is already missing. Google's framing is that it's one half of a trade: its systems blocked 3.4 billion dollars in fraud and abuse on Play in 2025, more guardrails are coming, and in exchange developers start sharing the cost of the disputes that still get through.

The other half of the trade is genuinely new, and it's the part worth building for. For the first time, Google asks for your side before a chargeback is decided.

You finally get a say, but only for 24 hours

When a dispute needs developer review, a PendingRefundReviewNotification lands on your Real-time Developer Notifications topic and a clock starts. You have 24 hours to answer through the orders.reviewrefund API with your preference, approve, decline or neutral, plus whatever evidence you have. Google then uses what you send to contest illegitimate chargebacks with the bank on your behalf. If the window closes in silence, the dispute proceeds without you. If the mechanism sounds familiar, it should: it works a lot like Apple's consumption request, which has been asking iOS developers the same kind of question for years.

Here is the before and after in one place:

What answering actually involves

The notification carries an order id and a pendingRefundToken, and the token matters: echo it back in your response or the response is rejected. To say anything useful about the buyer you also need to know who they are, which is what setObfuscatedAccountId at purchase time is for. If you've never attached an account id to purchases, matching a chargeback to a real user is guesswork, and that's the first thing to fix.

The evidence itself is more expressive than you'd expect from Google. Beyond your verdict and whether sample content was available before purchase, you can attach a consumption percentage (in milliunits, so 45200 means 45.2%) and up to 1,000 usage events, each carrying a timestamp, the IP address it happened from, a coarse location and a free-text description of up to 5,000 characters. Where and when the product was actually used is exactly the story a bank never hears from the cardholder.

The math on doing nothing

Chargeback fees are flat and product prices aren't. On a cheap consumable the bank's fee alone can exceed what the customer paid, so a single disputed coin pack can cost you a multiple of its price. Add the compute, storage and API calls you already spent serving that purchase and the arithmetic gets worse. The API is labeled optional, and technically it is. But for orders after August 3 you're paying for lost chargebacks either way, so opting out just means losing the same disputes without a fight.

What to do before August

• Turn on RTDN for all notification types. The review request rides the same topic as your subscription events, and if you only stream subscription notifications it will pass you by without a trace.
• Start attaching an obfuscated account id to every purchase. It's the only reliable way to connect a chargeback to a real user and their usage history.
• Work out where your usage evidence lives. Timestamps and IP addresses are what separate a customer who never launched the product from one who used it for a week and then called their bank.
• Automate the answer end to end, including a fallback that fires before the deadline when your data is missing. A 24-hour, first-answer-wins window is not something a support inbox survives.

This is the shape of problem RefundHalt was built for: we provision the Play topic, turn your usage data into evidence with IP geolocation attached, and answer inside the window every time, so silence never decides a dispute for you. But whether you build it or buy it, have it running before August. The first chargeback under the new rules won't wait for your roadmap.