W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: User Consent and Addresses

From: Adam Roach <abr@mozilla.com>
Date: Tue, 10 May 2016 08:58:29 -0500
To: Tommy Thorsen <tommyt@opera.com>, Dave Longley <dlongley@digitalbazaar.com>
Cc: Ian Jacobs <ij@w3.org>, Adrian Bateman <adrianba@microsoft.com>, Web Payments Working Group <public-payments-wg@w3.org>
Message-ID: <93132194-4cdc-c3f5-9781-3c8a140be52c@mozilla.com>
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
Received on Tuesday, 10 May 2016 14:28:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 May 2016 14:28:07 UTC