Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) from Marcos Cáceres on 2018-08-08 (public-webpayments-specs@w3.org from August 2018)

From: Marcos Cáceres <notifications@github.com>
Date: Wed, 08 Aug 2018 04:20:18 -0700
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/issues/27/411372293@github.com>

I'd like to exhaust @michelle's current proposal, which is #749. Honestly, the above sounds extremely complicated, and would like the various UX teams to explore how it might work best (the requirement is clear: "merchant needs the billing address to calculate, user want to protect their privacy until they hit pay" - let's leave it at that and lets explore how far we get). 

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

Received on Wednesday, 8 August 2018 11:20:49 UTC