Various embodiments are generally directed to continuous authentication of a user to a digital service based on activity of a contactless card positioned proximate to a computing device on which the digital service operates. For example, a series of periodic status messages may be provided between a client device and the contactless card to verify whether the contactless card remains active, wherein authorization to access the digital service continues while the contactless card is active, and terminates when the contactless card is inactive.

A method for processing, by a processing entity, of an authorization to implement a service and/or access an item. The method includes: reception, from a requesting device, of a request for implementing a service and/or accessing an item; searching for an indicator of dependency from at least one piece of data of said request for implementation; when an indicator of dependency is present, obtaining an authorization from a verification device to implement said service and/or access said item.

The invention relates to an electronic transaction method for a system comprising a user-associated payment device 3 or 4 and a payment terminal 1. The payment device 3 or 4 and the payment terminal 1 perform a cryptographic key exchange 500 before performing a transaction step 501. The payment device includes personal information PI about the user. The payment terminal includes a transaction policy including a condition relative to the personal information Pi. The method includes a verification step 510, 520, 530, prior to the transaction step 501, for securely verifying the condition of the transaction policy relative to the personal information using the cryptographic key.

A device and method for managing personal data. A request for an identifier (ID) token corresponding to a user is received from a virtual wallet. The ID token is generated and transmitted to the virtual wallet, where the ID token is then presented to a third-party entity by a device of the user. A request for the personal data corresponding to the ID token is received from the third-party entity. A trustworthiness score is determined that corresponds to the third-party entity based at least in part on an analysis of entity data corresponding to the third-party entity. The trustworthiness score and received request are transmitted to the virtual wallet and passed on to the user device. An indication of acceptance of the request and encrypted personal data associated with the generated ID token are received from the virtual wallet and transmitted to the third-party entity for processing.

A method for offline transmission of blockchain details includes: storing, in a computing device, a first private key and a currency amount; receiving a first destination address associated with a blockchain network and a transaction amount; generating a second private key; generating a second destination address associated with the blockchain network using the second private key; generating a blockchain transaction including at least the first destination address, the transaction amount, the second destination address, and a remainder amount based on at least the currency amount and the transaction amount; signing the generated blockchain transaction using the first private key; executing a query to replace the first private key with the second private key, wherein replacement of the first private key includes deletion of the first private key from the computing device; and transmitting the generated blockchain transaction.

Systems, methods, and devices for provisioning funding card numbers to merchant wallets are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for provisioning funding card numbers to third party wallets may include: (1) authenticating a customer using an electronic device; (2) redirecting the customer to a third-party website; (3) receiving, from the third-party website and via a first API, a request for funding primary account numbers (FPANs) associated with the customer; (4) providing the third-party website with a plurality of FPAN identifiers for FPANs associated with the customer; (5) receiving, from the third-party website and via a second API, a request for a FPAN associated with a selected FPAN identifier; (6) encrypting the FPAN associated with the selected FPAN identifier; and (7) communicating the encrypted FPAN to the third-party website.

A first security element is for transmitting an electronic coin data set to a second security element. The electronic coin data set is registered in a coin register of a payment system. The method has the steps of: setting a status of the electronic coin data set from the security element to an inactive status; transmitting the electronic coin data set from the first security element to the second security element; checking whether a receipt confirmation from the second security element has been received in the first security element; and deleting the transmitted electronic coin data set if the checking step results in that the receipt confirmation has been obtained by the first security element. The aforementioned relates to a payment system, a coin register, a security element, and a terminal for transmitting electronic coin data sets.

Systems, methods, apparatuses, and computer-readable media for server-side redirect of uniform resource locators (URLs) generated by contactless cards. In one aspect, a server may receive, from a client, a first request comprising a uniform resource locator (URL), where parameters of the URL include a cryptogram and a customer identifier of an account associated with the contactless card. The server may decrypt the cryptogram and determine a context of the account based on one or more attributes of the account. The server may select, based on the decryption of the cryptogram and the determined context, a first redirect URL of a plurality of redirect URLs. The server may transmit, to the client, a response including the redirect URL. The server may receive, from the client, a second request including the redirect URL. The server may transmit, to the client, a response including a resource at the redirect URL.

Systems and methods for authentication may include an authentication server. The authentication server may include a processor and a memory. The processor may be configured to receive an authentication request. The processor may be configured to transmit a notification. The processor may be configured to receive a response that is responsive to the notification, the response comprising a ciphertext and input data. The processor may be configured to generate a Fast Identity Online (FIDO) key pair including a FIDO public key and a FIDO private key. The processor may be configured to encrypt a challenge using the FIDO private key. The processor may be configured to transmit the FIDO public key to decrypt the challenge so as to complete the authentication request.

Embodiments described herein provide a user interface for interacting with a smart contract deployed to a blockchain. The user interface is custom-generated for each party to the smart contract. In particular, representations of actions that a particular party is enabled to perform and/or has already taken with respect to the smart contract are provided to that party via a user interface. A user experience generator queries the smart contract itself to determine which representations are to be provided to each party. The smart contract comprises functions and/or user experience annotations that indicate to the user experience generator which user interface representations should be provided to a particular user based on the party identity and/or the smart contract's state. The smart contract provides an event notification to the user experience generator, which prompts the user experience generator to query the smart contract to determine the allowed actions for a particular user.