App refund laws change with the customer's country, and almost none of them give you a say

Where your customer lives decides which refund law covers their purchase, and for most app sales that changes almost nothing you can act on. App refund laws read very differently across the European Union, the United Kingdom, and the United States, yet they share one quiet feature: none of them hand the developer a channel to argue the case. The store still decides, and only two narrow flows ever pause to ask for your side. Here is what each region actually grants a buyer, and why the law your customer invokes rarely reaches your server at all.

The 14-day EU refund right most app buyers never actually have

Ask a European customer and many will tell you they have a legal 14-day refund right on anything they buy online. They are half right. The EU Consumer Rights Directive gives consumers 14 days to withdraw from most distance purchases for any reason, with no justification required. For a physical parcel that rule is clean. For an app or an in-app purchase, it usually evaporates at the moment of sale.

Why the waiver almost always applies

The Directive carves out digital content that is delivered immediately. If the buyer gives express consent to start the download or streaming right away, and acknowledges that doing so ends the withdrawal right, the 14 days are gone. Every major store builds that consent straight into checkout. Google Play's own EEA terms say it plainly: because the digital content is available immediately, the buyer agrees they waive the automatic statutory right of withdrawal. Apple applies the same immediate-performance waiver to its EU media purchases. So the headline right exists, and for a normal app purchase it is spent before the app finishes installing.

Services keep the 14 days, apps do not

The waiver hangs on that word immediate. Where a purchase is a service rather than delivered digital content, the 14-day withdrawal right survives. Google Play spells out the split: for service purchases the buyer keeps the right by law to withdraw within 14 days of the date of purchase, with no reason needed. Most in-app purchases are content, not services, which is why the waiver is the rule and the surviving 14-day right is the exception.

What US and UK app refund laws actually give a buyer

Cross the Atlantic and the picture inverts. United States buyers have the weakest statutory footing of the three, and the United Kingdom keeps a narrower right than its shared history with the EU suggests. Neither position hands the developer more control. It only changes what the buyer can lean on.

There is no federal cooling-off period for a digital purchase in the United States. The Federal Trade Commission's cooling-off rule covers certain in-person and door-to-door sales, not apps. A US customer's refund runs entirely on Apple's or Google's store policy, which is discretionary. If the store says no, there is no statute standing behind the buyer to override it.

The UK keeps a quality right, not a change-of-mind right

The United Kingdom inherited the same 14-day cancellation rule under the Consumer Contracts Regulations 2013, and the same immediate-digital-content waiver applies, so a downloaded app sits where it does in the EU. What the UK adds is a quality right, not a change-of-mind right. The Consumer Rights Act 2015 says digital content must be of satisfactory quality, fit for purpose, and as described. If it is not, the buyer is owed a repair or replacement, and a price reduction down to a full refund if that fails. That is a faulty-content remedy, not a window to reject an app you simply regret. The much-quoted 30-day right to reject applies to physical goods, not to intangible digital content.

The one thing every app refund law shares, you get no say

Read down that table and the pattern is louder than any single row. Whether the refund is a surviving EU service withdrawal, a UK faulty-content remedy, or a discretionary US store refund, not one of them opens a channel for the developer to respond. The buyer asks the store or the law, the store decides, and you find out when the money is already gone.

There are exactly two flows across both stores where a developer is asked for evidence before the decision, and neither is a consumer-law right. Apple sends a CONSUMPTION_REQUEST and waits up to 12 hours for a Send Consumption Information call. Google Play sends a PendingRefundReviewNotification when a bank charges back and waits 24 hours for an orders.reviewrefund call. Those are the only windows. A statutory refund, a support refund, and a 48-hour self-service refund all skip them entirely.

What a country-driven refund actually costs you

The refunded price is the part everyone sees and the smallest part of the bill. What the customer's country changes is how often a refund lands and whether a bank fee rides along with it. What it never changes is the spend you already burned to fulfill the sale.

The store returns its cut, your spend does not come back

When a store grants a refund, it reverses its own commission too, so you lose your net proceeds rather than the full sticker price. That is the good news, and it is where the good news stops. The compute you paid for is spent. The API calls you were billed for per request or per token are spent. The files sitting in storage still cost you to hold. If the purchase funded a creator payout or a prize pool, that money already left. A refund pulls back the sale and leaves every one of those costs exactly where they were.

A chargeback is a different, heavier bill

A refund and a chargeback are not the same event, and the gap between them now has a date on it. When a customer disputes a charge with their bank instead of asking the store, the outcome is a chargeback, and a completed one is bank-final. For Google Play orders placed on or after August 3, 2026, a lost chargeback bills the developer the purchase price less Play's service fee, plus the bank's chargeback fee, a flat charge the card network sets. On the App Store, Apple is the merchant of record, so the bank fight is Apple's and you carry the lost proceeds, not a separate bank fee.

How to read refunds when the law changes by country

You cannot pick which refund law your customer sits under, and you cannot appeal most of what those laws decide. What you can do is stop treating every refund as the same event.

• Separate the refunds that had a review window from the ones that did not. A CONSUMPTION_REQUEST you answered and a chargeback review you contested are cases your evidence could move. A statutory withdrawal or a store-issued refund never had a window, in any country.
• Judge your refund defense on contestable cases only. A rising count of uncontestable refunds is a product or pricing signal, not a failure of your evidence.
• Record delivery and consumption at the moment they happen, not after a dispute lands. The two flows that do ask for your side reward telemetry you already hold, and punish the reconstruction you scramble for later.
• Answer the two windows automatically. A 12-hour and a 24-hour clock cannot wait for someone to read an inbox, and they do not extend because your customer is in a different time zone.

None of this is about beating the law in your customer's country. It is about knowing which refunds were ever yours to influence. RefundHalt answers the CONSUMPTION_REQUEST and the orders.reviewrefund call automatically, inside the window, with the delivery and usage evidence you recorded at the time of sale, and it keeps the refunds no law ever let you contest in their own ledger, so the number you judge yourself by stays honest.