TOKEN IDENTITY DEVICES

• US 20180189780A1
• Filed: 02/28/2018
• Published: 07/05/2018
• Est. Priority Date: 04/24/2015
• Status: Active Grant

• Current Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Original Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Granted Patent: US 10,915,890 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/321 using wearable devices
• CPC Class Codes: G06Q 20/363 with the personal data of a user
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety

Abstract

Disclosed embodiments include methods, systems, and computer-readable media configured to provide wearable devices storing tokens associated with digital versions of physical documents/cards. The wearable devices may further transfer tokens securely to interested parties without Bluetooth® or other network connectivity beyond NFC radio. In some embodiments, a token vault operator system may receive a request to establish a token vault account for a user, authenticate an identity of the user based at least on the received request, and generating a token vault ID associated with the user. The token vault operator system may further configure access to data sets generated for and associated with the token vault ID, generate tokens associated with the token vault ID, each token corresponding to one of the one or more data sets, and provide the generated plurality of tokens associated with the token vault ID to at least one user device.

Claims

1-20. -20. (canceled)

21. A system comprising:

at least one network communication device;

a storage device comprising instructions; and

at least one processor configured to execute the instructions to perform operations comprising;

generating a plurality of tokens associated with a token vault identification (ID), wherein the token vault ID is associated with a first user device and each token of the plurality of tokens associated with the token vault ID corresponds to one of one or more datasets;

receiving, via the at least one network device, a request to reprovision a token in the plurality of tokens, the token corresponding to a first data set in the one or more datasets;

dissociating the first token from the token vault ID;

generating a new token;

associating the new token with the token vault ID, the new token corresponding to the first data set;

determining a second user device in need of the generated new token; and

providing, via the at least one network device, the generated new token associated with the token vault ID to the second user device.

22. The system of claim 21, wherein the first or second user device is a wearable device.

23. The system of claim 21, the operations further comprising:

receiving a request for the first data set from the first user device, the request comprising the first token; and

denying access to the first data set based on the determination that the first token is dissociated from the token vault ID.

24. The system of claim 21, the operations further comprising:

receiving a request for the first data set from the second user device, the request comprising the new token; and

granting access to the first data set based on the determination that the new token is associated with the token vault ID.

25. The system of claim 21, wherein determining a second user device in need of the generated new token is based on determining that the second user device is associated with the first token.

26. The system of claim 25, wherein the first user device is the same or different from the second user device.

27. The system of claim 21, wherein a requestor device sends a request to reprovision the first token by receiving an interaction from the user.

28. The system of claim 21, the operations further comprising sending an indication to a requestor device representing that the new token is associated.

29. The system of claim 21, wherein the system comprises a binary addressing switch panel or a plurality of multipole toggle switches.

30. The system of claim 21, wherein determining a second user device in need of the generated new token is based on receiving, from the second user device, a request to provision a token.

31. The system of claim 30, the operations further comprising authenticating an identity of a user associated with the first user device based on the received request.

32. The system of claim 21, the operations further comprising configuring one or more token classes associated with the token vault ID, and wherein the one or more data sets comprise a data set for each of the one or more token classes.

33. The system of claim 21, further comprising a database configured to store the plurality of tokens.

34. The system of claim 21, the operations further comprising accessing the database to retrieve token information associated with the token identified in the request, the token information comprising at least:

(i) a link account number that indicates a funding account, a financial service provider associated with the funding account, and a payment network and (ii) one or more user preferences associated with the token.

35. The system of claim 34, the operations further comprising providing the generated new token associated with the token vault ID to the second user device according to the one or more user preferences.

36. A method comprising:

generating a plurality of tokens associated with a token vault identification (ID), wherein the token vault ID is associated with a first user device and each token of the plurality of tokens associated with the token vault ID corresponds to one of one or more datasets;

receiving, via a communication network, a request to reprovision a token in the plurality of tokens, the token corresponding to a first data set in the one or more datasets;

dissociating the first token from the token vault ID;

generating a new token;

associating the new token with the token vault ID, the new token corresponding to the first data set;

determining a second user device in need of the generated new token; and

providing, via the communication network, the generated new token associated with the token vault ID to the second user device.

37. The method of claim 36, further comprising:

receiving a request for the first data set from the user, the request comprising the first token; and

denying access to the first data set based on the determination that the first token is dissociated from the token vault ID.

38. The system of claim 36, further comprising:

receiving a request for the first data set from the second user device, the request comprising the new token; and

granting access to the first data set based on the determination that the new token is associated with the token vault ID.

39. The method of claim 36, further comprising providing the generated new token associated with the token vault ID to the second user device according to one or more user preferences.

40. A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

generating a plurality of tokens associated with a token vault identification (ID), wherein the token vault ID is associated with a first user device and each token of the plurality of tokens associated with the token vault ID corresponds to one of one or more datasets;

receiving, via a communication network, a request to reprovision a token in the plurality of tokens, the token corresponding to a first data set in the one or more datasets;

dissociating the first token from the token vault ID;

generating a new token;

associating the new token with the token vault ID, the new token corresponding to the first data set;

determining a second user device in need of the generated new token; and

providing, via the communication network, the generated new token associated with the token vault ID to the second user device.