All articles
Playbook8 min read

Accidental in-app purchases are the refunds you can't win, so the fix belongs on your purchase screen

Accidental in-app purchases come back as refunds on both stores, and no usage evidence proves a tap was meant. Here's how Apple and Google label them, what each one costs you in compute and payouts, and the purchase screen design that stops them before the charge exists.

A thumb hovering over a phone showing a mobile game shop while a small child's hand reaches in, the moment most accidental in-app purchases happen

Key takeaways

  • Apple labels every refund request with a customer-provided consumptionRequestReason. UNINTENDED_PURCHASE means the customer didn't intend to make the in-app purchase, and it sits alongside FULFILLMENT_ISSUE, UNSATISFIED_WITH_PURCHASE, LEGAL and OTHER.
  • Google Play's Voided Purchases API records an accidental purchase as voidedReason 4, Accidental_purchase, one of nine reasons numbered 0 to 8. Google stamps it after the purchase is already voided.
  • Apple sends a CONSUMPTION_REQUEST when a customer requests a refund on any product type. The developer has 12 hours to respond through Send Consumption Information, and only if the customer consented to sharing the data.
  • Google Play customers may get a refund within 48 hours of purchase without the developer being asked. After 48 hours, Google tells them to contact the developer, who can refund under its own policy and applicable law.
  • Google Play's purchase verification setting defaults to Always, which requires verification for every purchase through Google Play's billing system. Customers can change it to every 30 minutes or never, but verification is always required for apps or games for ages 12 and under.
  • In March 2023 the FTC finalized an order requiring Epic Games to pay $245 million in refunds. The FTC said Fortnite's counterintuitive, inconsistent and confusing button configuration let a single button press cause unwanted charges.
  • For Google Play orders placed after August 3, 2026, a chargeback costs the developer the purchase price, less Play's service fee, plus the bank's chargeback fees. An accident that reaches the bank costs more than one refunded in-store.

Accidental in-app purchases are the one refund case your evidence can't fix. Your server can prove the credits were spent and the content was delivered. It can't prove the tap was deliberate, and that's the only question an accidental purchase raises. So the refund goes through, and what you already paid to deliver the item stays paid. The place to beat these refunds isn't the refund flow at all. It's the purchase screen, before the charge exists.

How Apple and Google label accidental in-app purchases

Both stores give the accident its own label, but at very different moments. Apple attaches it to the refund request while the request is still open. Google attaches it to the void, after the money has already moved back.

StoreWhere the label appearsValueWhen you see it
AppleconsumptionRequestReason in the CONSUMPTION_REQUEST notificationUNINTENDED_PURCHASEWhile the request is open, before Apple decides
Google PlayvoidedReason in the Voided Purchases API4, Accidental_purchaseAfter the purchase is voided
Google PlayvoidedSource in the Voided Purchases API0 user, 1 developer, 2 GoogleAfter the purchase is voided

Apple asks before it decides

Apple's Send Consumption Information documentation says the App Store sends a CONSUMPTION_REQUEST when a customer requests a refund on any product type: consumable, non-consumable, non-renewing subscription or auto-renewable subscription. If the customer consented, you respond within 12 hours. If they didn't, Apple says not to respond at all.

The notification carries consumptionRequestReason, which Apple describes as the customer-provided reason for the request. It has five values. UNINTENDED_PURCHASE means the customer didn't intend to make the in-app purchase. The others are FULFILLMENT_ISSUE, UNSATISFIED_WITH_PURCHASE, LEGAL and OTHER. Apple uses the consumption data you send to inform its decision. The decision is still Apple's.

Google tells you afterward

Google Play's refund policy says a customer may be able to get a refund within 48 hours, depending on the details of the purchase. Nobody asks you. After 48 hours, Google tells the customer to contact the developer, who can process refunds according to their own policies and applicable law. Either way, the void shows up in the Voided Purchases API with a voidedReason, and 4 is Accidental_purchase.

The only Google Play flow that asks you for evidence is a chargeback. Google sends a PendingRefundReviewNotification, and you have 24 hours to call orders.reviewrefund with a refund preference and usage evidence. Google records your first call and ignores any later ones.

What accidental in-app purchases cost you in money

A refund returns the price. It doesn't return what you spent between the tap and the refund. For a product with real delivery costs, that gap is the loss.

Cost driverWhen you pay itRecovered after the refund?
Model or API calls behind spent creditsAt consumptionNo
Compute and bandwidth to deliver contentAt deliveryNo
Storage for files the customer createdEvery month you keep themOnly if you delete them
Payouts to creators, affiliates or partnersAt your payout runOnly if your terms allow a clawback
The purchase priceAt purchaseReturned to the customer

Here's a hypothetical. A $19.99 credit pack gets bought by a mis-tap, and a child spends every credit on image generations within the hour. The parent asks for the money back and gets $19.99. Your inference provider still invoices every generation at its normal rate. The refund was free for the customer. It wasn't free for you.

When the accident reaches the bank

A customer who doesn't know where to ask may call their bank instead. That turns the accident into a chargeback, and a chargeback is final once the bank decides. For Google Play orders placed after August 3, 2026, you pay the purchase price, less Play's service fee, plus the bank's chargeback fees. A refund costs you the sale. A chargeback costs the sale and a fee on top.

How to stop accidental in-app purchases on the purchase screen

The store's payment sheet is the last gate, and you don't control it. Everything before it is yours: where the buy button sits, what it looks like, and what one tap does.

What the FTC held against Epic

On March 14, 2023, the FTC finalized an order requiring Epic Games to pay $245 million to refund Fortnite players. The FTC said Epic used dark patterns to get players of all ages to make unintended purchases. Its complaint described a counterintuitive, inconsistent and confusing button configuration, where a single button press could lead to unwanted charges, and said children could buy items without parental consent.

The order bars Epic from charging consumers through dark patterns or without their affirmative consent. It also bars Epic from blocking consumers' access to their accounts for disputing unauthorized charges. The Commission voted 4-0. Epic separately agreed to a $275 million penalty under the Children's Online Privacy Protection Act Rule.

Give the buy button one job

  • Keep buy buttons away from preview, play and close buttons, especially on small screens.
  • Make the same button do the same thing on every shop screen. Never swap a preview control and a purchase control between items.
  • Put the price and the item name on the button or right next to it, so the tap and the charge read as one decision.
  • Never fire a purchase from a pop-up the player opened by tapping something else.

Add your own confirmation for expensive items

The store's sheet confirms payment. Your own step confirms intent. For your highest-priced consumables, add a second screen that names the item and the price, or a press-and-hold buy control. It costs a little conversion on your priciest product. It saves the delivery cost on every purchase that would've been refunded.

A developer sketching a purchase confirmation screen on paper beside a phone prototype, the design work that prevents accidental in-app purchases

Point families at Google Play's purchase verification

Google Play's purchase verification setting has three frequency options. Always is the default and requires verification for every purchase through Google Play's billing system, including inside apps. Every 30 minutes lets purchases go through for half an hour after one verification, on mobile only. Never turns it off, and Google warns that this may result in unauthorized purchases.

Verification is always required for apps or games for ages 12 and under. Biometric verification is optional, and Google notes that any biometric stored on the device can verify purchases for every Google Account on it. That's worth a line in your support article, because a shared family tablet is where accidental purchases start.

How to handle an accidental purchase refund when it lands

On the App Store

  • Read consumptionRequestReason on every CONSUMPTION_REQUEST. Store it with the transaction.
  • If the customer consented, answer within 12 hours with an accurate deliveryStatus and, for one-time purchases, consumptionPercentage.
  • When the reason is UNINTENDED_PURCHASE and nothing was used, GRANT_FULL is the honest refundPreference. When everything was spent, say so with accurate numbers. Apple weighs it. Apple decides.

On Google Play

  • Pull the Voided Purchases API on a schedule and revoke the unspent remainder of every voided item.
  • When a PendingRefundReviewNotification arrives, respond through orders.reviewrefund within 24 hours. Your first call is the one Google keeps.

Revoke the item, not the account

Take back what was refunded and leave the rest of the account alone. Locking players out over a disputed charge was one of the practices the FTC's Epic order prohibited, and it turns a small refund into a support fight.

Treat accidents as a product metric

Track the share of refunds tagged UNINTENDED_PURCHASE or Accidental_purchase, by product and by app version. A jump after a release points at a screen, not at your customers.

Frequently asked questions

Can I refuse a refund for an accidental in-app purchase?
Not on the store's side. On the App Store, Apple decides every refund, and you can only send consumption information within 12 hours if the customer consented. On Google Play, Google handles requests in the first 48 hours. After that, Google sends the customer to you, and you decide under your own policy and applicable law.
How do I know a refund was for an accidental purchase?
Check the reason field. On the App Store, the CONSUMPTION_REQUEST notification carries consumptionRequestReason, and UNINTENDED_PURCHASE means the customer didn't intend to buy. On Google Play, the Voided Purchases API returns voidedReason 4, Accidental_purchase.
Should I ban a player who refunded an accidental purchase?
No. Revoke the refunded item and keep the account open. The FTC's 2023 order against Epic Games barred it from blocking consumers' account access for disputing unauthorized charges, and a ban turns a small refund into a bigger dispute.
Does Google Play ask for a password on every in-app purchase?
By default, yes. Google Play's purchase verification setting defaults to Always, which requires verification for every purchase through Google Play's billing system. Customers can change it to every 30 minutes or never, but verification is always required for apps or games for ages 12 and under.
What does an accidental purchase cost if it turns into a chargeback on Google Play?
For orders placed after August 3, 2026, you pay the purchase price, less Play's service fee, plus the bank's chargeback fees. You also keep paying whatever it cost to deliver the item, such as model calls, compute and payouts.

Sources and further reading

RefundHalt

The refund autopilot for the App Store and Google Play

Keep reading

The next refund request is already on its way.

Set up RefundHalt in the time it takes to read another support email about a refund you didn't get to contest.