Abstract: The disclosed embodiments include processes that securely approve and execute exchanges of data between systems, apparatuses, and devices in a computing environment. For example, a terminal device may establish communications with a client device across a direct channel of communication, and may initiate an exchange of data with that additional device across the direct communications channel. The initiated data exchange may be characterized by a value of a data-exchange parameter, and the terminal device may determine to authorize the current data exchange in real-time based on cryptographically secure distributed ledger data maintained by the client device and provided to the terminal device across the direct communications channel. Further, and based on transmitted confirmation data, the client device may generate additional, cryptographically secure of the distributed ledger data to reflect the authorized data exchange.

Abstract: Computer-implemented cyber-security, behavior-generated, event-type signed processes and machines provide for authentication and immutable transactions to overcome security risks. Clients submit requests for an immutable transactions and interactions responsive to the request are sent by the server to the client. The server generates behavioral expectations for the interactions, stores them for future comparison purposes, and transmits those to the client. The client executes user events for the interactions. The client behaviorally analyzes the user events and generates behavioral vectors corresponding to the user events. Intermediate client hashes that culminate in a final client hash are generated. User events are sent to the server. The server generates a server hash based on the behavioral expectations and the user events. The server compares the final client hash to the server hash to determine if the transaction is authentic and should be stored as immutable.

Abstract: Systems and methods for the deployment of an application programming interface to cloud-based systems using a distributed ledger are disclosed. The system may include a cloud provider system and a distributed ledger. The cloud provider system may be configured to deploy cloud-based systems and/or APIs to enable one or more participant systems to leverage cloud-based resources. The distributed ledger may record events, functionalities, and operations from the cloud provider system, the participant systems, and the deployed cloud-based systems and APIs.

Abstract: In certain aspects of the disclosure, a computer-implemented method includes receiving an initial order based on a user input. The method includes mapping out correct steps from the initial order to settlement. The method includes validating instructions at each step. The method includes recording data pertaining to permit the settlement of the transaction.

Abstract: Systems, devices, and methods for creating and managing web3 app credentials, including: determining a private key and a public key; encrypting the determined private key into a plurality of separate keys; transmitting the first key to a third party provider; transmitting the second key to a cloud storage device; encrypting the first key and the second key; decrypting the second key; transmitting the decrypted second key; transmitting a transaction sign request to a secure third-party trusted execution environment; performing a user identity verification; transmitting a request to the third party provider for the first key; performing reconstruction of the original private key based on the first key and the second key; and signing a digital wallet transaction based on the reconstructed original private key received from the trusted execution environment.

Abstract: System and method to adjust in-vehicle content based on digital assets are described herein.

Abstract: Techniques for authenticating a digital asset represented by an NFT that is stored in a blockchain are disclosed. An NFT that has been minted for an asset is identified. The NFT was minted by generating metadata for the asset and by generating an original hash of the asset. The NFT is stored in a blockchain, and the metadata is stored in a centralized repository. The original hash is stored in either the repository or the blockchain. A potential transfer of the NFT is triggered. Triggering the potential transfer includes downloading, from the centralized repository, a local version of the asset. A local hash of the local version of the asset is generated. The local hash is compared against the original hash. If the two hashes are the same, then the transfer is permitted; otherwise, the transfer is not permitted.

Abstract: A distributed ledger system may include a first distributed ledger node associated with a first participant bank that maintains a first participant bank deposit account on a blockchain-based distributed ledger in a distributed ledger network; a second distributed ledger node associated with a second participant bank that maintains a second participant bank deposit account on the blockchain-based distributed ledger; and a third distributed ledger node associated with a liquidity provider that maintains a liquidity provider deposit account on the blockchain-based distributed ledger.

Abstract: A method performed by a session initiation system (SIS) for reducing a time to authenticate a user includes communicating, to a mobile device, session identifying information associated with a session. The mobile device is configured to subsequently communicate at least part of the session identifying information to an authentication server, and the authentication server is configured to subsequently communicate account information associated with the session identifying information to an intermediate gateway.

Abstract: When an online ticket is purchased, a record is maintained in a third-party online service; the record does not include the unique serial number of the ticket. The unique serial number is salted and/or hashed to generate a unique cryptographic value, which is stored with the record by the service. When the online ticket is redeemed, the unique serial number is again salted and/or hashed to produce a candidate cryptographic value. The records of the service are searched using the candidate cryptographic value and upon a match, the appropriate matching record is returned to the redeeming entity associated with the ticket by the service as evidence of authentication and as auditing information associated with the original purchased ticket.

Abstract: A computing system receives a code that is generated based upon an image of an iris of a first user. The image of the iris of the first user is captured by way of an iris scanning device that is under control of a second user. The computing system executes a search over a plurality of codes stored in a data store based upon the code, where the plurality of codes are generated based upon images of irises of a plurality of users. The computing system determines whether the code is included in the plurality of codes based upon search results for the search. Based upon a determination that the code is not included in the plurality of codes, the computing system causes an amount of cryptocurrency to be transferred to a cryptocurrency wallet of the second user.

Abstract: A digital checking system retrieves a first non-fungible token of a digital check from a distributed ledger implemented by a blockchain. The first token includes (i) a set of parameters of the digital check and (ii) a first service data describing a first transaction performed on the digital check. The set of parameters of the digital check includes a check amount, a payor, a payee, a check date, a bank identifier, and a user signature of the digital check. The system receives a second service data describing a second transaction performed on the digital check that is subsequent to the first transaction. The system stores a second non-fungible token of the digital check into the distributed ledger. The second token includes (i) the set of parameters of the digital check and (ii) the second service data.

Abstract: Expedited E-Commerce Tokenization alleviates the above mentioned concerns associated with cards for merchants as well as PSPs using tokens by establishing E-Commerce browser standards around tokenization for merchants and PSPs through a standard manner of requesting customer data in an encrypted manner following a standard.

Abstract: Embodiments provide electronic methods and systems for facilitating payment transactions to delivery agents. The method performed by a server system includes obtaining order related data associated with an order placed by a customer with a merchant. The method includes determining whether a payment transaction amount is within one or more transaction threshold limits or not. Further the method includes facilitating a credit transaction by an issuer server for effectuating a transfer of the payment transaction amount to a payment instrument of a delivery agent. The method further includes receiving a payment transaction request in response to using the payment instrument at a payment terminal associated with the merchant. The method includes transmitting a payment authorization request message to the issuer server.

Abstract: A banking processing method according is performed by a processing logic including an application for banking processing implemented on a user terminal and a computer-readable storage medium. The method comprises the steps of: when the application for banking processing is run, searching a hardware security area of the user terminal and confirming the existence of a certificate for confirming an execution history of the application for banking processing; when the existence of the certificate is confirmed, searching the security area and confirming the existence of a token key for identifying whether login information of the user has been set; when the existence of the token key is not confirmed, setting the login information of the user by providing a membership page for setting the login information of the user; and opening an account according to a request of the user whose login information has been set.

Abstract: In certain aspects of the disclosure, a computer-implemented method includes receiving an initial order based on a user input. The method includes mapping out correct steps from the initial order to settlement. The method includes validating instructions at each step. The method includes recording data pertaining to permit the settlement of the transaction.

Abstract: Systems and methods are described for license management. A system for license management includes a smart contract that records a licensing agreement between a first party and a second party on usage of a network function. The smart contract is persisted in a trade blockchain. The system also includes an e-licensing manager agent. The e-licensing manager agent retrieves the licensing agreement from the smart contract. The e-licensing manager agent monitors a usage of the network function by the second party in real-time based on the licensing agreement, record actions of the usage of the network function, and create a transaction record based on the recorded actions in an operation blockchain.

Abstract: Systems, methods, and apparatuses for providing a customer a central location to manage permissions provided to third-parties and devices to access and use customer information maintained by a financial institution are described. The central location serves as a central portal where a customer of the financial institution can manage all access to account information and personal information stored at the financial institution. Accordingly, the customer does not need to log into each individual third-party system or customer device to manage previously provided access to the customer information or to provision new access to the customer information. A user additionally is able to have user data and third-party accounts of the user deleted from devices, applications, and third-party systems via a central portal.

Abstract: Systems, methods, and apparatuses for providing a customer a central location to manage permissions provided to third-parties and devices to access and use customer information maintained by a financial institution are described. The central location serves as a central portal where a customer of the financial institution can manage all access to account information and personal information stored at the financial institution. Accordingly, the customer does not need to log into each individual third-party system or customer device to manage previously provided access to the customer information or to provision new access to the customer information. A user additionally is able to have user data and third-party accounts of the user deleted from devices, applications, and third-party systems via a central portal.

Abstract: Systems, methods, and apparatuses for providing a customer a central location to manage permissions provided to third-parties and devices to access and use customer information maintained by a financial institution are described. The central location serves as a central portal where a customer of the financial institution can manage all access to account information and personal information stored at the financial institution. Accordingly, the customer does not need to log into each individual third-party system or customer device to manage previously provided access to the customer information or to provision new access to the customer information.