Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)

Ok, but that’s a UX problem no? Or do we expect payment handlers to provide the billing address? 

Put differently, we know that we want:

1. Merchants to be able to request the billing address.
2. When the user selects a billing address, the address is sent to the merchant so they can calculate tax.
3. A means to update the total if needed (solved by ev.updateWith(), and retry()).

If the UA exclusively holds the billing address(es), then the above holds. If the payment handler holds the billing address, then we need to have a more detailed discussion... but it feels like that discussion is outside the scope of v1, personally. 



-- 
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/payment-request/issues/27#issuecomment-411406230

Received on Wednesday, 8 August 2018 13:32:44 UTC