Intelligent systems for identifying transactions associated with an institution impacted by an event using a dashboard

A transaction processing system communicatively coupled to a plurality of external institutions, the transaction processing system comprising:

• a memory that stores executable instructions and a plurality of accounts associated with the plurality of external institutions, wherein each external institution is associated with at least one account;
• and
• one or more hardware processors coupled to the memory, wherein the executable instructions are executed by the one or more hardware processors to cause the one or more hardware processors to:
• receive files from the plurality of external institutions;
• for each file:
• uncompress the received file into a plurality of transactions in a data file;
• load a copy of the plurality of transactions in a data structure in a transaction memory;
• receive a notification of a cyber event;
• create a circuit breaker event (CBE) data file;
• identify, from the notification, the cyber event and an entity comprising one or more of a country, an institution, and a payment system associated with the cyber event;
• assign a CBE identifier (ID) corresponding to the CBE and store the CBE ID in the CBE data file, the CBE ID including the cyber event and the entity;
• identify, in the memory, a set of accounts associated with the entity and the cyber event;
• store an account ID for each affected account of the one or more affected accounts in the CBE data file;
• generate a conditional rule corresponding to the CBE ID, the conditional rule comprising a set of rules including a condition associated with the account ID and an action if the condition is satisfied;
• store the record of the conditional rule in the CBE data file;
• determine, based on the conditional rule, whether to process a transaction according to the set of rules, wherein
• if the transaction does not satisfy the condition of the conditional rule:
• process the transaction according to the set of rules;
• store a record of the processed transaction in a processed transaction memory;
• and
• store information for the processed transaction in the CBE data file;
• if the transaction satisfies the condition of the conditional rule:
• store the transaction in the CBE data file as an impacted transaction;
• and
• store information for the impacted transaction in the CBE data file;
• calculate a total number of impacted transactions for each account ID, a total transaction amount for each account ID, a total number of account IDs having at least one impacted transaction, a total number of impacted transactions for the total number of account IDs, and a total transaction amount for the total number of account IDs;
• display the CBE ID, the conditional rule, and one or more of the total number of impacted transactions for each account ID, the total transaction amount for each account ID, the total number of account IDs having at least one impacted transaction, the total number of impacted transactions for the total number of account IDs, and the total transaction amount for the total number of account IDs;
• determine if each impacted transaction should be a released transaction or a cancelled transaction;
• send information relating to each cancelled transaction to the CBE data file;
• and
• process each released transaction based on transaction information of the released transaction.

A computer program product comprising executable instructions stored in a non-transitory computer readable medium that when executed by a processor causes the processor to:

• cause a memory to store a plurality of accounts associated with the plurality of external institutions, wherein each external institution is associated with at least one account;
• receive files from the plurality of external institutions, each file including a plurality of transactions;
• receive a notification of a cyber event:
• create a circuit breaker event (CBE) data file;
• identify, from the notification, an event type and an entity comprising one or more of a country, an institution, and a payment system associated with the event type;
• assign a CBE identifier (ID) corresponding to the CBE and store the CBE ID in the CBE data file, the CBE ID including the event type and the entity;
• and
• receive a circuit breaker notification including the CBE ID;
• identify a set of accounts associated with the entity and the event type;
• store the account ID for each affected account of the one or more affected accounts in the CBE data file;
• generate a conditional rule corresponding to the CBE ID, the conditional rule comprising a set of rules including a condition associated with the account ID and an action if the condition is satisfied;
• store the record of the conditional rule in the CBE data file;
• determine, based on the conditional rule, whether to process a transaction according to the set of rules, wherein:
• if the transaction does not satisfy the condition of the conditional rule:
• process the transaction according to the set of rules;
• store a record of the processed transaction in a processed transaction memory;
• and
• store information for the processed transaction in the CBE data file;
• if the transaction satisfies the condition of the conditional rule:
• store the transaction in the CBE data file as an impacted transaction;
• store information for the impacted transaction in the CBE data file;
• and
• calculate a total number of impacted transactions for each account ID, a total transaction amount for each account ID, a total number of account IDs having at least one impacted transaction, a total number of impacted transactions for the total number of account IDs, and a total transaction amount for the total number of account IDs;
• display the CBE ID, the conditional rule, and one or more of the total number of impacted transactions for each account ID, the total transaction amount for each account ID, the total number of account IDs having at least one impacted transaction, the total number of impacted transactions for the total number of account IDs, and the total transaction amount for the total number of account IDs;
• determine if each impacted transaction should be a released transaction or a cancelled transaction;
• send information relating to each cancelled transaction to the CBE data file;
• and
• process each released transaction based on transaction information of the released transaction.