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

Re: Review of Payment Apps Proposal

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 3 May 2016 22:31:32 -0400
To: public-payments-wg@w3.org
Message-ID: <57295F04.30408@digitalbazaar.com>
On 04/24/2016 01:52 PM, Zach Koch wrote:
> We strongly hope (and will push for) a registration spec to be 
> developed in parallel.

Thanks for the detailed response, Zach. Your reasoning makes sense from
a browser vendor perspective given the requirements you have in front of
you.

There are two things you've said in the past few weeks that have
resonated with my organization (as a non-browser vendor). The first is
the above - that registration of 3rd party payment apps is important to
your organization and there is a strong desire to make that work. This
partially allays fears that the browser vendors would band together and
get out into the market w/o registration in place (giving your
organizations a head start) and then delay implementation of 3rd party
payment app registration due to a lack of available bandwidth.

The second is something you and Adrian Bateman said on the call last
week, something to the effect that the Browser Payments API will be
released behind a browser flag initially (or via "origin trials"). This
partially allays fears that the first deployment of a very experimental
set of features (the Browser Payments API as it stands right now) won't
accidentally get so much uptake that the WG will have no power to change
it due to "broad deployment in the wild".

Those two sets of statements have made it easier (for my organization,
at least) to process issues in a more iterative approach without
worrying about the Browser API being shipped and all of a sudden being
set in stone when there is still much work that needs to be done on it
before CR.

So, thanks for the response, Zach. You're saying all the right things
and as long as the browser vendors execute the deployment of the Web
Payments API in the manner that you've outlined I think we'll be in good
shape.

We look forward to providing a developer-facing CR
testable/interoperable implementation of 3rd party payment app
registration via these sites (for the Browser API) when the time comes:

http://payment-app-demo.web-payments.io/
http://merchant-demo.web-payments.io/

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
JSON-LD Best Practice: Context Caching
https://manu.sporny.org/2016/json-ld-context-caching/
Received on Wednesday, 4 May 2016 02:32:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 May 2016 02:32:06 UTC