System and method for automatically filling webpage fields

• US 9,251,538 B1
• Filed: 09/22/2010
• Issued: 02/02/2016
• Est. Priority Date: 09/23/2009
• Status: Active Grant

• Current Assignee: Verient Incorporated
• Original Assignee: Verient Incorporated
• Inventors: Shakkarwar, Rajesh G.
• Primary Examiner(s): Subramanian, Narayanswamy
• Application Number:
  US12/888,330
• Time in Patent Office: 1,959 Days
• Field of Search: 705 35- 45
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/351 Virtual cards
• CPC Class Codes: G06Q 20/356 Aspects of software for card payments
• CPC Class Codes: G06Q 20/4018 using the card verification value [CVV] associated with the card
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A computer-implemented method for automatically populating fields of a webpage. The method includes transmitting data from a browser add-on installed in a second webpage to a code segment inserted in a first webpage, where the code segment is configured to populate one or more fields included in the first webpage with received data, where the browser add-on is not installed in the first webpage, and where the first webpage is displayed on a display device in a web browser application executing on a computer system; and executing the code segment to populate the fields included in the first webpage with the received data.

Claims

1. A computer-implemented method for automatically populating fields of a webpage, the method comprising:

generating, via a second webpage, a child product containing data that is linked to a core account that provides financial backing for the child product, wherein the data includes a child product card number;

pushing, via a processor, the data from a browser add-on installed in the second webpage to a code segment inserted in a first webpage, wherein the code segment causes one or more fields included in the first webpage to be populated with the data, wherein the browser add-on is not installed in the first webpage;

displaying the first webpage on a display device in a first instance of a web browser application executing on a computer system; and

executing the code segment to populate the one or more fields included in the first webpage with the data.

2. The method of claim 1, wherein the first webpage comprises a merchant payment page, the fields included in the first webpage comprise payment fields, and the data comprises payment data.

3. The method of claim 2, wherein the core account is held with a financial institution.

4. The method of claim 2, wherein the payment data includes a virtual card verification value (“

CVV”

), a virtual personal identification number (“

PIN”

), a virtual expiration date, or a virtual name on card.

5. The method of claim 2, wherein the payment data is transmitted from the second webpage to each open instance of the web browser application.

6. The method of claim 1, wherein the second webpage comprises a secure payment page.

7. The method of claim 1, wherein the code segment comprises a script.

8. The method of claim 1, further comprising downloading the browser add-on from a server and installing the browser add-on in the second webpage.

9. The method of claim 8, wherein, after downloading the browser add-on, the steps of installing the browser add-on in the second webpage, pushing the data from the browser add-on to the code segment inserted in the first webpage, and executing the code segment to populate the one or more fields included in the first webpage with the data are performed without restarting the first instance of a web browser application.

10. The method of claim 1, wherein the data is transmitted from the second webpage only to the first webpage and is not transmitted to other open instances of the web browser application.

11. The method of claim 1, further comprising displaying the second webpage on the display device in a second instance of the web browser application executing on the computer system.

12. A computer-readable storage medium storing instructions that, when executed by a processor, cause a computer system to automatically populate fields of a webpage, by performing the steps of:

generating, via a second webpage, a child product containing data that is linked to a core account that provides financial backing for the child product, wherein the data includes a child product card number;

determining that a code segment has been inserted into a first webpage, wherein the code segment causes one or more fields included in the first webpage to be populated with the data;

displaying the first webpage on a display device in a first instance of a web browser application executing on a computer system;

installing a browser add-on in a second webpage, wherein the browser add-on the data to be pushed to the first page;

pushing the data from the browser add-on installed in the second webpage to the code segment inserted in the first webpage; and

executing the code segment to populate the one or more fields included in the first webpage with the data.

13. The computer-readable storage medium of claim 12, wherein the first webpage comprises a merchant payment page, the fields included in the first webpage comprise payment fields, and the data comprises payment data.

14. The computer-readable storage medium of claim 13, wherein core account is held with a financial institution.

15. The computer-readable storage medium of claim 13, wherein the payment data includes a virtual card verification value (“

CVV”

), a virtual personal identification number (“

PIN”

), a virtual expiration date, or a virtual name on card.

16. The computer-readable storage medium of claim 13, wherein the payment data is transmitted from the second webpage to each open instance of the web browser application.

17. The computer-readable storage medium of claim 12, wherein the second webpage comprises a secure payment.

18. The computer-readable storage medium of claim 12, wherein the code segment comprises a script.

19. The computer-readable storage medium of claim 12, further comprising downloading the browser add-on from a server and installing the browser add-on in the second webpage.

20. The computer-readable storage medium of claim 12, wherein the data is transmitted from the second webpage only to the first webpage and is not transmitted to other open instances of the web browser application.

21. A computing system for automatically populating fields of an online merchant payment webpage, the computing system comprising:

a user device including a processor, a display device coupled to the processor and displaying an output from the processor, and a memory coupled to the processor and storing instructions executed by the processor, the user device to;

display the first webpage on the display device in a first instance of a web browser application executed by the processor;

receive, via a first webpage, a user selection to pay for goods or services using a payment product;

generate, via a second webpage, payment data linked to the payment product, wherein the payment data includes a payment card number;

determine that a code segment has been inserted into the first webpage, wherein the code segment causes one or more payment fields included in the first webpage to be populated with the payment data;

install a browser add-on in the second webpage,

push the payment data from the add-on installed in the second webpage to the code segment inserted in the first webpage; and

execute the code segment to populate the one or more payment fields included in the first webpage with the payment data; and

a payment processing platform coupled to the user device via a network and to generate or retrieve the payment product.

22. The computing system of claim 21, wherein the second webpage is a secure payment page.

23. The computing system of claim 21, wherein the payment data further comprises a card verification value (“

CVV”

), a personal identification number (“

PIN”

), an expiration date, a name, and combinations thereof.