W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2021

Re: DECISION: Regarding Call for Consensus to publish Payment Request API as a Proposed Recommendation; please review one change by 1 February.

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 29 Jan 2021 06:46:43 +0100
To: Ian Jacobs <ij@w3.org>
Cc: Marcos Caceres <marcos@marcosc.com>, Tom Jones <thomasclinganjones@gmail.com>, Web Payments Working Group <public-payments-wg@w3.org>
Message-ID: <1f228fc4-75b0-705b-399f-fc997a70b51d@gmail.com>
Hi Ian,

I understand that you must defend your project even if it [apparently] takes EONs of time to finish.

IMO, Google (the *company*, not Rouslan and Danyao) have done an abysmal job.  It takes a full-fledged team with quite different competencies to create/maintain the necessary demo/verification sites.

Since there is nothing to test of any significance without committing to major programming, the WG members and other interested parties have pretty much been left in the dark.

The W3C (including TAG and AC) have underestimated the difficulties with payments because you need to "sell" a solution not only to Merchants, but to Users and Banks as well.  It is still unclear what the "offer" is and "who uses this today?".

I would seriously consider another way of running the SPC effort where anybody could test the system-in-progress, and with a minimal investment in time.  The code for the entire setup should be public as well.


On 2021-01-28 18:49, Ian Jacobs wrote:
> Anders,
>> On Jan 28, 2021, at 11:44 AM, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>> Marcos,
>> AFAIK, a primary goal for the WG was to create a payment API that permitted writing payment applications in "pure" Web technology.
>> However, the companion API that enables this functionality (PaymentHandler), is currently only available in Chromium.
> Payment Handler API is a draft. We do not claim that is supported interoperably in multiple implementations. Of course we aspire to that.
>> What is worse is that the WG have not spent any cycles verifying that you actually can build payment applications that are competitive with the mobile native payment apps that currently "own" the market.
> I am aware of multiple experiments with Payment Handler API. It is not accurate to say that there are no efforts to see how
> to use the API in payments systems.
> Ian
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 718 260 9447
Received on Friday, 29 January 2021 05:47:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 29 January 2021 05:47:01 UTC