Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) from Zach Koch on 2016-03-13 (public-webpayments-specs@w3.org from March 2016)

From: Zach Koch <notifications@github.com>
Date: Sun, 13 Mar 2016 13:07:42 -0700
To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Message-ID: <w3c/browser-payment-api/issues/9/196044353@github.com>

I agree with Nick. We should use the same response and permit empty values. The payment app can be responsible for discerning when to require certain fields and when not to. We already assume that if a merchant supports a given payment method they know how to parse the response for that method, so this just means for Union Pay you may only get a PAN.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/9#issuecomment-196044353

Received on Sunday, 13 March 2016 20:08:22 UTC