App store refunds and chargebacks explained: who decides, who pays, what you can do
How refunds work on the App Store and Google Play, how card chargebacks on web billing differ, who decides and who pays, and the practical steps developers can take.
A customer who wants money back after buying your app, subscription or digital product has two very different doors to knock on: a store refund, decided by the App Store or Google Play, and a card chargeback, decided by card networks and banks. They follow different rules, cost different amounts and leave you different amounts of say. This article summarises the platforms' own documentation - Google Play Console Help and Stripe's dispute guide, both read on 20 November 2026, plus Apple's developer notices on refund notifications.
On the App Store: Apple runs the refund desk
On the App Store, Apple sells to the end user, and refund requests go to Apple, not to you: Apple's current support page (updated September 2026) tells customers to request a refund at reportaproblem.apple.com and says that "if Apple approves your request" the funds take additional time to return - the approval decision is Apple's. What you get as the developer is visibility and reaction time. Apple's developer notices describe App Store server notifications that carry refund notifications for all types of in-app purchases - consumables, non-consumables and non-renewing subscriptions - so your backend can learn about a refund when it happens; Apple's guidance for that notification is to take action in response: adjust the user's benefits, let the user know what changed, and tell them how to resubscribe. For lookups, the current App Store Server API exposes a Get Refund History endpoint (inApps/v2/refund/lookup) that returns a paginated list of a customer's refunded in-app purchases for your app.
On Google Play: Google can refund on your behalf, and you have support duties
Google Play Console Help says users are directed to you for defects, performance issues or missing content - the Play support team does not provide user support for individual apps. You must publish a valid contact email, answer customer questions about paid apps or in-app purchases within three business days, and respond within 24 hours if Google contacts you about an urgent product issue. On money: Google may issue refunds on your behalf for unauthorized charges, under Google Play's refund policies, or as a courtesy in some situations. Buyers can also come to you directly, and you may be independently responsible under the law for issuing refunds in some circumstances - you must issue refunds in line with your stated policy. You are allowed to run a more flexible refund policy than Google's, as long as you tell users about changes and comply with applicable law. Developers can issue refunds themselves from the Payments Merchant Center.
On web billing: a chargeback is not a refund
If you sell through your own checkout, the money-back mechanism is the card dispute. Stripe's dispute documentation describes the mechanics: a dispute, also called a chargeback, starts when a cardholder questions your payment with their card issuer. The issuer opens a formal dispute on the card network, which pulls the payment amount - plus one or more network dispute fees - back through your payment provider; Stripe then debits your balance for the payment amount and the dispute fee. Two consequences follow: you pay a dispute fee regardless of the immediate outcome, and the decision sits with banks and card networks, not with you or your provider.
What you can actually do
Keep your store contact email valid and staffed, because the three-business-day response clock on Google Play is a policy requirement, not a courtesy. Wire up Apple's refund server notifications so benefits stop when the money returns, instead of months later. Where you set your own policy, write it down and keep it consistent - Google explicitly holds you to your stated policy. And for web billing, keep clean records of what was delivered and when, because that evidence is what you have once a dispute is with the banks.
What to keep in mind
Store refund policies change and some obligations depend on regional consumer law, which this article does not cover; check the current store policy pages and local rules for your markets. On Apple specifically: the current handling described above comes from Apple's September 2026 support page and the current App Store Server API reference, while the all-in-app-purchase-types coverage of refund notifications comes from a June 2020 developer notice - confirm that coverage detail against Apple's latest notification documentation before building on it.