The in-app purchase bill isn’t a hypothetical. Google agreed to refund consumers at least $19 million after the FTC found it billed parents for unauthorized charges children made inside apps. Apple’s case was worse: it agreed to provide at least $32.5 million in refunds for the same reason. If a surprise charge from a free game just showed up on your statement, you’re not the first parent this has happened to, and you won’t be the last.
How a free game turns into a real bill
It starts innocently: a child downloads a game marked ‘free’ and starts playing. The game is designed around a loop that rewards spending — extra lives, faster progress, cosmetic items — and the purchase button sits one or two taps away from the gameplay itself. On many devices, once a parent enters a password or uses a fingerprint to approve one purchase, the app store treats the device as authorized for a window of time, sometimes fifteen minutes, sometimes longer, during which no further confirmation is asked. A child who sees that first purchase go through without friction can tap ‘buy’ dozens of times in a row without realizing real money is attached to each tap. The card on file, usually the parent’s, absorbs every charge instantly. By the time the parent checks their banking app, the single $0.99 add-on has multiplied into a three- or four-figure total, split across many small transactions that are each individually unremarkable but devastating in aggregate. The platforms involved don’t always design this on purpose to deceive, but the incentive structure rewards the length of the authorization window: a store that asks for a password on every tap sells fewer impulse purchases than one that asks once and lets the rest flow through. That commercial incentive is exactly why regulators stepped in rather than waiting for the platforms to fix the gap on their own, and why the fix still often has to come from a parent manually changing a setting rather than from a default that protects by itself.
A plausible week with a tablet and a loot box
The following scenario is illustrative and does not describe a real family or transaction.
Picture a weekday evening: a parent hands over a tablet so a child can play a racing game while dinner finishes cooking. The parent had unlocked a cosmetic pack earlier that day and entered their password to confirm it. For the next few minutes, the store doesn’t ask again. The child, chasing a flashing ‘unlock now’ banner, taps through a dozen in-game purchases without any sense that each tap pulls real currency from a real account. Three days later, the parent opens their bank app to find an unfamiliar run of small charges from the app store, none labeled clearly enough to explain what was bought, and no obvious way to tell which charge came from which screen tap. By the time the parent cross-references the game’s own purchase history against the bank statement, nearly a week has passed, and the refund window on at least one of the smaller charges has started to look tight. The frustrating part isn’t the amount on any single line — it’s that no single moment felt like a decision to spend money, just a string of taps on a screen that looked identical to the free gameplay around it.
How to stop the next bill before it happens
Getting a refund after the fact is possible but slow and not guaranteed every time. The more durable fix is closing the gap between a child holding a device and a purchase actually clearing. That means tightening settings on the device, separating the money the child can touch from the money you need protected, and building a habit of checking statements before charges pile up.
Require a password for every single purchase
Go into your app store’s parental or purchase settings and turn off any option that lets a single approval cover a window of time. On most platforms there’s a setting that asks for confirmation on every purchase rather than treating the device as ‘unlocked’ for fifteen minutes or more. This single change removes the mechanism that let one approved purchase open the door to dozens more. It’s worth checking this setting again after any major operating system update, since some updates have been known to quietly restore the default authorization window, undoing the protection without any notification to the account owner.
Move the card off the shared device entirely
Instead of leaving your main debit or credit card saved on a tablet or phone a child uses, remove it from that device’s payment methods and replace it with a prepaid balance or gift card credit specific to that app store account. If there’s no live card number to charge, there’s no large bill waiting to happen, no matter how many taps occur. This step alone tends to do more than any password setting, because it removes the financial exposure rather than just adding friction in front of it.
Set a hard spending cap tied to the child’s profile
Most major app stores let you create a managed or family account for a child with its own purchase limit, sometimes as low as zero without explicit approval. Set that cap deliberately, rather than relying on the default, and review it after any software update, since settings occasionally reset. If the platform allows a notification every time the child’s account attempts a purchase above a small threshold, turn that on too, so you hear about an attempted spending spree the same day it happens rather than the same week.
Check your statement weekly, not monthly
Small app-store charges often sit quietly for weeks before anyone notices the pattern. A short weekly glance at your card’s transaction list, specifically filtering for app store or digital purchase entries, catches a runaway spending spree within days instead of a full billing cycle, which matters if you want to request a refund while it’s still fresh. Most platforms give you a narrower window to dispute charges than your bank does, so the earlier you catch the pattern, the more options you still have open.
Why a dedicated virtual card changes the math
The core problem in nearly every one of these cases is the same: a real card, with a real limit, sitting behind a device a child can unlock. A virtual card service built for exactly this kind of exposure lets you issue a separate card number for the app store or for the child’s device specifically, funded with only the amount you’re willing to lose, and capped so it can’t be charged past that ceiling even if every confirmation screen gets tapped through. Some services let you freeze or delete that card instantly from your phone the moment you notice unusual activity, cutting off further charges without touching your main account at all. Because the card number is disposable and scoped to one purpose, a spending spree inside a game simply stops once the small funded balance runs out, rather than pulling from a card connected to your full checking account. This doesn’t require trusting a child to behave differently or hoping a setting never resets on its own; it puts a hard financial wall between the tap of a button and the rest of your money. For a household with more than one device in the hands of more than one child, a virtual card tool removes the need to remember which app store account has which limit, because the ceiling lives on the card itself, not buried three menus deep in a settings panel that gets reset by the next software update. Picture the same racing-game scenario from earlier, but with a $10-funded virtual card attached to the tablet instead of the family’s main debit card: the dozen taps on the ‘unlock now’ banner still happen, but the eleventh or twelfth purchase simply fails once the balance is gone, and the parent’s actual checking account never sees a single line item from the incident.
Veritasaffiliate link
Virtual cards for online payments — the main card stays out of checkouts
