W3C home > Mailing lists > Public > public-payments-wg@w3.org > December 2019

Re: State of "payment-method-credit-transfer"

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 6 Dec 2019 09:32:03 +0100
To: Ian Jacobs <ij@w3.org>
Cc: Web Payments Working Group <public-payments-wg@w3.org>, VIGNET cyril <Cyril.VIGNET@bpce.fr>, KUNTZ Vincent <Vincent.KUNTZ@swift.com>, Matt Saxon <matt.saxon@gmail.com>, Rouslan Solomakhin <rouslan@google.com>
Message-ID: <82b5cda3-10da-c524-4457-ce52c3f92342@gmail.com>
On 2019-11-12 22:00, Ian Jacobs wrote:

> The Web Payments WG interest is in ensuring that the anticipated good UX of PR API can be used to support those flows.

If you look into the work performed by the Financial API WG (FAPI) which is underpinning (or inspired) most of the Open Banking APIs, you will note that it is 90% about security solutions.

There are no visible relations between http://w3c.github.io/payment-method-credit-transfer/ and FAPI.  Shouldn't this work item rather be rebooted or be converted into W3C note?

Regarding the UX, the current recommendation among the UK implementers is to use push notifications and embedded authentication through mobile banking apps:

IMO, the lack of a credible Desktop/Web + Mobile wallet/whatever solution remains a major hurdle for the adoption of PaymentRequest.  The Open Banking Wallet [*] use QR codes but this solution bypasses PaymentRequest.


*] https://cyberphone.github.io/openbankingwallet/

> Ian
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 718 260 9447
Received on Friday, 6 December 2019 08:32:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:34 UTC