Re: User Consent and Addresses

I'm referring to the "Payment Apps" and the "HTTP API" spec proposals here:

    http://w3c.github.io/webpayments-http-api/#generating-a-payment-response


https://w3c.github.io/webpayments/proposals/paymentapps/payment-apps.html#submitting-the-paymentrequest-to-the-payment-app

Both of these propose to pass the payment request to the payment app by
using an HTTP POST.

-Tommy


On Tue, May 10, 2016 at 3:58 PM, Adam Roach <abr@mozilla.com> wrote:

> On 5/10/16 08:54, Tommy Thorsen wrote:
>
> I think many payment apps will want to supply shipping information along
> with the rest of the payment response, and I think we should allow that.
> However, since we are planning to pass the request to the payment app by
> means of HTTP POST, the onshippingaddresschange mechanism isn't going to
> work. The shipping address will have to be passed back in the payment
> response.
>
>
> I must be missing some context here. Can you point to one of the callflow
> diagrams that shows the scenario you're thinking of?
>
> --
> Adam Roach
> Principal Platform Engineer
> Office of the CTO
>