Centralized system for sensitive data conversion

A centralized data conversion architecture comprising non-transitory computer-readable media and a processor, the architecture utilizing computer-executable instructions stored on the media and executed by the processor for converting data into secure data via a centralized application programming interface (“API”), the centralized data conversion architecture comprising:

• one or more external networks in communication with an internal network via a communication, platform;
• a first firewall residing between the communication platform and one or more external platforms;
• a second firewall residing between the communication platform and the internal network, the internal network comprising:
• one or more internal APIs operating as a gateway to the centralized data conversion API for converting sensitive data to fictional data, the fictional data being transmitted to the external networks;
• two or more data repositories storing data associated with an entity of the internal network, the data is accessed via the one or more internal APIs, each data file comprising a user profile, each user profile comprising field names and associated value pairs, wherein each of the value pairs comprises non-sensitive data and sensitive data, the sensitive data comprising sensitive data strings, the sensitive data strings including a first sensitive data string and a second sensitive data string, and the non-sensitive data comprising one or more non-sensitive data strings;
• and
• wherein, prior to a transmission of data to one or more of the external networks, the one or more internal APIs are configured to, via the processor:
• retrieve the data from the data repositories;
• transmit the data to the centralized data conversion API, wherein the centralized data conversion API is configured to:
• search the data files for two or more user profiles associated with a user;
• identify two user profiles associated with the user, wherein the two user profiles are matching user profiles;
• for the data files comprising the matching user profiles, synchronize each of the sensitive data strings within the matching user profiles by:
• selecting a conversion algorithm from a plurality of conversion algorithms for the matching user profiles;
• and
• using the selected conversion algorithm, securing the data files comprising the matching user profiles by converting each of the sensitive data strings into fictional da ta strings within the matching user profiles, the converting comprising:
• for the first sensitive data stringy replacing each character in the first sensitive data string with a replacement character;
• and
• for the second sensitive data string;
• replacing a first sub-set of characters within the second sensitive data string with a third sub-set of characters;
• and
• maintaining a second sub-set of characters within the second sensitive data string;
• and
• following the converting, transmitting the data files comprising the matching user profiles to the external network;
• and
• for the data files comprising each of a non-matching user profile, the centralized data conversion API is further configured to:
• determine a file-type for each non-matching user profile within the data file;
• for each non-matching riser profile, select a conversion application from a plurality of conversion applications that supports the file-type of the non-matching user profile;
• using the selected conversion application, securing the data files comprising the non-matching user profiles by converting each of the sensitive data strings into fictional data strings within the non-matching user profile, the convening comprising:
• for the first sensitive data string, replacing each character in the first sensitive data string with a replacement character;
• and
• for the second sensitive data string, replacing a first sub-set of characters within the second sensitive data string with a third sub-set of characters, and maintaining a second sub-set of characters within the second sensitive data string;
• and
• following the converting, transmit each non-matching user profile within the data file to the internal API;
• and
• the internal API is further configured to transmit each non-matching user profile within the data file, via the communication platform, to the one or more external networks.