@mattsaxon, When I say "Basic Card implementation" I specifically mean any payment app that is populating the BasicCardResponse blob. That will either be a browser (acting as a basic card payment app) or a third party payment app. I am not sure I agree with your approach because (and I'm putting quotes here intentionally): "it doesn't matter if the card has an expiry date" if the payment app / browser does not collect it from the user. Thus, the existence of the data is not relevant. What matters is that it has been collected. Today the spec does NOT require collection of all pieces of data (cf the "optional" parts of the WebIDL). Therefore, if it does come down to the question of "if the payment app / browser has it, they must return it." Ian -- 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/webpayments-methods-card/issues/26#issuecomment-290174177
Received on Wednesday, 29 March 2017 18:07:26 UTC