- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Fri, 21 Aug 2020 08:06:01 +0200
- To: Web Payments Working Group <public-payments-wg@w3.org>
"in practice, this has moved our focus away from some other areas including moving along the rec track" To me the recent developments appears to pretty much invalidate the charter. In that case it might be useful taking a fresh look at the entire problem space. AFAICT, payment providers do not seem to be overly interested in putting money on Web-only solutions. Bank-centric Systems like "Swish", "MobilePay", "Vipps", "Twint", etc. have been very successful and do not have such limitations. That is, even if you apply state-of-the-art technology like WebAuthn/FIDO2, it probably still won't fly since the Web-only focus is too narrow. Regarding the open question "is there appetite for browsers to store payment credentials?" a problem is that there is no consensus what exactly a payment credentials is. Presumably it must match the needs of the backend/protocol as well making this a really big issue. Although https://cyberphone.github.io/doc/web/calling-apps-from-the-web.pdf surely is not "perfect", it should address just about every imaginable Web use-case without locking the payment industry into specific browser solutions that also are very difficult to upgrade. Anders On 2020-08-20 17:03, Ian Jacobs wrote: > Dear WPWG, > > Minutes from today’s discussion: > https://www.w3.org/2020/08/20-wpwg-minutes > > Next call: 3 September > https://github.com/w3c/webpayments/wiki/Agenda-20200903 > > Thank you, > > Ian > -- > Ian Jacobs <ij@w3.org> > https://www.w3.org/People/Jacobs/ > Tel: +1 718 260 9447 > > > > >
Received on Friday, 21 August 2020 06:06:18 UTC