Centralized identity authentication for electronic communication networks

• US 10,019,712 B2
• Filed: 11/20/2012
• Issued: 07/10/2018
• Est. Priority Date: 03/06/2000
• Status: Active Grant

• Current Assignee: CardinalCommerce Corporation (Visa, Inc.)
• Original Assignee: CardinalCommerce Corporation (Visa, Inc.)
• Inventors: Bhagavatula, Ravishankar S., Balasubramanian, Chandra, Sherwin, Francis M., Keresman, III, Michael A., Bowman, Jeffry J.
• Primary Examiner(s): Song, Hosuk
• Application Number:
  US13/682,196
• Publication Number:
  US 20130125213A1
• Time in Patent Office: 2,058 Days
• Field of Search: 713150, 713155, 713168, 713170, 713 1, 713 68, 726 2- 9, 705 50, 705 53, 705 67- 68, 705 70, 705 75- 79
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

A method of centralized identity authentication for use in connection with a communications network includes registering users of the communications network such that each registered user'"'"'s identity is uniquely defined and determinable, and registering a plurality of vendors having a presence on the communications network. The registered vendors selectively transact with registered users, wherein the transactions include: (i) the registered vendor selling goods and/or services to the registered user; (ii) the registered vendor granting the registered user access to personal records maintained by the registered vendor; and/or (iii) the registered vendor communicating to the registered user personal information maintained by the registered vendor. The method also includes each user'"'"'s identity being authenticated over the communications network prior to completion of transactions between registered vendors and registered users.

Claims

1. A method of centralized identity authentication over a communications network, comprising:

receiving registration data by a server, the registration data including authentication data for a user and a vendor, the user engaging in a transaction with the vendor, the transaction including the vendor providing the user access to data maintained by the vendor, and the server being remote from the user and the vendor;

receiving authentication data from the user and the vendor by the server over the communications network; and

authenticating identities of the user and the vendor by the server over the communications network prior to completion of the transaction, the authenticating including comparing the received authentication data with the authentication data of the received registration data;

wherein authenticating further includes;

receiving a dynamically changing password from at least one of;

an issued hardware token;

or

a software object.

2. The method according to claim 1, wherein authenticating further includes:

comparing data collected from a user attempting the transaction with corresponding data in a central database.

3. The method according to claim 1, further including:

collecting data about the registered user which includes at least one of;

name, address, length at residence, ownership or rental at residence, e-mail address, home phone number, work phone number, social security number, date of birth, mother'"'"'s maiden name, employer, income, or employment status.

4. The method according to claim 1, further including:

encrypting at least one communication related to the authentication.

5. The method according to claim 1, wherein the registered user includes a determination of credit worthiness which limits or restricts the transaction.

6. The method according to claim 1, further including:

restricting the transaction based on the registered user being authorized to transact with the registered vendor.

7. The method according to claim 1, further including:

restricting the transaction based on a comparison of data collected from the registered user and data stored by the registered vendor.

8. The method according to claim 1, further including:

recording the transaction in a database.

9. The method according to claim 1, further including:

notifying the user of a non-authentic user posing as the user and attempting to complete the transaction with the vendor.

10. The method according to claim 1, wherein authenticating includes receiving the dynamically changing password from an issued hardware token.

11. The method according to claim 1, wherein authenticating includes receiving the dynamically changing password from a software object.

12. A system of centralized identity authentication over a communications network, comprising:

a server of an authentication authority remote from a user, a trusted representative and a vendor, the server configured to;

receive registration data for the trusted representative from the trusted representative over the communication network, the registration data including authentication data for the user;

receive registration data including authentication data the vendor, the vendor engaging in a transaction with the user, the transaction including the vendor granting the user access to personal data of the user maintained by the vendor;

receive authentication data from the user and the vendor over the communications network;

authenticate identities of the user and the vendor over the communications network prior to completion of the transaction, the authentication including comparing the received authentication data with the authentication data of the received registration data; and

receive a dynamically changing password from at least one of;

an issued hardware token;

or

a software object.

13. The system according to claim 12, wherein the server is further configured to:

notify the registered user of a non-authentic user attempting to complete the transaction with the registered vendor and posing as the registered user.

14. The system according to claim 12, wherein the server is further configured to:

compare data collected from a user attempting the transaction with corresponding data in a central database.

15. The system according to claim 12, wherein the server is further configured to:

collect data about the registered user which includes at least one of;

name, address, length at residence, ownership or rental at residence, e-mail address, home phone number, work phone number, social security number, date of birth, mother'"'"'s maiden name, employer, income, or employment status.

16. The system according to claim 12, wherein the server is further configured to:

encrypt or decrypt at least one communication related to the authentication.

17. The system according to claim 12, wherein the server is further configured to:

limit or restrict the transaction based on a determination of credit worthiness.

18. The system according to claim 12, wherein the server is further configured to:

restrict the transaction based on the registered user being authorized to transaction with the registered vendor.

19. The system according to claim 12, wherein the server is further configured to:

restrict the transaction based on a comparison of data collected from the registered user and data stored by the registered vendor.

20. The system according to claim 12, wherein the server is further configured to:

record the transaction in a database.

21. A method of centralized identity authentication over a communications network, comprising:

authenticating, with a configured server, identities of a registered user and a registered vendor over the communications network prior to completion of a transaction between the registered user and the registered vendor;

notifying, with the configured server, the registered user of a non-authentic user attempt of the transaction with the registered vendor posing as the registered user;

receiving registration data by the server, the registration data including authentication data for the registered user and the registered vendor, the registered user engaging in a transaction with the registered vendor, the transaction including the vendor providing the registered user access to data maintained by the registered vendor; and

receiving authentication data from the registered user and the registered vendor by the server over the communications network;

wherein the authenticating includes comparing the received authentication data with the authentication data of the received registration data.

22. The method according to claim 21, wherein authenticating further includes:

receiving a dynamically changing password from at least one of;

an issued hardware token;

or

a software object.

23. A method of centralized identity authentication over a communications network, comprising:

authenticating, with a configured server, identities of a registered user and a registered vendor over the communications network prior to completion of a transaction between the registered user and the registered vendor; and

notifying, with the configured server, the registered user of a non-authentic user attempt of the transaction with the registered vendor posing as the registered user;

wherein authenticating further includes receiving a dynamically changing password from an issued hardware token.

24. A method of centralized identity authentication over a communications network, comprising:

authenticating, with a configured server, identities of a registered user and a registered vendor over the communications network prior to completion of a transaction between the registered user and the registered vendor; and

notifying, with the configured server, the registered user of a non-authentic user attempt of the transaction with the registered vendor posing as the registered user;

wherein authenticating further includes receiving a dynamically changing password from a software object.

25. The method according to claim 24, wherein authenticating further includes:

comparing data collected from a user attempting the transaction with corresponding data in a central database, such that an insufficient match therebetween results in a determination that the non-authentic user is attempting the transaction with the registered vendor posing as the registered user.

26. The method according to claim 24, further including:

collecting data about the registered user which includes all of;

name, address, length at residence, ownership or rental at residence, e-mail address, home phone number, work phone number, social security number, date of birth, mother'"'"'s maiden name, employer, income, and employment status.