What a refund costs your app is more than the price you hand back

When a customer gets their money back, the number you notice is the sale price leaving your account. That number is real, but it is the smallest line on the bill. What a refund costs your app is the sale you reverse plus everything you already spent to earn and serve it, minus the one thing the store quietly gives back. Read the whole invoice and refunds stop looking like a flat return of one price. They look like what they are, a loss with several parts, only one of which shows up in the refund line.

Here is the full accounting, with real numbers and where they come from. The store returns its commission, so you lose your share and not the customer's whole payment. The compute, API calls, storage, and payouts you already burned do not reverse. And a chargeback, which is a refund's meaner cousin, now carries a bank fee your business absorbs. Walk the bill top to bottom and you can price a refund correctly, which is the first step to spending your defense only where it pays.

What a refund costs, line by line

A refund has three cost layers, and only the first is obvious. The sale price you return is layer one. The commission math that decides how much of that price is actually yours to lose is layer two. And the money you already spent to deliver the purchase, which no refund touches, is layer three. Miss any of the three and you will misprice every refund in your ledger.

Layer one is the sale, but not the whole sale

The headline is the price the customer paid. On a refund the customer receives that full price back. But you never kept the full price in the first place, because the store took its commission at the sale. So the amount that actually leaves your pocket on a refund is your share, and the store's cut is settled separately. That distinction is the difference between losing ten dollars and losing seven, and it is settled differently on each store.

Apple gives its commission back

On the App Store, when Apple refunds a customer, Apple deducts your post-commission share, not the full price. A developer who checked their own App Store Connect payment report found that Apple removed the Extended Partner Share, the column that holds the developer's proceeds, when it issued their users' refunds. In plain terms, Apple returns its own commission and takes back only what it had paid you. There is a caveat on paper: Apple's Paid Applications Agreement reserves Apple's right to keep its commission notwithstanding a refund. In ordinary transactions that clause is essentially never exercised, but it is the reason you never treat the commission return as a guarantee for fraud or abuse cases.

Google returns the service fee too

Google Play works the same way and says so plainly. When you issue a refund, Google returns the service fee to you and you see the returned fee on your next earnings report. Google Play's service fee is commonly 15 percent on the first one million dollars a developer earns each year and on subscriptions, and 30 percent above that. Apple's commission is 30 percent for most apps, or 15 percent under the App Store Small Business Program and on auto-renewable subscriptions after a year of paid service. Whatever your rate, both stores hand their cut back on a refund, so the sale-price loss is your share, not the whole payment.

The costs you already spent do not come back

Layer three is the one no store can return, because the store never held it. The instant a purchase was delivered, you had already spent real money serving it. That spend is the same whether the customer keeps the purchase or asks for a refund an hour later, and a refund reverses none of it.

Name the drivers, because they are cash

These are not soft costs. They are line items you paid for: the compute cycles that ran the feature, the model API calls you were billed per token, the storage you provisioned for the customer's data, the bandwidth to deliver it, and any creator or partner payout you already sent for that transaction. A refund returns the sale. It does not claw back a single one of those. On a heavy purchase, an image batch, a long generation, a large export, layer three can be a meaningful fraction of the sale price all by itself, and it is spent before the refund request ever arrives.

A chargeback is a bigger bill than a refund

A chargeback is not a refund, and it does not cost the same. A refund is the customer asking the store for their money back. A chargeback is the customer asking their bank to force it back, and the bank charges a fee to run that dispute. Who eats that fee is where the two stores now diverge sharply.

Apple keeps chargebacks between the bank and itself

On the App Store, a card chargeback is resolved between the bank and Apple. Apple does not pass the disputed price back to you the way a refund deducts your proceeds, and there is no separate bank fee billed to your account. That does not make card disputes free, since a refund on the same transaction would still have cost you your share, but Apple absorbs the chargeback machinery itself.

Google Play now puts the chargeback on you

Google Play changed this on August 3, 2026. For orders placed after that date, a chargeback shifts the purchase price less Play's service fee, plus the associated chargeback fees from the financial institution, onto the developer. Google Play keeps covering the service fee for that transaction. Before this change Google absorbed chargeback losses entirely, so this is a real new cost, and Google frames it as bringing Play in line with industry standards and as a reason to use the Review Refund API to contest illegitimate disputes.

Put a number on the gap

Take a ten dollar in-app purchase on Google Play at a 15 percent service fee. If you refund it yourself, you lose your share, about 8.50 dollars, and Google returns the 1.50 dollar fee. If that same purchase instead becomes a chargeback after August 3, 2026, you lose the same 8.50 dollars and you also absorb the bank's chargeback fee, which the card industry commonly puts at 15 to 25 dollars per dispute. On a ten dollar sale, the bank fee alone can cost more than the sale. That is the whole argument for issuing a refund before a dispute can escalate: the sale is gone either way, but the bank fee is only on the table once the bank gets involved.

The refunds you never got to price

Some refunds are decided without you and still cost you the full amount. Google Play's 48-hour self-service refund is granted under Google's policy with no developer input, and the money math is the same, you lose your share plus whatever you already spent serving it. The auto-refund Google issues when your app fails to acknowledge a purchase within about three days is the same loss for a purchase the customer may never have used, and unlike the others it is fully preventable by acknowledging server-side. You cannot argue these down, but you can count them correctly, and you can stop the preventable ones at the source.

How to price and prevent, without a person in the loop

Two habits turn this from a leak into a number you manage. First, tag the real cost of every purchase, the compute, API, storage, and payout it triggered, so a refund debits an accurate figure and not just the sale price. Second, close the escalation path before it opens: acknowledge purchases server-side so the three-day auto-refund never fires, and issue a refund on a clearly bad order before it can become a chargeback and pick up a bank fee. RefundHalt runs this plumbing automatically, matching each refund and dispute to its account and flipping access the moment the outcome lands, so the only refunds you pay for are the ones you could never have prevented.