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

Yeah I think we should remove billing address support as well.

The only "support" for billing address in Payment Request API is the [requestBillingAddress](https://w3c.github.io/payment-request/#paymentoptions-dictionary) bit in `PaymentOptions`. The interpretation of this bit is delegated to the selected payment app, which returns the billing address via the method-specific [details](https://w3c.github.io/payment-request/#details-attribute) of `PaymentResponse`. Currently the payment app is also responsible for redacting the billing address when appropriate (Section [18.7](https://w3c.github.io/payment-request/#user-info))

So if both shipping and billing addresses are removed from the Payment Request API, the end state will be a consistent one: Payment Request API is concerned with collecting common payment inputs (e.g. amount, payee) and invoking the user-selected payment app via `show()`. The collection of shipping and billing addresses is the responsibility of merchants, who can either do this via forms, or use the payment-method-specific channel. Note that the vast majority of developers are already doing this today, so the simplification of the spec is just a recognition of the existing usage pattern in the wild.

I believe this will leave the Payment Request API in a simpler state to build upon in the future.

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