3 ms·

(Googler, opinions are my own). I work on payments, but I don't have intricate knowledge about how autofill and "google pay" accounts work. I think the confus

by kyrra 5y ago

(Googler, opinions are my own). I work on payments, but I don't have intricate knowledge about how autofill and "google pay" accounts work. I think the confusion here is around having a payments profiles and Google Pay. Looks like we started calling your payments profile now having a "Google Pay account". There is Google Pay (the app for tap-and-pay, along with P2P payments), then there is having a Payments Profile (which apparently we're now calling Google Pay, because that's not confusing), which you use for buying things on Google's properties. There used to be a https://payments.google.com https://payments.google.com but that just redirects to https://pay.google.com/ https://pay.google.com/. This is your payments profile. As far as I understand, when you added a card for chrome autofill, it would create a payments profile, as the card was stored as part of that system. The support docs say something like this: https://support.google.com/chrome/answer/142893?hl=en https://support.google.com/chrome/answer/142893?hl=en > When you’re signed in to Chrome and you enter your payment method into an online form, Chrome may ask if you want to save your payment info in Google Pay. If you accept, your payment information is saved in Google Pay. If Google Pay doesn’t support your payment method, Chrome may offer to save it locally on your device. The Google Pay app (used for Tap-And-Pay) has its own activation process for being able to use a card, as it requires a 2FA process (depending on your bank).

MomoXenosaga 5y ago
Interesting now I will make sure never to use my smartphone for payments.
JeremyNT 5y ago
I got bitten by a strange variant of this the other day. I tried using Lyft (which I'd done in the past on other phones), and on Android it uses "google pay" with seemingly no other option. Even though I had (somewhere, somehow) entered multiple cards into one of these google payment systems previously, none of them were actually usable for "tap to pay" purposes. I never cared about this fact because I have a Garmin watch which implements its own tap to pay. It turns out that Lyft required that I have a "tap to pay" account set up. Upon requesting a ride, I received an error stating that none of my existing Google Pay methods were valid. The only thing I could do at that point was to register one of the cards that Google already had on file for "tap to pay," which in turn required that I complete the provider MFA enrollment process. This meant that I had to sit on hold for 10 minutes and give them some personal information before I was even able to request a ride with Lyft. Which sucked, because I was tired and wanted to get home. The UX was completely terrible here. I don't know if Uber would've been the same way, but I want to nope right out of this entire stupid ecosystem.
- kyrra 5y ago
  Googler, opinions are my own. I think this is done as a way to do "in app" purchases that don't flow through Google. Tap-to-pay cards are effectively single use (due to the cryptogram that gets passed with it), it won't store the card with Lyft. The other way Google does integration with 3rd parties is the "Pay with Google" button on websites, that will vault your card on file at Google into stripe or braintree, then the merchant can use that for a transaction. Both of these methods move the liability of the payment onto the merchant (Lyft in this case).
throwra620 5y ago

by kyrra 5y ago

MomoXenosaga 5y ago

Interesting now I will make sure never to use my smartphone for payments.

JeremyNT 5y ago

I got bitten by a strange variant of this the other day. I tried using Lyft (which I'd done in the past on other phones), and on Android it uses "google pay" with seemingly no other option. Even though I had (somewhere, somehow) entered multiple cards into one of these google payment systems previously, none of them were actually usable for "tap to pay" purposes. I never cared about this fact because I have a Garmin watch which implements its own tap to pay. It turns out that Lyft required that I have a "tap to pay" account set up. Upon requesting a ride, I received an error stating that none of my existing Google Pay methods were valid. The only thing I could do at that point was to register one of the cards that Google already had on file for "tap to pay," which in turn required that I complete the provider MFA enrollment process. This meant that I had to sit on hold for 10 minutes and give them some personal information before I was even able to request a ride with Lyft. Which sucked, because I was tired and wanted to get home. The UX was completely terrible here. I don't know if Uber would've been the same way, but I want to nope right out of this entire stupid ecosystem.

kyrra 5y ago
Googler, opinions are my own. I think this is done as a way to do "in app" purchases that don't flow through Google. Tap-to-pay cards are effectively single use (due to the cryptogram that gets passed with it), it won't store the card with Lyft. The other way Google does integration with 3rd parties is the "Pay with Google" button on websites, that will vault your card on file at Google into stripe or braintree, then the merchant can use that for a transaction. Both of these methods move the liability of the payment onto the merchant (Lyft in this case).

throwra620 5y ago