Abstract: Disclosed are various embodiments for generating payment accessibility notifications for individuals with impairments. In one non-limiting example, a system includes a first computing device configured to identify a second computing device using a wireless communication protocol in a store location. A first notification for the first computing device is activated based at least in part on an accessibility type. A user interface is displayed for receiving client data, and the client data includes a product entered by a user. An expected amount is determined for the product based at least in part on the client data and transmitted to the second computing device. A pending amount for the product is received from the second computing device. A second notification is activated for the first computing device prior to a completion of the purchase based at least in part on the pending amount and the expected amount.

Abstract: The systems may include transmitting wallet provider script to a payment service provider server, presenting an electronic wallet payment tool on a merchant checkout page, receiving a first selection of the electronic wallet payment tool, retrieving an electronic wallet comprised in a transaction account associated with the consumer, transmitting transaction account information associated with a desired transaction account in the electronic wallet to the payment service provider server, receiving a virtual token from the payment service provider server, and/or transmitting the virtual token to payment service provider script integrated in a browser used by the consumer.

Abstract: Disclosed are various embodiments for authenticating users of applications using decentralized data models for storing a user's identity. A fingerprint for a computing device is received from an application executing on the computing device. An identity key associated with the fingerprint for the computing device is then obtained, the identity key being linked to a signed claim. The signed claim is retrieved and evaluated. The application executing on the computing device access is then granted access to the computing resource in response to evaluating the signed claim.

Abstract: Systems and methods for peer-to-peer secure document exchange are disclosed. The system may allow a document provider to securely transmit a certified document to a document verifier using decentralized storage. The verifier system may generate a session key pair and transmit the session public key to a trusted API provider. The trusted API provider may generate a session nonce. The verifier system may transmit the session nonce to the provider system. The provider system may use the session nonce to retrieve the session public key. The provider system may encrypt a certified document using the session public key and store the encrypted certified document in the decentralized storage. The verifier system may retrieve the encrypted certified document by polling the trusted API provider based on the session nonce. The verifier system may decrypt the encrypted certified document using the session private key.

Abstract: Disclosed are various embodiments for a mutual privacy-preserving transfer of information using natural language and oblivious transfer (OT) protocols. A receiver entity can send a response request with prompts and corresponding keys to a sender entity. The sender entity can generate the responses using an output of large language models. Before sending the responses to the receiver entity, the sender entity encrypts the responses. The receiver entity can only decrypt the response that is encrypted using the public key associated with the receiver entity.

Abstract: Disclosed are various embodiments for minimizing hallucination-based responses by verifying or otherwise identifying one or more accurate responses generated by multiple large language model (LLM) service providers to a prompt through the use of a decentralized network. LLM service providers can be part of a decentralized network that allows multiple LLM service providers to receive a prompt. Each LLM service provider in the network can generate a response to the prompt by applying the prompt to one or more LLM models associated with the LLM service. Once a response has been formulated, the LLM service provider can transmit the response in a decentralized data storage for storage. In various examples, a threshold number of stored responses can be compared to one other to determine a level of similarity between responses and to identify any response that may correspond to a hallucination and, therefore, an inaccurate response.

Abstract: Disclosed are various approaches for using generative large language models (LLMs) and a shared text corpus to facilitate automated in-depth authentication of a user. A private text corpus can be shared between the user account and a verification entity. At least one authentication prompt can be generated using a large language model trained at least in part on the private text corpus. At least one authentication prompt can be sent to an authentication agent associated with the user. The authentication agent can send an authentication response based at least in part on the at least one authentication prompt and the private text corpus. The authentication response can be verified based at least in part on the private text corpus.

Abstract: Disclosed are various embodiments for issuing virtual cards to client devices. Also disclosed are embodiments for provisioning a transaction terminal to process transactions with virtual cards. A zero-knowledge proof algorithm can be utilized to validate the transactions. A virtual card can be based upon a public key of a client device that is managed by a hardware security module.

Abstract: Disclosed are various approaches for authentication optimization for chatbot interactions. A chat request can be received including a cryptographic signature, a client identifier, and an utterance for a chatbot. An artificial intelligence model can be invoked to generate a similarity assessment using the utterance from the chat request, and at least one prior utterance stored in association with the client identifier. Approval or denial to waive validation of the signature can be identified using the similarity assessment and a set of predetermined chat validation rules. Validation of the signature can be omitted or performed based at least in part on the approval or denial decision. The utterance can be transmitted to a chatbot service.

Abstract: Disclosed are various approaches for managing the status of machine-learning models using distributed ledgers. A registration request for a machine-learning model can be received. The registration request can include a model name for the machine-learning model, a version identifier for the machine-learning model, a network address from which the machine-learning model can be retrieved, a source code hash for a source code version of the machine learning model, and a runtime hash for a binary executable version of the machine-learning model. A registration identifier can then be created based at least in part on the source code hash and the runtime hash. Subsequently, an entry in the distributed ledger can be created for the machine-learning model. The entry can include the registration identifier, the model name, the model version, the network address, the source code hash, and the runtime hash.

Abstract: Disclosed are various embodiments for using a distributed ledger to track the evolution or deployment of feature sets for machine-learning. An approval request to approve creation of a feature set record in a distributed ledger can be received. The approval request can include a feature set hash representing a feature set, a code hash representing a feature set generator, and a data hash representing a data set. An approval decision can be generated for the feature set record based at least in part on the approval request and at least one approval rule stored in an approval data store. The approval decision can be transmitted to a distributed agent. The approval decision can approve or reject creation of the feature set record in the distributed ledger.

Abstract: Disclosed are various approaches for issuing and verifying multi-claim verifiable credentials and verifiable presentations. In various embodiments, an issuer can send a request for information to a holder and obtain a response from the holder. The issuer can extract claims from the message, validate at least one of the claims, and generate a verifiable credential (VC) for the holder based at least in part on the claims, which can be sent to the holder. The holder can then generate a verifiable presentation (VP) based at least in part on the VC and send the VP to a verifier. The verifier can then verify the VP and interpret the claims within the VC.

Abstract: Disclosed are various embodiments for consolidated protocols for decentralized identifier communications (DIDComm). In various embodiments, an issuer can receive a secure connection request and request for a credential from a holder. The issuer can then send a second packet comprising an acceptance of the secure connection request to the holder and subsequently send a verifiable credential after establishing the secure connection. The holder can simultaneously send an acknowledgement for setting up the secure connection and receiving the verifiable credential. The holder can request a second secure connection with a verifier. After establishing the second secure connection, the holder can send a verifiable presentation or the verifiable credential to the verifier, which the verifier can verify.

Abstract: Disclosed are various embodiments for managing a graph of decentralized identifiers (DIDs) associated with verifiable credentials (VCs) and verifiable credential linkages or relationships including those denoting linkages amongst verifiable credentials of different users. The DID tree graph can be maintained and managed to ensure that the DIDs and corresponding VCs are accurate and that the linkages or relationships between DIDs and corresponding VCs are still valid. The DID tree graph can be queried to identify DIDs associated with a DID subtree representing an established relationship or linkage between one or more VCs.

Abstract: Disclosed are various embodiments for providing non-fungible tokens (NFT) as a mechanism for verifying ownership of payment instruments such as stored value payment instruments. First, a computing device can receive a purchase notification, the purchase notification indicating that a first user has purchased a stored value payment instrument. Then, the computing device can create a non-fungible token (NFT) on a distributed data store in response to receipt of the purchase notification. Next, the computing device can associate a unique identifier of the NFT with the stored value payment instrument. Subsequently, the computing device can receive a first public key associated with the first user. Then, the computing device can update an owner identifier of the NFT with the first public key associated with the first user.

Abstract: Disclosed are various embodiments for authenticating a user using non-fungible tokens (NFTs). A trusted token issuer verifies a user's identity according to identifying credentials (e.g., government issued identification, passport, driver's license, etc.) presented by the user and creates a non-fungible token in response to verifying the credentials. The non-fungible token is associated with a user identifier and can be used by an access provider to authenticate a user requesting access to restricted content provided by the access provider. For example, when a client device associated with the user requests access from an access provider to an access-restricted website or other type of access-restricted area (e.g., building, concert venue, network, etc.), the access provider (e.g., website server, building computing device, venue system, etc.) uses the properties of the non-fungible token to verify one's identity and permit access upon verification.

Abstract: Disclosed are various embodiments for using decentralized identity to verify account information for a user requesting a transfer of funds between one or more financial entities (e.g., banks, credit unions, brokerage firms, mortgage companies, etc.). A user having account with a first entity can request that a balance credential be created claiming that the balance of funds within the account meets or exceeds a predefined threshold. The balance credential can be created and saved on a distributed ledger in relation to a decentralized identity identifier (DID) of the user. When a second entity wants to verify the account balance of the user, the verifying entity which can use the DID to access the balance credential on the distributed ledger and validate the accessed credential.

Abstract: Systems and methods for the maintenance of merchant-stored transaction account data are disclosed. The system may include various merchant systems and issuer systems in communication via a blockchain network. The system provides a process for collaboration between various issuer systems and merchant systems to update and maintain merchant stored transaction account data in response to changes, cancellations, updates, or the like in various stored transaction account.

Abstract: Disclosed are various embodiments for generating payment accessibility notifications for individuals with impairments. In one non-limiting example, a system includes a first computing device configured to identify a second computing device using a wireless communication protocol in a store location. A first notification for the first computing device is activated based at least in part on an accessibility type. A user interface is displayed for receiving client data, and the client data includes a product entered by a user. An expected amount is determined for the product based at least in part on the client data and transmitted to the second computing device. A pending amount for the product is received from the second computing device. A second notification is activated for the first computing device prior to a completion of the purchase based at least in part on the pending amount and the expected amount.

Abstract: Disclosed are various embodiments for a service for decentralized browser based wallets. Various embodiments of the present disclosure can receive a first passcode and a second passcode from a security provider device. Various embodiments can use a cryptowallet to decrypt a first encrypted private key using the first passcode to generate a decrypted private key. Various embodiments can use a cryptowallet to sign a transaction request with the decrypted private key. Various embodiments can use a cryptowallet to generate a second encrypted private key by encrypting the decrypted private key using the second passcode.