Paying in the browser: W3C presents first draft for Payment Request API 1.1

The Web Payments Working Group of the World Wide Web Consortium (W3C) continues its efforts to further simplify online payment via browser by standardizing the Payment Request API for both providers and buyers. The organization has now presented the first public draft for version 1.1 of the Payment Request API, which includes some improvements in the processing of optional data for payment requests.

Easier handling of data for payment processing

While the API makes it easier for sellers to implement different payment methods on their websites or web shops, user agents take on important tasks on the customer side when processing the payment flow – including handling the data required for the payment process. In the course of a browser dialog, the relevant information for the purchase or payment processing is queried and sent to the PaymentRequest– pass class. About essential information such as payment methods (paymentMethods) and payment details (paymentDetails) In addition, the Payment Request API also provides users with a number of other suggestions such as delivery options.

The handling of additional optional data that is stored in {{PaymentCompleteDetails}} compiled is now more clearly regulated in version 1.1 of the API specification. Such additional information can be used, for example, to complete a payment request from the merchant’s website to the payment processor with a complete()– Pass call.

Since the first W3C recommendations for standardizing the checkout process in e-commerce, the Payment Request API has established itself in almost all common browsers. It simplifies payment processing on the desktop, in Progressive Web Apps (PWAs) and on mobile systems – including via Google Pay or Apple Pay. More details on the changes in the new draft specification can be found in the W3C announcement as well as in the Payment Request API documentation.

(map)

To home page