Abstract: Tokens are used for payment systems. The tokens are references or proxies to actual payment credit card or banking card numbers to improve security. However, verification of these tokens are often limited and rigid systems and are prone fraud. An improved token framework system is provided to allow for different entities to provision and verify the tokens using strong identity and strong authentication at the device level. For example, biometric identity and verification using the mobile device is used to authenticate the tokens during provisioning and subsequent transactions.

Abstract: Systems and methods are provided that allows users to execute a secure digital action that is authenticated by their digital wallet app (or wallet) on a user device or a wallet server. An identity issuer server issues a batch of verification credentials (VCs) for an identity holder to the wallet. The wallet stores the batch of VCs, respectively binds each VC in the batch of VCs with a given passkey from a plurality of passkeys, generates selective disclosures via a content generator server, and transmits the batch of VCs, as a plurality of VC presentations, to an identity verification server. An identity verification server requests and validates the plurality of VC presentations, and, responsive to validating the plurality of VC presentations, registers the plurality of device-bound passkeys respectively bound to the batch of VCs to generate a plurality of registered passkeys.

Abstract: Systems and methods are provided that allows users to execute a secure transaction that is authenticated by their digital wallet on their user device. A device-bound digital wallet authentication process includes first registering data with a user device, a network tokenization server, a card issuer server, a digital coordination and notification (DCN) server, and an access control server. The data includes a network-device token and an alias of a primary account number that are stored on the user device, the network tokenization server, and the card issuer server. The data also includes a notification token, a signing public key and the alias that are stored on the DCN server and the access control server. In the device-bound digital wallet authentication, the alias and the network-device token are used to securely authenticate the user device and transaction information associated with the digital wallet that is bound to the user device.

Abstract: A system is provided that allows users to execute a secure transaction that is authenticated by their user device. Personally identifiable information (PII), such as, but not limited to, biometric authentication data, is locally stored on the user's device so as to protect the PII. A user device private key is associated with the particular user device and the user, and the corresponding public key is registered with a User Device Authentication Alliance server (UDAAS) system. In an online transaction, a LoginID server or an Access Control server interact with the UDAAS to confirm the user is authentic and has confirmed the transaction.

Abstract: User accounts for blockchain technology are prone to security risks, such as account take-overs by malicious actors and lost or inaccessible wallets. A data access server system is herein provided to enable strong authentication credentials, such as FIDO2 public and private key pairs that adhere to Fast Identity Online (FIDO) protocols, to be used generate user account. The FIDO2 public key, also herein called a device authenticator public key, is embedded in a code script, and the code script is executed by the data access server system to verify the user using FIDO authentication. The data access server system also provides user tools to create credentials and associate one or more credentials with a blockchain user account. The user tools also enable rekeying of a blockchain user account with different credentials from another blockchain user account, with both accounts belonging to the same user.

Abstract: Systems and methods are provided that allows users to execute a secure transaction that is authenticated by their digital wallet on their user device. A device-bound digital wallet authentication process includes first registering data with a user device, a network tokenization server, a card issuer server, a digital coordination and notification (DCN) server, and an access control server. The data includes a network-device token and an alias of a primary account number that are stored on the user device, the network tokenization server, and the card issuer server. The data also includes a notification token, a signing public key and the alias that are stored on the DCN server and the access control server. In the device-bound digital wallet authentication, the alias and the network-device token are used to securely authenticate the user device and transaction information associated with the digital wallet that is bound to the user device.

Abstract: A system is provided that allows users to execute a secure transaction that is authenticated by their user device. Personally identifiable information (PII), such as, but not limited to, biometric authentication data, is locally stored on the user's device so as to protect the PII. A user device private key is associated with the particular user device and the user, and the corresponding public key is registered with a User Device Authentication Alliance server (UDAAS) system. In an online transaction, a LoginID server or an Access Control server interact with the UDAAS to confirm the user is authentic and has confirmed the transaction.