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;

determining, by the tokenization computing device, a token key based on the vendor associated with the sensitive data;

generating, by the tokenization computing device, a vendor-specific token associated 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 vendor-specific token with a second token associated with the second entity;

generating, by the tokenization computing device, a rollup identifier that points to a common token key for the vendor and the second entity;

storing, by the tokenization computing device, the rollup identifier in a lookup table;

generating, by the tokenization computing device, a token identifier associated with the sensitive data, wherein the token identifier identifies at least one of: the token key or a sanity value;

receiving, by the tokenization computing device, a request to cancel an electronic transaction, the request including the vendor-specific token and the token identifier;

determining, by the tokenization computing device, the token key based on the token identifier;

generating, by the tokenization computing device, sensitive data associated with the electronic transaction based on the token key; and

verifying, by the tokenization computing device, an accuracy of the generated sensitive data using the token identifier.

2. The method of claim 1 , further comprising:

cancelling, by the tokenization computing device, the electronic transaction upon verifying the accuracy of the generated sensitive data using the token identifier; and

sending, by the tokenization computing device, a confirmation of the cancellation to the vendor computing device.

3. The method of claim 1 , 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.

4. The method of claim 1 , wherein the token key is unique to the vendor.

5. The method of claim 1 , wherein the vendor-specific token is one of a plurality of tokens associated with a plurality of token identifiers.

6. The method of claim 5 , wherein the plurality of tokens is received in a token batch.

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

one or more processors; and

a memory storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations for tokenization of sensitive data, the operations comprising:

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

determining, by the tokenization computing device, a token key based on the vendor associated with the sensitive data;

generating, by the tokenization computing device, a vendor-specific token associated 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 vendor-specific token with a second token associated with the second entity;

generating, by the tokenization computing device, a rollup identifier that points to a common token key for the vendor and the second entity;

storing, by the tokenization computing device, the rollup identifier in a lookup table;

generating, by the tokenization computing device, a token identifier associated with the sensitive data, wherein the token identifier identifies at least one of: the token key or a sanity value;

receiving, by the tokenization computing device, a request to cancel an electronic transaction, the request including the vendor-specific token and the token identifier;

determining, by the tokenization computing device, the token key based on the token identifier;

generating, by the tokenization computing device, sensitive data associated with the electronic transaction based on the token key; and

verifying, by the tokenization computing device, an accuracy of the generated sensitive data using the token identifier.

8. The system of claim 7 , the operations further comprising:

cancelling, by the tokenization computing device, the electronic transaction upon verifying the accuracy of the generated sensitive data using the token identifier; and

sending, by the tokenization computing device, a confirmation of the cancellation to the vendor computing device.

9. The system of claim 7 , 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.

10. The system of claim 7 , wherein the token key is unique to the vendor.

11. The system of claim 7 , wherein the vendor-specific token is one of a plurality of tokens associated with a plurality of token identifiers.

12. A non-transitory computer-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations for tokenization of sensitive data, the operations comprising:

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

determining, by the tokenization computing device, a token key based on the vendor associated with the sensitive data;

generating, by the tokenization computing device, a vendor-specific token associated 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 vendor-specific token with a second token associated with the second entity;

generating, by the tokenization computing device, a rollup identifier that points to a common token key for the vendor and the second entity;

storing, by the tokenization computing device, the rollup identifier in a lookup table;

generating, by the tokenization computing device, a token identifier associated with the sensitive data, wherein the token identifier identifies at least one of: the token key or a sanity value;

receiving, by the tokenization computing device, a request to cancel an electronic transaction, the request including the vendor-specific token and the token identifier;

determining, by the tokenization computing device, the token key based on the token identifier;

generating, by the tokenization computing device, sensitive data associated with the electronic transaction based on the token key; and

verifying, by the tokenization computing device, an accuracy of the generated sensitive data using the token identifier.

13. The non-transitory computer-readable medium of claim 12 , the operations further comprising:

cancelling, by the tokenization computing device, the electronic transaction upon verifying the accuracy of the generated sensitive data using the token identifier; and

sending, by the tokenization computing device, a confirmation of the cancellation to the vendor computing device.

14. The non-transitory computer-readable medium of claim 12 , 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.

15. The non-transitory computer-readable medium of claim 12 , wherein the token key is unique to the vendor.

16. The non-transitory computer-readable medium of claim 12 , wherein the vendor-specific token is one of a plurality of tokens associated with a plurality of token identifiers.

17. The non-transitory computer-readable medium of claim 16 , wherein the plurality of tokens is received in a token batch.