Banking apps and Google Wallet that detect root
When a banking or payment app refuses to run on a rooted phone, it is using one or both of two kinds of check: its own search for signs of root, and Google's Play Integrity verdict. You can often get past the first. The second, on Android 13 and newer, is designed so that an unlocked phone can't honestly pass it.
Last updated 9 sourcesHow we check pages
The short answer
Whether you can make a banking app work depends on which check it uses. Apps that only look for signs of root on the phone can often be satisfied. Apps that require Play Integrity's DEVICE or STRONG verdict on Android 13 or newer cannot, while the bootloader is unlocked.
- App's own root checksOften fixableDenyList, a hiding module, no visible Magisk app
- Play Integrity BASICUsually passesGoogle says rooted devices are eligible
- DEVICE / STRONG, Android 13+FailsNeeds hardware proof of a locked bootloader
- Google Wallet tap to payNot supportedGoogle lists rooted and unlocked phones
How apps detect a rooted phone
Think of it as layers. The higher ones run inside the app and the phone's software, where Magisk and modules can change what the app sees. The lower ones come from the phone's secure hardware, which reports the bootloader state and signs that report with a key Magisk can't touch.
Where a banking app can see root
Top: checks inside the app. Bottom: what the phone's hardware reports.
-
The app's own checksLooks for the Magisk app,
su, changed mounts, hooksDenyListHiding modules -
Play Integrity: app and environmentOpt-in: Play licence, Play Protect, apps that can capture or control the screenInstall from Play
-
Play Integrity: device verdictBASIC, DEVICE, STRONG labels, decided on Google's serversBASIC: usuallyDEVICE on 13+: no
-
Hardware key attestationSecure hardware signs the boot stateReports unlocked
-
BootloaderUnlocked to install Magisk
- The app's own checks are written by the bank or its security vendor. They look for the Magisk app's package, an
subinary, unusual mounts, or hooking frameworks such as LSPosed (Vector). This is where the DenyList and hiding modules help. - Play Integrity is Google's service. The app asks Google for a verdict and gets labels back. By default an app receives only
MEETS_DEVICE_INTEGRITYor nothing; BASIC and STRONG are labels it opts in to. On Android 13 and newer, Google says DEVICE integrity requires "hardware-backed proof that the device bootloader is locked". The verdicts are explained on Play Integrity and root. - App and environment signals are optional extras an app can ask Play Integrity for: whether you installed the app from Google Play, the Play Protect status, and whether apps that can capture the screen, show overlays or control the device are running.
What helps with the app's own checks
Try these in order, and re-test the bank app after each one.
- Get the Magisk app out of sight. Since v31.1, the current stable release, the release notes recommend simply uninstalling the Magisk app once your root grants and modules are set up; root and modules keep working without it. On v30.7 and older, Hide the Magisk app in the app's settings reinstalls it under a random package name instead.
- Turn on Zygisk and add the app to the DenyList. In Magisk's settings, enable Zygisk, open Configure DenyList, and tick the bank app, including all of its processes. With Enforce DenyList on, Magisk reverts its mounts in those processes, and its source shows that no Zygisk modules are loaded into them either. More in Zygisk and the DenyList.
- If that isn't enough, try a hiding module. Magisk's FAQ says Magisk no longer hides root and leaves that to modules. Shamiko, Zygisk Assistant and NoHello are the common ones; they keep apps on the DenyList but need Enforce DenyList off. All three have had no new release for over a year (see the module catalog), so results vary.
- Remove what you don't need. Modules that hook apps or change the system, Xposed frameworks in particular, are among the things detection looks for. Disable them and test again.
- Clear the bank app's data after each change. Some apps remember a failed check.
What won't work
- If the app requires Play Integrity DEVICE or STRONG on Android 13 or newer, hiding root does not help. The verdict depends on the bootloader state reported by hardware, not on what is installed.
- Google Wallet tap to pay is not supported on rooted or unlocked phones, according to Google's own help page. PlayIntegrityFork describes partial workarounds, but there is no guaranteed way to make payments work.
- Google and banks change their checks without notice. A setup that works today may stop working after a server-side change or an app update.
If you rely on a banking or payment app every day, use it on a phone that is not rooted and has a locked bootloader. If that has to be this phone, see how to uninstall Magisk and read the relocking warnings first.
Questions people ask
I added my bank app to the DenyList and it still says rooted. Why?
Either the app found something the DenyList doesn't cover (the Magisk app itself, or traces a hiding module would handle), or it relies on Play Integrity, which the DenyList doesn't affect at all. Check which: if a Play Integrity checker shows no DEVICE label on Android 13 or newer, no app-side hiding will help. Magisk's FAQ says plainly that Magisk no longer handles root hiding and leaves it to modules.
Does Google Wallet tap to pay work on a phone with Magisk?
Google says no. Its Wallet help page lists phones that are rooted, run a custom ROM or have an unlocked bootloader, and says "Due to security risks, Google Wallet doesn't run on these phones." The PlayIntegrityFork README describes what its module can do for Wallet, but that is a workaround Google can break at any time, not a supported setup.
Where is "Hide the Magisk app"?
Not in the current version. It existed in the Magisk app's settings up to v30.7; v31.1 removed it, and its release notes say the most effective way to hide the Magisk app is to uninstall it after you have set up root grants and modules. Root and modules keep working without the app.
It worked yesterday and fails today. What changed?
Usually not your phone. Play Integrity verdicts are decided on Google's servers, and banks update their own checks. On October 16, 2026, for example, the PixelOS project reported that Google changed its server-side checks so devices without Remote Key Provisioning pass BASIC only, whatever keybox or fingerprint is used. Clearing the bank app's data after a change rules out a cached failure.
Will uninstalling Magisk make the bank app work?
It removes everything the app's own checks look for. It does not fix Play Integrity on Android 13 or newer while the bootloader stays unlocked, because DEVICE integrity requires hardware proof of a locked bootloader. Relocking is a separate step, and relocking with modified software can make a phone unbootable. Read relocking the bootloader first.
Should I add Google Play services to the DenyList?
Not if you use PlayIntegrityFork. Its README says to make sure Google Play services (com.google.android.gms) is not on the DenyList when Enforce DenyList is on, because that stops the module from working.
What about guides that promise STRONG integrity?
They present someone else's hardware attestation key, usually a leaked OEM "keybox", through modules such as Tricky Store. Google revokes leaked keys, phones that launched with Android 16 use only Remote Key Provisioning (which Google says those leaks don't affect), and you would be relying on stolen private keys. This site doesn't explain how to do it. See Play Integrity and root.
No match. Try another word from the error message.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- Magisk FAQ: Why is X app detecting root? (topjohnwu)
- Magisk v31.1 release notes: app hiding removed (topjohnwu)
- Magisk source: DenyList processes get no Zygisk modules, zygisk/module.cpp (topjohnwu)
- Play Integrity API: integrity verdicts (Android Developers)
- Play Integrity API: hardware-backed verdict improvements (Android Developers)
- Key and ID attestation: revocation and Remote Key Provisioning (Android Developers)
- Fix problems with tap to pay transactions (Google Wallet Help)
- PlayIntegrityFork README (osm0sis)
- PixelOS user guide: Play Integrity notice, October 16, 2026
Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.
Report a problem with this page