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 11:06:29 -0500
To: Andre Lyver <andre.lyver@shopify.com>, Adrian Hope-Bailie <adrian@hopebailie.com>, Ian Jacobs <ij@w3.org>
Cc: Adrian Bateman <adrianba@microsoft.com>, Web Payments Working Group <public-payments-wg@w3.org>
Message-ID: <c5b85b9f-845a-e502-97d1-396e35c09ace@mozilla.com>
On 5/10/16 11:02, Andre Lyver wrote:
> Agree with Adrian H-B.
> This behaviour is crucial to the checkout flow for merchants (and 
> especially Shopify). I think the fundamental piece that we are 
> forgetting is the fact that the final amount is going to change based 
> on a shipping address or shipping option change. This was the reason 
> for including the shippingoptionchange and shippingaddresschange 
> Events and their associated event handlers it in the Payment Request API.
> https://w3c.github.io/browser-payment-api/specs/paymentrequest.html#shipping-address-changed-algorithm.
> For example, a change of shipping address by the payer can invalidate 
> the shipping method selected (e.g. a change country from Canada to 
> U.S. may mean that CanadaPost is no longer available). This means that 
> a different shipping option will need to be selected, and as a result, 
> the final transaction amount will need to be updated (via 
> PaymentRequestUpdateEvent) _prior_ to proceeding with the actual payment.

That all sounds correct. It also sounds like a pretty compelling set of 
arguments for collecting the address and shipping method prior to 
initiating the payment flow.

Adam Roach
Principal Platform Engineer
Office of the CTO
Received on Tuesday, 10 May 2016 16:07:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 May 2016 16:07:03 UTC