5 ms·

Google Wallet does not utilize any form of tokenization to my knowledge. The best you'll get is a proxy card. But that proxy card is used for all merchants.

DannyBee 12y ago
Can you explain what the difference you think there is between a proxy card and tokenization, if the proxy card was randomly generated each transaction (which wallet supports) (Hint: There is no difference, both would be valid methods of tokenization by the spec :P)
- thrownaway2424 12y ago
  But the proxy card isn't randomly generated. It's always the same.
- natrius 12y ago
  Google gets your payment data. Apple doesn't.
  - DannyBee 12y ago
    Google is the payment processor. The tokenization spec completely supports and expects payment processors who are not issuing banks will have payment data :) (I know this goes against what some words in blogs on the internet say, but feel free to read the EMV tokenization spec yourself, and you'll see it's true. Tokenization != only issuing bank sees payment data. Maybe some "ecosystems" try to guarantee it, but it's certainly not required)
- simoncion 12y ago
  Google Wallet may support per-transaction proxy card randomization. Does it actually do this? Can you link to a spec or documentation that supports your claims? Thanks!
  - DannyBee 12y ago
    AFAIK, it does. But that's just what i'm told, if you have data that says it doesn't, ...
    - simoncion 12y ago
      Who told you? I work in nether finance, nor on the Wallet team, so I don't have information about the details of Wallet's workings. Regardless, it's proper for the claimant to provide data to support their claim. :)
Oletros 12y ago
From the Wallet FAQ [1]: > “Wallet also uses dynamically rotating credentials that change with each transaction and are usable for a single payment only.” Does it means that tokenizes something? [1] https://www.google.es/wallet/faq.html#tab=faq-security https://www.google.es/wallet/faq.html#tab=faq-security
- jusben1369 12y ago
  No. As I understand it, and it can change over time, Google stores your actual card. Then, when you're ready to make a transaction, they generate a one time use (mastercard) credit card. It has a finite amount of value to reduce the exposure to fraud (the value is very close the amount you are about to purchase something for). That one time use card then travels the networks very much in the same way that that one time gift card for $50 does. Apple uses _network_ tokenization. It too is like a credit card proxy and each token is device specific. The magic here is that the networks are supporting this technology (although not all back end merchant accounts yet) so they recognize the ApplePay specific network token and allow it to act like a normal credit card. The token is reusable unlike the one time use cards. Lose your phone (or have it stolen) and just that token is revoked - not your card and all your other automated billing etc with it.
  - Oletros 12y ago
    > Then, when you're ready to make a transaction, they generate a one time use (mastercard) credit card. This is the definition of tokenization > Apple uses _network_ tokenization. It too is like a credit card proxy and each token is device specific. The magic here is that the networks are supporting this technology (although not all back end merchant What? > The token is reusable unlike the one time use cards What? I think you have to re read how Apple Pay works and what tokenization really is because i Think you're a little confused
    - jusben1369 12y ago
      That you think a one time use card is the definition of a token makes this a non starter in terms of a discussion.
tonyhb 12y ago
I think Google Wallet even supports it from the HTML5 requestAutocomplete() API for web stores. Not sure if it's a unique card per transaction, but it's good to know you have some protection. Check out the HTML demo here: https://e60696416b5235dfd15e2b9bfc5dab0e3b37ade2.googledrive.com/host/0B28BnxIvH5DueUxvWVNsQXd5dU0/ https://e60696416b5235dfd15e2b9bfc5dab0e3b37ade2.googledrive...

DannyBee 12y ago

Can you explain what the difference you think there is between a proxy card and tokenization, if the proxy card was randomly generated each transaction (which wallet supports) (Hint: There is no difference, both would be valid methods of tokenization by the spec :P)

thrownaway2424 12y ago
But the proxy card isn't randomly generated. It's always the same.
natrius 12y ago
Google gets your payment data. Apple doesn't.
- DannyBee 12y ago
  Google is the payment processor. The tokenization spec completely supports and expects payment processors who are not issuing banks will have payment data :) (I know this goes against what some words in blogs on the internet say, but feel free to read the EMV tokenization spec yourself, and you'll see it's true. Tokenization != only issuing bank sees payment data. Maybe some "ecosystems" try to guarantee it, but it's certainly not required)
simoncion 12y ago
Google Wallet may support per-transaction proxy card randomization. Does it actually do this? Can you link to a spec or documentation that supports your claims? Thanks!
- DannyBee 12y ago
  AFAIK, it does. But that's just what i'm told, if you have data that says it doesn't, ...
  - simoncion 12y ago
    Who told you? I work in nether finance, nor on the Wallet team, so I don't have information about the details of Wallet's workings. Regardless, it's proper for the claimant to provide data to support their claim. :)

Oletros 12y ago

From the Wallet FAQ [1]: > “Wallet also uses dynamically rotating credentials that change with each transaction and are usable for a single payment only.” Does it means that tokenizes something? [1] https://www.google.es/wallet/faq.html#tab=faq-security https://www.google.es/wallet/faq.html#tab=faq-security

jusben1369 12y ago
No. As I understand it, and it can change over time, Google stores your actual card. Then, when you're ready to make a transaction, they generate a one time use (mastercard) credit card. It has a finite amount of value to reduce the exposure to fraud (the value is very close the amount you are about to purchase something for). That one time use card then travels the networks very much in the same way that that one time gift card for $50 does. Apple uses _network_ tokenization. It too is like a credit card proxy and each token is device specific. The magic here is that the networks are supporting this technology (although not all back end merchant accounts yet) so they recognize the ApplePay specific network token and allow it to act like a normal credit card. The token is reusable unlike the one time use cards. Lose your phone (or have it stolen) and just that token is revoked - not your card and all your other automated billing etc with it.
- Oletros 12y ago
  > Then, when you're ready to make a transaction, they generate a one time use (mastercard) credit card. This is the definition of tokenization > Apple uses _network_ tokenization. It too is like a credit card proxy and each token is device specific. The magic here is that the networks are supporting this technology (although not all back end merchant What? > The token is reusable unlike the one time use cards What? I think you have to re read how Apple Pay works and what tokenization really is because i Think you're a little confused
  - jusben1369 12y ago
    That you think a one time use card is the definition of a token makes this a non starter in terms of a discussion.

tonyhb 12y ago

I think Google Wallet even supports it from the HTML5 requestAutocomplete() API for web stores. Not sure if it's a unique card per transaction, but it's good to know you have some protection. Check out the HTML demo here: https://e60696416b5235dfd15e2b9bfc5dab0e3b37ade2.googledrive.com/host/0B28BnxIvH5DueUxvWVNsQXd5dU0/ https://e60696416b5235dfd15e2b9bfc5dab0e3b37ade2.googledrive...