A round trip resource sharing method and system with time slot locking is disclosed. The method may include issuing a time slot-based owner certificate and an owner resource profile through a shared resource transaction system; setting a shared resource to a time slot authentication and authorization device with the owner certificate and resource profile; disclosing the set shared resource to the transaction system; setting a lessee certificate and a lessee resource profile of a lessee who concluded a transaction to the time slot authentication and authorization device; using, by the lessee, the shared resource through the time slot authentication and authorization device or disclosing the shared resource to the transaction system for resale permitted by the owner.

A ledger based dynamic digital address masking solution for reducing vulnerability of private cryptographic keys used during digital transactions. Tokenized digital transaction addresses may be stored in association with an actual distributed ledger reference address. The tokenized transaction address, or recipient token, may be used to complete a variety of transactions for digital asset exchange without exposing the transaction address's actual reference address on the distributed ledger.

A processor may register one or more verifiable asset credential schemas. A verifiable asset credential schema may prescribe the format and content of asserting blockchain-backed asset state. The processor may register an issuer policy for the verifiable asset credentials. The issuer policy may be associated with a schema and intended credential holder(s). The processor may subscribe the asset credential issuer to one or more peers on the blockchain. The processor may issue commit notifications to a subscribing asset credential issuer in the form of schema-compliant committing-peer verifiable credentials. The processor may collect the committing-peer verifiable credentials from one or more peers. The processor may validate the committing-peer verifiable credentials satisfy the security policy and schema for a designated intended credential holder. The processor may issue a schema-compliant verifiable asset credential to the policy-designated credential holder(s).

Systems and methods disclosed herein provide automatic expense categorization of transactions or expenditures based on a machine learning (ML) model trained using anonymized transactional data for expenditures that are stored in a public blockchain. The anonymized transactional data for the expenditure and the expense category, may be distributed throughout the blockchain network and recorded in the blockchain. In some implementations, an expenditure may be submitted to the blockchain network for expense categorization. The transactional data for the expenditure may be anonymized to remove confidential and personal identifying information (PII) before it is distributed throughout the blockchain network. Each participating node of the blockchain network may utilize the ML model to identify an expense category for the expenditure. The participating nodes may provide a consensus mechanism in order to arrive at a shared understanding of how to categorize the expenditure.

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.

In accordance with a first aspect of the present disclosure, a user authentication system is provided, comprising: a user authentication token, said user authentication token comprising a fingerprint sensor and a secure element; an assistance device configured to be coupled to the user authentication token through an interface of said user authentication token; wherein the assistance device is configured to request the secure element to verify a personal unlock key to be captured by the secure element through the fingerprint sensor; wherein the secure element is configured to capture the personal unlock key through the fingerprint sensor, to verify the captured personal unlock key and to enroll, upon or after a positive verification of the personal unlock key, fingerprint reference data captured through the fingerprint sensor. In accordance with a second aspect of the present disclosure, a corresponding method for enrolling fingerprint reference data in a user authentication token is conceived. In accordance with a third aspect of the present disclosure, a corresponding computer program is provided.

Method of certification including receiving user data at a device of a certifying entity. The method includes generating a salt that is unique. The method includes hashing the data combined with the salt to create a generated hashed data. The method includes generating a certification record based on signing the generated hashed data using a private key of the certifying entity to create a signed certification of the data. The method includes hashing the certification record. The method includes transmitting the hashed certification record to a blockchain for storing. The method includes receiving a certification tx-ID of the hashed certification record. The method includes generating a certification data block including the certification record and the certification tx-ID. The method includes storing the certification data block to a side chain.

A method of associating a first party and a second party is provided, the method comprising receiving a first electronic message comprising information indicative of the first party; generating a first electronic token in response to receiving the information indicative of the first party; sending the first electronic token to the first party; receiving one or more second electronic messages from the second party, the one or more second electronic messages comprising the first electronic token and information indicative of the second party; generating a second electronic token in response to receiving the first electronic token and the information indicative of the second party from the second party; associating the information indicative of the first party, the second party and the second electronic token, the first party being identified on the basis of the first electronic token, and sending the second electronic token to the first party.

In some embodiments, exemplary user interfaces for provisioning an electronic device with an account are described. In some embodiments, exemplary user interfaces for providing usage information of an account are described. In some embodiments, exemplary user interfaces for providing visual feedback on a representation of an account are described. In some embodiments, exemplary user interfaces for managing the tracking of a category are described. In some embodiments, exemplary user interfaces for managing a transfer of items are described. In some embodiments, exemplary user interfaces for managing an authentication credential connected with an account are described. In some embodiments, exemplary user interfaces for activating a physical account object are described. In some embodiments, exemplary user interfaces for managing balance transfers are described.

The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.