# US 12,002,044 B2 · Browser extension with additional capabilities > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,002,044 B2 - Document ID: US12002044B2 - Status: Granted - Kind: B2 - Application number: 17/321,034 - Filed: 2021-05-14 - Published: 2021-09-02 - Granted: 2024-06-04 - Earliest claimed: 2015-11-11 - Assignees: Visa International Service Association - Applicants: Visa International Service Association - Inventors: Yobel Muchang; Svetlana Trushchenkova; Mayank Somaiya; Michael Jabbara; David Badley - Web page: https://patentgrep.com/patent/US12002044B2 ## CPC - G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists - G06F 3/0481: based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance - G06F 40/174: Form filling; Merging - G06Q 20/4014: {Identity check for transactions} - G06Q 20/40145: {Biometric identity checks} - G07G 1/0009: {Details of the software in the checkout register, electronic cash register [ECR] or point of sale terminal [POS]} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G07G: REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract An expedited payment service may be accessed through a browser extension. As an extension operates in a manner in which it has access to the underlying merchant data, the extension may allow an expedited payment service to work with virtually any merchant web site to complete payment transactions. ## Claims ### Claim 1 A processor-implemented method of enabling an expedited payment extension in a web browser to execute a purchase transaction on a user account with a merchant website, the method comprising: receiving, at a processor, an execute action to an extension area of the web browser to start the expedited payment extension; based on receiving the execute action, executing, through the processor, the expedited payment extension in the web browser, wherein the processor executes both the web browser and the expedited payment extension; based on executing the expedited payment extension, accessing, through the processor, authentication data by the expedited payment extension from the web browser, wherein the authentication data accessed by the expedited payment extension comprises merchant data corresponding to the merchant website; based on accessing the authentication data, communicating, through the processor, the authentication data comprising the merchant data to an authentication authority over a network; based on communicating the authentication data to the authentication authority, receiving, at the processor, an authentication approval from the authentication authority over the network; based on receiving the authentication approval, receiving, at the processor, payment data comprising a payment token in the web browser from the authentication authority, wherein the payment token is a one-time use code that is unique to the merchant website; based on receiving the payment data comprising the payment token, auto-filling, by the processor, the payment data comprising the payment token into at least one field of the web browser; and executing, at the processor, the transaction in the web browser executing the expedited payment extension, the transaction being executed in response to the authentication approval and based on auto-filling the payment data comprising the payment token. ### Claim 2 (depends on 1) The method of claim 1, wherein the execute action includes a mouse click and the extension area includes a visual indication in a browser action bar that the expedited payment extension is available. ### Claim 3 (depends on 1) The method of claim 1, wherein the authentication data further includes a password for a sign in name that is stored locally as a browser cookie. ### Claim 4 (depends on 1) The method of claim 1, wherein the network includes a dedicated network that receives the payment data and communicates the payment data to entities of the transaction. ### Claim 5 (depends on 1) The method of claim 1, further comprising receiving a selection at the processor of one payment device from a plurality of payment devices and the authentication data includes an amount available to spend on the selected payment device. ### Claim 6 (depends on 1) The method of claim 1, wherein the authentication data is further used to improve one or more fraud algorithms at the network. ### Claim 7 (depends on 1) The method of claim 1, wherein the extension area comprises at least one of a sidebar, a button, and a graphical user interface. ### Claim 8 (depends on 1) The method of claim 1, further comprising auto-filling one or more of a name, a billing address, and a shipping address in the extension area based on the payment data. ### Claim 9 (depends on 1) The method of claim 1, wherein executing, at the processor, the transaction in the web browser executing the expedited payment extension includes sending the payment data to the network and analyzing the payment data for one or more of verification, sufficient funds/amounts, and fraud. ### Claim 10 A networked system comprising a processor, a memory and an input-output circuit for enabling an expedited payment extension in a web browser, the processor being physically configured according to computer executable instructions for: receiving, at the processor, an execute action to an extension area of the web browser to start the expedited payment extension; based on receiving the execute action, executing, through the processor, the expedited payment extension in the web browser, wherein the processor executes both the web browser and the expedited payment extension; based on executing the expedited payment extension, accessing, through the processor, authentication data by the expedited payment extension from the web browser, wherein the authentication data accessed by the expedited payment extension comprises merchant data corresponding to a merchant website; based on accessing the authentication data, communicating, through the processor, the authentication data comprising the merchant data to an authentication authority over a network; based on communicating the authentication data to the authentication authority, receiving, at the processor, an authentication approval from the authentication authority over the network; based on receiving the authentication approval, receiving, at the processor, payment data comprising a payment token in the web browser from the authentication authority, wherein the payment token is a one-time use code that is unique to the merchant website; based on receiving the payment data comprising the payment token, auto-filling, by the processor, the payment data comprising the payment token into at least one field of the web browser; and executing, at the processor, in the web browser executing the expedited payment extension, the transaction being executed in response to the authentication approval and based on auto-filling the payment data comprising the payment token. ### Claim 11 (depends on 10) The networked system of claim 10, wherein the execute action includes a mouse click and the extension area includes extension area includes a visual indication in a browser action bar that the expedited payment extension is available. ### Claim 12 (depends on 10) The networked system of claim 10, wherein the authentication data further includes a password for a sign in name that is stored locally as a browser cookie. ### Claim 13 (depends on 10) The networked system of claim 10, wherein the authentication data is communicated to the authentication authority over the network, wherein the network includes a dedicated network that receives the payment data and communicates the payment data to entities of the transaction. ### Claim 14 (depends on 10) The networked system of claim 10, further comprising receiving a selection at the processor of one payment device from a plurality of payment devices and the authentication data includes an amount available to spend on the selected payment device. ### Claim 15 (depends on 10) The networked system of claim 10, wherein the authentication data is further used to improve one or more fraud algorithms at the network. ### Claim 16 (depends on 10) The networked system of claim 10, wherein the extension area comprises at least one of a sidebar, a button, and a graphical user interface. ### Claim 17 (depends on 10) The networked system of claim 10, further comprising auto-filling one or more of a name, a billing address, and a shipping address in the extension area based on the payment data. ### Claim 18 (depends on 10) The networked system of claim 10, wherein executing, at the processor, the transaction in the web browser executing the expedited payment extension includes instructions for sending the payment data to the network and analyzing the payment data for one or more of verification, sufficient funds/amounts, and fraud. ### Claim 19 (depends on 10) The method of claim 10, further comprising displaying, by the processor, a button in the web browser. ### Claim 20 (depends on 19) The method of claim 19, further comprising auto-filling one or more of a name, a billing address, and a shipping address in the extension area based on the payment data, wherein the auto-filling action is performed in response to receiving a selection by a user of the button. ### Claim 21 (depends on 10) The networked system of claim 10, wherein executing, at the processor, the transaction in the web browser executing the expedited payment extension includes instructions for displaying, by the processor, a button in the web browser. ### Claim 22 (depends on 21) The networked system of claim 21, wherein the auto-filling instruction is executed at the processor in response to receiving a selection by a user of the button. ### Claim 23 A processor-implemented method of enabling an expedited payment extension in a web browser to execute a purchase transaction on a user account with a merchant website, the method comprising: receiving, at a processor, an execute action to an extension area of the web browser to start the expedited payment extension; based on receiving the execute action, executing, through the processor, the expedited payment extension in the web browser, wherein the processor executes both the web browser and the expedited payment extension; based on executing the expedited payment extension, accessing, through the processor, authentication data by the expedited payment extension from the web browser, wherein the authentication data accessed by the expedited payment extension comprises merchant data corresponding to the merchant website; based on accessing the authentication data, communicating, through the processor, the authentication data comprising the merchant data to an authentication authority; based on communicating the authentication data to the authentication authority, receiving, at the processor, an authentication approval from the authentication authority; based on receiving the authentication approval, receiving, at the processor, payment data comprising a payment token in the web browser from the authentication authority, wherein the payment token is a one-time use code that is unique to the merchant website; based on receiving the payment data comprising the payment token, auto-filling, by the processor, the payment data comprising the payment token into at least one field of the web browser; and executing, at the processor, the transaction in the web browser executing the expedited payment extension, the transaction being executed in response to the authentication approval and based on auto-filling the payment data comprising the payment token.