You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.96K Posts
- 74.6K Comments
- Modlog
GrapheneOS. Everything works, except Google Pay NFC payments. Luckily, my bank has Google Pay alternative and can be used for NFC payments, so I am good.
I am happy so far. Stable as hell.
Hmm, the lack of no Google pay has been a concern/consideration as I think toward moving to an alternate ROM like graphene. I could give up pretty much anything on my pixel but I love and use the hell out of contactless payments.
Any idea why nfc payments wouldn’t work with Google pay but would with a bank app? Is a 3rd party privacy focused wallet technically feasible?
I don’t know why people would even attempt that, let alone see that as an issue, pretty weird for a privacy advocate to want to use Google pay. Google Pay clearly knows it’s on a modified device, hence it not working.
That said the NFC radio isn’t restricted, so other banking apps just see that you’re not rooted, and verified boot is good, so they work.
It’s one of the most secure ways to pay at retail. Payment card data is only shared with one party, payment methods are tokenized so retailers cannot swipe your payment information and use it again. I’ve had a couple of cards stolen by retailers like a coffee shop, that I had to close. It was a hassle. Also for online payments I much prefer GPay or PayPal, everything is clear, unauthorized payments are obvious and easy to fix.
Android supports multiple payment providers. Some banks implement their own payment provider (e.g. Sparkasse in Germany), most just rely on Google Pay (now Google Wallet). Google Wallet has strict requirements for the Play Integrity API. Because of the modifications to Android that GrapheneOS is implementing, it is not eligible to receive the required integrity attestation and thus, Google Wallet is refusing to work. Google could at any point reconsider and certify/whitlelist GrapheneOS, which would allow Google Wallet to work using GrapheneOS. Likelihood close to 0.
Any banking app implementing their own payment provider is completely independent of this decision unless it also relies on Play Integrity API attestation (or a similar mechanism).
out of curiosity, are you aware what changes exactly make the Play Integrity API eligibility requirements not able to be met? with Google play installed, the compatibility layer should be able to facilitate the necessary communication, I would think.
or are they just arbitrarily saying anything that’s not stock isn’t eligible?