| CPC G06Q 40/02 (2013.01) [G06F 16/9017 (2019.01); G06F 17/18 (2013.01)] | 20 Claims |
|
1. A system for identifying complete account identifiers from partial account identifiers, the system comprising an account identification computing device comprising at least one processor and a memory device in communication with the at least one processor, the processor further in communication with an interchange network, the at least one processor configured to:
receive messages communicated over the interchange network, the messages transmitted over the interchange network formatted according to a proprietary communications standard for requesting payment transactions;
extract, from the messages communicated over the interchange network based on the proprietary communications standard, transaction data for a plurality of transactions, wherein the transaction data for each of the plurality of transactions includes a unique merchant identifier and an account identifier;
build a merchant table using the transaction data for storage within a database, the merchant table stored within the database and including a plurality of merchant profiles, each of the merchant profiles including i) one of the unique merchant identifiers included in the plurality of transactions and ii) at least one account identifier associated with the unique merchant identifier;
identify, for each of the unique merchant identifiers included in the merchant table, a merchant name associated with the unique merchant identifier;
parse the plurality of merchant profiles included in the merchant table to retrieve and consolidate all unique merchant identifiers that are associated with the same merchant name;
generate a data file for each consolidated group of unique merchant identifiers, each data file storing a list of the consolidated unique merchant identifiers in association with a single cleansed merchant name;
build, using the generated data files, an updated merchant table that includes a plurality of updated merchant profiles, each updated merchant profile including one of the cleansed merchant names and a plurality of account identifiers associated with that cleansed merchant name, wherein a number of updated merchant profiles in the updated merchant table is less than a number of merchant profiles in the merchant table;
receive a list including a plurality of partial account identifiers that correspond to potentially exposed account identifiers;
perform a lookup within the database to determine a number of candidate account identifiers associated with each cleansed merchant name in the updated merchant table, wherein the candidate account identifiers are complete account identifiers associated one of with the cleansed merchant names that are at least a partial match to a partial account identifier on the list;
calculate, for each cleansed merchant name in the updated merchant table, at least one metric based on the number of candidate account identifiers associated with the respective cleansed merchant name;
identify, from among the cleansed merchant names in the updated merchant table, a source cleansed merchant name corresponding to a likely common source of the plurality of partial account identifiers based on the at least one metric;
match at least one candidate account identifier to a complete account identifier associated with the cleansed merchant name by matching one of the plurality of partial account identifiers linked to the source cleansed merchant name to the at least one candidate account identifier to output a matched account identifier, thereby identifying the matched account identifier as one of the potentially exposed account identifiers corresponding to the received list;
store a list of the matched account identifiers in the database, the list of the matched account identifiers flagged as high risk for being involved in a data breach event; and
transmit a message to an issuer of the at least one matched account identifier from the list of the matched account identifiers advising the issuer that the at least one matched account identifier was exposed to a data breach and susceptible to future fraudulent transactions.
|