'My Kid Bought Gems': How to Win In-Game Purchase Chargebacks
Win a kids in-game purchases chargeback with Visa CE 3.0 evidence, refund-or-fight math and checkout controls that stop family disputes early.

Photo: Pixabay
On this page 6 sections
Key takeaways
- Under Visa CE 3.0, last month's undisputed purchase doesn't count. The two earlier purchases on the same card must be 120 to 365 days old.
- Game sales have no shipping address. The matches must come from login, device ID and IP address, and at least one must be the device ID or IP address. Log a device ID at checkout.
- In the illustrative $120 example, winning every dispute costs the same as a quick refund and still leaves six disputes on your record.
- An RDR refund removes the dispute from Visa's VAMP count, but the issuer's fraud report still counts. A fraud report that qualifies for CE 3.0 is excluded.
You can win a kids in-game purchases chargeback if you can show the purchase came from the cardholder's own account and device, and if your response answers the reason code the bank actually used. For Visa fraud disputes, that proof follows a set format. Under Visa's Compelling Evidence 3.0 rule, you point to two earlier undisputed purchases on the same card that share device, IP or account data with the disputed sale. The cheapest dispute is still the one the parent never files, so most of your effort belongs at checkout and in your support inbox.
This applies only to some sellers. If you sell currency only through the Apple App Store or Google Play, the platform bills the customer and deals with the refund or dispute. What follows is for studios and publishers that take cards directly, through a web shop or a direct checkout in the game or launcher. Those disputes land on your merchant account and count against your ratios.
Why a Parent's Dispute Usually Arrives as Fraud
Friendly fraud is the industry term for a dispute filed by the cardholder or someone in their household, not by a criminal. Game purchases produce a lot of it. Tickets are small and frequent. Cards stay saved on shared tablets and consoles, so a child who watched a parent tap "Buy" once can repeat it all afternoon.
The parent usually isn't lying. The charges look unfamiliar, especially when the statement descriptor reads like a holding company instead of a game. The bank asks whether the cardholder authorized the charges, and the honest answer is no. So the claim gets filed as card-absent fraud: Visa reason code 10.4, "Other Fraud: Card-Absent Environment."
That framing shapes your response. You can't prove the child had permission, so don't try. Your case is that the purchase came from the cardholder's own household, on a device and network the card has used with you before. That is what separates a family dispute from a stolen card. Stolen cards are a different problem in this industry, covered in our piece on how stolen cards get turned into cash through in-game currency.
Match Your Evidence to the Dispute Category
Visa and Mastercard each use their own reason codes, and your dispute portal shows the exact one. For game purchases, four categories cover nearly everything.
| Dispute category | What the cardholder claims | What your response needs |
|---|---|---|
| Fraud, card-absent | "I didn't make or authorize this." | Proof the sale came from the cardholder's known device, network and account, with earlier undisputed purchases on the same card |
| Unrecognized transaction | "I don't know what this charge is." | The receipt, the account it posted to, and prior purchases on the same card |
| Not received | "The gems never showed up." | Delivery logs showing the currency was credited, plus usage afterward |
| Processing error | "I was charged twice." | Records showing separate purchases, or a refund if it really was a duplicate |
If you answer a fraud dispute with "the gems were delivered," you will usually lose, because delivery proves the order was filled, not who placed it. A not-received dispute answered only with device matches fails for the opposite reason.
How Visa's CE 3.0 Rule Applies to Kids' In-Game Purchases
Compelling Evidence 3.0 (CE 3.0) is a Visa network rule for reason code 10.4 disputes. According to summaries from cside and Chargeflow, you need:
- Two earlier transactions on the same card that were never reported as fraud or disputed.
- Both processed more than 120 and no more than 365 days before the dispute.
- At least two of four data elements matching across all three transactions: user ID, shipping address, IP address and device ID. At least one of the two must be the IP address or the device ID.
Game sales have no shipping address. So your two matches have to come from the account login, the device ID and the IP address, and at least one of them must be the device ID or the IP address. Login plus device ID works. So does device ID plus IP address with no login match at all, which covers a sibling's second account on the same family tablet. Chargeflow also notes that a device ID and a device fingerprint don't count as two separate elements.
The 120-day floor is easy to miss. Last month's undisputed purchase doesn't count, however clean it looks. Here is an illustrative timeline. Assume the dispute is processed on June 1 and the parent disputes five gem packs bought on May 20 from the family tablet.
| Earlier Visa purchase on the same card | Days before dispute | Matching elements | Counts for CE 3.0? |
|---|---|---|---|
| May 3 | About 30 | Login, tablet device ID, home IP | No, too recent |
| January 10 | About 140 | Login, tablet device ID, home IP | Yes |
| October 5 (prior year) | About 240 | Login, tablet device ID, different IP | Yes, on login plus device ID |
The October purchase qualifies only because the studio logged a persistent device ID. Home IP addresses change when a household switches internet providers or its provider assigns a new address. If the studio had relied on IP alone, October would match on login only, and the case would fall short. Two lessons follow. Keep at least 365 days of transaction history that you can search by card, and log a device identifier at checkout, not just at login.
Card history matters more than account age. If the card has no undisputed purchases with you from at least 120 days ago, the dispute can't qualify, however old the game account is. The reverse also holds. A game account opened last week can still qualify if the same card bought from you on the same tablet and home network months earlier.
CE 3.0 is a Visa rule, and its details get revised. Mastercard handles no-authorization disputes under its own evidence rules. Ask your processor what each network currently accepts before you build an evidence export around either one.
Evidence When CE 3.0 Doesn't Apply
Some cases still win on ordinary compelling evidence. Show the account creation date and the email on file, and whether either matches the cardholder's name. Add a short table of prior purchases on the card. Then include delivery and consumption logs showing the gems went into upgrades while the account kept logging in from the same device. Consumption alone doesn't defeat a fraud claim. It does show the value stayed in the cardholder's household and wasn't resold.
Skip gameplay screenshots and pasted terms of service, because analysts are looking for matching identifiers. If your game is directed at children, the federal Children's Online Privacy Protection Act (COPPA) and state privacy laws may limit what data you collect and keep. The FTC's 2022 settlement with Epic Games included a $275 million COPPA penalty, so have counsel confirm that your logging fits those rules.
An easy-to-follow response packet uses this order:
- A one-paragraph summary tying the disputed sale to the cardholder's device, network and account.
- The disputed transaction with its timestamp, IP address, device ID and account ID.
- Qualifying prior undisputed transactions that share those identifiers.
- Account details, including the creation date and the login history around the purchase.
- Delivery and consumption logs.
- Your refund policy and evidence that it was shown at checkout.
Refund or Fight: The Math on One Afternoon
Many processors charge a dispute fee whether you win or lose, and on small purchases that fee changes the decision. The example below is illustrative. The numbers are assumptions, not network rules or MannyPay pricing.
Assumptions: a child buys six gem packs at $20 each in one afternoon, $120 in total. Your processor charges $20 per dispute regardless of outcome. Processing fees on the original sales aren't returned when you refund. That's common but depends on your contract, and since those fees are the same in every row, the table leaves them out.
| What happens | Net cost to you | Disputes on your record |
|---|---|---|
| Parent emails support and you refund | $120 | None |
| Parent calls the bank and you accept the disputes | $240 ($120 in sales plus $120 in fees) | Six |
| Parent calls the bank and you fight and lose | $240 | Six |
| Parent calls the bank and you fight and win | $120 (you keep the sales but pay $120 in fees) | Six |
Even a perfect win costs the same as a quick refund, and it still leaves six disputes with your processor. Visa's monitoring has one exception, covered in the next section: a fraud report that qualifies for CE 3.0 is left out of Visa's ratio. That gives a strong case a reason to be fought beyond the $120. The decision rule:
- Refund when the parent reaches you before the bank, when the card has no qualifying CE 3.0 history, or when the currency is unspent and can be taken back.
- Fight when the card has qualifying CE 3.0 history, the currency was used and the cardholder never contacted you. Repeat disputers who already got a courtesy refund belong here too.
Many merchants get this rule wrong: a separate refund issued after a dispute is filed generally doesn't cancel the dispute, so you can end up paying the cardholder twice. If you decide not to fight, accept the dispute in your portal. Put your refund and take-back rules into a clear refund policy for spent currency and consumables. Before locking anyone out, read our guide on whether you can ban a player for filing a chargeback. The FTC alleged that Epic locked the accounts of customers who disputed unauthorized charges, and its order bars Epic from doing that.
Checkout Controls That Stop the Bank Call
Regulators have already shown where they draw the line. In 2014, Apple settled with the FTC by agreeing to refund at least $32.5 million for kids' in-app charges. The FTC had alleged that a single password entry opened a 15-minute window for more purchases and that parents weren't told. The FTC's 2023 final order against Epic required $245 million for consumer refunds. Among its allegations, the FTC said Epic let children run up charges without any parental involvement. The controls that answer those allegations also prevent disputes:
- Re-authentication at checkout. Require a password or biometric prompt for each purchase. If a session window allows more purchases without one, tell the account holder.
- Instant receipts. Email the account holder within seconds with the game name, item, dollar amount and a direct refund-request link. A parent who sees it that afternoon emails you instead of calling the bank.
- Spend caps. Set a default daily limit per account. Send a large first purchase or a rapid burst of purchases to an extra verification step.
- Parental approval. If your audience skews young, offer a parent-managed spending setting, and require purchase approval by default on younger accounts.
- Dollar prices beside gem counts. Show what each pack costs in real money at the moment of purchase.
- A recognizable descriptor. Put the game's name and a support URL in the statement descriptor.
3-D Secure authentication adds a cardholder verification step. It can shift liability for fraud-coded disputes to the card issuer, subject to network rules. A child who knows the parent's phone passcode can still get through, so treat it as one layer among several. Our guide to 3D Secure without losing checkout conversions covers setup. This section is general information, not legal advice, so have counsel review your purchase flow.
How Family Disputes Count Against Visa and Mastercard Thresholds
Visa revised its Acquirer Monitoring Program (VAMP) in 2025. According to Visa's VAMP fact sheet, the program centers on one ratio: fraud reports plus disputes, divided by settled transactions. For U.S. merchants, the "Excessive" level is 1.5%, and it only applies to a merchant with at least 1,500 fraud reports and disputes in a month. The 1.5% took effect April 1, 2026, down from 2.2%, as cside's VAMP summary notes. Acquirers (the banks that process for merchants) are measured on their whole portfolio at 0.5% and 0.7%. Mastercard's Excessive Chargeback Merchant program starts at 100 chargebacks and a 1.5% ratio in a calendar month.
Family fraud hurts because it comes in clusters, and a fraud-coded sale can count twice under VAMP: once as the issuer's fraud report and once as the dispute. Here is an illustration. A studio settles 3,000 Visa card-not-present sales in a month, and one household files six fraud disputes. That could add up to 12 counted events, a 0.4% ratio. A studio this size is nowhere near Visa's 1,500-event minimum, so Visa won't flag it as an Excessive merchant.
The bank that processes for it is a different story. That bank's whole portfolio is held to the 0.5% and 0.7% lines, so its risk team watches accounts running at ratios like this. Processors therefore set their own internal warning lines, and a single afternoon can get you close to one. Ask for your processor's line in writing, because that number is what triggers reserves and account reviews.
Two habits keep the count down. First, answer support emails about kids' purchases within hours, because a refund before the bank call prevents the dispute entirely. Second, ask your processor about pre-dispute alerts, and know what each one removes. Visa's fact sheet excludes disputes resolved through pre-dispute solutions. However, Chargeback Gurus reports that when a dispute is resolved through Visa's Rapid Dispute Resolution (RDR), the issuer's fraud report still counts. On a fraud-coded family dispute, an RDR refund cuts the VAMP impact in half.
It doesn't remove it. Visa also excludes fraud reports that qualify for CE 3.0, depending on when Visa pulls the data. Visa extended CE 3.0 to fraud reports that never became disputes, effective April 18, 2026. That makes the device and IP logging above worth even more. Ask which alert programs your processor's service uses and how each is counted. Low dispute levels also make the approval and reserve questions in our guide to video game merchant accounts for in-game items easier to answer.
This week, pull last quarter's Visa fraud disputes and run each one through the CE 3.0 test. You need two undisputed purchases on the same card that are 120 to 365 days old. Each must match the disputed sale on two of three elements (account login, device ID, IP address), and one of the two must be the device ID or IP address.
The disputes that fail show what to fix first: log retention, device IDs at checkout or faster refunds. If your current processor treats games as a problem rather than a category it understands, MannyPay offers payment processing for gaming businesses and high-risk merchant accounts. Request a free processing quote, and a MannyPay specialist will respond within one business day.
Sources
- Visa Acquirer Monitoring Program Fact Sheet (2025)
- Visa Announces Even More VAMP Changes (Chargeback Gurus)
- VAMP Thresholds 2026: Ratio Formula, Rules, and Merchant Survival Guide (cside)
- Visa Acquirer Monitoring Program (VAMP): Full Guide (Chargeback.io)
- Compelling Evidence 3.0 Requirements (cside)
- Visa Compelling Evidence 3.0 (CE3.0): Rules and 2026 Changes (Chargeflow)
- Compelling Evidence 3.0 Update, April 2026, Explained (Chargebacks911)
- Mastercard Chargeback Monitoring Program: ECM vs. EFM (Chargeback.io)
- FTC: Fortnite Video Game Maker Epic Games to Pay More Than Half a Billion Dollars (Dec. 2022)
- FTC Finalizes Order Requiring Fortnite Maker Epic Games to Pay $245 Million (Mar. 2023)
- FTC Business Blog: 15 Minutes of Game, the $32.5 Million Settlement With Apple (2014)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


