- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sat, 25 Apr 2020 07:07:01 +0200
- To: Web Payments Working Group <public-payments-wg@w3.org>
Assume that a bank wants to use W3C's PaymentHandler. They have two options: - Creating a unique payment method - Sharing a payment method with other banks Creating a unique payment method may be logical at first sight but makes it difficult for Merchants who need to deal with potentially thousands of different methods. So the only realistic solution is that banks standardize on a few common payment methods and associated PaymentHandler applications. What is not equally evident is the consequence of that, but as far as I can tell, a user with multiple banks would be forced to select PaymentHandler application from a browser generated list. In addition, there are no guarantees that PaymentHandler applications having a common method name, actually run the same code. The lack of signed/vetted code also adds user-related and infrastructural downsides, as well as constraining features. Native payment handlers like Apple Pay and Saturn do not suffer from any of these shortcomings. thanx, Anders
Received on Saturday, 25 April 2020 05:07:19 UTC