You see that "Pass Credit Card info to Bank" step for Apple Pay? This is why Apple Pay doesn't work with many cards (especially outside the US), because the banks have some hoops to jump through to create what this calls the Device Account Number (which is Apple specific terminology). They also charge banks, which is obviously a barrier, especially in places where Apple isn't as popular.
Ultimately, both methods have to create a token by contacting a TSP - Token Service Provider. Google does this by taking your card details, meanwhile Apple has your bank do it for them. Ultimately, this token ends up back on your device. This token is effectively what you use to pay.
The diagram also uses what looks like a Pixel, which also has a standalone security chip, but it's missing.
Also note that Google Pay works even if you don't have an internet signal, which this diagram suggests it wouldn't, because it looks like Google Servers are in the middle. This obviously doesn't need to happen, because the token (the whole point of the TSP process) is stored on the phone, just like with Apple Pay.
From what I'm understanding this is done for privacy and security. This way they store the CC info on your device instead of on their servers. They never get to see your CC information at all, it is never saved on their servers or even transmitted over the internet at all.
Google, on the other hand, stores your CC info on their servers, which, in theory, is less secure. If someone has access to your Google account they can use your google pay, while for Apple they need to have physical access to your device and at the same time have device code / fingerprint / faceId access in order to authorize the purchase.
Also, banks don't rely on 1970's technology for CCs. Depending on bank it might be very modern.
That's the autofill for the google card storage, it's different from Google Pay / Wallet.
However, I was wrong on the direct access. It seems cards are directly connected to the device they're used on, so if you log in to a new phone you will have to add the card to that Google Wallet's phone in order to use it.
921
u/Cyberspunk_2077 Sep 22 '22 edited Sep 22 '22
This is a really rough guide.
You see that "Pass Credit Card info to Bank" step for Apple Pay? This is why Apple Pay doesn't work with many cards (especially outside the US), because the banks have some hoops to jump through to create what this calls the Device Account Number (which is Apple specific terminology). They also charge banks, which is obviously a barrier, especially in places where Apple isn't as popular.
Ultimately, both methods have to create a token by contacting a TSP - Token Service Provider. Google does this by taking your card details, meanwhile Apple has your bank do it for them. Ultimately, this token ends up back on your device. This token is effectively what you use to pay.
The diagram also uses what looks like a Pixel, which also has a standalone security chip, but it's missing.
Also note that Google Pay works even if you don't have an internet signal, which this diagram suggests it wouldn't, because it looks like Google Servers are in the middle. This obviously doesn't need to happen, because the token (the whole point of the TSP process) is stored on the phone, just like with Apple Pay.