Multifactor authentication techniques described herein may allow a user to submit a recent proof of purchase as a part of a multifactor authentication process to access an account associated with a financial institution. As part of the login process, the user may submit a proof of purchase associated with a transaction. The financial institution may determine information associated with the transaction, such as a merchant associated with the proof of purchase, a time of the transaction, the last four numbers of the transaction card used, a dollar amount, or any combination thereof. If the information matches one or more records in the transaction history of the user's account, the financial institution may authenticate the user and provide access to the account. In this way, the financial institution may leverage transaction history known to the financial institution and the user to authenticate the user.

Various aspects of the subject technology relate to systems, methods, and machine-readable media for securely communicating personal information. The method includes receiving, from a user, personal information regarding the user. The method also includes storing the personal information in secure storage. The method also includes receiving, from a third party, a request for the personal information of the user. The method also includes receiving, from the user, authentication of the request for the personal information of the user. The method also includes in response to receiving the authentication, providing metadata to the third party comprising a promise to supply the personal information of the user, the metadata further comprising at least one of a timestamp, delta, or version number. The method also includes receiving, from a requestor, a notification for resolution of the promise, the notification identifying which of the personal information is required to complete a transaction.

Account functionality may be modified in response to an event. A processor may determine that a status of at least one of a user, a device associated with the user, and data associated with the user is potentially insecure due to the event. The processor may identify an account of the user. The account may provide access to electronic financial transaction functionality. In response to the determining that the status of at least one of the user, the device associated with the user, and the data associated with the user is potentially insecure, the processor may modify a condition affecting the access to the electronic financial transaction functionality.

In one arrangement, a method for using symmetric keys between two entities comprising a device and a host include initiating, by the device, a transaction involving original data, wherein the original data needs to be verified by the host. The method further includes deriving, by the device, a first key based on a previously generated key and a first number, wherein the first key is unique to the transaction, and the first number is randomly generated. The method further includes sending, by the device, the first key to the host for verification.

There is provided a processor(s) executing a blockchain smart contract, for: managing a primary reserve of primary tokens and a secondary reserve of secondary tokens, receiving a transaction request, obtaining an external price of the primary token, compute an updated value of the primary reserve according to the external price, in response to the updated total value of primary reserve being unequal to an initial staked value of the primary reserve, adjust primary and secondary dynamic reserve weights, wherein a total value computed by a function of the primary reserve after being increased or decreased by a target amount of primary tokens and using the adjusted primary and secondary dynamic reserve weights, is equal to the initial staked value of the primary reserve, and the total value of the primary reserve is maintained at a predefined ratio to a total value of the secondary reserve, and executing the transaction request.

Methods for managing security of a payment gateway are provided. In one aspect, a method includes assigning a username and a security key to a merchant. The method includes receiving a transaction request associated with the merchant, wherein the transaction request comprises the username assigned to the merchant, request parameters, and a signature code associated with the merchant, and wherein the signature code comprises the request appended to both the username assigned to the merchant and the security key assigned to the merchant. The method includes determining, in response to receiving the transaction request associated with the merchant, whether the signature code of the request is authentic. The method includes validating the transaction request based on determining that the signature code of the request is authentic. Systems and machine-readable media are also provided.

This application discloses a method implemented at a server to facilitate secure offline transactions. The server receives, from a client device, an authorization request that includes a user identifier, first financial account information and a secure code. The server authenticates the authorization request, and sends a first transaction approval to the client device. Then, in accordance with the information received in the authorization request, the server facilitates a secure transaction between the client device and a point-of-sale (POS) machine while the client device is offline. Specifically, the server receives, from the POS machine, a transaction request that includes at least the user identifier and the security code. The server retrieves the first financial account information from a memory according to the user identifier and the security code, performs a transaction operation associated with the first financial account information, and sends a second transaction approval to the POS machine.

Systems and methods build blockchains and verify assets for smart contracts. A system includes a memory, a blockchain, a set of nodes, a set of verifiers, a set of miners, and a consensus protocol. The memory can have a block data structure representing a transaction for an asset having an identifier and at least one verifiable characteristic. The consensus protocol can include rules for: receiving the stake at risk from the verifiers, providing the reputational score to the verifiers, verifying the verifiable characteristic of the asset by the verifiers, cryptographic verification by the miners, adding the new block to the blockchain by the miners, providing the reward to the miners, and distributing the copy of the blockchain to each node.

A method and apparatus for secured, peer-to-peer transfer of data rights over a computer network, the method being accomplished by a distributed computing system including a distributed ledger platform. Root rights are defined and delegated to wallets in a multilevel manner to thereby isolate wallets associated with the root right from cyber risk.

Gift givers typically find the process of selecting a personalized gift for a gift recipient to be time consuming with a low likelihood that the selected gift will be positively received by the recipient. The present disclosure describes analyzing a gift recipient's transaction history using machine learning techniques. Based on the analysis, one or more gift recommendations are provided to the gift giver. The one or more gift recommendations may comprise links to purchase products associated with the one or more gift recommendations. Additionally or alternatively, the one or more gift recommendations may comprise information about where the product may be purchased. This may improve the overall accuracy of the gift giving process, while reducing the stress surrounding gift giving. Additionally, the commercial opportunities of businesses may be expanded by partnering with sites that host the analysis.