Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9)

> The only benefit of being rigid is that the website can have better defined expectations about what data they will receive. In my opinion, if a website supports UnionPay cards then they expect to do a null value check against certain fields anyway so this value is negligible.

A couple of points of clarity;

1. UnionPay cards may have all the fields, it is just UnionPay Debit cards that don't. PR #95 covers this
2. I'd expect this data to be passed and processed by an acquirer rather than the merchant.

-1 to not making the PAN mandatory, when we have tokenised or encrypted PANs, that probably needs another data structure, it will need another PMI for sure. I think it should be clear in the spec that the Payment Application must return a PAN to use the BasicCardResponse format.




---
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/9#issuecomment-199301775