Re: [w3c/browser-payment-api] A distinct invoice address should be supported (#550)

Hi @GSPP,

Thank you for the comment. I have a couple of observations about past discussions:

* This was one of our earliest issues:
   https://github.com/w3c/browser-payment-api/issues/27

* We discussed it most recently face-to-face in March [1] . There is agreement that it's important for the use case of billing address affecting price for digital goodes. However at this time we do not plan to add the feature into the specification. This could well be a "v2" feature based on experience gained through the API. 

@rvm4, I have not checked in lately to see whether there are any proposals in the works around this feature.

It seems to me that the WG needs to do a better job of documenting this in our FAQ [2], so I have just started an entry [3]. It would also be good to show some good practice [4] for gathering the necessary data through some other means than Payment Request API. 

I am pinging @rsolomakhin and @andrelyver in particular to see if they have any good practice code to share.

Thanks again for the feedback,

Ian

[1] https://www.w3.org/2017/03/23-wpwg-minutes#vat
[2] https://github.com/w3c/payment-request-info/wiki/FAQ
[3] https://github.com/w3c/payment-request-info/wiki/FAQ#does-payment-request-api-enable-merchants-to-request-a-separate-billing-address
[4] https://github.com/w3c/payment-request-info/wiki/CodeExamples


-- 
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/550#issuecomment-308576057