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

[Blog post] The Next Innovation in Payment Handler Distribution

From: Ian Jacobs <ij@w3.org>
Date: Thu, 16 May 2019 11:38:11 -0500
Message-Id: <E5100E9F-B389-4CA8-AD92-B0A7F44665BE@w3.org>
To: Web Payments Working Group <public-payments-wg@w3.org>
Dear Web Payments WG,

Our discussions about an SRC payment method have included the topic of bootstrapping the payment handler ecosystem. We expressed this as a goal for the SRC payment method [1]:

    "At transaction time, if the merchant accepts the SRC payment method and the browser supports it (at least) through Payment Request and payment handlers, the user will be able to pay with an issued card. The user would either select a card previously enrolled in the SRC system or have the option to enroll one.”

In other words, there should always be an SRC payment handler available. In still other words, “canMakePayment()” should always return ‘true’. 

Of course, this would be desirable for many payment methods, which has led me to write this up:

   The Next Innovation in Payment Handler Distribution
   https://www.w3.org/blog/wpwg/2019/05/16/the-next-innovation-in-payment-handler-distribution/

This blog post describes three types of payment handler distribution: manual, just-in-time, and the new idea of “default payment handlers.” 

Thanks to Adrian Hope-Bailie, Rouslan Solomakhin, Nick Telford-Reed, Justin Toupin, and Danyao Wang
for discussion about this topic!

We don’t yet know whether any new specifications are required to support this idea; we will continue the
discussion in the context of the Payment Handler API.

Comments welcome,

Ian


[1] https://github.com/w3c/src/wiki#goals
--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447
Received on Thursday, 16 May 2019 16:38:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 16 May 2019 16:38:15 UTC