Google tilføjer aktivt en e-handelssmag til sin Chrome - browser takket være magien bag Payment Request API . På det seneste har Chrome udvidet sine muligheder for at gøre din internetbrowsingoplevelse mere produktiv. Og hvilken bedre måde er der end at forenkle online købsoplevelser, der i sidste ende øger brugernes produktivitet?

Google Chrome omdefinerer onlinebetalingsoplevelsen

Google Chromes nye et-klik-udbetalingsoplevelse med et enkelt tryk^{(one-click, one-tap checkout experience)} er tilgængelig bag chrome://flags , der giver brugerne mulighed for at prøve eksperimentelle Web Payments API- funktioner. Et andet eksperimentelt Chrome - flag, der falder ind under den samme webbetalingskategori^{(Web Payments)} , gør det muligt for Payment Request API at åbne en minimal brugergrænseflade, når det er muligt.

Nu vil Chrome dramatisk forbedre og fremskynde din e-handelsoplevelse^{(speed up your e-commerce experience)} . Som et resultat heraf bringer Chrome en større revision af den måde, den gemmer betalingsrelaterede oplysninger på. På denne måde søger Chrome at forenkle processen med at placere e-handelsordrer på Mac , Windows , Linux , Chrome OS og Android .

Payment Request API har eksisteret i et stykke tid nu. Google siger dog, at dets fokus er flyttet fra at forsøge at finde ud af, hvordan Payment Request API kan være direkte værdifuldt for handlende til, hvordan API'erne^(APIs) kan muliggøre bedre betalingsappoplevelser på nettet.

“We’ve learned that building a compelling payment flow requires much more than just returning a credit card number. That’s why we are switching gears to focus on enabling payment apps through the Web Payments APIs,” said Eiji Kitamura, Developer Advocate at Google.

Chrome ønsker ikke kun at fungere som et mellemled mellem forhandlere, brugere og betalingsmetoder, men giver også brugere en formularfri betalingsoplevelse i applikationsgrænsefladen. Det muliggør hurtigere check-out og betalingsbehandling med minimal brug af mobilenhedens tastatur. Derfor^(Hence) kan udviklere forbedre brugerens betalingsoplevelse i betydeligt omfang.

På trods af, at 66 procent^{(66 percent)} af den kommercielle trafik stammer fra mobile enheder, siger Google , at mobilkonverteringer er omkring en tredjedel^(one-third) af desktopkonverteringerne. Google mener, at de lavere konverteringer på mobile enheder er resultatet af komplekse betalingsformularer.

Tidligere forenklede Google kasseprocessen med Autofill , som den siger resulterede i en forbedring på 25 procent i konverteringer på mobile enheder. ^{(25 percent)}Selvom Autofyld^(Autofill) måske slipper af med den manuelle karakter af dataindtastning, tror Google , at det stadig er baseret på det samme betalingsflow, noget Google aktivt forsøger at løse med Payment Request API .

Bygge bro over den oprindelige betalingsapp-kløft

Native apps tilbyder en friktionsfri online betalingsoplevelse i modsætning til webapps. Chrome -brugere skal ofte udfylde en lang formular og følge flere trin gennem pop op-vinduer og omdirigeringer for at gennemføre en betaling på nettet. Nu lover Payment Request og Payment Handler API'er^{(Payment Handler APIs)} tilsammen at bygge bro over den oprindelige betalingsappkløft^{( bridge the native payments app gap)} i Chrome.

“Payment Request API provides a standardized way to invoke a version-mediated, low-friction payment flow on the web similar to what users might already be familiar with in many native apps,” Kitamura continued. “Payment Handler API allows payment apps to plug into the primary guest API to enable form-free payments on the web.”

Tester Chromes hurtigere betaling

Websites kalder Payment Request API og tilbyder parametre for betalingen, herunder omkostninger og kompatible betalingsmuligheder. Chrome bestemmer derefter skæringspunktet mellem betalingsmetoder, der understøttes af webstedet, og betalingsmetoder, som brugeren har konfigureret i browseren. I sidste ende giver Chrome brugerne mulighed for at vælge deres foretrukne betalingsmetode.

Chrome -brugere kan indtaste en ny adresse til leveringen eller vælge den eksisterende. De kan vælge leveringsmetoden, hvor det er relevant. Betalingsmetoden kan være kreditkort eller en af ​​wallet-apps, der er installeret på deres enhed, såsom Google Pay . Til sidst trykker brugeren på 'Betal'. Chrome anmoder derefter om et svar fra den valgte betalingsmetode.

Betalingsbehandleren verificerer først anmodningen og returnerer derefter svaret direkte til serveren. På denne måde har hjemmesiden alle de nødvendige oplysninger til at behandle betalingen, hvilket yderligere eliminerer behovet for at forlade konteksten for betalingssiden.

I mellemtiden resulterer Payment Handler API i et helt nyt økosystem, der gør det muligt for en webbaseret betalingsapplikation at fungere som en betalingsmetode og integrere sig i forhandlerwebsteder, takket være standard Payment Request API .

Wallet - apps såsom Google Pay kan bygges oven på Web Payments API'erne^{(Web Payments APIs)} . Der er forskellige måder, hvorpå en eksisterende betalingsapp kan integreres med Payment Request API . Som Google forklarer, er en af ​​mulighederne at implementere Payment Handler API ved at tilføje en servicemedarbejder til deres eksisterende betalingsoplevelse.

Fremtiden for e-handel med Google Chrome

Funktionen 'Delegation' i Payment Handler API giver en betalingsapp mulighed for at give alle de oplysninger, som forhandleren anmoder om, såsom forsendelses- og kontaktoplysninger. Tidligere kom den samme information altid fra browseren.

Indtil videre ønsker Google, at betalingshandlere^{(Payment Handlers)} skal have tid nok til at tilpasse sig fremtiden for problemfri e-handel via webbrowsere. Hvad er en betalingsformidler^{(Payment Handler)} , spørger du måske? Nå^(Well) , en Payment Handler er en webapplikation, der håndterer en anmodning om betaling på vegne af brugeren.

Webapps^(Web) skal angive, om de håndterer leveringsadresse og kontaktoplysninger. De kan enten angive, om de understøtter hver af betalingsmulighederne separat, eller angive, om de understøtter alle betalingsmulighederne. Google siger, at en fuld delegation af leveringsadresse og betalers kontaktoplysninger til betalingshandlere^{(Payment Handlers)} er slutbilledet.

Ifølge et teknisk dokument set af TheWindowsClub , gør Google det ikke obligatorisk for betalingshandlere^{(Payment Handlers)} at håndtere forsendelses-/kontaktkrav når som helst snart.

Chrome kan med det samme hoppe til en betalingsbehandler. Hvis e-handelswebstedet angiver understøttelse af en enkelt betalingsmetode i Payment Request API , skal betalingsmetoden identificeres med en URL . I et andet scenarie skal brugeren have mindst én betalingshandler^{(Payment Handler)} installeret for den understøttede betalingsmetode.

Hvis brugeren ikke har nogen betalingsbehandler installeret for betalingsmetoden, skal betalingsbehandleren registreres gennem just-in-time registrering. Når disse betingelser er opfyldt, vil en brugerbevægelse og Chrome udløse betalingsanmodning^{(Payment Request)} , og browseren springer arket over.

“Together, delegation and skip-the-sheet enable payment apps to more easily transition their existing flows to the Payment Handler API.”

En fungerende prototype af funktionen er bag flaget "Experimental Web Platform features" på skrivebordet^(Desktop) . Google planlægger at implementere funktionen på alle platforme undtagen Android Webview, da den siger, at Payment handler API ikke er implementeret til Android Webview .

Kasse med et enkelt klik for at erstatte grundlæggende kort i Chrome

Chrome udfaser i sidste ende støtten til den grundlæggende^(basic-card) betalingsmetode med kort, har Google bekræftet. Google tilføjede oprindeligt Payment Request API til Chrome i form af basiskort som et alternativ til formularbaserede kreditkortbetalinger. Med basiskort kan kunderne vælge de kreditkort, der er gemt i browseren, for at foretage hurtigere betalinger. Google siger, at det fryser funktionsudvikling på Chromes^(Chrome) indbyggede grundlæggende kortsupport, undtagen fejlrettelser.

Ud over Chrome er Payment Request API også kompatibel med den nye Chromium-baserede Microsoft Edge^{(Chromium-based Microsoft Edge)} . I mellemtiden er funktionen i øjeblikket under udvikling i Firefox- og Safari - browsere.

Google Chrome ships online shopping feature to place orders with one tap

Google is actively adding an e-commerce flavor to its Chrome browser thanks to the magic behind the Payment Request API. Of late, Chrome is expanding its capabilities to make your internet browsing experience more productive. And what better way is there than simplifying online purchasing experiences that ultimately boost users’ productivity?

Google Chrome redefines online payments experience

Google Chrome’s new one-click, one-tap checkout experience is available behind chrome://flags that allows users to try experimental Web Payments API features. Another experimental Chrome flag falling under the same Web Payments category allows the Payment Request API to open a minimal UI when possible.

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

The Payment Request API is around for quite some time now. However, Google says its focus has moved from trying to figure out how Payment Request API can be directly valuable to merchants to how the APIs can enable better payment app experiences on the web.

“We’ve learned that building a compelling payment flow requires much more than just returning a credit card number. That’s why we are switching gears to focus on enabling payment apps through the Web Payments APIs,” said Eiji Kitamura, Developer Advocate at Google.

Chrome not only wants to act as an intermediary between merchants, users, and payment methods but also provides users with form-free payments experience within the application interface. It enables faster check out and payment processing with minimal use of the mobile device keyboard. Hence, developers can improve the user’s payment experience to a significant extent.

Despite 66 percent of commercial traffic originating from mobile devices, Google says mobile conversions are about one-third of the desktop conversions. Google believes the lower conversions on mobile devices are the result of complex checkout forms.

In the past, Google simplified the checkout process with Autofill, which it says resulted in a 25 percent improvement in conversions on mobile devices. Although Autofill might get rid of the manual nature of data entry, Google thinks it is still based on the same checkout flow, something Google is actively trying to address with the Payment Request API.

Bridging the native payments app gap

Native apps offer a friction-less online payment experience, unlike web apps. Chrome users often have to fill a lengthy form and follow multiple steps through pop-ups and redirects to complete a payment on the web. Now, Payment Request and Payment Handler APIs together promise to bridge the native payments app gap within Chrome.

“Payment Request API provides a standardized way to invoke a version-mediated, low-friction payment flow on the web similar to what users might already be familiar with in many native apps,” Kitamura continued. “Payment Handler API allows payment apps to plug into the primary guest API to enable form-free payments on the web.”

Putting Chrome’s faster checkout to test

Websites call the Payment Request API and offer parameters of the payment including cost and compatible payment options. Chrome then determines the intersection of payment methods supported by the site and payment methods that the user has configured within the browser. Ultimately, Chrome allows users to choose their preferred method of payment.

Chrome users can enter a new address for the delivery or choose the existing one. They can select the delivery method where applicable. The payment method can be credit cards or one of the wallet apps that are installed on their device such as Google Pay. Finally, the user taps on ‘Pay.’ Chrome then requests a response from the selected payment method.

The payment processor first verifies the request and then returns the response directly to the server. This way, the website has all of the necessary information to process the payment, further eliminating the need for leaving the context of the checkout page.

Meanwhile, the Payment Handler API results in a whole new ecosystem, allowing a web-based payment application to act as a payment method and integrate itself into merchant websites, courtesy of the standard Payment Request API.

Wallet apps such as Google Pay can be built on top of the Web Payments APIs. There are different ways an existing payment app can integrate with the Payment Request API. As Google explains, one of the options is to implement the Payment Handler API by adding a service worker to their existing payment experience.

The future of e-commerce with Google Chrome

‘Delegation’ feature in the Payment Handler API allows a payment app to provide all the information requested by the merchant such as shipping and contact information. Previously, the same information used to always come from the browser.

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

Web apps must specify whether or not they handle shipping address and contact info. They can either specify if they support each of the payment options separately or specify if they support all of the payment options. Google says a full delegation of providing shipping address and payer’s contact information to Payment Handlers is the end picture.

According to a technical document seen by TheWindowsClub, Google is not making it mandatory for Payment Handlers to handle shipping/contact requirements anytime soon.

Chrome can straightaway jump to a payment handler. If the e-commerce website indicates support for a single payment method in Payment Request API, then the payment method must be identified with a URL. In a different scenario, the user must have at least one Payment Handler installed for the supported payment method.

In case the user has no payment handler installed for the payment method, the payment handler should be registered through just-in-time registration. When these conditions are satisfied, a user gesture and Chrome will trigger Payment Request and the browser will skip the sheet.

“Together, delegation and skip-the-sheet enable payment apps to more easily transition 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 since it says Payment handler API is not implemented for Android Webview.

One-click checkout to replace basic cards within Chrome

Chrome is eventually deprecating the support for the basic-card payment method, Google has confirmed. Google initially 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 the credit cards stored in the browser to make faster payments. Google says it is freezing feature development on Chrome’s built-in basic card support, except 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 posts

• Google Chrome reagerer ikke. Vil du genstarte nu?

• Sådan rettes filoverførselsfejl i Google Chrome-browseren

• Sådan ændres standardudskriftsindstillingerne i Google Chrome

• Sådan ødelægger du profil på browserlukning i Google Chrome

• Anna Assistant er en perfekt stemmeassistent til Google Chrome

• Google Chrome fryser eller går ned på Windows 10-computer

• Tab Manager-udvidelser for at øge produktiviteten i Google Chrome

• ERR_NAME_NOT_RESOLVED, fejlkode 105 i Google Chrome

• Sådan aktiverer eller deaktiverer du rullebar fanestrip i Google Chrome

• Google Chrome rydder ikke browserhistorik og -data

• Google Chrome venter på cache - hvad gør jeg!?

• Google Chrome vs Firefox Quantum til Windows-pc

• Sådan aktiverer eller deaktiverer du fanerulningsknapper i Google Chrome

• Sådan aktiverer du den nye Material Design UI til Google Chrome browser

• Sådan deaktiveres eller aktiveres mørk tilstand i Google Chrome på Windows 10

• Ret ERR_QUIC_PROTOCOL_ERROR i Google Chrome

• Skype-udvidelsen til Google Chrome giver dig adgang til Skype til internettet og mere!

• The Great Suspender vil automatisk suspendere faner på Google Chrome

• Sådan installeres Google Chrome ved hjælp af Windows PowerShell

• Ret ERR_SSL_PROTOCOL_ERROR på Google Chrome