What's New in Payments

Google to sunset Payment Request API

Rethinking Payment Request for iOS Chrome — Google — “The best way to enable more seamless and secure payments on the web is to enable an interoperable ecosystem, where digital wallets can bring their best experience to the web. This means shifting focus to the Payment Handler API, which is an emerging W3C standard that allows third party payment handlers, which can be either native mobile apps or progressive web apps, to integrate with the browser to handle Payment Requests… This shift in focus means that we will eventually sunset Chrome’s built-in ‘basic-card’ payment handler.”


What's New in Payments

EMVCo, W3C and Fido Alliance to work together on payments security and interoperability

Web Payment Security Interest Group Charter — World Wide Web Consortium — “The mission of the Web Payment Security Interest Group is to enhance the security and interoperability of web payments. The group pursues its mission by creating a forum for organizations to define areas of collaboration and identify gaps between existing technical specifications in order to increase compatibility among different technologies.”


W3C adopts password-free login standard

W3C approves WebAuthn as the web standard for password-free logins — VentureBeat — “The specification lets users log into online accounts using biometrics, mobile devices, and/or Fido security keys. WebAuthn is supported by Android and Windows 10. On the browser side, Google Chrome, Mozilla Firefox, and Microsoft Edge all added support last year. Apple has supported WebAuthn in preview versions of Safari since December.”


What's New in Payments

W3C: All major browser makers ‘now implementing Payment Request API’

Standards for streamlined checkout gain traction — World Wide Web Consortium — “With these technologies, users no longer complete web forms to provide payment credentials, shipping information, and contact information. Instead, the user registers support for different payment methods — such as card payments, proprietary native mobile payments, bitcoin or other distributed ledgers, or credit transfers — with the browser or other user agent.”