W3C home > Mailing lists > Public > public-payments-wg@w3.org > September 2017

RE: Just Released: W3C Web Payments Polyfill and Demo (video)

From: David Ezell <David_E3@VERIFONE.com>
Date: Sat, 9 Sep 2017 15:22:23 +0000
To: Manu Sporny <msporny@digitalbazaar.com>, w3c-webpayments-wg <w3c-webpayments-wg@digitalbazaar.com>
Message-ID: <SN1PR0301MB16158CFB8DBCFB711919D607C86A0@SN1PR0301MB1615.namprd03.prod.outlook.com>
Hi Manu:
I'm late[1] saying "thank you."  I think this announcement is a tremendous step for universal adoption of the WG's work.
From my position at NACS, the approach will allow for much wider adoption among NACS software suppliers.  And of course, wider adoption
in our kind of retail market segment helps smooth adoption in other segments.

We're excited to see the results of working with the test suite and addressing the other issues mentioned on this thread.
Thanks very much.

Best regards,
David

[1] All of us here in Florida have become increasingly distracted.

> -----Original Message-----
> From: Manu Sporny [mailto:msporny@digitalbazaar.com]
> Sent: Wednesday, September 06, 2017 3:17 PM
> To: w3c-webpayments-wg
> Subject: Just Released: W3C Web Payments Polyfill and Demo (video)
>
> Hi Web Payments WG and WPIG (bcc'd),
>
> Exciting news. The engineering team at Digital Bazaar has been hard at work
> creating a production grade polyfill for both the Payment Request API and the
> Payment Handler API in Chrome, Safari, Edge, and Firefox.
> We're announcing a beta release to developers today.
>
> An introductory video giving some background as well as recordings showing it
> working in all major browsers can be found here (6 minutes
> runtime):
>
> https://www.youtube.com/watch?v=Yb-gWT1t1Rg

>
> What does this mean for the W3C Web Payments work?
>
> * When the polyfill hits production, we expect that ~90% of all browsers
>   (roughly 2.8 billion people) will immediately get support for the Web
>   Payments APIs across desktop and mobile browsers.
>
> * Web developers won't need to wait for browsers to implement the latest
>   Web Payments API in order to deploy to their customers. Instead, the
>   polyfill will provide missing browser features until the browsers
>   support them.
>
> * This will enable us to more rapidly test and deploy new payment
>   features, greatly reducing the cost of innovation in the group, and
>   enabling more people to participate in the design and development
>   process.
>
> * The polyfill is one more implementation of the specs.
>
> What is next?
>
> * We'll continue to harden the polyfill for production usage.
>
> * We plan to provide technical review feedback on both specs after
>   having implemented them.
>
> * We'll pick an open license that works for all orgs and implementers.
>
> * We still need to implement some simple things, like better
>   animations/transitions when selecting payment instruments and things
>   like shipping address selection.
>
> * There are some issues in Safari that require preference changes that
>   we're trying to work around.
>
> * The foundation of the polyfill is, as predicted, almost exactly the
>   same as the verifiable claims polyfill, which may have repercussions
>   for how these sorts of APIs are designed at W3C. We'll produce a
>   report detailing the similarities before W3C TPAC.
>
> We'll bring up these topics as the work progresses in the WPWG. This email is
> just a heads up regarding this new capability for the Web Payments groups.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Rebalancing How the Web is Built
> http://manu.sporny.org/2016/rebalancing/

>

*********************************************************
This electronic message and any attachments are intended only for the use of the addressee. The information in this electronic message is confidential and proprietary, and may include privileged information. If you are not the intended recipient, please delete this electronic message and any attachments and notify the sender of the error. Please be aware that any unauthorized use, dissemination, distribution or copying of this message or any attachments is strictly prohibited.
Received on Saturday, 9 September 2017 15:22:59 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 9 September 2017 15:23:01 UTC