- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sat, 11 Jan 2020 08:37:36 +0100
- To: "www-tag@w3.org" <www-tag@w3.org>
The PaymentRequest API has been in the workings for 5 years but has not yet reached REC state.
There never was a need for a specific payment API on the Web, you rather need new Web primitives [*]. Now this topic has come back, but this time from the WG itself: https://github.com/adrianhopebailie/modal-window/blob/master/explainer.md
"However, the presented UI component could be useful for other use cases
(e.g. authentication, sharing, access to third-party services) and an innovative use
of the payment APIs (creation of a fake payment context) to demonstrate this is
shown in this demo"
Unfortunately the pretty severe architectural issues doesn't end there.
Recently it was found out that one of the most touted features (enumerating matching payments methods in the browser chrome), has become a hurdle and should be skipped [*].
Regarding the latest mission by the Payment WG, you may take a peek at: https://lists.w3.org/Archives/Public/public-payments-wg/2020Jan/0009.html
Another troubled area is the Web(only) based https://www.w3.org/TR/payment-handler/ Why is that? The payment industry appears to have to 99% based their developments on native mobile apps. I have written a short paper why this is likely to remain a fact: https://github.com/cyberphone/doc/blob/gh-pages/payments/paymenthandler.md#the-w3c-paymenthandler
Thanx,
Anders
*] Claimed by yours truly from the very beginning
Received on Saturday, 11 January 2020 07:37:42 UTC