The W3C Web Payments Working Group has published the first public drafts of payment specifications which include a Payment Request API, payment method identifiers, and basic card payment. The basic idea behind the specifications is to make payments easier and more secure for end users. The W3C Web Payments Working Group was formed in October of last year and a number of major technology companies are contributing to the group including Apple, Facebook, Google, IBM, and Microsoft. These first public drafts have been released early and are incomplete. The group expects the payments specifications will be finalized and published as W3C recommendations sometime in 2017.
These early drafts of payment specifications include a Payment Request API, payment method identifiers, and basic card payment:
- Payment Request API - The Payment Request API specification describes a Web API that allows merchants to accept multiple payment methods without requiring extensive integration with payment platforms. Web browsers will enable the payment process between the merchant and the end user.
- Payment Method Identifiers – The payment method identifiers specification includes definitions for “payment method identifier strings” that are used to determine which payment methods are supported.
- Basic Card Payment – The basic card payment specification describes the data formats used by the Payment Request API. It provides support for payments made by credit or debit cards.
The Payment Request API specification will support a number of different payment methods. The W3C Web Payments Working Group flows task force is working on analyzing different payment flows including (but not limited to) Bitcoin Basic, PayPal Standard, Apple Pay Native, and Masterpass.
The W3C Web Payments Working Group is currently focused on the Payment Request API specification. However, the group plans on working on a specification for enabling payments via HTTP API in addition to a Web browser in the near future.
To view the complete W3C public drafts of payment specifications, visit the W3C website.