Token identity devices
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.
1. A system, comprising:
a database configured to store a plurality of tokens, each token of the plurality of tokens associated with one or more token vault IDs;
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:
receiving a request to establish a token vault account for a user, the request comprising at least one of customer identification information, medical history information, or an access credential to an external data set;
authenticating an identity of the user based at least on the received request;
generating a token vault ID associated with the user;
configuring access to one or more data sets generated for and associated with the token vault ID, the one or more data sets being stored in the database or at least one external storage database;
generating a plurality of tokens associated with the token vault ID, each token of the plurality of tokens associated with the token vault ID corresponding to one of the one or more data sets;
providing the generated plurality of tokens associated with the token vault ID to at least one user device;
receiving, by a requestor device, a token and a request for information associated with the received token;
determining that a token class of the received token matches an entity type associated with the requestor device; and
providing the requested information to the requestor device based in part on the determined match.
2. The system of claim 1 , the operations further comprising:
identifying a first token from among the generated plurality of tokens based on the received token; and
accessing one or more permissions associated with the identified first token, wherein the requested information is further provided to the requestor device based on the accessed one or more permissions.
3. The system of claim 1 , wherein the received token corresponds to a token passed to the requestor device by NFC radio from the at least one user device.
4. The system of claim 1 , wherein receiving the request comprises receiving the request from the user device.
5. The system of claim 1 , the operations further comprising configuring one or more token classes associated with the token vault ID.
6. The system of claim 5 , wherein the one or more data sets comprise a data set for each of the one or more token classes.
7. The system of claim 1 , the operations further comprising:
receiving a request to reprovision a first token in the generated plurality of tokens, the first token corresponding to a first data set in the one or more data sets;
dissociating the first token from the token vault ID;
generating a new token associated with the token vault ID, the new token corresponding to the first data set; and
providing the generated new token associated with the token vault ID to the least one user device.
8. A method, comprising:
receiving a request to establish a token vault account for a user, the request comprising at least one of customer identification information, medical history information, or an access credential to an external data set;
authenticating an identity of the user based at least on the received request;
generating a token vault ID associated with the user;
configuring access to one or more data sets generated for and associated with the token vault ID, the one or more data sets being stored in a database;
generating a plurality of tokens associated with the token vault ID, each token of the plurality of tokens associated with the token vault ID corresponding to one of the one or more data sets;
providing the generated plurality of tokens associated with the token vault ID to at least one user device;
receiving, by a requestor device, a token and a request for information associated with the received token;
determining that a token class of the received token matches an entity type associated with the requestor device; and
providing the requested information to the requestor device based in part on the determined match.
9. The method of claim 8 , further comprising:
identifying a first token from among the generated plurality of tokens based on the received token; and
accessing one or more permissions associated with the identified first token, wherein the requested information is further provided to the requestor device based on the accessed one or more permissions.
10. The method of claim 8 , wherein the received token corresponds to a token passed to the requestor device by NFC radio from the at least one user device.
11. The method of claim 8 , wherein receiving the request comprises receiving the request from the user device.
12. The method of claim 8 , further comprising configuring one or more token classes associated with the token vault ID.
13. The method of claim 12 , wherein the one or more data sets comprise a data set for each of the one or more token classes.
14. The method of claim 8 , the method further comprising:
receiving a request to reprovision a first token in the generated plurality of tokens, the first token corresponding to a first data set in the one or more data sets;
dissociating the first token from the token vault ID;
generating a new token associated with the token vault ID, the new token corresponding to the first data set; and
providing the generated new token associated with the token vault ID to the least one user device.
15. 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:
receiving a request to establish a token vault account for a user, the request comprising at least one of customer identification information, medical history information, or an access credential to an external data set;
authenticating an identity of the user based at least on the received request;
generating a token vault ID associated with the user;
configuring access to one or more data sets generated for and associated with the token vault ID, the one or more data sets being stored in a database;
generating a plurality of tokens associated with the token vault ID, each token of the plurality of tokens associated with the token vault ID corresponding to one of the one or more data sets;
providing the generated plurality of tokens associated with the token vault ID to at least one user device;
receiving, by a requestor device, a token and a request for information associated with the received token;
determining that a token class of the received token matches an entity type associated with the requestor device; and
providing the requested information to the requestor device based in part on the determined match.
16. The non-transitory computer readable medium of claim 15 , further comprising:
identifying a first token from among the generated plurality of tokens based on the received token; and
accessing one or more permissions associated with the identified first token, wherein the requested information is further provided to the requestor device based on the accessed one or more permissions.
17. The non-transitory computer readable medium of claim 15 , wherein the received token corresponds to a token passed to the requestor device by NFC radio from the at least one user device.
18. The non-transitory computer readable medium of claim 15 , further comprising configuring one or more token classes associated with the token vault ID.
19. The non-transitory computer readable medium of claim 18 , wherein the one or more data sets comprise a data set for each of the one or more token classes.
20. The non-transitory computer readable medium of claim 15 , the method further comprising:
receiving a request to reprovision a first token in the generated plurality of tokens, the first token corresponding to a first data set in the one or more data sets;
dissociating the first token from the token vault ID;
generating a new token associated with the token vault ID, the new token corresponding to the first data set; and
providing the generated new token associated with the token vault ID to the least one user device.