Re: [w3c/webpayments] Update to tokenized card spec to include more examples and additional… (#213)

Thanks, Kevin! I have a couple of minor suggestions:

* s/The intention is for this to extend from/This specification extends

* s/supports sending the/supports sending a/          (We've not introduced the notion of a "token/cryptogram combination" yet)

* I suggest we delete "There is often a higher cost associated with issuer tokens." People are going to decide which token type they want to use for a variety of reasons, and this feels to me both incomplete as far as "help in making a choice" and also unnecessary to understand the specification. 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

Received on Thursday, 16 February 2017 20:37:04 UTC