The short answer: for orders placed after August 3, 2026, Google Play no longer absorbs chargeback costs. The developer now bears the purchase price (minus Google's service fee) plus the card-network or bank chargeback fee, typically reported at $15–$25 per dispute. Google keeps only its own service fee. For you as a buyer, the practical consequence is simple: developers now have real money at stake in every dispute, so expect them to contest refunds and chargebacks harder — and to use Google's new Review Refund API to do it.
What actually changed
Until August 2026, Google absorbed chargeback losses on Play purchases and simply notified the developer after the fact. From orders placed after August 3, 2026, the split reported across developer press is:
- Developer pays: the purchase price minus Google's service fee, plus the chargeback fee assessed by the financial institution (typically $15–$25).
- Google pays: only its own service fee on the transaction.
On a $5 in-app purchase, that means a lost dispute can cost the developer roughly $20–$30 once the fee is added — several times the sale itself. The change was posted quietly in Play's developer terms in early 2026 rather than announced widely, which is why many developers — and buyers — only noticed it when disputes started landing.
The Review Refund API
Alongside the cost shift, Google launched a Review Refund API (July 2026) that lets developers submit delivery and consumption evidence — that the item was delivered, used, or consumed — when a chargeback request arrives. One industry summary reports developers have a short window (around 24 hours) to contest through this route, so evidence has to be ready in advance. The API does not change who pays if the dispute is lost; it only gives developers a structured way to fight.
That matters for buyers because the evidence a developer can now surface quickly — login records, item-consumption logs, device data — is exactly the evidence that decides friendly-fraud cases. A refund request that once sailed through because nobody had an incentive to contest it may now meet a prepared response.
What this means for you as a buyer
- Refunds may get slower and more contested. A developer that used to shrug at a refund now has a financial reason to check whether you used the item first.
- “I didn't recognize it” needs more care. Check your Play order history and family sharing before disputing: a family member's purchase or a forgotten subscription is the most common “unknown” Play charge, and a developer's usage logs will show it.
- The chargeback route is unchanged for you. Your bank dispute still runs on the usual clocks — roughly 120 days from the transaction under network rules, and the FCBA's 60-day written-notice window for credit cards. What changed is only who bears the cost on the other side.
Your refund playbook now
- Start in Play, not at your bank. Google's self-service refund window is about 48 hours from purchase; after that, request through the developer or Play support. A store refund is faster than a bank dispute and does not put your account standing at risk.
- Keep the paper trail: order number, purchase date, what was delivered, when you asked for a refund, and the developer's reply.
- If you go to your bank, be precise: say whether the item never arrived, was not as described, or was unauthorized — each runs under a different reason code, and a vague “fraud” claim on a purchase you actually used is the easiest kind for a developer to defeat.
- Use our App Store & Google Play Refund Checker to map the store route against the bank route before you choose.
How Apple already worked this way
Apple's App Store has long passed chargeback costs to developers, so this change brings Google Play into line with Apple's model rather than inventing a new one. The lesson from Apple's ecosystem applies here too: where developers pay, developers contest — and buyers who document their case (order, delivery, refund request) win more often than buyers who file a bare “I want my money back.”
FAQ
Do I now pay a fee when I dispute a Google Play purchase?
No. The cost shift is between Google and the developer. You pay nothing extra to dispute; the developer bears the purchase price plus the network chargeback fee if the dispute is lost.
Does this change my refund rights?
No. Your rights against the store and your bank are unchanged. What changed is the developer's incentive to contest — so your evidence matters more than it used to.
What is the Review Refund API?
Google's July 2026 tool letting developers submit delivery and consumption evidence when a chargeback request arrives. It helps developers contest disputes; it does not decide them, and it does not change who pays if the dispute is lost.
Should I still dispute a Play charge with my bank?
Only after the store route. Request a refund in Play or from the developer first — the roughly 48-hour self-service window is the fastest path — and keep the bank dispute for cases where the store refuses or the charge was genuinely unauthorized.
Related reading
Sources (checked October 26, 2026): Google Play developer chargeback policy change (orders after August 3, 2026), as reported by Tebex, Verisoul, Chargebacks911 and Xsolla in 2026 (developer bears purchase price minus service fee plus a typically $15–$25 network fee; Google bears its service fee; Review Refund API launched July 2026); Google Play refund windows from Google's own support pages, as covered in our App Store & Google Play guide.
This guide is general information only — not legal or financial advice. Last updated: October 26, 2026.
Chargeback Clock