Tokenizing Sensitive Data

• US 20120304273A1
• Filed: 05/27/2011
• Published: 11/29/2012
• Est. Priority Date: 05/27/2011
• Status: Active Grant

• Current Assignee: Worldpay, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Fifth Third Processing Solutions, LLC (Fidelity National Information Services Incorporated)
• Inventors: Bailey, Bryan T., Romer, John, Doyle, Chris, Gifford, Jeremy, Zibart, Kevin
• Granted Patent: US 8,943,574 B2
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06F 21/60 Protecting data
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Included are embodiments for tokenizing sensitive data. Some embodiments of systems and/or methods are configured to receive sensitive data from a vendor, determine a token key for the vendor, and utilize a proprietary algorithm, based on the token key to generate a vendor-specific token that is associated with the sensitive data. Some embodiments include creating a token identifier that comprises data related to the token key sending the vendor-specific token and the token identifier to the vendor.

Claims

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

receiving sensitive data from a vendor;

determining a token key for the vendor;

utilizing a proprietary algorithm, selected based on the token key, to generate a vendor-specific token that is associated with the sensitive data;

creating a token identifier that comprises data related to the token key; and

sending the vendor-specific token and the token identifier to the vendor.

2. The method of claim 1, further comprising decrypting the sensitive data from the vendor.

3. The method of claim 1, wherein the data related to the token key includes an identification of a token key version and wherein the token key includes a sanity value for determining accuracy of the vendor-specific token.

4. 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 bank account number, a social security number, a telephone number, and an address.

5. The method of claim 1, further comprising:

receiving a request to cancel a transaction with the vendor, wherein the request comprises the vendor-specific token and the token identifier;

determining from the token identifier, the token key;

utilizing the token key to generate the sensitive data; and

utilizing the sensitive data to cancel the transaction.

6. The method of claim 1, further comprising:

receiving a request to change the vendor-specific token, wherein the request is accompanied by the vendor-specific token and the token identifier;

identifying from the token identifier, the token key for the vendor-specific token;

utilizing the token key to generate an updated token; and

updating the token identifier to reflect the updated token.

7. The method of claim 1, further comprising generating a rollup identifier associated with the vendor-specific token, wherein the rollup identifier provides a pointer to a common token key for a plurality of entities.

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

a memory component that stores logic that when executed by the system, causes the system to perform at least the following;

receive sensitive data from a vendor;

determine a token key for the vendor, the token key identifying a proprietary algorithm for generating a token;

utilize the proprietary algorithm, selected based on the token key, to generate a vendor-specific token that is associated with the sensitive data;

create a token identifier that comprises data related to the token key; and

send the vendor-specific token and the token identifier to the vendor.

9. The system of claim 8, wherein the logic further causes the system to decrypt the sensitive data from the vendor.

10. The system of claim 8, wherein the data related to the token key includes an identification of a token key version and wherein the token key includes a sanity value for determining accuracy of the vendor-specific token.

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

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

receive a request to cancel a transaction with the vendor, wherein the request comprises the vendor-specific token and the token identifier;

determine from the token identifier, the token key;

utilize the token key to generate the sensitive data; and

utilize the sensitive data to cancel the transaction.

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

receive a request to change the vendor-specific token, wherein the request is accompanied by the vendor-specific token and the token identifier;

identify from the token identifier, the token key for the vendor-specific token;

utilize the token key to generate an updated token; and

update the token identifier to reflect the updated token.

14. The system of claim 8, 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 common token key for a plurality of entities.

15. 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 sensitive data from a vendor;

determine whether the sensitive data has previously been tokenized;

in response to determining that the sensitive data has previously been tokenized, retrieve a stored token and a stored token identifier from a data storage component and send the stored token and the stored token identifier to the vendor;

in response to determining that the sensitive data has not previously been tokenized;

determine a token key for the vendor;

utilize a proprietary algorithm, based on the token key to generate a generated token that is associated with the sensitive data;

create a token identifier that comprises data related to the token key; and

send the generated token and the token identifier to the vendor.

16. The non-transitory computer-readable medium of claim 15, wherein the program further causes the computing device to decrypt the sensitive data from the vendor.

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

18. The non-transitory computer-readable medium of claim 15, wherein the token key includes a sanity value for determining accuracy of the generated token and wherein the data related to the token key includes an identification of a token key version.

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

receive a request to cancel a transaction with the vendor, wherein the request comprises the generated token and the token identifier;

determine from the token identifier, the token key;

utilize the token key to generate the sensitive data; and

utilize the sensitive data to cancel the transaction.

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

receive a request to change the generated token, wherein the request is accompanied by the generated token and the token identifier;

identify from the token identifier, the token key for the generated token;

utilize the token key to generate an updated token; and

update the token identifier to reflect the updated token.