Tokenizing sensitive data
AssigneeVantiv, LLC
InventorsBryan T. Bailey, John Romer, Chris Doyle, Jeremy Gifford, Kevin Zibart
Life of this patent
Estimating the term…
Abstract
Included are systems and methods for tokenizing sensitive data. Some of the 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 systems and/or methods 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.
Claims14
A method for tokenization of sensitive data, comprising:
- receiving, by a computing device, sensitive data from a vendor;
- determining, by the computing device, a token key for the vendor, wherein the token key is unique to the vendor;
- linking, by the computing device, the token and the token identifier to provide token generation data, token version data, token key data, and a sanity value;
- utilizing, by the computing device, a proprietary algorithm, selected based on the token key, to generate a vendor-specific token that is associated with the sensitive data;
- creating, by the computing device, a token identifier that comprises data related to the token key;
- sending, by the computing device, the vendor-specific token and the token identifier to the vendor;
- receiving, by the computing device, a request to cancel a transaction with the vendor, wherein the request comprises the vendor-specific token and the token identifier;
- determining, by the computing device, from the token identifier, the token key;
- utilizing, by the computing device, the token key to generate the sensitive data;
- and
- utilizing, by the computing device, the sensitive data to cancel the transaction, wherein the data related to the token key includes an identification of a token key version and wherein the token key includes the sanity value for determining accuracy of the vendor-specific token.
A system for tokenization of sensitive data, comprising:
- a computing device;
- and
- a memory component that is coupled to the computing device and 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, the token identifier further providing token version data and a sanity value, wherein the sanity value is utilized for determining accuracy of the vendor-specific token;
- send the vendor-specific token and the token identifier to the vendor;
- 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.
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, wherein the token identifier additionally comprises token generation data, token version data, and a sanity value, wherein the sanity value is utilized for determining accuracy of the vendor-specific token, and wherein the data related to the token key includes an identification of a token key version;
- send the generated token and the token identifier to the vendor;
- 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.
Dependencies are inferred from the claim text.