What Happens When Players Dispute the Money They Spent?
Gross revenue is a story you tell yourself. Net revenue — after refunds, chargebacks, and clawbacks — is the number that pays your team. Mini-games sit in a particularly nasty corner of this: instant digital goods, often bought by minors on a parent's card, often after a losing streak. Here is how the dispute machinery actually works and what you can do before it eats you.
Q: What's the difference between a refund and a chargeback, and why should you care?
A refund is clean: the player (or you) asks the store — Apple or Google — for the money back, it's returned, done. A chargeback is the player going around the store to their bank or card issuer to reverse the charge; the issuer passes it to the platform, and the platform lands it on you as a dispute. Chargebacks cost fees, and a high chargeback rate can get your ability to take payments suspended entirely. The silent majority of game disputes is friendly fraud — the player got the goods and disputed anyway, often "I didn't authorize this" from a parent who found the statement. You cannot outsource this to "the platform handles it"; the platform handles it by debiting you.
Q: Why do mini-game IAPs attract disputes more than you'd expect?
Digital goods are structurally high-risk: no shipping, instant delivery, and — crucially — a short emotional window. A kid spends during a session; a parent sees a $49 charge three days later and disputes it as unauthorized. Both Apple and Google will frequently side with the parent and claw back the amount from your balance. Your only real defense is proof: what was purchased, when, what was delivered, and what age/consent signals you captured at the moment of purchase. Weak or absent auth at checkout equals weak disputes, and you lose them by default.
Q: What can you actually do to reduce disputes and win them?
Log proof of delivery server-side, tied to the device and account — not just "we have a record," but a defensible one. Put an age gate and, where it matters, a parental-consent step in the purchase flow; it sharply cuts unauthorized-claim success. Offer an in-game refund request with a window you control, because a player who gets a clean refund from you won't open a bank dispute. And resist over-aggressive bans: a banned player disputes out of spite, and you'll lose that one too. The tradeoff worth naming: tighter consent UX slightly lowers conversion but cuts clawbacks far more — most teams under-price that trade.
Q: How do you model this so it doesn't sink you?
Track net revenue from day one, with refunds + chargebacks + clawbacks as a visible line item — for games with kid exposure this is routinely 2–8% of gross, not rounding error. Set a chargeback-rate alarm well below the platform's punitive threshold, because once you cross it, payouts can be frozen while you argue. Keep a lightweight dispute process so a spike doesn't become a fire. And accept the uncomfortable truth: some fraud is the cost of doing business. The goal is to stay comfortably under the threshold where platforms punish you, not to chase zero — zero is unachievable and the pursuit will damage the honest players.
| Type | Who initiates | Direct cost | Your defense | Prevention |
|---|---|---|---|---|
| Refund | player / store | low | n/a | in-game window |
| Chargeback | bank / issuer | fees + loss | proof of delivery | age gate, consent |
| Clawback | platform | full amount | purchase signals | minor-spend controls |
