IP Library Granted Patent US 11,675,974
Granted Patent B2
US 11,675,974 · App. 17/186,861 · Granted Jun 13, 2023

Browser extension for field detection and automatic population

Inventors: Dwij Trivedi (Oakton, VA); Matthew de Ganon (Dobbs Ferry, NY); Kunal Arora (Great Falls, VA)
Assignee: Capital One Services, LLC
G06F40/221G06F16/957G06F40/174G06Q20/12
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,675,974
App. No.
17/186,861
Granted
Jun 13, 2023
Kind
B2
Abstract

Methods and systems for a browser extension application are disclosed. In some embodiments, a browser extension application is configured to receive from a browser extension server a regular expression configured to detect a plurality of fields in a web page and execute the regular expression to detect a transaction field in the web page and automatically populate the transaction field with stored data. The application is further configured to detect an unrecognized field in the web page, provide suggested transaction data, and detecting manual population of the unrecognized field with the suggested transaction data. The application is further configured to providing to the browser extension server an indication of the unrecognized field and receive from the browser extension server an updated regular expression configured to detect the unrecognized field in the web page.

Claims (56)

1. A system for executing a browser extension application comprising:

at least one processor; and

at least one storage device storing instructions that, when executed by the processor, cause the processor to perform operations comprising:

receiving, from a browser extension server, a regular expression configured to detect a plurality of fields in a web page;

executing the regular expression to detect a transaction field in the web page;

receiving from the browser extension server a secure token associated with the detected transaction field;

automatically populating the detected transaction field with the token;

detecting an unrecognized field in the web page;

in response to detecting the unrecognized field, providing suggested transaction data;

detecting a selection of at least a portion of the suggested transaction data to populate the unrecognized field; and

providing, to the browser extension server, an indication of the selection of the suggested transaction data.

2. The system of claim 1 , wherein the operations further comprise providing to the browser extension server programming language describing the web page.

3. The system of claim 1 , wherein the suggested transaction data is received from the browser extension server.

4. The system of claim 1 , wherein the operations further comprise receiving an updated regular expression configured to detect the unrecognized field in the web page in response to sending a query to the browser extension server.

5. The system of claim 1 , wherein:

the web page comprises a merchant-provided payment process, the merchant-provided payment process comprising a message; and

the operations further comprise:

providing, to the browser extension server, an indication of a transaction field detected in the message.

6. The system of claim 1 , wherein the operations further comprise:

providing, to the browser extension server, an indication of an element detected in the web page.

7. The system of claim 1 , wherein the transaction field comprises a payment field.

8. A method comprising:

receiving, from a browser extension server, a regular expression configured to detect a plurality of fields in a web page;

executing the regular expression to detect a transaction field in the web page;

receiving from the browser extension server a secure token associated with the detected transaction field;

automatically populating the detected transaction field with the token;

detecting an unrecognized field in the web page;

in response to detecting the unrecognized field, providing suggested transaction data;

detecting a selection of at least a portion of the suggested transaction data to populate the unrecognized field; and

providing, to the browser extension server, an indication of the selection of the suggested transaction data.

9. The method of claim 8 , further comprising providing to the browser extension server programming language describing the web page.

10. The method of claim 8 , wherein the suggested transaction data is received from the browser extension server.

11. The method of claim 8 , further comprising receiving an updated regular expression configured to detect the unrecognized field in the web page in response to sending a query to the browser extension server.

12. The method of claim 8 , wherein:

the web page comprises a merchant-provided payment process, the merchant-provided payment process comprising a message; and

the method further comprises:

providing, to the browser extension server, an indication of an additional transaction field detected in the message.

13. The method of claim 8 , further comprising: providing, to the browser extension server, an indication of an additional element detected in the web page.

14. The method of claim 8 , wherein the transaction field comprises a payment field.

15. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving, from a browser extension server, a regular expression configured to detect a plurality of fields in a web page;

executing the regular expression to detect a transaction field in the web page;

receiving from the browser extension server a secure token associated with the detected transaction field;

automatically populating the detected transaction field with the token;

detecting an unrecognized field in the web page;

in response to detecting the unrecognized field, providing suggested transaction data;

detecting a selection of at least a portion of the suggested transaction data to populate the unrecognized field; and

providing, to the browser extension server, an indication of the selection of the suggested transaction data.

16. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise providing to the browser extension server programming language describing the web page.

17. The non-transitory computer-readable medium of claim 15 , wherein the suggested transaction data is received from the browser extension server.

18. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise receiving an updated regular expression configured to detect the unrecognized field in the web page in response to sending a query to the browser extension server.

19. The non-transitory computer-readable medium of claim 15 , wherein:

the web page comprises a merchant-provided payment process, the merchant-provided payment process comprising a message; and

the operations further comprise:

providing, to the browser extension server, an indication of an additional transaction field detected in the message.

20. The non-transitory computer-readable medium of claim 15 , wherein the transaction field comprises a payment field.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2023
From: TRIVEDI, DWIJ; DE GANON, MATTHEW; ARORA, KUNAL
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 063435/0759 →
Continuity (4)
Continuation 15674621 · Aug 11, 2017
Continuation 15669396 · Aug 4, 2017
Provisional Application 62371276 · Aug 5, 2016
Related Publication 20210182483A1 · Jun 17, 2021
Cited By (2)
US 12,231,459 US 12,341,803