Method and system for creating a unique identifier

• US 10,257,178 B2
• Filed: 10/15/2015
• Issued: 04/09/2019
• Est. Priority Date: 04/15/2013
• Status: Active Grant

• Current Assignee: Visa Europe Limited (Visa, Inc.)
• Original Assignee: Visa Europe Limited (Visa, Inc.)
• Inventors: Carpenter, Paul Michael, Sumpster, Jonathan Paul, Thompson, Andrew Paul, Abrathat, Christopher Ian, Rusca, Jonathan, Lacour, Jean-Christophe Gilbert, Philpotts, Michael Ronald
• Primary Examiner(s): Poltorak, Piotr
• Application Number:
  US14/884,153
• Publication Number:
  US 20160036800A1
• Time in Patent Office: 1,272 Days
• Field of Search: None
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06Q 20/306 using TV related infrastructures external card used for payment with client device H04N21/4185
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

Method and apparatus for creating a second unique identifier for a user in a second system based on a first unique identifier for a user in a first system. A first authentication process is initiated based on a first unique identifier associated with the user in the first system. Responsive to the user successfully authenticating during the first authentication process, the second unique identifier for a user in the second system is generated. The second unique identifier is based on user data associated with the first unique identifier in the first system, and the second unique identifier is different from the first unique identifier.

Claims

1. A method of creating a second unique identifier based on a first unique identifier, the method comprising:

receiving, by a second system from a user terminal operated by a user, the first unique identifier, wherein the first unique identifier is a primary account number;

identifying, by the second system, a first system based on the first unique identifier, the first system being different from the user terminal;

initiating, by the second system, a first authentication process based on the first unique identifier; and

responsive to the user successfully authenticating during the first authentication process;

receiving, by the second system, user data from the first system;

generating, by the second system, based on at least a part of the user data associated with the first unique identifier in the first system, at least a part of the second unique identifier, the second unique identifier being different from the first unique identifier;

storing, by the second system, the first unique identifier;

receiving, by the second system, the second unique identifier from the user terminal; and

initiating, by the second system, a payment transaction using the stored first unique identifier and the at least part of the user data.

2. The method of claim 1, wherein the second unique identifier comprises a username to be associated with a second system password to define credentials for use in the second system.

3. The method of claim 1, wherein the first unique identifier is associated with a first system password to define credentials for the user in the first system.

4. The method of claim 1, wherein the first authentication process is conducted between the user and the first system.

5. The method of claim 1, wherein the first authentication process uses at least the first unique identifier to authenticate the user.

6. The method of claim 1, comprising:

sending the generated second unique identifier to the user;

receiving user input from the user, the user input confirming that the generated second unique identifier is to be used; and

activating the generated second unique identifier in the second system based upon the user input.

7. The method of claim 1, comprising:

sending the generated second unique identifier to the user;

receiving user input from the user, the user input indicating that the generated second unique identifier is not to be used and providing a different, user-defined second unique identifier; and

activating the user-defined second unique identifier in the second system based upon the user input.

8. The method of claim 1, comprising:

generating a plurality of second unique identifiers;

sending the generated plurality of second unique identifiers to the user;

receiving user input from the user, the user input indicating that a one of the plurality of generated second unique identifiers is to be used; and

activating the indicated second unique identifier in the second system based upon the user input.

9. The method of claim 1, comprising:

receiving a plurality of elements of the user data associated with the first unique identifier from the first system; and

storing at least one or more of the plurality of elements of the user data received from the first system, other than the at least part of the user data upon which at least a part of the second unique identifier is generated.

10. The method of claim 1, comprising:

after the generating of the second unique identifier, conducting a second authentication process in which the user is authenticated based, at least, on the second unique identifier; and

responsive to the second authentication process being successful, allowing access to the second system.

11. The method of claim 1, wherein the primary account number (PAN) is associated with a financial instrument.

12. The method of claim 1, wherein the part of user data associated with the first unique identifier in the first system, from which at least a part of the second unique identifier is generated, comprises a contact data element.

13. The method according to claim 2, wherein the part of user data associated with the first unique identifier in the first system, from which at least a part of the second unique identifier is generated, comprises an email address or telephone number.

14. The method of claim 1, wherein the first system comprises an issuing bank data processing system.

15. The method of claim 1, wherein the second system comprises a payment wallet data processing system.

16. Apparatus for creating a second unique identifier based on a first unique identifier, the apparatus comprising at least one memory including computer program code, and at least one processor in data communication with the at least one memory, wherein the at least one processor is configured to:

receive, from a user terminal operated by a user, the first unique identifier, wherein the first unique identifier is a primary account number;

identify a first system based on the first unique identifier, the first system being different from the user terminal;

initiate a first authentication process based on the first unique identifier; and

responsive to the user successfully authenticating during the first authentication process;

receive user data from the first system;

generate, by a second system, based on at least a part of the user data associated with the first unique identifier in the first system, at least a part of the second unique identifier, the second unique identifier being different from the first unique identifier;

storing, by the second system, the first unique identifier;

receiving, by the second system, the second unique identifier from the user terminal; and

initiating, a payment transaction using the stored first unique identifier and the at least part of the user data.

17. A non-transitory computer-readable medium comprising computer-executable instructions which, when executed by a processor, cause a computing device to perform a method of creating a second unique identifier based on a first unique identifier, the method comprising:

receiving, by a second system from a user terminal operated by a user, the first unique identifier, wherein the first unique identifier is a primary account number;

identifying a first system based on the first unique identifier, the first system being different from the user terminal;

initiating a first authentication process based on the first unique identifier; and

responsive to the user successfully authenticating during the first authentication process;

receiving, by the second system, user data from the first system;

generating, by the second system, based on at least a part of the user data associated with the first unique identifier in the first system, at least a part of the second unique identifier, the second unique identifier being different from the first unique identifier

storing, by the second system, the first unique identifier;

receiving, by the second system, the second unique identifier from the user terminal; and

initiating, by the second system, a payment transaction using the stored first unique identifier and the at least part of the user data.