zlacker

[parent] [thread] 3 comments
1. sfRatt+(OP)[view] [source] 2025-06-05 20:59:43
> GrapheneOS you cannot use Google Pay (one major feature of a phone)

News to me. Edit: I misread parent comment.

replies(1): >>6581+B1
2. 6581+B1[view] [source] 2025-06-05 21:09:43
>>sfRatt+(OP)
Google Play != Google Pay.
replies(1): >>sfRatt+23
◧◩
3. sfRatt+23[view] [source] [discussion] 2025-06-05 21:19:41
>>6581+B1
Apologies. I misread. Yeah, it sucks that Google Pay doesn't work on GrapheneOS.

Though Google Pay is also probably the least private of the major tech-company payment platforms (the others being Apple Pay, Samsung Pay, and Garmin Pay). It is, I think, the only one that actually requires an open network connection on the phone to work. The others all generate one-time codes that get sent through the payment machine's network for verification by Apple/Samsung/Garmin on the backend (i.e. you can tap an Apple Watch to pay with all its radios off, but you can't do that with Google Pay).

From what I gather, Garmin Pay can work with GrapheneOS if you have one of their smartwatches. And Privacy.com works, but not with tap-to-pay.

replies(1): >>9-133-+Y8
◧◩◪
4. 9-133-+Y8[view] [source] [discussion] 2025-06-05 22:18:13
>>sfRatt+23
> Garmin Pay can work with GrapheneOS

As an aside - I think the Paypal app in Germany offers HCE tap-to-pay, and In the UK/Europe 'Curve' is a Google pay replacement that runs fine on GrapheneOS (and they have first-party support for huawei phones that don't even ship Google play services anymore)

[go to top]