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

@ianbjacobs This is better than nothing.. but I can give you another use case where it's absolutely mandatory for merchant to capture some information at the time of placing order (for legal reasons) and it can't be assumed that customer is going to provide this after the checkout. From our experience, not many customers read instructions on thank you page. 

Here is the use case - 

A merchant offering click and collect / Ship to store functionality sells Knives (some geographies have strict signature requirements on delivery/collection for such items) OR Let's say XBox games (which are 18+). Merchant needs to make sure customer declares in this case that are above 18. In addition to these declarations, obviously merchants are supposed to check IDs.and 

Also in some cases some merchants may also ask who will be collecting the item in store and customer placing order can nominate a 'pick up person' to collect the order (You can see Walmart.com for 'pick up person' functionality). This can be provided post checkout as proposed by you and @mustafa-x



-- 
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-308259437