Home › Guides › Apps without Google

Banking apps on a de-Googled phone

Checked against the makers' own pages · Last reviewed October 15, 2026

Why some apps refuse to run

Google's Play Integrity API lets an app ask Google whether it is "running on a genuine and certified Android device," installed from Google Play and unmodified. Google pitches it to fight fraud, cheating and tampered apps. The app's server then decides what to do with the answer: keep working, limit features or block you.

A "certified" device is one whose maker pre-installs Google's apps and that Google tests to run them and the Play Store. GrapheneOS says it "isn't certified by Google," and that apps blocking it do so "because we do not license Google Mobile Services (GMS)" (Google's bundle of apps and services). /e/OS says the higher Play Integrity verdicts "require certified hardware."

Many apps also have their own checks. GrapheneOS notes that banking apps often use "crude anti-tampering mechanisms," and that most "have extensive dependencies on Play services." [1][2][3][4][5][7]

The Play Integrity verdict levels

Google's documentation describes three device labels an app can receive:

If none apply (for example, a rooted phone or an emulator), the verdict is blank. Which level an app demands is up to its developer. Google advises developers to use the API "alongside other signals" rather than as their only anti-abuse tool.

GrapheneOS says it passes basic integrity but isn't certified by Google. /e/OS says: "On /e/OS, microG can pass the Basic verdict; the Device and Strong verdicts require certified hardware and are out of reach." An app that requires Device or Strong integrity will not accept such a phone. [1][2][3][5]

What GrapheneOS says

GrapheneOS's usage guide says it passes basic integrity "but isn't certified by Google," and that it doesn't try to fake the checks because spoofing "would be very fragile and would repeatedly break."

Its attestation compatibility guide asks app developers to use Android's standard hardware attestation API (a check signed by the phone's security chip) and to allow GrapheneOS's official signing keys. GrapheneOS argues this is "a much stronger form of attestation than the Play Integrity API" and doesn't depend on Google services.

The same page keeps a list of apps that block GrapheneOS through Play Integrity. As of Oct. 15, 2026 it names apps such as Authy, TextNow, Strava and Volkswagen, plus government apps from Australia, Brazil, Italy and Singapore, and asks users to contact app makers and leave reviews pointing to the guide. GrapheneOS also links a third-party banking compatibility list kept by PrivSec.dev, while noting it "does not make any guarantees regarding the list's validity." [3][4]

Google Wallet and tap-to-pay

Google's Wallet help page says Google Wallet "may not work in stores" with phones that run developer versions of Android, are rooted, "run a custom ROM, or have modified factory software," haven't been approved by Google, or have an unlocked bootloader. It adds: "If you installed a modified operating system on your phone, before you can make contactless payments, you must reinstall your phone's original operating system." [6]

What you can try

- Install Google Play's pieces, if your system offers them. On GrapheneOS, the guide says that for many banking apps "it's enough to set up the GrapheneOS sandboxed Google Play feature in the same profile." - Sign in system-wide on /e/OS. /e/OS says you reach the Basic verdict by choosing "Sign in with Google system-wide" in App Lounge, which adds your Google account to microG. - Check GrapheneOS's exploit-protection setting. If you turned off "Native code debugging" in Settings > Security & privacy > Exploit protection, GrapheneOS suggests turning it back on, since it can break some banking apps' self-checks. - Turn Developer options off after use. Google's developer-verification FAQ notes that some banking apps won't run with Developer Mode on, and says you don't need to keep it on after setting up the advanced flow for sideloading. - Ask the app maker. GrapheneOS encourages users to send developers its attestation guide.

Before buying a phone for a specific banking app, check with the bank whether it supports custom operating systems. [3][4][5][8]

Questions people ask