Method and apparatus for completing, securing and conducting an E-commerce transaction

• US 7,930,213 B1
• Filed: 08/24/1999
• Issued: 04/19/2011
• Est. Priority Date: 09/11/1998
• Status: Expired due to Fees

• Current Assignee: Jack A. Turpin, RPX Corporation
• Original Assignee: RPX-LV Acquisition LLC (RPX Corporation)
• Inventors: Philyaw, Jeffry Jovan, Mathews, David Kent
• Primary Examiner(s): FADOK, MARK A
• Application Number:
  US09/382,426
• Time in Patent Office: 4,256 Days
• Field of Search: 705/26, 705/27, 705/14, 379/91.01, 379/93.03, 455/415, 235/425, 235/462.01, 707505-507
• US Class Current: 705/26.1
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A method of conducting and on-line transaction. A user at a PC (302) of a first location completes a profile information sheet and transmits it across a secure network (2708) to a central registration server (2704) at a second location also disposed on the network (306). The central registration server (2704) transmits a unique bar code and associated unique ID back to the user PC (302) at the first location, in response to the user sending the completed profile information sheet to the registration server (2704). When the user accesses a vendor server (2700) disposed on the network (306) for the purchase of products and/or services, the user transmits the bar code to the vendor server (2700) when prompted to complete a vendor payment form. The vendor server (2700) sends the bar code to the central registration server (2704) where the bar code is matched to the user profile information. The profile information is returned to the vendor server (2700) and automatically inserted into the vendor payment form. The vendor server then processes the transaction according to the credit information provided. Some or all fields of the vendor payment form are inserted with encoded information depending upon the user selecting a standard or invisible mode of payment, respectively. The payment form is then presented to the user at the user PC (302) for acceptance or rejection of the transaction.

Claims

1. A method of processing profile information of a user for conducting an on-line transaction between the user and a vendor, comprising the steps of:

entering profile information of a user into a profile form at a user location disposed on a network prior to conduction of an on-line transaction between the user and the vendor, the vendor disposed at a vendor location on the network;

issuing to the user a unique code representing stored profile information of the user in response to the user transmitting the profile form from the user location to a second location on the network for storage thereat, the second location disposed on the network;

initiating an on-line transaction by selecting a product of the vendor at a user location;

after selecting the product, providing to the vendor location by the user the unique code for purchase of the product, during the on-line transaction, which on-line transaction requires the user to view a vendor payment form at the user location representing information about the transaction, and which vendor payment form includes fields that are associated with information obtainable from the stored profile information of the user and which must be viewed by the user prior to completion of the on-line transaction;

providing the stored profile information from the second location to the vendor location in response to the vendor location receiving and processing the unique code; and

automatically inserting by the vendor at least a portion of the stored profile information of the user into the vendor payment form for respective associated fields therein for presentation to the user at the user location after such insertion such that, when the user receives the form for viewing, such insertion has already occurred, such that the user has not viewed the form other than with already populated certain fields prior to reception, and wherein said vendor location receives said profile information from said second location in response to said vendor location transmitting said unique code to said second location.

2. The method of claim 1, wherein the user fills in the profile form only one time.

3. The method of claim 1, wherein the profile form is transmitted to the second location over a public switched telephone network.

4. The method of claim 1, wherein the unique code is unique and has a unique ID number associated therewith.

5. The method of claim 1, wherein the unique code has a unique ID number associated therewith and the user provides the unique ID number to the vendor location for payment purposes.

6. The method of claim 1, wherein the step of automatically inserting causes all of the profile information to be entered into the vendor payment form as encoded information.

7. The method of claim 1, wherein the step of automatically inserting causes only a portion of the profile information to be entered into the vendor payment form as encoded information.

8. The method of claim 7, wherein the portion of the profile information is credit information.

9. The method of claim 1, wherein the profile information comprises name, address, ship-to address, and credit information.

10. The method of claim 4, wherein the second location is a central registration server having a database of the profile information associated with respective unique codes and unique ID numbers.

11. The method of claim 10, wherein the second location is a credit card company server.

12. The method of claim 1, wherein the unique code is placed on a credit card.

26. The method of claim 1, and further comprising transmitting the populated form to the vendor location to complete the on-line transaction.

13. A system for processing profile information of a user for conducting an on-line transaction between the user and a vendor, comprising;

profile information of a user entered into a profile form at a user location disposed on a network prior to conduction of an on-line transaction between the user and the vendor, the vendor disposed at a vendor location on the network;

a unique code representing stored profile information of the user issued to the user in response to said user transmitting said profile form from said user location to a second location on the network for storage thereat, said second location disposed on said network;

wherein said unique code is provided to the vendor location by the user for purchase of a product of the vendor after the user has viewed and made a selection of the product, during the on-line transaction, which on-line transaction requires the user to view a vendor payment form at the user location representing information about the transaction, and which vendor payment form includes fields that are associated with information obtainable from the stored profile information of the user and which must be viewed by the user prior to completion of the on-line transaction;

wherein said profile information is provided from said second location to said vendor location in response to said vendor location processing said unique code; and

wherein at least a portion of said stored profile information of the user is automatically inserted into said vendor payment form by the vendor for respective associated fields therein for presentation to said user at the user location after such insertion such that, when the user receives the form for viewing, such insertion has already occurred, such that the user has not viewed the form other than with already populated certain fields prior to reception, and wherein said vendor location receives said profile information from said second location in response to said vendor location transmitting said unique code to said second location.

14. The system of claim 13, wherein said user fills in said profile form only one time.

15. The system of claim 13, wherein said profile form is transmitted to said second location over a public switched telephone network.

16. The system of claim 13, wherein said unique code comprises a bar code.

17. The system of claim 13, wherein said unique code has a unique ID number associated therewith and said user provides said unique ID number to said vendor location for payment purposes.

18. The system of claim 13, wherein all of said profile information is automatically inserted into said vendor payment form as encoded information.

19. The system of claim 13, wherein only a portion of said profile information is entered into said vendor payment form as encoded information.

20. The system of claim 19, wherein said portion of said profile information is credit information.

21. The system of claim 13, wherein said profile information comprises the user'"'"'s name, address, ship-to address and credit information.

22. The system of claim 17, wherein said second location is a central registration server having a database of said profile information associated with respective said unique code and said unique ID number.

23. The system of claim 22, wherein said second location is a credit card company server.

24. The system of claim 13, wherein said unique code is placed on a credit card.

25. The system claim 17, wherein said second location is a central registration server having a database of said profile information associated with respective said unique code and said ID number.

27. The system of claim 13, wherein the populated form is transmitted to the vendor location to complete the on-line transaction.