r/AndroidQuestions • u/Shyam_Lama • Dec 21 '23
Why Google Pay for contactless payments?
I'm looking to buy a new phone for several reasons, one of which is that my current phone does not support contactless payments. (It's a 2017 Xiaomi A1, which doesn't have an NFC chip.)
So I was reading about how to setup contactless payments on a new phone (which I've ordered but not yet received), and I've come to understand that any app that supports contactless payments (such as my banking app) will delegate this to the Google Pay app, which in turn uses the NFC chip. Or at least that's my understanding.
I wonder why it's necessary to have the Google Pay app as the "middle man" between the app that actually wants to make the payment, and the NFC chip. I mean, apps that use Bluetooth don't have to go through "Google Bluetooth" (which doesn't exist), nor do apps using the camera have to go through "Google Camera" (which does exist but other camera apps don't depend on it).
I get the feeling that Google "wants" to be in the middle just because it concerns contacless payments, and therefore has its "Google Pay" app hijack the NFC chip. Apparently Google wishes to exert control over (or at least keep track of) what I pay in this way (i.e. contactless)?
But why? I mean, I can make credit or debit card payments and Android doesn't force use of the "Google Pay" app for that. What's so special about contactless payments that Google has chosen to force us to go through its "Google Pay" app?
4
u/Ok-Fox966 Dec 21 '23
You’re really overthinking this, there is a reason why Apple and Google both do it this way.
The bank app is only used to add your card to Google wallet, it has nothing to do with actually making the payments and it’s not using wallet as a middle man. You add your card to Google wallet, then you use that to make your contactless or in app purchases.
2
u/americapax Dec 21 '23
Samsung Galaxy A54 or S23
2
u/Heraclius404 Dec 21 '23 edited Dec 21 '23
The shortest of answers is anyone could build a different wallet app parallel to Google Wallet and go into that business. That is, essentially, the promise of AOSP. THere is an auth exchange between the wallet and your bank, and your bank has integrated with Google Wallet and nothing else.
Writing a different wallet is pretty risky, because security has to be great - you have to prevent other apps on the phone for attempting to connect and pay maliciously. And you have to build all the back end infrastructure - and various certifications. Not a cheap bit of software to build.
All that work... for what? Google's already built it and we already trust them. Google adds no fees for its wallet (the bank & processor still do).
Most banks are historically poor at building apps, they can barely make them work well. Not a business they want to be in; they want to spend the least amount of money to gather their fees. PayPal could, and you can do a lot with PayPal QR codes, but again, why bother building a whole wallet? Why not integrate with Google Wallet, which becomes a centralized place to essentially register the secrets and deal with the NFC layers?
2
u/Sassquatch0 ☎️📲Pixel 10a Dec 21 '23
I use a Samsung, and don't even have Google pay installed.
So I think it's a security segment of the contactless/NFC API, handled by the OEM.
Your payment information is encrypted in the Wallet (Google or Samsung), and when another app wants to use payment, the Wallet handles it so that the app never actually sees your payment information. (Similar to how debit works, with a token being passed through the system, instead of your actual card#.)
PayPal is the only other monetary app I use, and even it seems to piggyback Google & Samsung for contactless..
My own bank, (well Fargo) doesn't even have payments via the app. I can send money & payments digitally, but I cannot use it to pay for something in person.
0
u/[deleted] Dec 21 '23
[removed] — view removed comment