- From: Shane McCarron <notifications@github.com>
- Date: Fri, 22 Apr 2016 09:24:48 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Friday, 22 April 2016 16:25:45 UTC
Why would a new token only become supported with a new browser version? The browser is not part of the transaction except as a string matching engine in this instance. You would need a payment app that recognized the token and a merchant who wanted to use it. Unless you think these tokens are enumerated in the WebIDL.... Which would be silly. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/11#issuecomment-213498114
Received on Friday, 22 April 2016 16:25:45 UTC