Re: PaymentRequest API - Chrome Issue

[Rouslan Solomakhin]

Hi Jim!

Great to hear from you! The shippingaddressupdate event is now being redacted, because calculations of the shipping price should not require recipient, organization, addressLine and phoneNumber. I recommend that you subscribe to payment...@chromium.org mailing list, where we announce changes such as this one. I hope this helps.

Cheers,

Rouslan

On Tue, Nov 12, 2019 at 7:05 PM Jim Olguin <jol...@zobristinc.com> wrote:

Hi Chrome Dev Team!

I saw your emails attached to the PaymentRequest API for Chrome and was wondering if you could shed some light on an issue we are having with Chrome. 

I'm a contractor currently working on behalf of Vanity Fair. We implemented web payments awhile back using the PaymentRequest API with Chrome. It's been doing great until recently. 

The recent release of Chrome 78 is causing problems with our customers completing web payments through Chrome.

 

Customers are unable to select a valid saved shipping address due to an issue with PaymentAddress object not being populated correctly on the PaymentRequest instance. 

We noticed that address info and phone info is not being passed to the PaymentRequest API. 

You will see below addressLine is not populated after selecting an address from my saved addresses in Chrome. Also, phone is not populated, even though there is a phone value on the form.

Also, noticed that this was happening on your own sample page for PaymentRequest API

 

However, it was working on Chrome 76. 

Any insight you can provide on this would be beneficial. 

Thanks!

Jim Olguin

UI Developer