How to Fix Google Play Store Error 403
What error 403 means
Error 403 shows up when you tap Install on the Google Play Store and, instead of downloading, you get a message that the app could not be downloaded due to error 403. Tapping Install again ends the same way — the store isn’t failing to reach Google, it’s actively declining the request.
The classic setup behind this error is simple: two Google accounts live on the same phone. Many people keep a personal account and a work or secondary account on one device, and the Play Store is free to use either one for purchases. When the store tries to place the download under the account that isn’t tied to the phone’s billing profile — or that doesn’t own the app you’re installing — Google’s servers reject the request and you see error 403. It is, in effect, a permissions decline, not a network failure.
That said, the error can also appear when only one account seems to be present. A second account that was removed from the phone sometimes leaves stale account data behind in the Play Store’s cache, and the store keeps offering that ghost account at checkout. A leftover proxy entry in your mobile data settings can produce the same declined response, and a purchase made on one account and retried on another trips the same guard. The good news is that every one of these cases clears the same way: make the phone speak to the store with exactly one clean account.
Common causes
- Two Google accounts on one phone: the store places the purchase under the wrong account and Google declines it.
- Paid app bought on another account: the signed-in account doesn’t own the app, so the store refuses the install.
- Stale account data in the Play Store cache: a removed account lingers in cached state and confuses the store.
- Leftover proxy in mobile data settings: a proxy entry in your APN routes store traffic through a dead server.
- Account sign-in session is stale: the Google account’s login session on the device has degraded and needs a fresh sign-in.
How to fix error 403 — step by step
Work through these fixes in order. Most people clear error 403 by step three.
- Check which account the Play Store is using. Open the Play Store and tap your profile picture at the top right — the email shown is the account placing the order. If the app is free, any account works; if you paid for the app, switch to the account that bought it using the drop-down under your profile picture, then retry the download.
- Remove the extra Google account. Go to Settings > Passwords & accounts, tap the secondary Google account, and tap Remove account. When two Google accounts live on one phone, the store often places the purchase under the wrong one and Google declines it with error 403. You can re-add the account later once the app is installed.
- Clear the Play Store’s cache and data. Go to Settings > Apps > See all apps > Google Play Store > Storage & cache and tap Clear cache, then Clear storage. This wipes the stale session that still references the removed account. Reopen the Play Store, sign back in if asked, and try the download again.
- Remove and re-add your main Google account. Go to Settings > Passwords & accounts, tap your Google account, and tap Remove account, then restart the phone. After the restart, go back to Settings > Passwords & accounts > Add account > Google and sign in again. A fresh sign-in rebuilds the account link the store needs to approve downloads.
- Clear any proxy in your mobile data settings. Go to Settings > Network & internet > SIMs > Access point names, tap your active APN, and check the Proxy field. If it has any value, delete it and tap Save. A leftover proxy entry can route store traffic through a dead server and trigger error 403 on some carrier networks.
- Retry the download on stable Wi-Fi. Connect to reliable Wi-Fi and make sure the purchase goes through your one remaining Google account — tap the profile icon in the Play Store to confirm the email. If the app was paid, install it from your library (Play Store > profile icon > Manage apps & device > Manage > Not installed) so the store knows you own it.
Did this fix it? Quick checklist
- The app downloads to the end without the error 403 pop-up
- The Play Store shows your correct account under the profile icon
- Other apps install and update without interruption
- A removed secondary account can be re-added safely after the install
If error 403 still appears after the account cleanup, the purchase itself may be the problem — check that the app’s payment went through under the account you’re signed into (Play Store > profile icon > Payments & subscriptions > Budget & history). A declined payment method produces the same 403 response, and updating the card or payment profile fixes it where account shuffling cannot.
Frequently asked questions
What does Play Store error 403 mean?
It means the Google Play Store declined the download request. The most common trigger is a mismatch between the Google account signed into the Play Store and the account the phone or the app purchase is tied to — the store refuses a purchase it cannot attribute to a single account.
Why do I get error 403 with only one Google account on my phone?
A second account may have been removed incompletely, leaving stale account data in the Play Store’s cache. Clearing the store’s cache and data, or removing and re-adding your account, clears that leftover state. A proxy entry in your mobile data APN settings can also cause error 403.
Will removing my Google account delete my data?
Photos, contacts, and emails synced to your Google account are safe and come back when you sign in again. Downloads tied to the removed account — like offline maps or unsynced app data — may be lost, so sync or back up anything important first.
I paid for the app — will I be charged again after these fixes?
No. Once you sign in with the same Google account that bought the app, open the Play Store’s library under your profile icon and install it from your list of owned apps. Google will not charge you again for an app you already own.