Rule based transaction authorization server

A system for reducing a response time of a transaction approval process, the system comprising:

• a rule management server having a first response time in applying a transaction rule, the rule management server comprising a first processor and first memory, the first memory configured to store a first set of code instructions, the first set of code instructions, when executed by the first processor, causes the first processor to:
• store a volume of data associated with a plurality of fields of third-party named entities,
• receive a transaction rule that includes a third-party named entity restriction,
• extract a set of tags from the transaction rule, the set of tags identifying columns of the volume of data for the third-party named entity restriction to apply based on relevant fields of third-party named entities,
• identify a set of columns in the volume of data based on the set of tags, and
• filter the volume of data to generate a reduced volume of data, the reduced volume of data comprising data in one or more columns in the identified set of columns;
• receive, via an application programming interface (API), external operational data associated with a particular client, the external operational data comprising a condition relevant to an account associated with the particular client,
• automatically modify the transaction rule for the account in near real-time based on the external operational data,
• responsive to modifying of the transaction rule, dynamically re-identify the set of columns relevant to the modified transaction rule, regenerate the reduced volume of data, and automatically push both the modified transaction rule and the regenerated reduced volume of data;
• and
• an authorizer server configured to approve transactions in real time, the authorizer server in communication with the rule management server, the rule management server being a separate server from the authorizer server, the authorizer server having a second response time in applying a transaction rule using a reduced volume of data, the second response time being shorter than the first response time due to the reduced volume of data, the authorizer server comprising a second processor and second memory, the second memory configured to store a second set of code instructions, the second set of code instructions, when executed by the second processor, causes the second processor to:
• receive from a transmission by the rule management server, the reduced volume of data and the transaction rule,
• store the reduced volume of data in the authorizer server, the reduced volume of data being a replication of a subset of the volume of data that is stored in the rule management server related to third-party named entities,
• receive, via an automatic push transmission from the rule management server, the regenerated reduced volume of data,
• receive a transaction data payload related to a pending transaction associated with an account of a particular client,
• determine that the transaction rule that includes the third-party named entity restriction governs the pending transaction,
• determine an identity of a particular third-party named entity in the transaction data payload, wherein determining the identity of the particular third-party named entity in the transaction data payload comprises:
• parsing a version of a particular third-party named entity name from the transaction data payload, and
• determining that the version of the particular third-party named entity name belongs to an existing named entity, and
• generate a query for the reduced volume of data stored in the authorizer server to determine attributes of the existing named entity based on the reduced volume of data, and
• conduct a real-time transaction approval process for the pending transaction using the transaction rule.