Re: [w3c/browser-payment-api] Required fields (#176)

@zkoch which would we enforce this at the API level anyway?

To me this IDL simply provides a standardized data model for the payment app to hang data off so that the website (or PSP) that gets the response knows where to find things. If we are too restrictive we will force people to write new payment method specs to simply change a field from mandatory to optional.

A question for @zkoch and @adrianba (or any other browser vendor) is whether you expect the browser to do any validation of this data when it comes back from a third-party payment app? I expected it to be entirely opaque.

---
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/pull/176#issuecomment-216484400