Australian Banking Apps on GrapheneOS
The question we get asked most before every sale. Here's the honest answer.
Banking app compatibility is the single most common concern before a SOVEREIGN purchase. The answer, for the vast majority of Australian banks, is straightforward: yes, they work — through Sandboxed Google Play.
Sandboxed Google Play is GrapheneOS's approach to running Google's services inside a fully isolated environment. It has no special system privileges — it runs like any other app, subject to the same per-app permission controls. Banking apps can't detect that they're on a custom OS, because from their perspective they aren't: Verified Boot is re-locked, Play Integrity checks pass, and the device looks like a standard Pixel. We configure Sandboxed Google Play on every Advanced and Elite package.
Most apps work out of the box. A small number need a single settings change. A very small number have genuine compatibility issues. The table below covers every major Australian bank and government app we've tested.
How banking apps run on GrapheneOS
GrapheneOS ships without Sandboxed Google Play installed by default — this is a deliberate privacy choice, not a limitation. It's available to install at any time from the built-in Apps repository (GrapheneOS's own first-party app catalogue), and takes about two minutes. Your banking apps are then installed inside this sandboxed environment through the Play Store as normal.
The key difference from stock Android is that Google Play Services has no elevated system privileges. It cannot read your contacts, access your location, or reach your files without an explicit per-app permission grant — the same model every other app on the device is subject to. This means you retain granular control over exactly what Google can and can't see.
Your banking app cannot detect that it's on GrapheneOS. The bootloader is re-locked after installation, Verified Boot is active, and Play Integrity checks pass identically to a factory Pixel. There is no root access — GrapheneOS does not root the device, and banking apps that check for root will find nothing.
For maximum isolation, install Sandboxed Google Play inside a separate user profile (Settings > System > Multiple users > Add user) or Android's Private Space. Your banking apps then run in complete separation from your main profile — effectively a jail within the phone. Your day-to-day apps never interact with Google's services unless you deliberately switch profiles.
Australian bank app compatibility
The following table reflects testing on GrapheneOS with Sandboxed Google Play installed. Status may change with app updates — if you find something outdated, contact us and we'll update it.
| Bank | App | Status | Notes |
|---|---|---|---|
| Commonwealth Bank | CommBank | Works | Requires Sandboxed Google Play. Works reliably including NetBank and cardless cash. |
| NAB | NAB Mobile Banking | Works | Sandboxed Google Play required. Full functionality including PayID. |
| Westpac | Westpac Mobile Banking | Works | Works with Sandboxed Play. If login fails, enable exploit protection compatibility mode for the app. |
| ANZ | ANZ Australia | Works | Reliable. Full internet banking and card controls work. |
| ANZ | ANZ Plus | Works | Newer app, works cleanly with Sandboxed Play. |
| ING | ING Australia | Works | One of the most reliable banking apps on GrapheneOS. |
| Macquarie Bank | Macquarie Mobile Banking | Works | Works with Sandboxed Play. |
| Up Bank | Up | Works | Fintech app, generally very compatible. |
| Bendigo Bank | Bendigo Bank | Works | Sandboxed Play required. |
| Bank of Queensland | BOQ Mobile | Works | Works reliably. |
| Suncorp Bank | Suncorp Bank | Works | Functions fully with Sandboxed Play. |
| St George | St George Mobile Banking | Works | Westpac subsidiary — same compatibility. |
| BankWest | BankWest | Works | CommBank subsidiary — same compatibility. |
| HSBC Australia | HSBC Australia | Works | Works with Sandboxed Play. |
| ME Bank | ME Bank | Works | Generally compatible. |
| Ubank | Ubank | Works | NAB subsidiary — reliable. |
| Great Southern Bank | Great Southern Bank | Works | Works with Sandboxed Play. |
| BPAY | Via banking apps | Works | BPAY functions through all compatible banking apps above. |
| PayID | Via banking apps | Works | PayID works through all compatible banking apps above. |
| Google Pay | Google Pay | Works | Install via Sandboxed Google Play. NFC tap-to-pay works. |
| Afterpay | Afterpay | Works | Works with Sandboxed Play. |
| Zip | Zip | Works | Works with Sandboxed Play. |
| Services Australia | myGov | Works | Government identity app — works with Sandboxed Play. |
| Centrelink | Express Plus Centrelink | Works | Works with Sandboxed Play. |
| ATO | ATO app | Works | Tax Office app works with Sandboxed Play. |
| Medicare | Express Plus Medicare | Works | Works with Sandboxed Play. |
If your banking app won't open
Work through these steps in order. Most issues resolve at step one or two.
- 01
Install Sandboxed Google Play
This resolves the majority of banking app failures. Open the Apps repository (the built-in GrapheneOS app store), locate Google Play Services, and install the full Sandboxed Google Play package. Restart the app after installation. Most banking apps that appeared broken will work immediately.
- 02
Enable exploit protection compatibility mode
GrapheneOS ships with hardened memory protection enabled by default. Most apps are unaffected. Occasionally a banking app will crash on launch due to the hardened memory allocator (hardened_malloc). When this happens, GrapheneOS shows a crash notification — tap it to enable exploit protection compatibility mode for that specific app only. This relaxes memory protection for just that one app while leaving everything else fully hardened. Manual path: Settings > Apps > [App name] > Exploit protection compatibility mode: On.
- 03
Check Play Integrity status
Some banking apps run a Play Integrity check before allowing access. Sandboxed Google Play passes this by default on GrapheneOS with a re-locked bootloader. If you're still having issues, confirm your Verified Boot status is active: Settings > About phone > Device status. A locked, verified device should pass all standard integrity checks automatically.
- 04
Move banking apps to a separate user profile
If you want maximum isolation between your banking apps and your private profile — or if you're experiencing persistent compatibility issues — install Sandboxed Google Play inside a second user profile: Settings > System > Multiple users > Add user. Banking apps then run in complete isolation from your day-to-day profile. Some customers prefer this arrangement regardless of compatibility, purely for privacy.
- 05
Contact us before purchasing
If you've worked through the above and your specific banking app still has issues, contact us before placing an order. We test every banking app our customers need as part of our right-sizing consult — if an app won't work on GrapheneOS, we'll tell you honestly before you buy.
What about Apple Pay and tap-to-pay?
Apple Pay is exclusive to Apple devices and isn't available on any Android phone, including those running GrapheneOS. The functional equivalent on Android is Google Pay, which installs via Sandboxed Google Play and works fully — including NFC contactless payments in shops, transit gates, and parking meters.
All major Australian banks support Google Pay. If you currently use Apple Pay on public transit — Opal in NSW, Myki in Victoria, Go Card in Queensland — Google Pay is accepted at the same tap-on readers. The one caveat is that some state transit cards require a dedicated app to top up, rather than Google Pay directly, and those apps are all compatible with Sandboxed Play.
A note on banking app privacy
Banking apps are among the most data-hungry applications on the market. CommBank, NAB, Westpac, and the major banks collect significant behavioural, device, and location data — and by using their app, you've agreed to this in their terms of service. Sandboxed Google Play limits what Google's services can access, but the banking apps themselves still collect what they always have. GrapheneOS does not change that.
The practical recommendation: install your banking apps in a separate user profile or Private Space, grant only the minimum permissions each app needs (deny location access unless a specific feature requires it), and review each app's permission grants individually. GrapheneOS's per-app network and sensor permission controls give you oversight that isn't available on stock Android — use them. Your bank doesn't need your location every time you check your balance.
Frequently asked questions
- Do I need Google Play to use banking apps on GrapheneOS?
- Yes, for most banking apps. GrapheneOS includes Sandboxed Google Play — a version of Google's services that runs as a normal sandboxed app with no special system privileges. Install it from the built-in Apps repository. Your banking apps then work as they would on stock Android, but Google can't access your data beyond what the sandboxed app is explicitly permitted.
- Will my bank app know I'm using a custom operating system?
- No. GrapheneOS re-locks the bootloader after installation, which restores Verified Boot. Your device passes Play Integrity checks the same as a stock Pixel. Your banking app sees a standard, verified Android device.
- Can I use banking apps without installing Google Play at all?
- Some banking apps are available via Aurora Store, which provides anonymous access to Play Store apps without signing in. However, apps that require Google Play Services to function — which most banking apps do — will need Sandboxed Google Play installed to work correctly.
- What if my banking app worked before and now it doesn't?
- App updates occasionally change compatibility. Enable exploit protection compatibility mode for the specific app (Settings > Apps > [App name]) and check for a GrapheneOS update. If you're a SOVEREIGN customer, contact us — this is covered under our support service.
- Is it safe to do banking on GrapheneOS?
- GrapheneOS is significantly more resistant to the threats that matter for mobile banking — malware, spyware, malicious apps — than stock Android or iOS. Your banking session is at least as safe as on a stock device, and in most threat models, substantially safer.
Ready to order?
All Advanced and Elite packages include Sandboxed Google Play configured and ready — your banking apps installed, tested, and working before the phone leaves our hands.
Compatibility may change with app updates. This guide is updated regularly. Last verified: July 2026. If you find outdated information, contact us and we'll correct it.