- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Thu, 07 Apr 2016 11:32:49 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Thursday, 7 April 2016 18:33:44 UTC
In TAG review @triblondon said: >> If the sequence is empty, then this indicates that the merchant cannot ship to the current shippingAddress. > shippingOptions appears not to support the idea of a transaction that does not require shipping (eg a digital service). This is covered off by the PaymentOptions interface but it would be worth clarifying that shippingOptions is only expected to be supplied by the merchant when they are also requesting shipping address in PaymentOptions --- 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/128
Received on Thursday, 7 April 2016 18:33:44 UTC