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

Payment Request API currently specifies a [standardized interface](https://w3c.github.io/payment-request/#dom-paymentoptions) for merchants to request shipping and contact information from payment methods. However, [Basic-Card](https://w3c.github.io/payment-method-basic-card/) is the only payment method that supports this interface. The two other payment methods in production, [Apple Pay](https://developer.apple.com/documentation/apple_pay_on_the_web/applepaypaymentrequest) and [Google Pay](https://developers.google.com/pay/api/web/reference/request-objects#PaymentDataRequest), both implement shipping and contact information collection via [method-specific data](https://w3c.github.io/payment-request/#dom-paymentmethoddata). Other payment app developers have also [requested](https://github.com/w3c/payment-handler/issues/337) shifting the collection of such information from the browser to the payment apps.

On the other hand, shipping address is a sensitive piece of personally identifying information of the user. It has been pointed out (e.g. #842) that any interface for collecting shipping address should support richer negotiation to avoid unnecessary collection of user information.

Given the lack of developer interest for the browser to provide shipping address, and the significant development effort involved to fully implement #842, I'd like to propose that we split out the shipping address related behaviors from Payment Request API 1.0 and to be considered in a future iteration of Payment Request API.

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