In-App Purchase Chargebacks: How App Developers and Game Studios Win
Quick answer
In-app purchases are among the hardest chargebacks to win because they often involve "I didn't make this purchase" claims, including children using parents' accounts. Key evidence: device logs showing the purchase was made from the account holder's device, session activity proving account access, and IP address matching the cardholder's home location. Apple and Google handle some disputes directly — but chargebacks still reach merchants through acquiring banks.
The in-app purchase dispute landscape is complicated by two layers of intermediaries — Apple and Google — who each have their own dispute resolution processes sitting above the card network chargeback process. Understanding which layer a dispute enters determines both your evidence strategy and your realistic win rate.
How In-App Purchase Chargebacks Work
Unlike physical goods, in-app purchases leave no shipping address or delivery confirmation. The absence of tangible proof of delivery makes these disputes structurally harder to defend. The chargeback flow:
- Cardholder contacts their issuing bank to dispute an in-app purchase charge they claim is unauthorized.
- The dispute flows from the issuing bank → card network (Visa/Mastercard/Amex) → the relevant store (Apple/Google) or directly to your acquiring bank if you process payments independently.
- Apple and Google attempt resolution first using their own dispute policies, which tend to be customer-friendly. If they resolve in the cardholder's favor, they claw back the payment from the developer.
- If the dispute isn't resolved at the platform level (or if the purchase was processed outside Apple/Google billing), a formal chargeback reaches you through your acquiring bank.
The key practical difference from physical goods: your evidence must demonstrate the purchase was intentionally made by someone with legitimate access to the account — not that a product was delivered to a particular address.
Apple App Store vs Google Play — Who Handles What
The dispute path differs significantly between Apple and Google:
| Scenario | Apple | Google Play |
|---|---|---|
| Platform billing dispute | Apple resolves first; if cardholder wins, Apple deducts from developer payout (not a formal chargeback) | Google resolves first; unresolved disputes escalate to formal chargeback reaching the developer |
| Apple Pay / Google Pay dispute | Formal chargeback can reach the developer through acquiring bank | Formal chargeback can reach the developer through acquiring bank |
| Direct payment (outside platform billing) | Full chargeback reaches developer directly | Full chargeback reaches developer directly |
| Developer appeal options | Limited — Apple's customer-friendly policies give developers little recourse | Google Play Console dispute resolution center; evidence can be submitted |
| Default outcome for developers | Typically favors cardholder without strong evidence | Typically favors cardholder without strong evidence |
Both platforms have customer-friendly policies, meaning developers lose by default unless they submit strong evidence. The absence of a response is treated as acceptance of the chargeback.
Most Common Dispute Reasons for In-App Purchases
(a) Child made the purchase — most common
The most frequent in-app purchase dispute type. Parent claims their minor child used the account or device to make purchases without permission. These are difficult to win because card networks and platforms generally side with the cardholder — but parental control configuration status is your strongest defense.
(b) Account takeover
A criminal gained access to the customer's account (usually via phishing or credential stuffing) and made purchases. These can be winnable if you can show the purchase came from the account holder's own device and historical IP range — which would suggest the account wasn't actually taken over, or that the cardholder is misrepresenting the situation.
(c) Forgotten purchase / unrecognized billing descriptor
Customer doesn't recognize the merchant name on their card statement. This is especially common when your billing descriptor doesn't match your app name (e.g., "MOBILEGAMES LLC" instead of your app's brand name). This dispute type is preventable — clear descriptors and purchase receipts eliminate most of these cases before they become chargebacks.
(d) Subscription auto-renewal
Customer forgot a subscription was active and disputes the renewal charge. Strong evidence: prior payment history showing repeated successful renewals, renewal reminder emails sent before the charge, and accessible cancellation instructions in the app. The longer the renewal history, the stronger your position.
Evidence That Wins In-App Purchase Chargebacks
Building a winning evidence package for in-app purchases requires logs and data that physical goods merchants don't typically need. Start collecting and retaining this data before disputes occur:
- Device ID logs showing purchase from account holder's registered device. If the purchase was made from a device the account has used for prior payments, this is strong evidence that the account holder (or someone with physical access to their device) made the purchase.
- Session logs with timestamps showing the account was actively used before, during, and after the disputed purchase. An account with continuous activity surrounding a purchase is harder to claim was accessed by an unauthorized party.
- IP address matching the cardholder's registered location. If the purchase IP matches the account's historical home IP range, this undermines account takeover claims.
- In-game or in-app activity logs showing purchased items were used — this is the strongest signal available. If virtual currency was spent, items were equipped, or features were accessed after the purchase, the account holder almost certainly made the purchase or knows who did.
- Email confirmation sent to the account email (which was not disputed as compromised). If the cardholder received a receipt and didn't dispute it at the time, this weakens late-stage unauthorized claims.
- Prior purchase history from same account and device — establishes behavioral pattern. Multiple prior purchases without disputes make a single "unauthorized" claim less credible.
- For child disputes specifically: document whether the account was set up without parental controls enabled. If parental controls were available and the account holder chose not to use them, responsibility shifts to the cardholder.
Evidence retention
Most payment processors require evidence within 7–14 days of the chargeback notification. Device logs, session data, and IP records must be retained and queryable by transaction ID or account ID to build evidence packages quickly. Set up retention policies before you need them.
How to Reduce In-App Purchase Disputes
The most effective in-app purchase chargeback strategy is prevention. Most disputes in this category are avoidable:
| Prevention measure | Dispute type it prevents |
|---|---|
| Billing descriptor matching app name exactly | "I don't recognize this charge" disputes |
| Immediate purchase confirmation email with itemized receipt | Forgotten purchases and unrecognized charges |
| In-app purchase receipt accessible in account history | Disputes where cardholder can't find proof of purchase |
| Parental control prompt at account setup (and before purchases on shared devices) | "My child made this purchase" disputes |
| Subscription reminder email 7 days before renewal | Subscription auto-renewal disputes |
| Easy, visible cancellation process | "I couldn't cancel" disputes and friendly fraud based on frustration |
Implementing all six measures consistently typically reduces in-app purchase dispute rates by 30–50%. The subscription reminder email and clear billing descriptor alone address the two largest dispute categories.
Frequently Asked Questions
Who handles in-app purchase chargebacks — Apple/Google or me?+
What is the best evidence to win an in-app purchase chargeback?+
How do I fight "my child made this purchase" claims?+
Can I win an in-app purchase account takeover dispute?+
How do billing descriptor mismatches cause in-app purchase chargebacks?+
ChargeMate builds evidence packages for in-app purchase disputes, including device log analysis and session documentation. $10/case.
See outsourcing plans →