Abstract: Examples describe data security and routines structured to avoid conflicts. One example includes accessing data for a merchant website including a framework with a first routine for a function, and accessing an account security element for the merchant website with a second routine associated with an account security system for the function. The second routine is optimized to avoid conflicts with the first routine. The framework is automatically updated while the second routine is maintained with no changes. The merchant website data is then transmitted with the updated first routine and the account security element with the second routine, where the updated first routine and the second routine facilitate data security on the client device without framework conflicts when the updated first routine for the function and the second routine for the function operate concurrently on the client device.

Abstract: Examples described herein include systems, methods, instructions, and other implementations for data security. One example includes receiving a checkout communication received from a merchant system, where the checkout communication does not include client information, and processing the communication to authenticate a validated checkout system. A client token is generated in response to an authentication that the checkout communication is from the validated checkout system and transmitted to allow verification of the merchant system. An account communication is then received including the client token and client information, where the client information is not received from the merchant system. A tokenized client account number is generated and used to allow the merchant system to process the secure transaction without access to the client information.

Abstract: Examples described herein include systems, methods, instructions, and other implementations for data security. One example includes receiving a status inquiry associated with a secure transaction, a merchant system, and a client device. The status inquiry is processed to determine that the merchant system associated with the status inquiry has been previously validated and that the status inquiry is from the merchant system. Then, in response to the determination that the merchant system has been previously validated, postback data including a tokenized client account number associated with client information is accessed and the tokenized client account number is transmitted. The tokenized client account number facilitates processing the secure transaction without the merchant system having access to the client information.

Abstract: In response to receipt of a request for an assessment of a user at a system and from a client terminal, the system identifies a duration of time available for responding to the request and starts a timer. The system transmits requests for information about the user to data sources. The system can and receive some responsive datasets back from the data sources, and can determine which responsive datasets are optimal to wait for and which are not based on how closely the timer is approaching the duration of time available for responding to the request. The system generates the assessment of the user based on the datasets that the system received before the timer reached a threshold time that is based on the duration of time available for responding to the request, and sends the assessment of the user to the client terminal.

Abstract: Disclosed embodiments may provide a framework to implement post-purchase tender switches. For example, following a transaction made with a particular payment instrument, a customer may be offered the ability to apply for a preferred payment instrument and/or to switch his or her tender type to the preferred payment instrument for the previous transaction.

Abstract: Systems, devices, methods, instructions, and other implementations are described for network data management. One embodiment involves request data received at a device associated with a digital lockbox, where the request data includes identifying information for an originating device associated with a location and is associated with a user device. A unique token is generated with the identifying information. The unique token can be used to tokenize a network link to create a secure one-time link. The system transmits the one-time link, which can then be used to facilitate secure communications between a computing system associated with the originating device and the user device.

Abstract: A classification modeling system receives a request to identify a classification model from a set of classification models. The request includes a data set and specifies one or more metrics for evaluating performance of the set of classification models in classifying data from the data set. The system uses the set of classification models to generate a set of classifications and determines the performance of the set of classification models based on the set of classifications and according to the one or more metrics. Based on the performance of the set of classification models, the system selects a classification model and provides the classification model to fulfill the request.

Abstract: A transaction classification system obtains a data set including first data associated with a first characteristic and second data associated with a second characteristic. In response to obtaining the data set, the system uses a classification model to generate a classification by classifying the first data into majority data and the second data into minority data. From the classification and using the classification model, the system determines a cost. The system modifies the classification model based on this cost to generate an updated classification model. The system uses the updated classification model to re-classify a subset of the first data into the minority data and a subset of the second data into the majority data.

Abstract: The electronic device may invoke a host application. The device may display a first host user interface on the display, the first host user interface including a first host user interface component associated with a child application. In response, the device may invoke, using the host application, the child application executed at the electronic device. The device may transmit, using the host application, a request for data associated with a child user interface component to the child application. The device may transmit, using the child application, the request for data associated with the child user interface component to a child application server, wherein the data associated with the child user interface component is inaccessible by the host application. The device may receive, using the child application, the data associated with the child user interface component from the child application server. The device may display the child user interface component.

Abstract: The electronic device may invoke a host application. The device may display a first host user interface on the display, the first host user interface including a first host user interface component associated with a child application. In response, the device may invoke, using the host application, the child application executed at the electronic device. The device may transmit, using the host application, a request for data associated with a child user interface component to the child application. The device may transmit, using the child application, the request for data associated with the child user interface component to a child application server, wherein the data associated with the child user interface component is inaccessible by the host application. The device may receive, using the child application, the data associated with the child user interface component from the child application server. The device may display the child user interface component.

Abstract: The present disclosure is related to object recognition and tracking using multi-camera driven machine vision. In one aspect, a method includes capturing, via a multi-camera system, a plurality of images of a user, each of the plurality of images representing the user from a unique angle; identifying, using the plurality of images, the user; detecting, throughout a facility, an item selected by the user; creating a visual model of the item to track movement of the item throughout the facility; determining, using the visual model, whether the item is selected for purchase; and detecting that the user is leaving the facility; and processing a transaction for the item when the item is selected for purchase and when the user has left the facility.

Abstract: A system and method for processing promotions in connection with digital purchasing. Data associated with a digital purchase request made by a consumer (the data comprising a token, an amount associated with the transaction, a promotional code for each item included in the digital purchase request associated with a promotion, a default transaction amount, and a single default promotional code) is received from a merchant server. The single default promotional code is assigned to all items included in the digital purchase request that are associated with promotions. Using the token, account information associated with the consumer is retrieved from a database. For each promotional code received, promotional information is retrieved. The retrieved promotional information is displayed. The digital purchase request is submitted for processing using the single default promotional code.

Abstract: A method for use an earned autopay account, an available autopay account, an earned points account, and an available points account each associated with a customer. The method includes storing a cache including first and second numbers of points stored in the available autopay account and the available points account, respectively. A points authorization request requesting a first transaction amount is received from a requesting computing device. A second transaction amount is subtracted from the first and/or second numbers of points. A points redemption request including a third transaction amount is sent to the payment processing computing device. Each of the first, second, and third transaction amounts includes a particular monetary value and/or a corresponding transaction number of points. The payment processing computing device subtracts the third transaction amount from the available points account and/or the available autopay account.

Abstract: Disclosed are systems and techniques for dynamically providing real-time offers. For instance, user eligibility for one or more offers can be determined based on a plurality of dynamic user attributes associated with the user and one or more data sets corresponding to similarly situated users. An input can be received corresponding to an acceptance by the user of at least one offer selected from the one or more offers. In response to receiving the input, an updated plurality of the dynamic user attributes can be retrieved, wherein the dynamic user attributes are constantly updated in real time based on user activity. Based on the updated plurality of dynamic user attributes and the one or more data sets corresponding to the similarly situated user, it can be determined whether the user remains eligible for the at least one offer. An offer confirmation can be sent upon confirming eligibility.

Abstract: A framework is provided for an automated and distributed system including onboarding to a network utilizing a digital ledger, payment processing and settlement, and a data marketplace in which users control access to their data. The ledger is stored within a distributed architecture. The ledger includes blocks, wherein a complete copy of the ledger is stored on one or more nodes, and the ledger is capable of verifying the blocks. A credential request is provided that includes information that when received at a first node can be used to perform a credential lookup. A verified, issued credential is received when the credential lookup is successful. The framework allows for generating a zero knowledge proof using the verified, issued credential and for providing the zero knowledge proof. When the zero knowledge proof is received at a second node, the zero knowledge proof can be used to verify a criteria.

Abstract: In one aspect, a distributed ledger system include a first network node configured to detect a triggering condition for processing a claim; collect user and broker information for processing the claim; convert the information from a first computer-readable format to a second computer-readable format; validate the converted information based on corresponding digital signatures; generate claim state objects based on the validated information to be used by each node of the distributed ledger system to execute a smart contract for processing the claim; receive one or more updated claim state objects from a second network node reflecting updated processing status of the claim to be used by each node of the distributed ledger system to execute the smart contract for processing the claim; and process the claim based on results of execution of the smart contract using the one or more updated claim state objects.

Abstract: A method that includes obtaining, by an application executing on a computing system, a list of properties defining at least one property. The executing application writes an uncompiled class definition implementing a compiled interface and writes one or more properties of the compiled interface into the uncompiled class definition. The executing application writes the at least one property and at least one serialization attribute into the uncompiled class definition. The executing application causes the uncompiled class definition to be compiled, loads the compiled class definition, and creates an object by instantiating the compiled class definition. The object is serializable. The executing application may reflect on the compiled interface to obtain the one or more properties. Each of the one or more properties is strongly typed.

Abstract: Computer-implemented methods are provided for receiving information corresponding to a transaction, wherein the information is received via a single processing of an instrument. A balance for the transaction is automatically determined based on a coverage plan associated with the information from the instrument and services associated with the transaction. Upon detecting selection of an account for the balance, an amount from the account is allocated for the balance and is provided to complete the transaction.

Abstract: Systems and methods are provided for persistent login. Such persistent login may be based on linking user identity across accounts of different entities to allow each entity to maintain control over their respective sets of user data, while providing a streamlined user experience that avoids much of the repetitive need to login to different services with different login credentials (e.g., during periods of heavy use). Such persistent login may utilize a set of tokens issued and exchanged between devices of the partnering entities. Such tokens may include an access token, refresh token, and identity token. When a user associated with a first entity requests access to information secured by a second entity, such request may be associated with the access token. If the access token is determined to be expired, the refresh token may be used to refresh the access token, which may also trigger issuance of a new refresh token.

Abstract: The electronic device may invoke a host application. The device may display a first host user interface on the display, the first host user interface including a first host user interface component associated with a child application. In response, the device may invoke, using the host application, the child application executed at the electronic device. The device may transmit, using the host application, a request for data associated with a child user interface component to the child application. The device may transmit, using the child application, the request for data associated with the child user interface component to a child application server, wherein the data associated with the child user interface component is inaccessible by the host application. The device may receive, using the child application, the data associated with the child user interface component from the child application server. The device may display the child user interface component.