Stephan-P Greetings,
Most banking app work fine. See https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/ for a list of crowd sourced banking app reports.
Stephan-P I get the impression that more Banking apps are moving away from proprietory app towards deploying and referring to Google Pay services
Most of them already had extensive dependencies on Play services. In the past, these banking apps were increasingly using Google's SafetyNet attestation service to check the integrity and certification status of the operating system. SafetyNet is replaced with the new Play Integrity API.
See https://github.com/PrivSec-dev/banking-apps-compat-report/issues/342 for explanation.
There are possible workaround solutions in this guide (when using our Sandboxed Google Play): https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos
However, more are slowly becoming not compatible, see https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos#:~:text=issuecomment%2D1766887298%29-,Not%20compatible,-Due%20to%20the
Stephan-P If I'd want to persuade my bank to support privacy and security enhanced Android variants, I could point their app development departments to:
Perhaps this may help you as an additional reference point for information on how one bank is handling this issue:
https://discuss.grapheneos.org/d/12470-grapheneos-recognised-by-uk-starling-bank/38
https://github.com/PrivSec-dev/banking-apps-compat-report/issues/39
could this also be beneficial to, say /e/os or LineageOS?
No. These projects don't meet the security standards and only a few devices have verified boot on e/os iirc, while lineageos doesn't even lock the bootloader.