- From: Zach Koch <notifications@github.com>
- Date: Thu, 02 Mar 2017 00:05:44 -0800
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 2 March 2017 08:06:33 UTC
The reason we left this out is that it's unclear how shippingOptions should be treated. One answer is that the shippingOptions array becomes a set of possible pickup locations. But for major merchants, this can be a really, really long list and there's no reasonable way for the merchant to filter them since we don't have a way to pass back the users current zip code for example. We could also say that "storePickup" doesn't have shipping option support and the merchant is responsible for showing a list of potential stores after the transaction is finished, but this also feels deficient because...what if the item isn't available after you purchase at the location you want? -- 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/389#issuecomment-283584165
Received on Thursday, 2 March 2017 08:06:33 UTC