Patent classifications
G06Q20/356
SYSTEMS AND METHODS FOR PREDICTING PERFORMANCE
The present disclosure relates to system and methods for predicting performance caused by software code changes. For this purpose, an augmented machine learning model predicts a latency of software module with updated code executed in a production environment. In some aspects, the latency is predicted based on a change of deviation that is determined by comparing the latency of the software module with updated code and the latency of the software module without updated code, whereas the software modules are executed in environments different from the production environment.
UNIFIED TRANSACTION SERVICES FOR MULTI-TENANT ARCHITECTURES
A method for using unified transaction services in a multi-tenant architecture system is discussed. The method includes receiving a request, at a first service provider, to provide a first transaction service for a user. The method includes accessing a first representation of the first service provider in a first hierarchical data structure, the first hierarchical data structure being managed by a second service provider, the second service provider managing user identity of the user. The method includes determining, based on the first representation, that transaction resources required for completion of the first transaction service are provided at the second service provider using a resource representation. The method also includes, responsive to determining that the transaction resources are accessible at the first service provider, accessing, at the first service provider, the transaction resources via the resource representation.
DYNAMICALLY CONFIGURABLE TRANSACTION MANAGEMENT CONTROLLER AND METHOD THEREOF
Technologies for managing payment authorization request messaging for payment transactions include a transaction management controller. The transaction management controller receives a transaction amount for a payment transaction from a business management engine and a payment transaction type from a point of interaction device. The transaction management controller initializes a transaction processing module that corresponds to the received payment transaction type. The transaction processing module defines payment processing parameters for processing payment transactions of the payment transaction type. One or more of the payment processing parameters are modified based on configuration data received from a remote configuration device. The transaction management controller processes the payment transaction as a function of the payment processing parameters. Other embodiments are described and claimed.
METHOD AND SYSTEM FOR ACCEPTING PAYMENTS ON MOBILE APPLICATION
A system and a method for accepting a payment on an application is provided. The method is implemented by a processor. The processor receives login information from a client to activate a banking application; selects quick accept entry points associated with the client's business banking demand deposit account (DDA) based on determining that the client is eligible for the quick accept entry points in response to the login information; sets up a payment receiving option for receiving a payment via the banking application; causes the banking application to receive transaction amount data corresponding to a transaction between the client and a customer; causes the banking application to process the transaction amount data; and automatically updates the DDA to reflect receipt of the transaction amount data.
Computer-based systems and methods involving biometric authentication aspects for handling exceptions, enabling deactivation and/or performing other functionality
Systems and methods involving biometric authentication of transaction cards including aspects of exception handling, deactivation and other features are disclosed. In one embodiment, an exemplary computer-implemented method may comprise generating a first user interface having one or more interactive UI elements that enable a card owner to manage a plurality of features associated with a transaction card, and determining, if a biometric-activated control is enabled and the vendor is not excluded from the biometric-activated control, whether the transaction card is biometrically-active. Further, the interactive UI elements may include elements such as a first UI element that is configured to allow the card owner to enable a biometric-activated control of the transaction card, and/or a second UI element that is configured to allow the card owner to exclude one or more vendors from the biometric-activated control.
Metadata driven orchestration engine
An efficient reusable, extensible light weight framework statelessly orchestrates system activities in any application which involves a series of sequential or parallel set of activities involving computational logic, data retrieval and persistence services. Actual orchestration steps and activities and computational logic are specified into configuration files, separate from the orchestration engine itself, thereby eliminating the need to code for such logic and activities. The framework can eliminate the need to code business logic and orchestration of data retrieval services by externalizing them into configuration files, resulting in lower costs to implement, test and maintain such system during its lifespan.
SYSTEMS AND METHODS FOR DEPLOYING ENTERPRISE SOFTWARE UPDATES
Systems and methods for deploying enterprise software updates are provided. An identity of an application in an application group that is designated active is obtained in response to a command to run a first application on a client device. Only one application in the application group is designated active at any given time. In response to a determination that an identity of a second application in the application group matches the identity of the single application in the application group that is designated active, a procedure is run that includes terminating the first application and executing the second application. The executing retrieves all or a portion of a shared data element stored on the client device. The shared data element is shared between the first application and the second application, thereby allowing an application with an active status to run while preserving shared data associated with an inactive application.
Transactions between services in a multi-tenant architecture
A method for facilitating transactions by tenants in a multi-tenant architecture system is discussed. The method includes generating, with a multi-tenant computer system, a first representation of an entity in a first hierarchical data structure associated with an entity interface tenant of the multi-tenant computer system. The method includes receiving, with the multi-tenant computer system, a set of entity-specific policies useable to generate requests to individual ones of a plurality of transaction processing computer systems. The method includes generating, with the multi-tenant computer system, a second representation of the entity in a second hierarchical data structure associated with a particular transaction processing service tenant of a plurality of transaction processing service tenants of the multi-tenant computer system. The method includes linking, with the multi-tenant computer system, the first representation and the second representation in a unified hierarchical data structure useable to provide a unified identity for the entity for requests.
DYNAMICALLY CONFIGURABLE TRANSACTION MANAGEMENT CONTROLLER AND METHOD THEREOF
Technologies for managing payment authorization request messaging for payment transactions include a transaction management controller. The transaction management controller receives a transaction amount for a payment transaction from a business management engine and a payment transaction type from a point of interaction device. The transaction management controller initializes a transaction processing module that corresponds to the received payment transaction type. The transaction processing module defines payment processing parameters for processing payment transactions of the payment transaction type. One or more of the payment processing parameters are modified based on configuration data received from a remote configuration device. The transaction management controller processes the payment transaction as a function of the payment processing parameters. Other embodiments are described and claimed.
API charging system, API charging management method, and API charging program
An API management device includes: a reception unit configured to receive a selection of a charging condition when using an API; a receiver configured to receive a request for the API from the application; a transmitter configured to transmit a response according to the request to the application; and a history storage configured to store a history of the request for the API and the response for each of the applications that use the API. A charging management device includes: a charging condition storage configured to store the charging condition received by the reception unit for each of the applications that use the API when using the API; an acquisition unit configured to acquire information on the history from the history storage; and a determination unit configured to determine a charge value for the application that uses the API based on the charging condition and the information on the history.