4 ms·

There's multiple forms of "Google Pay" and people seem to be confused about this. You are talking about adding a card to tap-to-pay, and therefore generating a

There's multiple forms of "Google Pay" and people seem to be confused about this. You are talking about adding a card to tap-to-pay, and therefore generating a tokenized device account. That requires verification as you are essentially "creating" a "new" card. "Google Pay" is also the name of the peer-to-peer transfer service Google has (had?) which accepts debit and credit cards and allows you to pay others. This only uses standard address verification. "Google Pay" is also the name of the payment processing service Google uses for their own services, like the Play Store. Adding a card here also only uses standard address verification. Data is shared between these three systems. If you have already registered cards with 2/3, they will be pre-populated when you try and add a new tap-to-pay card, and at that point you do the SMS verification.

jjulius 5y ago
>There's multiple forms of "Google Pay" and people seem to be confused about this. >Data is shared between these three systems. I understand the point you're making, but if the three systems share the same name, and they all share data between themselves, then for all intents and purposes it's one system.
- mynameisvlad 5y ago
  The point I'm really making is that not all forms of Google Pay require the same amount of verification, so it's quite conceivable that the author of the Tweet didn't go through rigorous 2FA like the GP comment did. Whether it's considered one or multiple systems is a pedantic opinion that will depend on the person and doesn't really change the core point I'm making.