Abstract: Systems and methods for executing filtered electronic transactions are disclosed. One method includes receiving, by an acquirer system of a filtered transaction processing system, a transaction request including transaction data from a merchant system, the transaction data including enhanced data or non-enhanced data. A status of the merchant system may be determined based on the transaction data, the status of the merchant system indicative of a participating status or a non-participating status. Upon determining the status of the merchant system indicative of the participating status, the transaction request may be transmitted to a first transaction network. The first transaction network may forward the transaction request to a categorization engine of the filtered transaction processing system. The categorization engine may categorize one or more items associated with the transaction request into one or more categories. The transaction request may be executed based on the one or more categories.

Abstract: A method for managing sessions with an application server via an identity management system is described. The method may include receiving, via an application protocol interface (API) of a cloud service of the identity management system, a first request associated with a first user for user access to an account of the application server. The API may transmit a second request for a secrets service to encrypt a password associated with the first user to a public key of a keypair. The API may receive a message including the encrypted password and forward the encrypted password to an end-client. The identity management system may establish a session on behalf of the first user for the account of the application server based on the end-client having access to a private key of the keypair.

Abstract: A method for managing sessions with an application server via an identity management system is described. The method may include receiving, via an application protocol interface (API) of a cloud service of the identity management system, a first request associated with a first user for user access to an account of the application server. The API may transmit a second request for a secrets service to encrypt a password associated with the first user to a public key of a keypair. The API may receive a message including the encrypted password and forward the encrypted password to an end-client. The identity management system may establish a session on behalf of the first user for the account of the application server based on the end-client having access to a private key of the keypair.

Abstract: Methods, systems, devices, and computer-readable media for automatically updating software in secure enclaves are described. A secrets management system may receive an indication that an updated version of software code to be executed in an isolated execution environment, e.g., an enclave, is available for deployment. An identifier associated with the updated version of the software code may be determined. Configuration data may be updated to indicate identifiers associated with the current and updated versions of the software code. The updated configuration data may be used to update a key policy to include the identifiers of the current and updated versions of the software code. The updated key policy may be applied to one or more managed keys and may be used to update a key management application programming interface (API) to enable both the current and updated versions of the software code to access the one or more managed keys.

Abstract: A method for managing sessions with an application server via an identity management system is described. The method may include receiving, via an application protocol interface (API) of a cloud service of the identity management system, a first request associated with a first user for user access to an account of the application server. The API may transmit a second request for a secrets service to encrypt a password associated with the first user to a public key of a keypair. The API may receive a message including the encrypted password and forward the encrypted password to an end-client. The identity management system may establish a session on behalf of the first user for the account of the application server based on the end-client having access to a private key of the keypair.

Abstract: Systems and methods for executing filtered electronic transactions are disclosed. One method includes receiving, by an acquirer system of a filtered transaction processing system, a transaction request including transaction data from a merchant system, the transaction data including enhanced data or non-enhanced data. A status of the merchant system may be determined based on the transaction data, the status of the merchant system indicative of a participating status or a non-participating status. Upon determining the status of the merchant system indicative of the participating status, the transaction request may be transmitted to a first transaction network. The first transaction network may forward the transaction request to a categorization engine of the filtered transaction processing system. The categorization engine may categorize one or more items associated with the transaction request into one or more categories. The transaction request may be executed based on the one or more categories.