Last updated: October 21, 2026
Quick answer: How to Block In-App Purchases on iPhone and Android usually takes 2 settings: on iPhone, use Screen Time; on Android, use Google Play authentication and Family Link. Want the strictest setup? Block purchases on the device, then keep approval rules on the account.
In-app purchases are easier to shut down once the right buying settings are switched on. What matters is the goal: block purchases outright, require approval each time, or simply force a password prompt before every sale. This guide on How to Block In-App Purchases on iPhone and Android follows both platforms through 2 main paths. One size does not fit both.
Key takeaways
- On iPhone, the control point is Screen Time and its purchase settings.
- On Android, the main control point is Google Play purchase authentication, usually paired with Family Link for a child’s device.
- “Block purchases,” “require approval,” and “ask for a password” are not the same thing.
- If a child can still install an app, they may still reach an in-app store unless purchase controls are set separately.
- The strongest setup is usually device controls plus account-level purchase rules.
How to block in-app purchases on iPhone
On iPhone, the cleanest route is Screen Time > Content & Privacy Restrictions > iTunes & App Store Purchases. From there, you can block app installs, deleting apps, and in-app purchases in one place.
- Open Settings and tap Screen Time. If Screen Time is off, turn it on first so the purchase controls appear.
- Tap Content & Privacy Restrictions and switch it on. When this works, the menu opens into detailed limits instead of a simple on/off screen.
- Tap iTunes & App Store Purchases. This section is where Apple separates app installs from in-app buying.
- Tap In-app Purchases and set it to Don’t Allow. The change should show as a blocked setting rather than a prompt setting.
- If you also want to stop app installs, set Installing Apps to Don’t Allow. That matters because a child who can install new games can still run into purchase prompts inside them.
- Set a Screen Time passcode if you have not already. Without a passcode, the person using the phone can undo the restriction in minutes.
- Test the result by opening an app that normally offers coins, lives, or a subscription. The purchase button should fail, disappear, or produce a restriction message instead of a working checkout flow.
This approach beats relying only on Apple ID password prompts, because it changes the device rule itself. It is also tighter than approval-only setups. The trade-off is pretty simple: for an adult who actually buys things in apps, a full block can feel heavy-handed. In that case, a password prompt may be the better fit.
For Apple’s own wording on Screen Time and purchase controls, see Apple’s support page on Screen Time and purchase restrictions.
How do I disable in-app purchases on Android?
On Android, disabling in-app purchases usually means tightening Google Play authentication and, for child accounts, adding Family Link approval rules. Android does not use one single system switch the way iPhone does, so the exact path depends on whether the phone belongs to an adult or a child.
- Open the Google Play Store app on the Android device.
- Tap the profile icon, then open Settings. When this works, you will see Google Play options rather than the phone’s general settings.
- Go to Authentication or Purchase authentication. The label can vary slightly by device and Play Store version.
- Choose the option that asks for authentication for every purchase. That gives you a password or biometric prompt before each paid item is approved.
- If the device is for a child, open the Family Link app on the parent’s phone. This is the account-level tool Google uses for supervised child accounts.
- Turn on require approval for purchases and, if available, approval for downloads. That stops a child from buying paid apps or making purchases inside supported apps without a parent okay.
- Check the child’s Google account settings in Family Link to confirm the supervision is active. If the account is not supervised, purchase approvals may not apply the way you expect.
- Open a game or app with a store tab and try a purchase flow. A working setup should stop at a password or approval screen instead of completing the order.
Android can be a little messy here. Different phones show slightly different menus, and a manufacturer skin may move the path around. The purchase rule still lives in Google Play, but the route to it may not be identical on every Samsung, Pixel, or other Android device.
Because of that variation, a child-friendly setup is usually better than trying to memorize one exact menu path. If you are protecting a child rather than controlling your own phone, approval-based settings are usually more practical than a total block. They let the child keep using legitimate app features while preventing surprise charges.
For Google’s help pages on Google Play purchase authentication and Family Link purchase approvals, see Google’s support documentation.
Block purchases, require approval, or just ask for a password?
The right setting depends on how strict you need the control to be. A full block stops the purchase path entirely, approval adds a parent gate, and password prompts still allow the purchase if the right account owner confirms it.
A full block is best when the device is for a younger child or when accidental spending has already been a problem. On iPhone, that usually means Don’t Allow for in-app purchases. On Android, the closest match is supervised purchase approval combined with tighter account settings, because Android often works by authentication rather than a single universal off switch.
A require approval setup fits family-shared Android devices better than a hard block. If a child wants a one-time app or add-on, you can approve it without handing over permanent buying power. This is the middle ground most parents want, and it works best when the child account is under Family Link supervision. Clean, but not carefree.
A password prompt is better for an adult device or a shared household tablet where buying is allowed, just not casually. Set to every purchase, it adds friction without making the store unusable. The drawback is obvious: anyone who knows the Apple ID password, Google password, or has the approved biometric can still buy.
A generic mistake is treating one setting as if it covers all devices. An iPhone restriction does not control an Android tablet, and a Google Play rule does not automatically stop purchases inside a separate app store on another platform. That is why a household with both iPhone and Android devices often needs two different setups.
How to stop accidental purchases on your child’s phone?
If the goal is to stop accidental purchases on your child’s phone, the fastest practical fix is to block the purchase path at the device level rather than rely on a warning. On iPhone, use Screen Time to set In-app Purchases to Don’t Allow. On Android, use Family Link to require approval for purchases and downloads.
A practical setup is: parent passcode on iPhone, supervised child account on Android, and no saved payment method on the child profile unless an adult truly needs it. That last part matters because a 2-tap checkout is exactly what leads to surprise charges. Blink and the money is gone.
The most common failure is leaving app installs open while blocking only paid items. Many free games still push coins, boosters, and subscriptions from inside the app. If the child can install that app without approval, the spending temptation is still there. Blocking downloads as well as purchases gives cleaner results.
A second weak spot is shared credentials. If the child knows the parent Apple ID or Google password, purchase controls are easier to bypass. A 6-digit device passcode does not matter if the account password is already in the child’s head. Change the shared password and move the purchase rule into Screen Time or Family Link instead of trying to enforce it by memory.
What to check if the purchase block still does not work
If a purchase still goes through, the usual problem is that the wrong account or the wrong device got the restriction. The fix is usually in the account layer, not the app itself.
Start with the active account. On iPhone, confirm the restriction is on the same Apple ID that is making the purchase. On Android, confirm the Google account in Play Store is the supervised child account and not a second adult account added to the phone. A second account can turn the whole setup into a loophole.
Next, check whether the setting is set to prompt instead of block. “Require password” still allows a purchase after approval. “Ask every time” still allows the purchase if the right person approves it. Only a true block stops the transaction from completing.
Then check app-specific billing. Some apps send you through their own subscription flow after the app is already installed. In that case, device-level restrictions still help, but the store rules need to be paired with account approval rules. On Android, that is where Family Link matters. On iPhone, Screen Time should still be the first line of defense.
If you manage both platforms in one household, write the rule down once: iPhone uses Screen Time purchase restrictions; Android uses Google Play authentication and Family Link. That keeps the system from drifting after a phone reset or a new tablet setup. Otherwise, the rule slowly gets fuzzy.
What this setting can and cannot do
Purchase blocking stops spending, not app content. It will not remove ads, hide every upsell, or replace full parental controls. It also will not stop a child from seeing a purchase button inside an app; it only stops the transaction from finishing.
That limitation matters because some readers expect a purchase block to act like a full child-safety suite. It does not. A child can still open a game, tap a gem pack, and reach the checkout screen. The point of the restriction is that the checkout should fail, ask for approval, or demand a password. If your goal is broader content filtering, that belongs in a separate setup for screen time and content restrictions.
The upside is narrower and more reliable than a broad “parental control” promise. You are targeting one behavior: buying things inside apps. That makes the setup easier to audit. If a checkout is still going through, the fault is usually in the account rule, the supervision status, or the purchase prompt setting.
If you want the bigger picture after this, the hub on Parental Controls and Device Setup is the right next stop. It covers the broader setup without mixing it into the purchase-blocking steps here.
How do I stop accidental purchases on my child’s phone?
Use a device-level block, not just a warning. On iPhone, turn on Screen Time and set In-app Purchases to Don’t Allow. On Android, use Family Link to require approval for purchases and downloads. Also remove saved payment methods from the child’s account if you do not need them there.
Can I require a password for every app purchase?
Yes, on many setups you can require authentication for each purchase. On iPhone, that is handled through Screen Time and Apple ID purchase rules. On Android, Google Play offers purchase authentication settings, and Family Link can add approval steps for supervised child accounts. The result is friction, not a total block.
How do I disable in-app purchases on iPhone?
Open Settings > Screen Time > Content & Privacy Restrictions > iTunes & App Store Purchases and set In-app Purchases to Don’t Allow. If you want a stricter setup, also block app installation and protect the settings with a Screen Time passcode. According to Apple, that passcode helps prevent easy reversal.
How do I disable in-app purchases on android?
Open the Google Play Store, go to Settings, then find Purchase authentication and set it to require approval every time. For a child account, use Family Link to require parent approval for purchases and, if available, downloads. Android usually handles this through Google Play and supervision rather than one universal off switch.
Drafted with AI; not yet reviewed by a person.
