Browser extension for limited-use secure token payment

Patent metadata

Field	Value
Publication number	US-10887299-B2
Application number	US-201916700645-A
Country	US
Kind code	B2
Filing date	Dec 2, 2019
Priority date	Dec 16, 2015
Publication date	Jan 5, 2021
Grant date	Jan 5, 2021

Abstract

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

The invention claimed is:

1. A browser extension server, comprising:
a communication device configured to communicate with (i) a first computing device executing a browser extension application and a web browser application, and (ii) a second computing device executing an authentication application;
a memory storing instructions; and
a processor configured to execute the instructions to perform operations comprising:
receiving from the first computing device, through the browser extension application, an indication of a financial service account associated with the first computing device,
receiving, through the browser extension application, an indication of a payment field in a web page provided by the first computing device through the web browser application,
in response to receiving the indication of the payment field, (i) generating a secure token mapped to the financial service account and (ii) transmitting, to the second computing device, an authentication request through the authentication application,
in response to transmitting the authentication request, receiving an authentication response from the second computing device through the authentication application, and
in response to determining that the authentication response satisfies the authentication request, providing the browser extension application with the secure token for populating the payment field.

2. The browser extension server of claim 1 , wherein generating the secure token comprises:
providing to the first computing device an offer to generate the secure token;
receiving from the first computing device an acceptance of the offer; and
in response to receiving the acceptance, generating the secure token.

3. The browser extension server of claim 1 , wherein the secure token comprises a single-use token.

4. The browser extension server of claim 1 , wherein the secure token comprises a time-limited token.

5. The browser extension server of claim 1 , wherein:
the web page comprises a web page associated with a merchant; and
the secure token comprises a merchant-specific token.

6. The browser extension server of claim 5 , wherein the operations further comprise:
receiving through the browser extension application the indication of the payment field in a subsequent visit to the web page; and
in response to receiving the indication of the payment field, automatically providing the browser extension application with the secure token for repopulating the payment field.

7. The browser extension server of claim 1 , wherein the operations further comprise:
receiving an indication of personal information associated with the first computing device, wherein the personal information comprises at least one of a name, a shipping address, or a billing address;
receiving through the browser extension application a personal information field in the web page provided through the web browser application; and
in response to receiving the personal information field, providing the browser extension application with the personal information for populating the personal information field.

8. The browser extension server of claim 1 , wherein the operations further comprise, further in response to receiving the indication of the payment field, providing the browser extension application with a request for visually highlighting the payment field in the web browser application.

9. The browser extension server of claim 1 , wherein:
the authentication request comprises instructions for generating an authentication response; and
the authentication response indicates that the instructions have been followed.

10. The browser extension server of claim 1 , wherein:
the authentication request requests input from a user of the second computing device; and
the authentication response comprises an indication of the requested input.

11. A method comprising:
receiving from a first computing device, through a browser extension application executed at the first computing device, an indication of a financial service account associated with the first computing device;
detecting, through the browser extension application, a payment field in a web page provided by the first computing device through a web browser application;
in response to detecting the payment field, (i) generating a secure token mapped to the financial service account and (ii) transmitting, to a second computing device, an authentication request through an authentication application executed at the second computing device;
in response to transmitting the authentication request, receiving an authentication response from the second computing device through the authentication application; and
in response to determining that the authentication response satisfies the authentication request, populating the payment field with the secure token through the browser extension application.

12. The method of claim 11 , wherein generating the secure token comprises:
providing to the first computing device an offer to generate the secure token;
receiving from the first computing device an acceptance of the offer; and
in response to receiving the acceptance, generating the secure token.

13. The method of claim 11 , wherein the secure token comprises a single-use token.

14. The method of claim 11 , wherein the secure token comprises a time-limited token.

15. The method of claim 11 , wherein:
the web page comprises a web page associated with a merchant; and
the secure token comprises a merchant-specific token.

16. The method of claim 15 , further comprising:
redetecting the payment field in a subsequent visit to the web page; and
in response to redetecting the payment field, repopulating the payment field with the secure token.

17. The method of claim 11 , further comprising:
receiving an indication of personal information associated with the first computing device, wherein the personal information comprises at least one of a name, a shipping address, or a billing address;
detecting a personal information field in the web page provided in the web browser; and
in response to detecting the personal information field, populating the personal information field with the personal information.

18. The method of claim 11 , further comprising, further in response to detecting the payment field, visually highlighting the payment field in the web browser application.

19. The method of claim 11 , wherein:
the authentication request comprises instructions for generating an authentication response; and
the authentication response indicates that the instructions have been followed.

20. The method of claim 11 , wherein:
the authentication request requests input from a user of the second computing device; and
the authentication response comprises an indication of the requested input.

Assignees

• Capital One Services Llc

Inventors

• De Ganon Matthew
• Arora Kunal
• Poole Thomas
• Kahn Daniel
• Trivedi Dwij
• Moreton Paul

Classifications

• G06F21/33

  using certificates · CPC title

• G06F21/31

  User authentication · CPC title

• H04L63/168 Primary

  above the transport layer · CPC title

• G06Q20/38215

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

• G06F21/6263

  during internet communication, e.g. revealing personal data from cookies · CPC title