Token activation

• US 8,656,180 B2
• Filed: 12/06/2011
• Issued: 02/18/2014
• Est. Priority Date: 12/06/2011
• Status: Active Grant

• Current Assignee: WwPass Corp.
• Original Assignee: WwPass Corp.
• Inventors: Shablygin, Eugene, Zakharov, Vasily, Bolotov, Oleg, Scace, Eric
• Primary Examiner(s): Smithers, Matthew
• Application Number:
  US13/312,072
• Publication Number:
  US 20130145172A1
• Time in Patent Office: 805 Days
• Field of Search: 713/185
• US Class Current: 713/185
• CPC Class Codes: G06F 21/33 using certificates

Abstract

Systems and methods for activating a token to enable a user to enter a transaction based on information received from a recovery key and a passcode are described herein.

Claims

1. A computer-implemented method comprising:

generating a recovery key identifiable by a unique token identifier by;

storing a user identifier and one or more encryption keys in a location associated with the recovery key; and

storing an enabled state associated with the token identifier of the recovery key; and

generating a passcode associated with the user;

providing the passcode and the recovery key to the user;

using the recovery key to obtain the user identifier and the one or more encryption keys;

creating an inactive token by storing the user identifier on a blank token; and

activating the inactive token to enable a user to enter a transaction, the activation being based on information received from the recovery key and the passcode received from the user.

2. The method of claim 1, wherein storing the user identifier and the one or more encryption keys in a location associated with the recovery key comprises storing the user identifier and the one or more encryption keys on the recovery key.

3. The method of claim 1, wherein storing the user identifier and the one or more encryption keys in a location associated with the recovery key comprises storing the user identifier and the one or more encryption keys in a data container identified by an access code that is based in part on a the token identifier of the recovery key.

4. The method of claim 1, wherein activating the inactive token comprises:

associating an active state with a token identifier of the active token.

5. The method of claim 4, wherein:

storing the enabled state associated with the token identifier of the recovery key comprises storing the enabled state in a look-up table indexed by token identifiers; and

storing the active state associated the token identifier of the active token comprises storing the active state in the look-up table.

6. The method of claim 4, wherein:

storing the enabled state associated with the token identifier of the recovery key comprises storing the enabled state in a data container accessible based on an access code generated based on a combination of the token identifier of the recovery key and a service provider identifier; and

storing the active state associated the token identifier of the active token comprises storing the active state in a data container accessible based on an access code generated based on a combination of the token identifier of the active token and the service provider identifier.

7. The method of claim 1, further comprising:

receiving an encryption algorithm identifier from the recovery key; and

storing the received encryption algorithm identifier on the token.

8. The method of claim 1, wherein receiving, the user identifier and the one or more encryption keys from the recovery key comprises storing the user identifier and the one or more encryption keys in a storage location accessible based on a combination of a service provider identifier and a code.

9. The method of claim 8, further comprising:

receiving the code from the user; and

accessing the stored user identifier and one or more encryption keys from the storage location.

10. The method of claim 1, wherein activating the inactive token comprises:

requesting the passcode from a user;

in response to the request, receiving the passcode from a user; and

upon verification of the passcode, activating the inactive token by updating state information associated with the token.

11. The method of claim 1, wherein the enabled state prevents the user of the recovery key for performing transactions other than those associated with token and passcode management.

12. A computer program product tangibly embodied in a non-transitory machine readable medium comprising instructions that when executed cause a processing device to:

generate a recovery key identifiable by a unique token identifier by storing a user identifier and one or more encryption keys in a location associated with the recovery key and storing an enabled state associated with the token identifier of the recovery key; and

generate a passcode associated with the user;

provide the passcode and the recovery key to the user;

use the recovery key to obtain the user identifier, the one or more encryption keys;

create an inactive token by storing the user identifier on a blank token; and

activate the inactive token to enable a user to enter a transaction, the activation being based on information received from the recovery key and the passcode received from the user.

13. The computer program product of claim 12, wherein the instructions to store the user identifier and the one or more encryption keys in a location associated with the recovery key comprise instructions to store the user identifier and the one or more encryption keys on the recovery key.

14. The computer program product of claim 12, wherein the instructions to store the user identifier and the one or more encryption keys in a location associated with the recovery key comprise instructions to store the user identifier and the one or more encryption keys in a data container identified by an access code that is based in part on a the token identifier of the recovery key.

15. The computer program product of claim 12, wherein the instructions to activate the token comprise instructions to associate an active state with a token identifier of the active token.

16. The computer program product of claim 15, wherein:

the instructions to store the enabled state associated with the token identifier of the recovery key comprise instructions to store the enabled state in a look-up table indexed by token identifiers; and

the instructions to store the active state associated the token identifier of the active token comprise instructions to store the active state in the look-up table.

17. The computer program product of claim 15, wherein:

the instructions to store the enabled state associated with the token identifier of the recovery key comprise instructions to store the enabled state in a data container accessible based on an access code generated based on a combination of the token identifier of the recovery key and a service provider identifier; and

the instructions to store the active state associated the token identifier of the active token comprise instructions to store the active state in a data container accessible based on an access code generated based on a combination of the token identifier of the active token and the service provider identifier.

18. The computer program product of claim 12, further comprising instructions to:

receive an encryption algorithm identifier from the recovery key; and

store the received encryption algorithm identifier on the token.

19. The computer program product of claim 12, wherein the instructions to receive the user identifier and the one or more encryption keys from the recovery key comprise instructions to store the user identifier and the one or more encryption keys in a storage location accessible based on a combination of a service provider identifier and a code.

20. The computer program product of claim 19, further comprising instructions to:

receive the code from the user; and

access the stored user identifier and one or more encryption keys from the storage location.

21. The computer program product of claim 12, wherein the instructions to activate the token comprise instructions to:

request the passcode from a user;

in response to the request, receive the passcode from a user; and

upon verification of the passcode, activate the token by updating state information associated with the token.

22. The computer program product of claim 12, further comprising instructions to cause the enabled state to prevent the user of the recovery key for performing transactions other than those associated with token and passcode management.

23. A system comprising:

a processing device; and

a memory comprising instructions that when executed cause the processing device to;

generate a recovery key identifiable by a unique token identifier by storing a user identifier and one or more encryption keys in a location associated with the recovery key and storing an enabled state associated with the token identifier of the recovery key; and

generate a passcode associated with the user;

provide the passcode and the recovery key to the user;

using the recovery key to obtain the user identifier, the one or more encryption keys;

creating an inactive token by storing the user identifier on a blank token; and

activate the inactive token to enable a user to enter a transaction, the activation being based on information received from the recovery key and the passcode received from the user.

24. The system of claim 23, wherein the instructions to store the user identifier and the one or more encryption keys in a location associated with the recovery key comprise instructions to store the user identifier and the one or more encryption keys on the recovery key.

25. The system of claim 23, wherein the instructions to store the user identifier and the one or more encryption keys in a location associated with the recovery key comprise instructions to store the user identifier and the one or more encryption keys in a data container identified by an access code that is based in part on a the token identifier of the recovery key.

26. The system of claim 23, wherein the instructions to activate the token comprise instructions to associate an active state with a token identifier of the active token.

27. The system of claim 26, wherein:

the instructions to store the enabled state associated with the token identifier of the recovery key comprise instructions to store the enabled state in a look-up table indexed by token identifiers; and

the instructions to store the active state associated the token identifier of the active token comprise instructions to store the active state in the look-up table.

28. The system of claim 26, wherein:

the instructions to store the enabled state associated with the token identifier of the recovery key comprise instructions to store the enabled state in a data container accessible based on an access code generated based on a combination of the token identifier of the recovery key and a service provider identifier; and

the instructions to store the active state associated the token identifier of the active token comprise instructions to store the active state in a data container accessible based on an access code generated based on a combination of the token identifier of the active token and the service provider identifier.

29. The system of claim 23, further comprising instructions to:

receive an encryption algorithm identifier from the recovery key; and

store the received encryption algorithm identifier on the token.

30. The system of claim 23, wherein the instructions to receive the user identifier and the one or more encryption keys from the recovery key comprise instructions to store the user identifier and the one or more encryption keys in a storage location accessible based on a combination of a service provider identifier and a code.

31. The system of claim 23, wherein the instructions to activate the token comprise instructions to:

request the passcode from a user;

in response to the request, receive the passcode from a user; and

upon verification of the passcode, activate the token by updating state information associated with the token.