Google wuxuu si firfircoon ugu darayaa dhadhanka e-ganacsiga biraawsarkiisa Chrome iyadoo ay ugu wacan tahay sixirka ka dambeeya Codsiga Lacag-bixinta API^{(Payment Request API)} . Waagii danbe, Chrome waxa uu balaadhinayaa awoodiisa si uu khibradaada baadhista intarneedka uga dhigo mid midho dhal leh. Maxaase ka fiican in la fududeeyo waayo-aragnimada wax iibsiga ee internetka ee ugu dambeyntii kor u qaadaysa wax soo saarka isticmaalayaasha?

Google Chrome wuxuu^{(Google Chrome)} dib u qeexayaa khibrada lacag bixinta ee khadka tooska ah

Google Chrome-ka cusub ee hal-guji, hal-taabo ee hubinta khibrada^{(one-click, one-tap checkout experience)} ayaa laga heli karaa gadaasha chrome://flags u oggolaanaya isticmaaleyaasha inay tijaabiyaan tijaabada Bixinta Shabakadda API^{(Web Payments API)} . Calan kale oo tijaabo Chrome ah oo hoos imanaya isla qaybta Lacag-bixinta Shabakadda^{(Web Payments)} ayaa u oggolaanaysa Codsiga Lacag-bixinta API^{(Payment Request API)} inuu furo UI ugu yar marka ay suurtogal tahay.

Hadda, Chrome wuxuu doonayaa inuu si weyn u horumariyo oo uu u dedejiyo khibradaada e-commerce^{(speed up your e-commerce experience)} . Natiijo ahaan, Chrome wuxuu dib u habeyn weyn ku keenayaa habka uu u keydiyo macluumaadka lacag-bixinta la xiriira. Sidan, Chrome wuxuu eegayaa inuu fududeeyo habka loo soo dejiyo amarada ganacsiga e-commerce ee Mac , Windows , Linux , Chrome OS , iyo Android .

Codsiga Lacag-bixinta API^{(Payment Request API)} wuxuu ku dhow yahay in muddo ah hadda. Si kastaba ha ahaatee, Google ayaa sheegaysa in diirada ay ka guurtay isku dayga in ay ogaato sida Codsiga Lacag-bixinta API^{(Request API)} ay si toos ah qiimo ugu yeelan karto baayacmushtarka sida API-yadu^(APIs) ay awood ugu siin karaan khibradaha app lacag-bixinta ee shabakada.

“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 kaliya ma rabo inuu u dhaqmo sidii dhex dhexaadiye u dhexeeya ganacsatada, isticmaalayaasha, iyo hababka lacag bixinta laakiin sidoo kale waxay siisaa isticmaalayaasha khibrad lacag-bixin la'aan ah gudaha interface-ka codsiga. Waxay awood u siinaysaa hubinta degdega ah iyo habaynta lacag bixinta iyadoo la isticmaalayo ugu yar ee kiiboodhka qalabka moobaylka. Sidaa darteed^(Hence) , horumariyayaashu waxay wanaajin karaan khibradda lacag-bixinta isticmaalaha ilaa xad la taaban karo.

In kasta oo 66 boqolkiiba^{(66 percent)} taraafikada ganacsiga ee ka yimid aaladaha mobilada, Google wuxuu leeyahay beddelka mobilada waa qiyaastii seddex meelood meel^(one-third) beddelka desktop-ka. Google wuxuu aaminsan yahay beddelka hoose ee aaladaha mobilada inay tahay natiijada foomamka hubinta adag.

Waagii hore, Google wuxuu fududeeyay habka hubinta ee Autofill , taas oo ay sheegtay in ay keentay 25 boqolkiiba^{(25 percent)} hagaajinta beddelka qalabka mobile. Inkasta oo Autofill laga yaabo inay ka takhalusto dabeecadda gacanta ee gelitaanka xogta, Google waxay u maleyneysaa inay weli ku saleysan tahay isla socodka hubinta, wax Google ah ayaa si firfircoon isku dayaya inuu wax ka qabto Codsiga Lacag-bixinta API^{(Payment Request API)} .

Isku-dubbaridka farqiga u dhexeeya lacag-bixinta asalka ah

Barnaamijyada waddaniga ahi waxay bixiyaan waayo-aragnimo lacag-bixineed-yar oo khadka ah, oo ka duwan abka shabakadda. Isticmaalayaasha Chrome^(Chrome) inta badan waa in ay buuxiyaan foom dheer oo ay raacaan tillaabooyin badan iyaga oo soo bandhigaya iyo dib u jiheynta si ay u dhammaystiraan lacag bixinta shabakadda. Hadda, Codsiga^{(Payment Request)} Lacag-bixinta iyo Gacan-hayaha Lacag-bixinta APIs^{(Payment Handler APIs)} waxay si wada-jir ah u ballan-qaadayaan inay xakameeyaan farqiga u dhexeeya abka lacag-bixinta ee^{( bridge the native payments app gap)} gudaha 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.”

Dhigista hubinta degdega ah ee Chrome si loo tijaabiyo

Websaydhyadu waxay wacayaan Codsiga Lacag-bixinta API^{(Payment Request API)} waxayna bixiyaan cabbirrada lacag-bixinta oo ay ku jiraan qiimaha iyo ikhtiyaarrada lacag-bixinta ee habboon. Chrome ayaa markaa go'aaminaya is-goysyada hababka lacag-bixinta ee ay taageerto goobta iyo hababka lacag-bixinta ee isticmaaluhu uu ku habeeyey browserka dhexdiisa. Ugu dambeyntii, Chrome wuxuu u oggolaanayaa isticmaaleyaasha inay doortaan habka lacag-bixinta ee ay doorbidayaan.

Isticmaalayaasha Chrome^(Chrome) waxay geli karaan ciwaan cusub oo loogu talagalay gudbinta ama waxay dooran karaan ka jira. Waxay dooran karaan habka gaarsiinta marka ay khuseyso. Habka lacag-bixintu wuxuu noqon karaa kaararka deynta ama mid ka mid ah apps boorsada lagu rakibay qalabkooda sida Google Pay . Ugu dambeyntii, isticmaaluhu wuxuu ku dhufanayaa 'Bix.' Chrome ayaa markaa ka codsada jawaabta habka lacag bixinta ee la doortay.

Processor-ka lacag-bixinta ayaa marka hore xaqiijiya codsiga ka dibna si toos ah ugu soo celi jawaabta server-ka. Sidan, shabakadu waxay haysataa dhammaan macluumaadka lagama maarmaanka ah si loo habeeyo lacag bixinta, taasoo sii fogaynaysa baahida loo qabo ka tagista macnaha guud ee bogga hubinta.

Dhanka kale, Handler Payment API^{(Payment Handler API)} waxa uu keenayaa nidaam deegaan cusub oo dhan, taas oo u oggolaanaysa codsiga lacag-bixinta ku salaysan shabakadda in uu u dhaqmo sidii hab lacag-bixineed oo uu isu dhexgeliyo mareegaha ganacsatada, ixtiraamka heerka Codsiga Lacag-bixinta API^{(Payment Request API)} .

Apps-ka jeebka^(Wallet) sida Google Pay waxa lagu dul dhisi karaa API-yada Lacag-bixinta Shabakadda^{(Web Payments APIs)} . Waxaa jira siyaabo kala duwan abka lacag-bixinta ee jira uu ula midoobi karo Codsiga Lacag-bixinta API^{(Payment Request API)} . Sida Google u sharaxo, mid ka mid ah xulashooyinka ayaa ah in la hirgeliyo Handler Payment API^{(Payment Handler API)} adoo ku daraya shaqaale adeeg khibradooda lacag-bixineed ee jira.

Mustaqbalka ganacsiga e-commerce ee Google Chrome

Qaabka 'Weftida' ee ku jira Handler Payment API^{(Payment Handler API)} wuxuu u ogolaanayaa abka lacag-bixinta inuu bixiyo dhammaan macluumaadka uu codsado ganacsadaha sida rarida iyo macluumaadka xiriirka. Markii hore, xogta la mid ah ayaa had iyo jeer ka iman jirtay browserka.

Hadda, Google wuxuu rabaa Handlers Payment^{(Payment Handlers)} si ay u helaan wakhti ku filan si ay ula qabsadaan mustaqbalka ganacsiga e-commerce ee bilaa dhibka ah ee daalacashada webka. Waa maxay Gacan-haye Lacag-bixineed^{(Payment Handler)} , ma waydiin kartaa? Hagaag^(Well) , Gacan-hayaha Lacag-bixinta^{(Payment Handler)} waa arji shabakadeed oo wax ka qabta codsiga lacag-bixinta isagoo ka wakiil ah isticmaalaha.

Barnaamijyada shabakadu^(Web) waa inay caddeeyaan inay maamulayaan cinwaanka rarida iyo macluumaadka xidhiidhka. Waxay qeexi karaan haddii ay si gaar ah u taageeraan mid kasta oo ka mid ah xulashooyinka lacag-bixinta ama waxay qeexi karaan haddii ay taageeraan dhammaan xulashooyinka lacag-bixinta. Google waxa ay sheegtay in wafti buuxa oo bixinaya ciwaanka rarida iyo xogta xidhiidhka bixiyaha ay tahay^{(Payment Handlers)} sawirka dhamaadka.

Marka loo eego dukumeenti farsamo oo uu arkay TheWindowsClub , Google kama dhigayso wax qasab ah Handlers lacag bixinta^{(Payment Handlers)} si ay u qabtaan shuruudaha rarida/xidhiidhka wakhti kasta dhawaan.

Chrome wuxuu isla markiiba u boodi karaa maamulaha lacag bixinta. Haddii shabakada e-commerce ay muujiso taageerada hal hab oo lacag bixin ah oo ku jirta Codsiga Lacag bixinta API^{(Payment Request API)} , markaa habka lacag bixinta waa in lagu gartaa URL . Xaalad kale, adeegsaduhu waa inuu haystaa ugu yaraan hal Khabiir Lacag-bixineed^{(Payment Handler)} oo lagu rakibay habka lacag bixinta ee la taageeray.

Haddii isticmaaluhu aanu haysan maamule lacag-bixineed oo lagu rakibay habka lacag-bixinta, maamulaha lacag-bixinta waa in lagu diwaan-geliyo is-diiwaangelin-waqti-yar. Marka shuruudahan la qanciyo, tilmaanta isticmaale iyo Chrome ayaa kicin doona Codsiga Lacag bixinta^{(Payment Request)} oo browserku wuxuu ka boodi doonaa xaashida.

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

Nooca shaqada ee sifada ayaa ka dambeysa calanka "Tijaabada Astaamaha Mareegaha Shabkada" ee ku yaal Desktop . Google ayaa qorshaynaysa in ay fuliso sifada dhamaan aaladaha marka laga reebo Android Webview maadaama ay sheegtay in maamulaha lacag bixinta ^(Payment)API aan loo fulin Android^{(Android Webview)} Webview .

Hal-guji hubinta si aad u bedesho kaadhadhka aasaasiga ah gudaha Chrome

Chrome wuxuu ugu dambeyntii meesha ka saarayaa taageerada habka bixinta kaadhka aasaasiga ah, ^(basic-card)Google ayaa xaqiijiyay. Google ayaa markii hore ku dartay Codsiga Lacag- bixinta API ^{(Payment Request API)}Chrome qaab kaadhadhka aasaasiga ah si ay beddel ugu noqoto bixinta kaararka deynta ee foomka ku salaysan. Kaararka aasaasiga ah, macaamiishu waxay dooran karaan kaararka deynta ee ku kaydsan browserka si ay lacag-bixin degdeg ah u sameeyaan. Google waxa uu sheegay in uu qaboojinayo horumarinta sifada Chrome^(Chrome) ee ku dhex dhisan taageerada kaadhka aasaasiga ah, marka laga reebo hagaajinta cayayaanka.

Marka lagu daro Chrome , Codsiga Lacag-bixinta API^{(Payment Request API)} sidoo kale wuxuu la jaan qaadayaa Chromium-ka cusub ee Microsoft Edge^{(Chromium-based Microsoft Edge)} . Dhanka kale, muuqaalku wuxuu hadda ku socdaa horumarinta Firefox iyo browsers Safari .

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 ka jawaabi maayo, hadda dib ma loo bilaabay?

• Sida loo hagaajiyo Khaladaadka Soo Dejinta Faylka ee browserka Google Chrome

• Sida loo beddelo Default Print Settings gudaha Google Chrome

• Sida loo burburiyo Profile-ka Browser-ka ee ku xidhan Google Chrome

• Anna Assistant waa kaaliyaha codka ugu fiican Google Chrome

• Sida loo awood UI Naqshad Shayga cusub ee browserka Google Chrome

• Sida si toos ah loogu shido Hubiyaha Higaada gudaha Google Chrome

• Google Chrome si loo xaddido isdiiwaangelinta riixitaanka ilaa 90 maalmood

• Sida loo beddelo cabbirka farta caadiga ah ee browserka Google Chrome

• Sida loo sahlo ama loo joojiyo Buttons-wareejinta ee Google Chrome

• Sida looga saaro badhanka xakamaynta warbaahinta caalamiga ah ee Google Chrome ka

• Sida loo hagaajiyo Aw, Snap! fariinta qaladka ee browserka Google Chrome

• Suspender Great wuxuu si toos ah u joojin doonaa tabs Google Chrome

• Xawaaraha Fiidiyowga ee Mozilla Firefox iyo Google Chrome

• Kordhinta Google Chrome oo aan shaqaynayn Windows 11/10

• Sida looga ilaaliyo isticmaalayaasha inay ku rakibaan Extensions Google Chrome

• Sida loo damiyo ama loo sahlo qaabka mugdiga ah ee Google Chrome gudaha Windows 10

• Google Chrome wuxuu sugayaa kaydinta - maxaan sameeyaa!?

• Google Chrome vs Firefox Quantum ee Windows PC

• Hagaaji File Blurry Sanduuqa wada hadalka ku fur Google Chrome iyo Microsoft Edge