Web Payments is an emerging web standard being developed by the W3C to simplify online payments and enable a broader set of players to participate easily in the payments ecosystem on the web. The standards are flexible; they work with various types of payment systems and are intended to work on any browser on any device, payment method, or payment service provider. This flexibility enables development simplicity, deployment consistency, and future compatibility with emerging payment technologies.
Benefits of Web Payments:
For consumers, they simplify checkout flow, by making it a few taps instead of typing small characters many times on a virtual keyboard.
For merchants, they make it easier to implement with a variety of payment options already filtered for the customer.
For payment handlers, they allow bringing any type of payment methods to the web with relatively easy integration.
For payment service providers, they bring new payment methods and enhance the ability of businesses to serve more customers with a better developer experience and more secure solutions.
Standard and OpenWeb Payments are an open payment standard for the web platform for the first time in history. They are available for any players to implement.
Easy and ConsistentWeb Payments make checkout easy for the user, by reusing stored payments and address information and removing the need for the user to fill in checkout forms. Since the UI is implemented by the browser natively, users see a familiar and consistent checkout experience on any website that makes use of the standard.
Secure and FlexibleWeb Payments provide industry-leading payment technology to the web, and can easily integrate a secure payment solution.
This document aims at developers who are working for payment industries, especially at merchants, payment service providers and payment handlers.
All developers should start with reading through the "Basics" section.
Merchants without PCI-DSS compliance should then consult with their payment service provider to see if they have support for the Payment Request API. If they don't, consider forwarding this document and ask them to support the W3C Payment APIs. UX considerations of the "Merchant Guide" should be also helpful.
Merchants or payment service providers with PCI-DSS compliance should proceed to the "Merchants Guide" and learn the Payment Request API in details.
Payment handlers should proceed to the "Payment Apps Developer Guide" section. Depending on your technology set, consider implementing either the Android payment app or the web-based payment app by reading through the respective section.