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

The WebPayment API vs Personal Payment Terminal

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Sun, 22 May 2016 06:35:14 +0200
To: Web Payments Working Group <public-payments-wg@w3.org>, Web Payments IG <public-webpayments-ig@w3.org>
Message-ID: <dc2d55d5-b99d-8e9d-9251-0f1424f73480@gmail.com>
Dear list,

The following should NOT be regarded as criticism, but as information about existing products and stuff in development that doesn't really fit into the current WebPayment API and vision.

If you take a peek in this paper of mine
http://webpki.org/papers/payments/goodbye-mobile-wallet-hello-personal-payment-terminal.pdf
you will realize that the idea that the browser "owns" the payment UI may not turn on the entire industry, particularly not the payment providers (banks).

That you haven't heard anything like that from W3C members is probably because you essentially must be a Web programmer in order to "decipher" the current Web Payment specs.

Personally, I don't see competition as a problem, but as an opportunity.

However, there IS a problem with this alternative path to payments and that is that the link from the Web to Personal Payment Terminals is more or less undefined.  Here I believe the W3C could do a major service by generalizing this part rather than (as now), binding it to a single application and API.  The security issues that have been mentioned from time to time have apparently been solved.  What's missing is simply a description of how.

Sincerely,
Anders Rundgren
WebPKI.org
Received on Sunday, 22 May 2016 04:35:52 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 22 May 2016 04:35:53 UTC