Really?..so why are we not seeing the same banks having the same problem with Goggle Wallet that been in place for some years..
FYI I have worked in the past for American Express doing network design.. and now with security company doing PCI compliance for business.... and moving in to pen testing/white hat hacking...
It odd the banks only screwed up and exposed ApplePay but not Goggle Wallet....
So whats the variable that the same banks has two different result’s with two different systems?
Two totally different payment models.
Google Wallet is merely a payment system that uses an Android App to connect to Google through NFC in place of normal credit card processing services for Credit Cards that are registered with Google. To do this, Google stores the credit card numbers, the card holder's name, and ID information on their servers. The Google Wallet App generates a one-time Token which is transmitted to Google where it is linked to the credit card data, and then Google converts it to a normal credit/debit card sale and sends it on to the issuing bank. Google is intimately involved with every transaction made with Google Wallet. . . and acts as the clearing house for the transfer of funds. Acting as an agent for the people who have entrusted their credit/debit cards with them have almost become a Quasi transfer bank similar to PayPal. As such, they have to be sure they are representing the correct person, the owners of the cards.
On the other hand, taking a hands off approach, Apple never registers a card number or any user's ID information. Apple knows a user is using ApplePay, but that's it. Apple will know a transaction has taken place, but not where, with whom, or the amount. . . and only after the fact when they get anonymous aggregated payment of fees. Apple never stores the card number on an Apple server. Apple never sees the card number or the name on the card. Apple is never involved in any of the transactions made with ApplePay. Any such identifiable information never leaves the control of the card and iPhone owner. It is stored on the iPhones Secure Enclave in the processor under 256 bit AES encryption keyed to the fingerprint of the owner. Aple never stores the card number on an Apple server. Apple never sees the card number or the name on the card. Apple is never involved in any of the transactions made with ApplePay. Apple is NOT acting as an agent for the user of the Credit/Debit card.
As I stated, Google does the validation process. Users provide Google with the credit card number, their address, the card's security number on the back (I never have quite figured out what is so secure about that number on the back of the card), if it's a Debit Card, their PIN, their Social Security Number, other identifying information such as their mother's maiden name, and then Google will validate their card with the issuing bank. Then when ever the owner of the card used their Google Wallet, Google would step between the merchant and their Credit Card processor and do the processing instead, charging the merchant Google's fees, which were generally quite a bit higher than what the Credit Card and the Merchant may have agreed to.
Since Google Wallet has taken on far more of a financial involvement, they are far more at risk of fraud than is Apple so must take a greater participation in making sure the cards belong to the people registering them. As a matter of financial self-interest to Google, Google took care of validating the cards.
Apple does not validate anything except that the owner of the iPhone has an AppleID account with a credit card attached. . . it leaves the validation of the card and the fact it is the owner installing it to the issuing banks themselves to do, just as the banks do when they issue a card in the first place.