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 us

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