Tokenizing sensitive data

1. A method for tokenization of sensitive data, comprising:

receiving, by a tokenization computing device, sensitive data from a vendor computing device associated with a vendor;

generating, by the tokenization computing device, a vendor-specific token that is associated with the sensitive data;

receiving, by the tokenization computing device, a request to change the vendor-specific token;

generating, by the tokenization computing device, a new token for associating with the sensitive data;

receiving, by the tokenization computing device, an indication of joining of the vendor with a second entity, wherein the indication includes a request to associate the new token with a second token from the second entity;

updating, by the tokenization computing device, the new token and a token identifier associated with the new token to generate a rollup identifier that points to a common token key for the vendor and the second entity; and

sending, by the tokenization computing device, the updated new token and the updated token identifier to the vendor, wherein the updated token identifier is configured to provide token generation data and a sanity value.

2. The method of claim 1 , further comprising:

receiving, by the tokenization computing device, a request to rotate the updated new token;

accessing, by the tokenization computing device, a table to determine whether the updated new token is associated with the rollup identifier;

in response to determining that the updated new token is associated with the rollup identifier, determining, by the tokenization computing device, the common token key that is utilized for entities in a predetermined group;

updating, by the tokenization computing device, a third token from a third entity according to the common token key; and

sending, by the tokenization computing device, the updated third token to the vendor.

3. The method of claim 1 , wherein the vendor specific-token is based on at least in part on a token key, wherein the token key is unique to the vendor.

4. The method of claim 1 , wherein the new token is generated utilizing a new token key for the vendor.

5. The method of claim 1 , wherein the sanity value validates the tokenization of the updated new token.

6. A system for tokenization of sensitive data, comprising:

a processor; and

a memory component that is coupled to the computing device and stores logic that when executed by the processor, causes the system to perform at least the following:

receive sensitive data from a vendor computing device associated with a vendor;

determine a token key for the vendor;

generate a vendor-specific token associated with the sensitive data;

generate a token identifier associated with the vendor-specific token, the token identifier comprising data related to the token key;

link the vendor-specific token and the token identifier in a database;

receive, from the vendor computing device, a request to change the vendor-specific token, wherein the request is accompanied by the token identifier that is associated with the vendor-specific token, wherein the token identifier is configured to provide token generation data and a sanity value;

utilize the token identifier to determine a location of the sensitive data;

retrieve the sensitive data;

generate a new token for associating with the sensitive data; and

send the new token and the token identifier to the vendor computing device.

7. The system of claim 6 , wherein the sensitive data includes at least one of the following: a credit card number, a debit card number, a prepaid card number, a social security number, a bank account number, a telephone number, and an address.

8. The system of claim 6 , wherein the logic further causes the system to store the new token and the token identifier.

9. The system of claim 6 , wherein the logic further causes the system to generate a rollup identifier associated with the vendor-specific token, wherein the rollup identifier provides a pointer to a token key, wherein the token key is common to a plurality of entities.

10. The system of claim 6 , wherein the logic further causes the system to perform at least the following:

receive a request to rotate the new token;

access a table to determine whether the new token is associated with a rollup identifier;

in response to determining that the new token is associated with a rollup identifier, determine a new token key that is utilized for entities in a predetermined group;

update the new token according to the new token key; and

send the updated new token and the token identifier to the vendor computing device.

11. A non-transitory computer-readable medium for tokenization of sensitive data that stores a program that when executed by a computing device, causes the computing device to perform at least the following:

receive a request to change a token that is associated with sensitive data, wherein the token is generated based at least in part on a token key that is unique to a vendor, wherein the request is accompanied by a token identifier that is associated with the token, and wherein the token and the token identifier are linked in a database, and the token identifier is configured to provide token generation data and a sanity value;

identify the token key and a version for the token from the token identifier;

generate a new token for associating with the sensitive data;

receive an indication of joining of the vendor with a second entity, wherein the

indication includes a request to associate the new token with a second token from the second entity;

update the new token and the token identifier to generate a rollup identifier that points to a common token key to the vendor and the second entity; and

send the updated new token and the token identifier to a vendor computing devices.

12. The non-transitory computer-readable medium of claim 11 , wherein the sensitive data includes at least one of the following: a credit card number, a debit card number, a prepaid card number, a bank account number, a social security number, a telephone number, and an address.

13. The non-transitory computer-readable medium of claim 11 , wherein the program further causes the computing device to perform at least the following:

receive a request to rotate the updated new token;

access a table to determine whether the updated new token is associated with the rollup identifier;

in response to determining that the updated new token is associated with the rollup identifier, determine the common token key that is utilized for entities in a predetermined group; and

update a third token from a third entity according to the common token key.

14. The non-transitory computer-readable medium of claim 11 , wherein the program further causes the computing device to store the updated new token and the token identifier.