Browser extension for limited-use secure token payment

US12069037B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12069037-B2
Application numberUS-202318311017-A
CountryUS
Kind codeB2
Filing dateMay 2, 2023
Priority dateDec 16, 2015
Publication dateAug 20, 2024
Grant dateAug 20, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include receiving from the first computing device an indication of a financial service account associated with the first computing device, detecting a payment field in a web page provided by the computing device through the web browser application and, in response, generating a secure token mapped to the financial service account. The operations may further include sending the second computing device an authentication request, receiving an authentication response, and populating the payment field with the secure token.

First claim

Opening claim text (preview).

The invention claimed is: 1. A system for populating a data field with a secure token, the system comprising one or more processors and a memory storing program instructions that, when executed by the one or more processors, causes the one or more processors to perform operations comprising: sending, by a browser extension application, a set of messages to a server, the set of messages comprising an indication of a field in a web page and an indication of an account; receiving an option to generate a secure token, wherein the secure token is mapped to the account; generating, by the browser extension application, the secure token based on a response indicating an acceptance of the option; sending the secure token to the server; and populating, by the browser extension application, the field in the web page with the secure token. 2. A method comprising: sending, by a first application, a set of messages to a server, the set of messages comprising an indication of a field in a web page and an indication of an account; receiving an option to generate a secure token, wherein the secure token is mapped to the account; generating, by the first application, the secure token based on a response indicating an acceptance of the option; sending the secure token to the server; and populating, by the first application, the field in the web page with the secure token. 3. The method of claim 2 , wherein the set of messages comprises a field identifier of the field. 4. The method of claim 2 wherein the secure token is associated with an identifier of a second set of computing devices configured to provide web pages over a network. 5. The method of claim 2 , wherein populating the field in the web page comprises presenting a pop-up notification in the first application. 6. The method of claim 2 , wherein the field is a first field, and wherein generating the secure token comprises generating the secure token based on a detection of a second field associated with target input field identifier. 7. The method of claim 2 , wherein sending the set of messages comprises transmitting an authentication request via an authentication application executed at a second computing device, wherein the authentication request comprises an indication of a requested input for the authentication request. 8. The method of claim 2 , wherein the field in the web page is a first field, further comprising: retrieving a name associated with the account; and populating, via the first application, a second field in the web page with the name. 9. The method of claim 2 , wherein generating the secure token comprises randomly generating the secure token. 10. The method of claim 2 , wherein the secure token is a single-use token, further comprising providing the single-use token to another computing device to execute a first transaction, and wherein the single-use token is not used execute a second transaction. 11. The method of claim 2 , further comprising: retrieving a script of the web page; and searching through the script to detect a field identifier for the field, wherein sending the set of messages to the server comprises sending the set of messages based on a detected match between the field identifier and a target input field identifier. 12. One or more non-transitory, computer-readable media storing instructions that, when executed by one or more processors, cause operations comprising: obtaining, from a computing device, a set of messages indicating a first input field in a web page and an account identifier associated with an account; providing, to the computing device, an option to generate a secure token; receiving an acceptance of the option; in response to receiving the acceptance and to a user being authenticated based on an authentication response, obtaining the secure token, wherein the secure token is mapped to the account; and providing the secure token to an application operating on the computing device to populate the first input field with the secure token. 13. The one or more non-transitory, computer-readable media of claim 12 , the operations further comprising: retrieving user-related information associated with the account; and providing the user-related information to the computing device to populate a second input field of the web page. 14. The one or more non-transitory, computer-readable media of claim 12 , the operations further comprising: providing the application to the computing device; and wherein obtaining the set of messages comprises obtaining the set of messages from the application. 15. The one or more non-transitory, computer-readable media of claim 12 , wherein the computing device is a first computing device, the operations further comprising: transmitting an authentication request to a second computing device; and receiving the authentication response in response to the authentication request. 16. The one or more non-transitory, computer-readable media of claim 12 , the operations further comprising: storing, in a database, the secure token, wherein the secure token is stored in association with a set of computing devices. 17. The one or more non-transitory, computer-readable media of claim 12 , wherein obtaining the secure token comprises: detecting that an identifier of the first input field matches an identifier of a set of computing devices configured to provide web pages over a network; and retrieving a previously used token based on the identifier of the set of computing devices, wherein the secure token is the previously used token. 18. The one or more non-transitory, computer-readable media of claim 12 , wherein the authentication response is determined based on a geolocation information of a second computing device. 19. The one or more non-transitory, computer-readable media of claim 12 , wherein obtaining the secure token comprises: determining that the authentication response satisfies a set of authentication criteria, wherein the secure token is obtained in response to determining that the authentication response satisfies the set of authentication criteria. 20. The one or more non-transitory, computer-readable media of claim 19 , wherein the authentication response is a first authentication response, and wherein determining that the first authentication response satisfies the set of authentication criteria comprises: generating a new authentication response; and comparing the first authentication response with the new authentication response.

Assignees

Inventors

Classifications

  • Identity check for transactions · CPC title

  • Form filling; Merging · CPC title

  • Use of certificates or encrypted proofs of transaction rights · CPC title

  • specially adapted for electronic shopping systems · CPC title

  • H04L63/168Primary

    above the transport layer · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12069037B2 cover?
Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memo…
Who is the assignee on this patent?
Capital One Services Llc
What technology area does this patent fall under?
Primary CPC classification H04L63/168. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 20 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).