Google Play Vs. App Store Chargebacks

blog 10 1

Learn how Justt can help you keep more revenue.

Book a demo today.

In the world of mobile app developers, there is iOS and Android; however, the two are not created equal. They have important differences, even when it comes to chargebacks.  This article tackles specifically the subject Google Play vs. App Store chargebacks, so app developers can better understand the process for each and keep a greater share of their earnings in the event of payment disputes.

 

In a nutshell:

  • Apple maintains its own internal payments dispute system when a user complains directly to the App Store, similar conceptually to PayPal’s dispute system.
  • Google Play only addresses disputes filed against Google as the merchant of record by cardholders with their issuer and then seeks to collect funds from the developer.
  • Apple gives developers 12 hours to respond to payment disputes
  • Google Play gives developers up to 24 hours to respond to disputes.
  • Both companies do not expect or enable developers to send full representment letters to them, instead they request specific data points.
  • In the case of an internally handled App Store payment dispute, developers do not get hit with a chargeback fee.

App Store Chargebacks for Beginners

Apple’s App Store tries to resolve payments disputes between cardholding users and app developers without involving issuers. The process is streamlined to be much much more basic and faster than the traditional credit card chargeback process.

For starters, developers have only 12 hours to respond to a payment dispute submitted to Apple. Assuming they respond in time, Apple then has 7-10 days to decide on the case.

For their evidence submission to Apple, the developer has just five data points to choose from:

  • A binary true or false statement indicating whether the consumer consented to provide consumption data
  • An integer that represents the percentage of the in-app purchase the customer consumed to the thousandths place (e.g. 99.999%)
  • A value indicating whether the app successfully delivered a properly working in-app purchase
  • A value that indicates whether the developer prefers based on operational logic to grant the refund through the App Store or not
  • A true or false statement indicating whether the developer provided prior to purchase a free trial of the content or information about its functionality

Google Play Chargebacks: What Changed in 2026

Google Play, in contrast to the App Store, recently changed how it handles chargebacks. Before July 2026, Google which serves as Merchant of Record (MOR) for developers using its app store, would accept chargebacks from users issuing banks as the cost of doing business. No more.  

In July, Google Play launched its Review Refund API, which enables app developers to submit data that Google can craft into a representment letter to win chargeback cases filed by cardholders’ issuers. Google does not clarify in its documentation who pays the chargeback fee if the case is won. 

If Google loses or the developer does not submit data in time, the developer is debited for the chargeback and the chargeback fee, but Google credits them the original transaction fee. The app orders subject to Google Play’s new chargeback rules are those made August 3, 2026 and or later.

Developers on Google Play are given more types of data to provide as evidence that a purchase was legitimate, as compared with Apple’s App Store. They also receive a full 24 hours to respond to payment disputes, double what Apple provides developers.

How Justt Helps Developers Handle All Their Chargebacks

Whether a dispute lands in Apple’s internal resolution system, Google Play’s new Review Refund API, or a traditional card-network chargeback, the underlying challenge for developers is the same: very little time to respond with very specific data requirements.

That compressed timeline is exactly where Justt’s AI-native dispute resolution platform adds the most value. Instead of an engineering or support team scrambling to pull consumption data, delivery status, or refund preferences within a 12- or 24-hour window, Justt automates the evidence-gathering and submission process, mapping the data Apple and Google actually request directly from a developer’s existing systems.

This matters even more now that Google Play has shifted real financial exposure onto developers. Under the new rules, a developer who doesn’t respond in time, or responds with incomplete evidence, simply eats the transaction amount plus the chargeback fee. Justt helps developers build a consistent, always-ready evidence pipeline so that every Review Refund API submission reflects the strongest available case, rather than whatever a support agent can piece together in a few hours.

The platform becomes even more critical for developers operating outside Apple’s and Google’s proprietary dispute systems entirely — for example, apps using alternative billing or external web checkouts. Purchases made through those channels don’t go through Apple’s or Google’s internal dispute flows at all; they’re contested the traditional way, directly with the card networks and issuers. That’s Justt’s core strength: full representment, at scale, across any payment channel a developer uses.

Ronen Shnidman

Written by

Ronen Shnidman

Ex-journalist and major fan of fintech and OSINT, I write regularly for leading industry outlets in finance and fraud prevention. Outlets I contribute to include Payments Dive, Finextra, and Merchant Fraud Journal, and I have been cited by PYMNTS.com

Apply for this position