Tokenization and encryption for secure data transfer

A non-transitory computer readable medium comprising stored instructions for securing data, the instructions when executed by at least one processor cause the at least one processor to:

• receive a transaction request file including transaction requests, each transaction request having a set of fields;
• generate a first modified transaction request file by replacing, for each transaction request, untokenized values of a subset of the fields with tokenized values;
• for each transaction request, store, in a datastore, a representation of the untokenized values in conjunction with an identifier of the transaction request in the modified transaction request file, the identifier generated from the tokenized values;
• determine a total number of transaction requests in the first modified transaction request file;
• compare the total number of transaction requests to a minimum request threshold;
• and
• generate, responsive to determining that the total number of transaction requests is less than the minimum request threshold, a new modified transaction request file by:
• combining the one or more transaction requests of the first modified transaction request file and one or more transaction requests of a second modified transaction request file such that the combined transaction requests is equivalent to or greater than the minimum request threshold;
• send the new modified transaction request file to a first destination;
• detokenize the first modified transaction request file by, for each transaction request:
• regenerating the identifier of the transaction request from the tokenized values;
• querying the datastore using the identifier of the transaction request to retrieve the representation of the untokenized values;
• and
• replacing the tokenized values with the untokenized values using the representation of the untokenized values;
• and
• send the detokenized modified transaction request file to a second destination.

A method for securing data, the method comprising:

• receiving a transaction request file including transaction requests, each transaction request having a set of fields;
• generating a first modified transaction request file by replacing, for each transaction request, untokenized values of a subset of the fields with tokenized values;
• for each transaction request, storing, in a datastore, a representation of the untokenized values in conjunction with an identifier of the transaction request in the first modified transaction request file, the identifier of the transaction request generated from the tokenized values;
• determining a total number of transaction requests in the first modified transaction request file;
• comparing the total number of transaction requests to a maximum request threshold;
• generating, responsive to determining that the total number of transaction requests is greater than the maximum request threshold, a plurality of new modified transaction request files by:
• dividing the one or more transaction requests of the first modified transaction request file among the plurality of new modified transaction request files such that each of the total number of transaction requests in the plurality of new modified transaction request files is less than the maximum request threshold;
• sending the new modified transaction request file to a first destination;
• detokenizing the first modified transaction request file by, for each transaction request:
• regenerating the identifier of the transaction request from the tokenized values;
• querying the datastore using the identifier of the transaction request to retrieve the representation of the untokenized values;
• and
• replacing the tokenized values with the untokenized values using the representation of the untokenized values;
• and
• sending the detokenized modified transaction request file to a second destination.