Google actively adds an e-commerce flavor to its Chromium browser thanks to the magic behind the Payment Request API. Lately, Chrome is expanding its capabilities to make your internet browsing experience more productive. And what better way is there than to simplify online shopping experiences that ultimately increase user productivity?

Google Chrome redefines the online payment experience

The new of Google Chrome One-click, one-click checkout experience is available behind chrome://flags which allows users to try experimental features of the Web Payments API. Another experimental Chrome flag under the same Web Payments category allows the payment request API to open a minimal UI when possible.

Now Chrome wants to drastically improve and speed up your e-commerce experience. As a result, Chrome is bringing a major overhaul to how it stores payment information. In this way, Chrome seeks to simplify the process of placing e-commerce orders on Mac, Windows, Linux, Chrome OS, and Android.

the Payment Request API has been there for a while now. However, Google says its focus has shifted from trying to understand how the payment request API can be directly valuable to merchants to how APIs can enable better payment application experiences on the web.

“We’ve learned that creating an engaging checkout flow takes more than just returning a credit card number. That’s why we’re shifting gears to focus on enabling payment apps through the Web Payments APIs,” said Eiji Kitamura, Developer Advocate at Google.

Check your payment

Chrome not only wants to act as an intermediary between merchants, users, and payment methods, but also provides users with a formless payment experience in the app interface. It enables faster checkout and payment processing with minimal use of the mobile device keyboard. Therefore, developers can significantly improve the user’s payment experience.

Despite 66 percent of commercial traffic from mobile devices, according to Google, mobile conversions are approximately a third office conversions. Google thinks the drop in conversions on mobile devices is the result of complex checkout forms.

In the past, Google simplified the checkout process with autofill, which it said resulted in a 25 percent improved conversions on mobile devices. While autofill may remove the manual nature of data entry, Google believes it’s still based on the same checkout flow, which Google is actively trying to address with the Payment Request API.

Bridging the Native Payment App Gap

Native apps provide a frictionless online payment experience unlike web apps. Chrome users often have to fill out a long form and go through several steps via pop-ups and redirects to make a payment on the web. Now the payment request and payment handler APIs together promise to bridging the native payment app gap in Chrome.

“The Payment Request API provides a standardized way to invoke a low-friction, version-based payment flow on the web, similar to what users are already familiar with in many native apps,” Kitamura continued. “The Payment Manager API allows payment applications to connect to the main guest API to enable formless payments on the web. »

Test Chrome’s faster checkout

Websites call payment request API and offer payment parameters including cost and compatible payment options. Chrome then determines the intersection of the payment methods supported by the site and the payment methods the user has configured in the browser. Ultimately, Chrome lets users choose their preferred payment method.

Chrome users can enter a new address for delivery or choose the existing one. They can select the delivery method if applicable. The payment method can be a credit card or one of the wallet apps installed on their device, such as Google Pay. Finally, the user presses “Pay”. Chrome then requests a response from the selected payment method.

Add a card payment request API

The payment processor first verifies the request and then sends the response back directly to the server. This way, the website has all the information needed to process the payment, eliminating the need to leave the context of the payment page.

Meanwhile, the Payment Handler API creates a whole new ecosystem, enabling a web-based payment application to act as a means of payment and integrate with merchant websites, thanks to the standard API of payment request.

Wallet applications such as Google Pay can be built on the Web Payments APIs. An existing payment application can integrate with the payment request API in different ways. As Google explains, one option is to implement the Payment Manager API by adding a service worker to their existing checkout experience.

The future of e-commerce with Google Chrome

‘Delegation’ function in the Payment Manager API allows a payment application to provide all information requested by the merchant such as shipping and contact information. Previously, the same information always came from the browser.

For now, Google wants Payment handlers have enough time to adapt to the future of hassle-free e-commerce via web browsers. What is a payment manager, you might ask? Well, a payment handler is a web application that handles a payment request on behalf of the user.

Web applications should specify whether or not they handle shipping address and contact information. They can either specify whether they support each of the payment options separately, or specify whether they support all payment options. Google says full delegation of delivery address and payer contact information to payment handlers is the final picture.

Web payment indicators

According to a technical document seen by TheClubWindowsGoogle isn’t forcing payment processors to handle shipping/contact requirements anytime soon.

Chrome can immediately switch to a payment handler. If the e-commerce website indicates support for only one payment method in the payment request API, the payment method must be identified by a URL. In a different scenario, the user must have at least one payment handler installed for the supported payment method.

If the user does not have a payment handler installed for the payment method, the payment handler must be registered via just-in-time registration. When these conditions are met, a user gesture and Chrome will trigger a payment request and the browser will skip the sheet.

“Together, delegation and sheet skipping make it easier for payment applications to transfer their existing flows to the payment handler API. »

A working prototype of the feature is behind the “Experimental Web Platform Features” flag on Desktop. Google plans to implement the feature on all platforms except Android Webview, as it says the payment handler API is not implemented for Android Webview.

One-click payment to replace base cards in Chrome

Payment Request API Web Browsers

Chrome ends up deprecating support for the basic map payment method, Google has confirmed. Google originally added the Payment Request API to Chrome in the form of basic cards as an alternative to form-based credit card payments. With Basic Cards, customers can select credit cards stored in the browser to make faster payments. Google says it’s freezing feature development on Chrome’s built-in basemap support, except for bug fixes.

In addition to Chrome, the payment request API is also compatible with the new Chromium-based Microsoft Edge. Meanwhile, the feature is currently in development in Firefox and Safari browsers.

Related : How to legally get Microsoft Office Pro Plus 2016 for less than $10

Previous articleHow to set JAVA_HOME in Windows 11/10
Next articleFixed blurry file open dialog in Google Chrome and Microsoft Edge


Please enter your comment!
Please enter your name here