G06Q20/38215

Information sharing methods, apparatuses, and devices

Examples in this application disclose an information sharing methods, media, and systems. One example method includes receiving, by a trusted execution environment (TEE), a user verification result acquisition request from a first institution, where the user verification result acquisition request is configured to request a verification result associated with a user, receiving first encrypted data of the user from a second institution, decrypting the first encrypted data to obtain first user basic data, receiving second encrypted data of the user from a trusted institution, decrypting the second encrypted data of the user to obtain second user basic data, in response to the user verification result acquisition request, determining the verification result of the user to indicate whether the first user basic data matches the second user basic data, and sending the verification result of the user to the first institution.

Infusing custom qualities into an artificially intelligent entity
11496308 · 2022-11-08 ·

Some examples of the present disclosure relate to infusing custom qualities into an artificially intelligent entity. In one example, a system can initiate execution of a smart contract that is configured to generate a correlation between a second non-fungible token (NFT) and a first NFT. The first NFT can include personality fields with default values defining default personality characteristics for an artificially intelligent entity. The second NFT can include a personality field with a customized value defining a customized personality characteristic assignable to the artificially intelligent entity. The correlation can be configured to impart the customized personality characteristic to the artificially intelligent entity.

SYSTEMS AND METHODS FOR MINTING A PHYSICAL DEVICE BASED ON HARDWARE UNIQUE KEY GENERATION
20220353074 · 2022-11-03 ·

Minting a physical computing device based on unique key generation, wherein the key generation is configured to create a private-public key pair. In implementations, the key pair may be generated upon initialization of the physical computing device, such that the physical computing device is minted with the key pair. The key pair may be utilized as a token for supply-chain billings, payments, auditing, etc. associated with the physical computing device.

CRYPTOGRAPHICALLY ENFORCED MULTI-SIGNATURE APPLICATION WITH PRECONDITIONED ELECTRONIC MECHANISM FOR UNILATERAL WITHDRAWAL

A method and device for executing the method to: control an unused transaction output (utxo) stored in a first digital wallet of a first user according to a private key of the first user; generate a transaction for transferring rights over the utxo from the first digital wallet to a second digital wallet; generate a cryptographic hash of the transaction into a unique transaction identification of the transaction; transmit the unique transaction identification of the transaction to a party other than the first user; in response to transmission of the unique transaction identification of the transaction, receive a redeem transaction cryptographically signed by a private key of the party other than the first user; cryptographically sign the received redeem transaction with the private key of the first user; store the redeem transaction in the first digital wallet; and transmit confirmation that the redeem transaction is valid.

METHODS AND SYSTEMS OF PROVIDING VERIFICATION OF THE IDENTITY OF A DIGITAL ENTITY USING A CENTRALIZED OR DISTRIBUTED LEDGER

Methods and systems of providing verification of the identity of a digital entity are provided, including receiving information and a public key of the digital entity, wherein the information has been previously attested to in an attestation transaction stored within a centralized or distributed ledger at an attestation address, the centralized or distributed ledger providing a record of transactions; deriving an attestation address using the information and the public key of the digital entity; verifying the existence of the attestation transaction at the attestation address in the centralized or distributed ledger and verifying that the attestation transaction has not been revoked; receiving at the processor associated with the user a cryptographic challenge nonce signed by the digital entity's private key; and verifying the digital entity's identity with the cryptographic challenge nonce signed by the digital entity's key.

Systems and Methods for Control and Reconciliation of Virtual Token Accounts

A system for control and reconciliation of virtual token accounts is disclosed. The system may receive a request to generate a virtual token. The request to generate the virtual token may comprise a parent transaction account and an authorization control, an intelligent supplier analytic, and/or an enhanced client data record. The system may generate the virtual token, and associate the virtual token to the parent transaction account. The generated virtual token may comprise a virtual token balance and a virtual token ID, and may also comprise the authorization control, the intelligent supplier analytic control, and/or the enhanced client data record.

USER AUTHENTICATION USING A BROWSER COOKIE SHARED BETWEEN A BROWSER AND AN APPLICATION

A system and/or method may be provided to authenticate a user. An example method of authenticating a user includes receiving, by a merchant application, a user request to complete a transaction using a payment service provider. The method also includes in response to receiving the user request to complete the transaction, retrieving, by the merchant application, a browser cookie stored on a user device and associated with one or more user interactions with a browser included in the user device and the payment service provider. The method further includes in response to receiving the user request to complete the transaction, launching, by the merchant application, an instance of the browser that reads the browser cookie and authenticates the user based on the browser cookie.

SYSTEMS AND METHODS FOR COST ALTERING PAYMENT SERVICES

Cost altering payment services (“CAPS”) system in association with a distributed enhanced payment (“DEP”) processing system includes a merchant point of sale (“POS”) terminal system and a remote enhanced payment management system (“EPMS”). The remote EPMS receives payment transactions including additional risk mitigating payment transaction (“RMPT”) information and based on that additional RMPT information provides altered transaction costs. The remote EPMS provides facilities for the merchant to review and revise payment management services so as to utilize additional RMPT information received from the merchant POS terminal system so as to alter transaction costs. Such facilities provide information to determine the relative potential transaction cost benefits of various payment management service sets utilizing cost profiles that represent the costs of archival, recorded and projected future transactions. The remote EPMS provides “transaction guidance” technology to be utilized by the merchant's POS terminal system to facilitate prompting for and acquiring additional RMPT information.

Transaction-enabled systems for providing provable access to a distributed ledger with a tokenized instruction set

Transaction-enabling systems including a controller are disclosed. The controller can access a distributed ledger including an instruction set, tokenize the instruction set, interpret an instruction set access request, and, in response to the instruction set access request, provide a provable access to the instruction set.

Rule-Based Token Service Provider

Methods and systems are provided to receive token context data from a token request, determine parameters of a custom token, and generate and communicate the custom token. Tokens may be generated that are compatible with one or more payment providers from a plurality of possible payment providers. Data related to current and future conditions of the payment providers, merchant preferences, customer preferences, locations of the merchant, customer, and/or the transaction, and regulatory rules may be used to select the payment provider.