3 ms·

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" wi

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).

3 ms·

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" wi

by JeremyNT 5y ago

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).