Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) from Domenic Denicola on 2018-07-09 (public-webpayments-specs@w3.org from July 2018)

From: Domenic Denicola <notifications@github.com>
Date: Mon, 09 Jul 2018 13:45:15 -0700
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/issues/27/403614316@github.com>

So I'm reviewing some patches, but then I went over to look at the basic card spec, and see it currently requires a "billingAddress". The only mention I found of basic card in this thread via Ctrl+F was https://github.com/w3c/payment-request/issues/27#issuecomment-337064813.

How is this reconciled? Is "basic card billing address" distinct from "PaymentRequest payer address"? Will UIs have three separate address fields, if the web developer passes requestPayerAddress and also uses basic-card? Or is there a plan to somehow sunset billingAddress from basic card?

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

Received on Monday, 9 July 2018 20:45:39 UTC