Abstract: A system for stable and streamlined transaction approval includes a rule management server and an authorizer server that operates independently of the rule management server. The rule management server is configured to receive a transaction rule associated with an account specified by a client entered through a portal generated by a graphical user interface. The server is further configured to identify data relevant to the transaction rule and transmit the transaction rule and the data identified to an authorizer server. The authorizer server is configured to receive transaction data related to a pending transaction of the credit card and apply the transaction rule to the transaction data and the data identified by the rule management server to determine whether to approve the pending transaction. The authorizer server operates independent of the rule management server and can be optimized to approve transactions quickly and operate in a stable condition.

Abstract: A system for stable and streamlined transaction approval includes a rule management server and an authorizer server that operates independently of the rule management server. The rule management server is configured to receive a transaction rule associated with an account specified by a client entered through a portal generated by a graphical user interface. The server is further configured to identify data relevant to the transaction rule and transmit the transaction rule and the data identified to an authorizer server. The authorizer server is configured to receive transaction data related to a pending transaction of the credit card and apply the transaction rule to the transaction data and the data identified by the rule management server to determine whether to approve the pending transaction. The authorizer server operates independent of the rule management server and can be optimized to approve transactions quickly and operate in a stable condition.

Abstract: A system for detects and manages recurring transactions incurred by members of a client organization. The system includes a computing server that is configured to classify named entities into a category of transacting named entities. For example, the computing server classifies a list of named entities that offer subscription services and hence, create recurring transactions with the client organization. The computing server receives transaction data and determines that a target transacting named entity extracted from the received data belongs to the category (e.g., there is a named entity in the received transaction data that has sold a service to the client organization more than once). The computing server may then determine the presence and frequency of a subscription transaction series in the received transaction data, and cause a predicted a timing of an upcoming transaction in the subscription transaction series to be displayed in a graphical user interface (GUI).

Abstract: A system for detects and manages recurring transactions incurred by members of a client organization. The system includes a computing server that is configured to classify named entities into a category of transacting named entities. For example, the computing server classifies a list of named entities that offer subscription services and hence, create recurring transactions with the client organization. The computing server receives transaction data and determines that a target transacting named entity extracted from the received data belongs to the category (e.g., there is a named entity in the received transaction data that has sold a service to the client organization more than once). The computing server may then determine the presence and frequency of a subscription transaction series in the received transaction data, and cause a predicted a timing of an upcoming transaction in the subscription transaction series to be displayed in a graphical user interface (GUI).

Abstract: A system for detects and manages recurring transactions incurred by members of a client organization. The system includes a computing server that is configured to classify named entities into a category of transacting named entities. For example, the computing server classifies a list of named entities that offer subscription services and hence, create recurring transactions with the client organization. The computing server receives transaction data and determines that a target transacting named entity extracted from the received data belongs to the category (e.g., there is a named entity in the received transaction data that has sold a service to the client organization more than once). The computing server may then determine the presence and frequency of a subscription transaction series in the received transaction data, and cause a predicted a timing of an upcoming transaction in the subscription transaction series to be displayed in a graphical user interface (GUI).

Abstract: A system for flexible account creation and approval includes a computing server and a communication platform server that operates independently of the computing server. The computing server is configured to receive an account creation request initiated through interfaces of the communication platform server or the computing server. The computing server facilitates approval of the requests, which can include sending request approvers the request for review at interfaces of the communication platform server or the computing server. By enabling account creation and approval through various servers that can access the same information to provide consistent experiences, the system offers users more flexibility in choosing one of the available servers.

Abstract: A system for stable and streamlined transaction approval includes a rule management server and an authorizer server that operates independently of the rule management server. The rule management server is configured to receive a transaction rule associated with an account specified by a client entered through a portal generated by a graphical user interface. The server is further configured to identify data relevant to the transaction rule and transmit the transaction rule and the data identified to an authorizer server. The authorizer server is configured to receive transaction data related to a pending transaction of the credit card and apply the transaction rule to the transaction data and the data identified by the rule management server to determine whether to approve the pending transaction. The authorizer server operates independent of the rule management server and can be optimized to approve transactions quickly and operate in a stable condition.

Abstract: A system for stable and streamlined transaction approval includes a rule management server and an authorizer server. The rule management server is configured to receive a transaction rule that includes a list of named entities specified by a client. The rule management server stores past transaction data and analyzes patterns in the past data to determine a named entity identification rule. The authorizer server receives a transaction data payload related to a pending transaction associated with the client and identifies a noisy data field in the transaction data payload. The noisy data field includes a representation of a particular named entity and one or more irrelevant strings. The authorizer server parses the particular named entity based on the named entity identification rule and determines whether the particular named entity is one of the named entities in the list. The authorizer server conducts a transaction evaluation using the result.