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

RE: Google I/O talk about PaymentRequest

From: Bakshi, Sanjay <sanjay.bakshi@intel.com>
Date: Mon, 23 May 2016 16:43:49 +0000
To: Rouslan Solomakhin <rouslan@google.com>, Anders Rundgren <anders.rundgren.net@gmail.com>
CC: Adrian Hope-Bailie <adrian@hopebailie.com>, Ian Jacobs <ij@w3.org>, Payments WG <public-payments-wg@w3.org>
Message-ID: <473D6F3278454E40868E59A67C5B26830A9182A1@ORSMSX101.amr.corp.intel.com>
Hi Rouslan,
Are there any plans to support PaymentRequest on desktop Chrome too?
Best…sanjay

From: Rouslan Solomakhin [mailto:rouslan@google.com]
Sent: Monday, May 23, 2016 9:33 AM
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: Adrian Hope-Bailie <adrian@hopebailie.com>; Ian Jacobs <ij@w3.org>; Payments WG <public-payments-wg@w3.org>
Subject: Re: Google I/O talk about PaymentRequest

Hm, perhaps my wording in the video was cryptic. "Third-party apps" means "payment apps". Merchant website developers can try out PaymentRequest today. (They can access Chrome's Autofill data and Android Pay through PaymentRequest today in Chrome Dev for Android.) See https://goo.gl/spaces/2Npre43gX9odYPKn9 for more details and updates.

On Mon, May 23, 2016 at 9:30 AM Rouslan Solomakhin <rouslan@google.com<mailto:rouslan@google.com>> wrote:
We are prototyping now, but the web developers cannot access our prototypes yet. Third-party integration means two things:

1) Chrome provides a way for any app to say "I am a payment app". This includes both native apps and websites.
2) A developer of a payment app modifies their App to hook into Chrome.

Website-based payment apps are being discussed in this WG now. I'd like to define Android native payment app API as well. I expect it to be intent-based. That way an browser on Android can talk to any Android native payment app via the package manager. Stay tuned for updates.

The reason for the stretched out time-line is mostly due to engineering and planning. Testing, integration, productionizing, UI polish---all of that takes time.

On Mon, May 23, 2016 at 1:39 AM Anders Rundgren <anders.rundgren.net@gmail.com<mailto:anders.rundgren.net@gmail.com>> wrote:
On 2016-05-22 20:46, Rouslan Solomakhin wrote:
> Thank you! Let's build something great together :-D

In the video at 26:20 there is a slide saying that third-party application
integration is slated for "Early 2017".  Does this mean that you cannot even
prototype now, although there's a beta browser supporting the current
Web Payment API?  I don't really understand what you mean with third-party
integration either, what exactly is required from Google's side?

Anders


>
> On Fri, May 20, 2016 at 11:03 PM Adrian Hope-Bailie <adrian@hopebailie.com<mailto:adrian@hopebailie.com> <mailto:adrian@hopebailie.com<mailto:adrian@hopebailie.com>>> wrote:
>
>     Great work Rouslan!
>
>     Looking forward to getting a lot more developer eyes on the work now.
>
>     On Saturday, May 21, 2016, Ian Jacobs <ij@w3.org<mailto:ij@w3.org> <mailto:ij@w3.org<mailto:ij@w3.org>>> wrote:
>
>         Hi all,
>
>         Today at Google I/O, Rouslan and Alex Sieke presented PaymentRequest in:
>
>           Bringing seamless checkouts to the mobile web
>           https://youtu.be/yelPlCVZLEE

>
>         Congrats to both of them and many thanks for inviting developers and
>         merchants to help improve the API by commenting on the spec.
>
>         I was glad to see these goals for the API emphasized:
>
>          * Cross-browser
>          * Cross-device
>          * Open ecosystem (which touched on both “any payment method” and “third party apps”).
>
>         Have a good weekend,
>
>         Ian
>
>         --
>         Ian Jacobs <ij@w3.org<mailto:ij@w3.org>>      http://www.w3.org/People/Jacobs

>         Tel:                       +1 718 260 9447
>
>
>
>
>
>     --
>     Sent from a mobile device, please excuse any typos
>
Received on Monday, 23 May 2016 19:38:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 May 2016 19:38:17 UTC