Google Is Shifting Chargeback Costs to Developers. Winning Cases Will Depend on Your Data.
Later this year, Google will begin sharing chargeback costs with Android developers. When a player disputes a Play Store purchase directly with their bank, the developer pays the purchase price — minus Play's service fee — plus whatever chargeback fee the financial institution charges. Until now, Google absorbed those costs. That changes later in 2026.
Google will still contest illegitimate chargebacks on developers' behalf. But the outcome of those contests will increasingly depend on what developers bring to them.
The API Changes What's Expected of You
Alongside the cost change, Google is launching a Review Refund API in July 2026. It's optional, but functionally, it's the mechanism that determines whether Google can fight a chargeback effectively on your behalf. It’ll let developers share transaction-level data with Play: delivery status, item consumption, order state. With that information, Google can build a stronger case against illegitimate disputes. Without it, they're working with payment records alone.
Friendly fraud, where a player purchases a bundle, uses the items, then disputes the charge, is the pattern this data is designed to surface. It's also the hardest pattern to prove without game-side signals. A payment record shows a transaction occurred. Player behavior data shows what happened next.
Connecting your data sources to Google's API is now a payments operations task that lives on the publisher's side. Before this policy change, it didn't exist on Android (DTC is another story).
What "Payment Operations" Actually Means for a Game Studio
Running this well requires more than a technical integration. It means having someone who owns the process — monitoring dispute rates, tracking outcomes, understanding which evidence wins cases and which doesn't, and staying on top of response deadlines. For publishers who haven't needed that function before, the honest answer is: this probably warrants a dedicated hire.
Evidence quality is where most cases are won or lost. Publishers managing disputes without a specialist function typically win 20-30% of cases. With structured evidence and a consistent process, that win rate can exceed 80% (based on our own benchmarks).
The gap between those numbers isn't procedural. It's about knowing what to submit.
Why Gaming Disputes Require Gaming Expertise
Generic payment dispute evidence — transaction records, delivery confirmation — is a starting point. In mobile gaming, it's rarely enough on its own.
The disputes that matter most are the ones where a player claims they never authorized a purchase, or that the item wasn't delivered, while the game data tells a different story. Winning those cases means painting a complete picture of that player: their payment history, their in-game activity, their consumption behavior, their session data around the time of the disputed transaction. A player who logged 12 hours of gameplay using the items they're now disputing is not a fraud victim. But that argument only works if you can make it with data.
This is where gaming-specific payments expertise has real value. At Appcharge, we handle disputes across $1B in annual transactions — and we've built our evidence process around the signals that matter in gaming specifically. We know how to combine payment history with player behavior to construct a counter-dispute file that reflects the full picture. We recover approximately 80% of disputed GMV as a result — roughly $2M annually that would otherwise be written off across our partners' DTC revenue.
That expertise is directly applicable to how publishers should be thinking about their IAP dispute process now.
What to Do Before July
The Review Refund API launches in July. That's the practical deadline for getting your data pipeline in order. Three things worth moving on now:
Decide how you're going to own this. Dispute management is now an explicit cost center with an explicit process attached to it. That means someone needs to own it — monitoring rates, reviewing outcomes, assembling evidence. Whether that's a new hire or existing employees, the decision is worth making before the cost change kicks in and cases start accumulating.
Map your data sources. Which systems hold the signals Google's API needs — delivery state, item consumption, session activity? Are they connected to your payments infrastructure, or siloed? The integration work is more manageable when scoped early.
Understand your current dispute rate. Most publishers don't have a clean number here. Establishing a baseline — volume, rate, resolution outcomes — is the foundation for everything else. You can't improve what you're not measuring.
Publishers who build an operational response to this — owning their dispute data, connecting to the API, tracking outcomes — will win more cases than those who treat it as a fixed cost.
Appcharge processes over $1B in annual DTC transactions for mobile game publishers. Our Payment Operations and Risk teams handle dispute management, fraud prevention, and chargeback recovery 24/7 — giving our partners the operational infrastructure and data architecture to protect revenue across every channel.
