Re: [w3c/browser-payment-api] Adding custom fields next after shipping options have been added. (#548)

Hi @mustafa-x,

This topic is one of the earliest that the Working Group has pondered: for the data collection portion of the API, what fields should be supported? Opinions have varied, as you might imagine, and we've reached reasonable consensus on a sort of "minimal" set that can be returned quickly and without typing. 

>From a UI perspective, I understand that it would be handy to have an extra form field
nearby. But special instructions and notes to the merchant are not likely to stored data
quickly reused, which is the strong suit of PR API. 

My expectation (based on WG discussion) is that we may learn through broad deployment
that we need to add additional fields.

In the meantime, it would be great to show some code for how a merchant might
use the PR API response to trigger additional UI (in a Web page) to gather this
information.

For that reason I'm pinging @rsolomakhin and @andrelyver to see if they have
code suggestions, and ideally we would add them to our developer portal:
  https://github.com/w3c/payment-request-info/wiki/CodeExamples

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/browser-payment-api/issues/548#issuecomment-307826810