Abstract: Techniques for generating explanations for machine learning (ML) are disclosed. These techniques include identifying an ML model, an output from the ML model, and a plurality of constraints, and generating a plurality of neighborhoods relating to the ML model based on the plurality of constraints. The techniques further include generating a predictor for each of the plurality of neighborhoods using the ML model and the plurality of constraints, constructing a combined predictor based on combining each of the respective predictors for the plurality of neighborhoods, and creating one or more explanations relating to the ML model and the output from the ML model using the combined predictor.

Abstract: A method includes receiving a request from a customer to open a subscription account, creating the subscription account for the customer, and deducting a fee from the subscription account. The fee is structured to subsidize benefit fees associated with benefits for the customer. The method includes determining a benefit for the customer. The benefit is offered by a third-party vendor in exchange for an associated fee. The method includes reimbursing the subscription account for the customer in an amount of the fee associated with the benefit. The method includes gathering financial information associated with the customer, analyzing the financial information to identify positive financial behavior of the customer, invoking a graphical depiction executable via a user interface on a device associated with the customer, determining that the positive financial behavior meets a threshold, and offering the customer a reward based on the positive financial behavior meeting the threshold.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method generally includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of widgets and storing the correlations in the model. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes selecting one or more widgets to include in a custom user interface definition based, at least in part, on the user intent. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: A method may include receiving, from a source application, partial data that is incomplete for use by a target application, obtaining a set of contextual data correlated with the partial data, assigning, using a ranking model, confidence levels to the set of contextual data, selecting, from the set of contextual data, contextual data according to the confidence levels assigned to the set of contextual data, generating augmented partial data using the contextual data and the partial data, determining that the augmented partial data satisfies a transaction completion criterion of a transaction schema, and in response to determining that the augmented partial data satisfies the transaction completion criterion, sending the augmented partial data to a transaction store used by the target application.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store and a registry configured to receive a request to register a universal resource identifier (URI) to a data store with a first secure identifier. The first secure identifier may be generated, using an encoding function and by a user, from a user identifier of the user. The registry may be further configured to store the URI of the data store with the first secure identifier, and receive, from an entity, a request to lookup a data store registered with a second secure identifier. The second secure identifier may be generated by the entity. The registry may be further configured to retrieve the URI of the data store in response to the request to lookup the data store, and transmit, to the entity, the URI of the data store.

Abstract: Systems and methods relate to providing subscription accounts. A method includes receiving a request from a customer to open a subscription account, creating the subscription account for the customer, and deducting a subscription fee from the subscription account. The method also includes determining a benefit for the customer. The benefit is offered by a third-party vendor in exchange for a benefit fee. The method further includes reimbursing the benefit fee to the subscription account for the customer. The method additionally includes gathering financial information associated with the customer, analyzing the financial information to identify positive financial behavior of the customer, determining that the positive financial behavior meets a threshold, and offering the customer a reward based on the positive financial behavior meeting the threshold.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The detailed transaction may identify at least one selected from a group consisting of products and services received by the user from the first entity. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method generally includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of widgets and storing the correlations in the model. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes selecting one or more widgets to include in a custom user interface definition based, at least in part, on the user intent. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method generally includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of widgets and storing the correlations in the model. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes selecting one or more widgets to include in a custom user interface definition based, at least in part, on the user intent. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The detailed transaction may identify at least one selected from a group consisting of products and services received by the user from the first entity. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store and a registry configured to receive a request to register a universal resource identifier (URI) to a data store with a first secure identifier. The first secure identifier may be generated, using an encoding function and by a user, from a user identifier of the user. The registry may be further configured to store the URI of the data store with the first secure identifier, and receive, from an entity, a request to lookup a data store registered with a second secure identifier. The second secure identifier may be generated by the entity. The registry may be further configured to retrieve the URI of the data store in response to the request to lookup the data store, and transmit, to the entity, the URI of the data store.

Abstract: A method may include receiving, via a network and from a source application, partial data including values for parameters defined according to an application programming interface (API). Each parameter may be defined by the API as optional. The partial data may be incomplete for use by a target application. The method may further include obtaining a set of contextual data correlated with the partial data, generating augmented partial data by combining the partial data and contextual data selected from the set of contextual data, determining that the augmented partial data satisfies a transaction completion criterion of a transaction schema, and in response to determining that the augmented partial data satisfies the transaction completion criterion, sending the augmented partial data to a transaction store used by the target application.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive a request, from a service provider, to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a determination that the detailed transaction is valid. The system may further include a validator configured to obtain, from a registry, a validation rule corresponding to the secure identifier, and perform the determination. The determination may include applying the validation rule to the request. The system may further include the registry. The registry may be configured to store at least the validation rule.

Abstract: A system may include transaction storage devices. Each transaction storage device may include a data store. The system may further include a registry configured to receive, from a user, a first secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The registry may be further configured to receive a first selection of a first data store of a first transaction storage device, and store a first registration of the first data store with the first secure identifier. The first registration may include a universal resource identifier (URI) of the first data store. The registry may be further configured to receive, from a service provider, a first request to lookup a data store registered with the first secure identifier, retrieve the first registration, and transmit, to the service provider and using the first registration, the URI of the first data store.