Why your banking app will not open
A banking app that opens on one phone and refuses on another is running a device integrity check. It asks Google's services to attest that the device is a genuine Android device with an unmodified system, and it refuses to run if the answer is anything other than a clean pass. That mechanism is why a phone you consider perfectly secure can be rejected.
What actually gets checked
| Check | What trips it |
|---|---|
| System integrity | Root, custom recovery, unlocked bootloader |
| Device certification | Custom systems, some inexpensive imports |
| Play Services present and current | De-Googled phones, very old devices |
| Developer options and USB debugging | Some apps refuse while these are on |
| Overlay permissions | Apps that can draw over the screen |
| Accessibility services | Apps with accessibility access installed |
Реклама
What you can actually do
- Turn off USB debugging Several banking apps refuse while it is enabled, and this is the most common easy fix.
- Check for overlay and accessibility apps Screen filters, automation tools and some launchers hold these permissions. Disable them and retry.
- Update Play Services An outdated version fails attestation on some checks.
- Uninstall root management tools Hiding root from an app is a losing arms race and increasingly detected.
- Use the website instead Bank websites are usually not subject to the same check, and this is the practical answer for a phone that will not pass.
The trade you are making
- Banking and payment apps work
- Contactless payment works
- Some streaming apps require it too
- Company device policies are satisfied
- Full control over the system
- Remove preinstalled software properly
- Run a system that receives updates after the maker stopped
- No dependence on Google's services
There is no configuration that gives both. The realistic arrangements are a standard phone, or a modified phone plus a second device or a browser for the things that refuse to run on it.
Is the check making you safer?
Partly. Attestation genuinely blocks a class of attack where malware modifies the system to intercept a banking session, and the banks are not being unreasonable in wanting it.
It is also a blunt instrument. A carefully maintained custom system receiving security patches after the manufacturer abandoned the phone is arguably safer than the stock system it replaced, and it fails the check anyway. The check measures conformity, not security, and those overlap without being the same.
Turn off USB debugging, check overlay and accessibility apps, and accept that a modified system will not pass. The website is the fallback.
Frequently asked questions
Will installing an APK stop my banking app working?
No. Installing apps from outside the Play Store does not affect integrity attestation. Modifying the system does.
Can I hide root from a banking app?
Sometimes, briefly. Detection improves continuously and the effort exceeds the benefit for most people.
Why does it work on my old phone and not the new one?
Either the new phone is uncertified, or something on it holds overlay or accessibility permission, or debugging is enabled.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
