Re: [w3c/payment-request] Split shipping address from Payment Request API 1.0 (#939)

#842 also covers billing address.  As I said in https://github.com/w3c/payment-request/issues/842#issuecomment-468355050, I've seen cases in the wild (in the US) where merchants ask for only postcode for fraud prevention. In https://github.com/w3c/payment-request/issues/842#issuecomment-469536532 @marcoscaceres observes that billing addresses are (sometimes) used for tax computation, which brings along the full complement of concerns I outlined in https://github.com/w3c/payment-request/issues/842#issuecomment-473907871, even though [my comment](https://github.com/w3c/payment-request/issues/842#issuecomment-473907871) makes the opposite assumption about billing addresses being used for tax computation.

As for splitting shipping address out of the Payment Request API: the payment method, whether Basic-Card or otherwise, is still faced with the task of negotiating which portions of the shipping address to share.  My understanding from the block diagram @ianbjacobs shared with me is that Payment Request is the only channel to the payment method.  If that's true (and perhaps it's not), then Payment Request still needs to have the machinery to pass along the request(s) re: negotiation of address components to the payment method.  My open-ended question is: "If this change is made, what channel(s) remain for payment methods to negotiate which portions of the shipping address to share?"

-- 
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/939#issuecomment-811230947