This list includes banking apps that have been tested, submitted, reviewed, and verified as compatible.
LIST | SUBMIT | UPDATE | POSSIBLE WORKAROUND SOLUTIONS
Welcome to the crowd-sourced dataset for GrapheneOS users on currently supported devices.
New visitors are encouraged to read the official usage guide on banking apps for comprehensive details about how these apps function on GrapheneOS.
Please read GrapheneOS’s important announcement, officially released on Dec 1, 2023:
X | Mastodon | Bluesky
Also available as a pinned issue, detailing the latest developments about SafetyNet’s replacement by Play Integrity API, which could impact some banking apps’ compatibility with GrapheneOS after the app updates.
This section covers how to submit or update a banking app report.
There are several methods for GrapheneOS users to contribute their banking app report:
| Method | Description | Action |
|---|---|---|
| GitHub | Fill out the form on the issue tracker using your GitHub account | SUBMIT REPORT |
| Non-GitHub | View gist → Raw → Save template markdown file to fill out. | Gist |
| Curl | Terminal → curl -O → paste copied url (gist form .md template) ⟶ |
Copy link address |
Alternatively, curl and pipe the output directly into your preferred text editor for editing, for example:
curl https://gist.githubusercontent.com/akc3n/e845078ddbbb28ada0dd055c51ec45af/raw/c2bb563db726b80491a59c68d7f15c0897f563a0/banking-app-report-issue-form.md\?T | nvim -
Please avoid opening a new issue to update the status of a banking app report.
Instead, use CTRL + F on this page or search on the issue tracker for the app and open its Report. Then, simply add your update as a comment to the existing report.
For non-GitHub users, if you have tried all the combinations from these possible workaround solutions and still cannot resolve your specific banking app compatibility issue, feel free to contact me for further assistance.
GrapheneOS has a detailed guide for app developers on how to support GrapheneOS with the hardware attestation API. Direct use of the hardware attestation API provides much higher assurance than using SafetyNet so these apps have nothing to lose by using a more meaningful API and supporting a more secure OS.
GrapheneOS users are strongly encouraged to share this documentation with app developers who enforce only being able to use the stock OS. Send an email to the developers and leave a review of the app with a link to this information. Share it with other users and create pressure to support GrapheneOS rather than locking users into the stock OS without a valid security reason. GrapheneOS not only upholds the app security model but substantially reinforces it, so it cannot be justified with reasoning based on security, anti-fraud, etc.
Refer to https://github.com/PrivSec-dev/banking-apps-compat-report/issues/342 or the official GrapheneOS announcement on Mastodon/X/Bluesky for more information.
]]>