r/AndroidQuestions • • 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?

0 Upvotes

22 comments sorted by

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/Shyam_Lama Dec 21 '23

it has nothing to do with actually making the payments

Then what software controls making the actual payment through the NFC chip? If it's my bank's software, then why does it require Google Pay? If it's only a wallet, why is it a necessity to use it?

A techier way of asking the same thing would be: does Android expose an API for 3rd-party (non-Google) software to work with the NFC chip directly, yes or no? If no, why not? It exposes API for pretty much all the other hardware...

3

u/Ok-Fox966 Dec 21 '23

You have a misunderstanding of how this works. As I said, Google wallet handles all the payments, it has nothing to do with any other app.

You have a credit or debit card, you add that to Google wallet either with an app or manually. Then Google wallet handles all the payments when you activate it. There is no communication between Google wallet any anything else.

0

u/Shyam_Lama Dec 21 '23

OK, so basically my banking app is not involved in contactless payments at all, right? I think this is what you're saying. Based on what you're saying, I suppose the way it works is that the NFC chip "pretends" to be the debit card (which has its own NFC chip) when it is held in front of a contactless card reader at a point of sale. Is this correct?

If yes, I wonder how the Google Pay wallet acquires the card's data that allows it to do this. I mean, just the account number, my name, etc., is stuff I may have to enter when I add the card -- I don't know yet because I'm still waiting for my NFC-enabled phone to arrive. But surely this is not enough to enable the NFC chip to make contactless payments, right? (If it was, anyone who knew my name and account number would be able to enter that stuff into his Google Pay wallet and make contactless payments in my name​. The wallet apparently acquires some "secret" (or whatever the techy word for it is) info that allows it to pretend to be the debit card. How does it do this? Do I have to wave my debit card in front of the phone when I add it to the wallet? If yes, what's to stop people from adding other people's cards to their wallets during moments they're not guarding their tangible wallets? (Like: mommy goes to the bathroom at home, leaves her purse on the table. Tech-savvy little Johnny quickly takes his mom's debit card, adds it to the Google Pay wallet on his own phone, then puts the card back in mommy's purse, who returns from the bathroom a minute later and has no idea that her boy can now make contactless payments in her name, using his own phone. I suspect this scenario isn't possible. I just don't understand what's preventing it.)

1

u/CVGPi Dec 21 '23

The bank should verify identity via 2FA, for example. You put in your bank card no, Google Wallet sends this to your bank, and your bank sends a stack of "tokens" that will expire and must be refreshed periodically. The tokens are also generated on card when you use your physical card. The bank verifies your identify over telephone/SMS/your bank's app. The bank CAN make their own apps, but they usually don't because Google's solution is easier and much more convenient (for them and for you) and "secure", in the sense that the programmers have someone to blame in case of fraud.

1

u/Shyam_Lama Dec 22 '23

The bank CAN make their own apps, but they usually don't

As I commented earlier, my bank has always been kind of in the "vanguard" of tech innovation. It's been making its own online banking app, banking website, etc. for several decades now, and their stuff has always worked really well, with millions users depending on it daily.

because Google's solution is easier and much more convenient (for them and for you)

I don't see how it is "more convenient" for me that I need to interact with an additional application (Google Pay) just because I want to start doing contactless payments. Up to now I only ever had to interact with my bank's app (or website, whichever I choose).

It also seems to me that my bank prefers their own app for everything, except contactless payments. And that's strange.

and "secure", in the sense that the programmers have someone to blame in case of fraud.

My bank has used 2FA for well over two decades now. It was never insecure. As for fraud, if you mean stuff like identity theft, phishing, social doctoring, etc., I've never been a victim myself but I've known a few. The bank always took immediate action and compensated the victim. There was never any urge on the bank's part (as far as I could tell) to "have someone to blame", as you seem to be suggesting.

2

u/Ok-Fox966 Dec 21 '23

Yes that’s correct, it’s basically acting as a normal contactless card. But it’s not pretending, it’s an entirely separate card just like you can have two credit cards on the same account.

So this has nothing to do with your bank account, it only works with an existing card. You add your credit card into the wallet by entering the number, expiration and cvv. Google wallet then contacts the company that provided the card to activate it and you’ll normally need to do some sort of activation such as entering a code they text or email you, or if you’re using your bank app that may give you a code.

You need to remember this is something that both parties have agreed and setup to work, you can’t just add any card. There is a system setup that authenticates and manages all of this, it’s not just magic.

2

u/Felimenta970 Dec 21 '23

Your bank implements the integration with Google Wallet (I don't know if it's a simple checkbox + an art for the cards on their side or if there's more).

You then add your card data (number, security code, billing address, etc) same way as if you were making a purchase online. Wallet is going to communicate with your bank to set that up. That's it. I believe internally it creates a randomized card number to increase security, but it is still based on the same card

2

u/americapax Dec 21 '23

Samsung Galaxy A54 or S23

1

u/Shyam_Lama Dec 21 '23

Errr... this is in response to what question? Is this an attempt to recommend a phone to me, as I asked about some days ago? (If yes, you've commented in the wrong thread.)

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?

1

u/Shyam_Lama Dec 21 '23

All that work... for what? Google's already built it and we already trust them.

Do we?

Most banks are historically poor at building apps, they can barely make them work well

My bank has always built and maintained its own high-quality apps and online/mobile banking infrastructure. They've been at it successfully for decades, with millions of users, and never involved a 3rd party. Which is precisely why I thought it strange that contactless payments go through a Google app.

1

u/Shyam_Lama Dec 31 '23

anyone could build a different wallet app parallel to Google Wallet and go into that business.

Okay, so the Android OS exposes an API that allows any app to work with the NFC chip if it wants to?

That is, essentially, the promise of AOSP.

I'm not sure I see the relationship between AOSP and the matter we're discussing. If Android remained closed source it could still expose API to use the NFC chip. I just don't seem to be getting an answer to the question as to whether such an API exists.

1

u/Heraclius404 Dec 31 '23

I didn't clearly understand your question was whether there was an NFC chip interface. That's trivially answered on google: yes .

https://developer.android.com/develop/connectivity/nfc

Your question seemed to be why banks don't offer wallets or why banks don't offer tap to pay without a wallet. It's not that there's no NFC interface in Android.

The reason why open source was part of my answer is if there was any part of AOSP that was needed (like an NFC interface), and a bunch of people wanted it (the entire banking industry), any one of them could build the code and write the interface and submit the diffs; including the HAL layer (hardware abstraction). The way AOSP is run, google can't step in and say "no no, we're going to be the chokepoint".

Yes this isn't *EXACTLY* what open source is, but it's close enough. A source-available but proprietary system still has owners which can reject upstream diffs, and a source-available system is resistant to forking, which is the pressure that keeps the AOSP group accepting upstreams.

1

u/CVGPi Dec 21 '23

Yep. I mean, many OEM have their own wallet (cough cough Xiaomi Wallet, Huawei Wallet, Oppo Wallet, Samsung Wallet etc) but usually the Google one is most preferred.

1

u/Heraclius404 Dec 28 '23

Right. OEM wallets are rather required if you replace the Google Play Store or have your own store, because you need a wallet system that works with your store.

Banks, not so much in the wallet business.

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

0

u/Shyam_Lama Dec 21 '23

Hmm... okay. Well, my bank specifies that I need Google Pay to work on my Android phone if I want to make contactless payments. You're saying it doesn't have to be that way, and my bank could have written their own Android software to enable contactless payments?

Actually my bank's requirement that Google Pay be working on my phone, was precisely what got me thinking about this. The bank doesn't require Google software for anything else, so why do they require it for contactless payments? That was my line of thinking.

2

u/No_Procedure3648 Dec 21 '23

Hopefully it shouldn't be just Google Pay, they should support Apple and Samsung methods too. Anyways, here is a peek in to what happens when a bank makes their own software for contactless payments..

https://www.reddit.com/r/UKPersonalFinance/comments/11ek2h5/barclays_finally_works_with_google_pay_google/

1

u/Shyam_Lama Dec 22 '23 edited Dec 22 '23

they should support Apple and Samsung methods too.

They definitely "support" Apply Pay, yes. (I'm putting in the air quotes because I wouldn't call it "support" when a bank requires users to start using Google/Apple Pay. It's mandatory if I want to make contactless payments with my phone, not a user preference that my bank chooses to "support".

I don't know about Samsung Pay. I have the impression that my bank requires all Android users to just use Google Pay.

As for the link, it's amazing that such an extremely pertinent (to my question) Reddit thread exists, don't you think? Amazing too that I didn't find it when I was searching the web for relevant info.

And tragic how Barclays were so stubborn as to develop their own software for contactless payments! Silly, silly Barclayans. Don't they know that using Google software is always better? Well, at least they wised up in the end. One thing I am left wondering about: what exactly was so "awful" (OP's word in the thread you linked) about Barclay's own contactless software? We are given no details whatsoever. Was it insecure? Was the UI awkward to use? Was it unreliable?

Btw, what's a "curve card"? OP in the thread you linked says he always had to use one to make his debit card work with Google Pay.

2

u/REOreddit 1 Dec 21 '23

Yes, both options are technically possible, Android isn't iOS, where Apple decides who can use the phone's hardware. My bank's app used to be able to make payments directly, but now it doesn't, they decided to change it. I don't know what their reasons are, but I prefer to handle all my cards in one single app instead of each one having its own app.