Friendly fraud is the chargeback where the customer already got what they paid for, and it's the one dispute your evidence can still touch

Friendly fraud is the dispute nobody warns you about, because the person filing it is not a criminal with a stolen card. It is your actual customer. They bought your in-app purchase with their own card, they used what they bought, and then they told their bank the charge was a mistake. The money reverses, the goods stay spent, and on the bank's side the case looks identical to real fraud. For app developers this matters for one reason: it is the single dispute type where your own evidence is still an input to the decision, and both stores give you only a few hours to supply it. Here is what friendly fraud actually costs, why it keeps climbing, and the narrow lever Apple and Google leave you.

What friendly fraud is, and why it is not always fraud

Friendly fraud, also called first-party fraud or chargeback fraud, happens when the genuine cardholder makes a purchase and then requests a chargeback from their issuing bank after receiving the goods or services. The name is deliberately backwards. The person on the other side is not a third-party attacker, but the same customer who tapped buy.

Intent is not always there. Some of it is deliberate abuse, a way to keep the content and claw back the cash. But plenty of it is honest confusion: a cardholder who forgot a legitimate purchase, a parent who did not recognize a charge a family member made, or straightforward buyer's remorse dressed up as a billing error. To your accounting it does not matter which. The money leaves either way.

How it differs from true fraud

True fraud is a stranger using a card that is not theirs, and the fraud tooling built into the stores is aimed squarely at it: device signals, velocity checks, stolen-card patterns. Friendly fraud walks straight through all of that, because every signal is legitimate. The real account, the real device, the real card, the real purchase. The only thing that is false is the claim made to the bank afterward, and that claim arrives long after your fraud checks have passed.

How big friendly fraud has gotten

Friendly fraud is not a rounding error anymore, and the trend lines all point one way. Juniper Research projects it will account for 28 percent of all chargebacks globally by 2031, driven by shifting consumer attitudes toward disputing charges. Chargebacks911's 2026 Chargeback Field Report, a survey of more than 250 merchants, found 83.4 percent saying friendly fraud has risen over the past three years, and 74.4 percent calling it a moderate or significant concern.

The cost is compounding alongside the volume. Industry data for 2026 puts the true cost of fraud at about $5.13 for every dollar disputed, once fees, lost goods, and handling are counted, and merchants who fight disputes win only about 43.8 percent of the ones they contest and net back roughly 10.7 percent after the effort. The lesson in those last two numbers is not that fighting is pointless. It is that fighting after the fact is a bad bet, and stopping the dispute from succeeding in the first place is where the money is.

Why friendly fraud costs an app developer more than the price

The number that hurts is never just the purchase price. It is the price plus everything you already spent to fulfill the purchase, and with a digital product almost all of that spend happens before the dispute arrives. A refund of an unopened box is a wash. A friendly-fraud chargeback on a consumed in-app purchase is a loss stacked on top of a cost you cannot recover.

The delivered cost you already paid

Walk the money backward from the dispute. The generated output burned GPU minutes you were billed for. The feature ran API calls that charged you per token or per request. The files the customer downloaded still sit in storage you are paying to hold. If the purchase funded a payout to a creator or a prize pool, that money already left your account. Friendly fraud reverses the sale and leaves every one of those costs in place. The customer keeps the value, you keep the bill.

On Google Play, the dispute now bills you directly

Until recently a chargeback on either store was mostly the store's loss to carry. That changed on Android. For Google Play orders placed on or after August 3, 2026, Google Play and the developer share chargeback costs, which in practice means a lost dispute bills you the purchase price less Play's service fee, plus the bank or card-network chargeback fee. That fee is set by the network, not Google, and industry reporting commonly puts it at $15 to $25 per dispute, a flat charge that can dwarf the price of a low-cost purchase.

On the App Store, Apple carries the bank, you lose the proceeds

Apple is the merchant of record, so a card chargeback on an App Store purchase is resolved between the cardholder's bank and Apple, and you never see that case or a bank fee for it. What you do lose is the money. When a refund is granted, the amount comes out of your proceeds, and for the refund requests Apple does route to you, your evidence is the only influence you get. The bank-fee exposure is a Google Play story; the lost-proceeds story is both stores.

The narrow window where your evidence still counts

There are exactly two moments where a store pauses and asks the developer for evidence before deciding, and friendly fraud is precisely the case they exist for. Both are short, and both close without you if you miss them.

Apple's 12-hour CONSUMPTION_REQUEST

When a customer asks Apple for a refund on an eligible in-app purchase, Apple sends your server a CONSUMPTION_REQUEST notification and waits up to 12 hours for you to call Send Consumption Information. You return structured data: whether the item was delivered, how much of it was consumed, and your refund preference. Apple still makes the call, but your answer is a documented input, and it is the one place a friendly-fraud refund on Apple can be countered.

Google Play's 24-hour orders.reviewrefund

On Android the trigger is a PendingRefundReviewNotification. From the moment it arrives you have 24 hours to call the orders.reviewrefund method with a refund preference and usage evidence, the order's delivery state and the item's consumption status. Google folds that into its decision and, where the evidence supports it, contests the chargeback with the bank on your behalf. Google records only your first call for a given notification, so gather the evidence before you respond, not after.

The friendly-fraud disputes you can never touch

Not every money-back event gives you a say, and it helps to know which ones are decided over your head so you spend effort only where it pays.

• A completed chargeback is bank-final. Once the issuing bank sides with the cardholder, no appeal to Apple or Google reverses it. Your only influence is the evidence submitted before the decision.
• Google Play's 48-hour self-service refund is Google's to grant under its own policy. You are not consulted and are notified only when it shows up as a voided purchase.
• Support-granted refunds on either store are final, with no developer appeal channel.
• An unacknowledged Google Play purchase auto-refunds at around 72 hours. That is an integration gap, not a dispute, and the fix is to acknowledge purchases server-side, not to contest anything.

How to make friendly fraud contestable before it happens

You cannot stop a customer from calling their bank. You can decide, well ahead of time, whether the dispute that follows is answerable or an automatic loss. Everything that makes friendly fraud winnable has to exist before the notification arrives.

Record delivery and consumption at the moment it happens

The evidence both stores ask for, that the item was delivered and used, only convinces if it was logged when it happened. Record what each purchase granted and whether it was consumed at the time of use, not reconstructed after a dispute lands. A reviewrefund call or a consumption response is only as strong as the telemetry sitting behind it.

Automate the answer, not a person

Wire CONSUMPTION_REQUEST and PendingRefundReviewNotification into a handler that assembles the evidence and responds on its own. A 12-hour and a 24-hour clock cannot depend on someone noticing an inbox. The disputes you win are the ones answered automatically, inside the window, every time.

Judge your protection by contestable cases only

Split your refunds into the ones with a review window and the ones without. Friendly-fraud refund requests and chargeback reviews are where a save rate means something, because there was a decision your evidence could move. Store-issued refunds carry information, not a verdict on your defenses. RefundHalt is built around that split: it answers the consumption request and the reviewrefund call automatically with the delivery and usage evidence you recorded, and keeps the uncontestable refunds in their own ledger so your numbers stay honest.