Disclosed is a system for enrolling a user for facilitation of transactions using biometric authentication. The enrolling system includes an application program that is configured to: receive a user attribute; create an anonymous client reference (ACR) associated with the user attribute; and receive a biometric template. The biometric template has been determined from an input of a biometric. The enrolling system is further configured to create an association between the biometric template and the ACR.

The present disclosure relates to a method for approving the use of a card by using a token-ID, wherein, in a state where a card token ID, identification information of a user, a push token ID, and a public key of the user are registered in a blockchain database and a blockchain transaction ID corresponding thereto is managed, when payment request information is acquired, a relay server: requests authentication of order data from a user terminal; checks whether a user signature value obtained in response to the authentication request is valid, and registers the order data in the blockchain database; and registers, in the blockchain database, approval result information which is obtained through verification of the order data by a financial server, and transmits the approval result information to at least one of a service providing terminal and the user terminal.

Systems and methods for real-time account access, allowing access to accounts (such as deposit, credit, or debit accounts) through network processing infrastructures such as Electronic Funds Transfer (EFT). In some embodiments, consumers and/or merchants are able to effect transaction requests against accounts, using a pseudo-identifier or other identifier, and without the need to provide an account number or card number. In other embodiments, payment networks are able to route and process transaction requests against accounts, without having a card number or account number. In other embodiments, account processing systems are able to determine an appropriate account based on transaction requests that do not contain card numbers or account numbers.

A bridge service is provided to support multi-user simulated contactless cards that in response to receiving a request to provision a secure element with payment card profile information of a user, provisions a token representing the payment card profile, converts the token representing the payment card profile into a format for the payment application; and provides the payment card profile to the payment application, the payment card profile comprising a single use key. The bridge service enables simulated contactless cards to store payment card information for a user on volatile memory instead of the persistent, secure element memory.

A virtual payment system for paying for goods, services and content ordered over an internetwork is disclosed. The virtual payment system includes a commerce gateway. Buyers and sellers becomes registered participants by applying for virtual payment buyer and seller accounts. Once an account is established with the commerce gateway, a digital certificate is stored on the registered participant's computer. A buyer can then order a product, i.e., goods, services or content from a seller and charge it to the virtual payment account. When the product is shipped, the seller notifies the commerce gateway, which applies the charges to the buyer's virtual payment account. The buyer can settle the charges using a prepaid account, a credit account, or by using reward points earned through use of the virtual payment account. A buyer may create sub-accounts.

A system and method are provided for monitoring transaction events. The method includes connecting the event processor device with at least one payment services channel and listening for events provided by the at least one payment services channel. The method also includes detecting an event associated with a masked transaction being facilitated by a payment service that masks a payment card number. The method also includes determining from the masked transaction a user identifier associated with the transaction, determining from the user identifier the payment card number, and confirming that the payment card number is linked to the loyalty program with the loyalty partner. When the payment card number is linked to the loyalty program, the method includes sending a message to the loyalty partner to have the loyalty partner execute a loyalty program action associated with the transaction that would have otherwise been masked at the point of sale.

A mobile wallet computer server receives a fund access request from a user device. The fund access request is made in connection with a payment transaction. The mobile wallet server generates a tokenized card number, transmits the tokenized card number to the user device, and receives receive the tokenized card number from a card network computer system after having been routed from the user device via a merchant computer system and via an acquirer processor computer system. The mobile wallet computer server converts the tokenized card number to the actual credit card account number of the user and transmits the actual credit card account number to the card network computer system to process the payment transaction.

A mobile device includes a display device; a processor; and a memory device configured to store instructions that, when executed by the processor, cause the processor to: present, by the display device, a user interface to a user of the mobile device for accessing a mobile online banking application; upon accessing the mobile online banking application, provide, by the display device, an option to a create a mobile wallet; responsive to receiving an indication to create the mobile wallet, provide, by the display device, a list of accounts held by the user; and receive a selection of at least one account from the list accounts to provision the at least one account to the mobile wallet for use in future mobile wallet transactions such that the at least one account from the list of accounts is auto-provisioned to the mobile wallet.

A method for implementing transactions includes receiving, by a first computing system, a transaction request from a second computing system, the transaction request indicating a first account number that is an alias of a transaction account having a second account number, and specifying a transaction. The method further includes determining the second account number by referencing a data structure that associates the first account number and the second account number, determining a verification policy associated with the second account number, and transmitting a verification challenge based on the verification policy. The method yet further includes receiving a response to the verification challenge, determining to authorize the transaction request based on the response to the verification challenge, and implementing the transaction involving the transaction account specified by the transaction request.

A method including receiving a request based on a sender initiating a funds transfer. The funds transfer can be for the sender to make a payment to a non-financial institution. The sender can have a sender account at a sender financial institution. The non-financial institution can have a recipient account at a recipient financial institution. The method also can include facilitating obtaining sender identifying information from the sender. The method additionally can include facilitating sending at least (a) the sender identifying information, (b) a recipient public identifier of the non-financial institution, and (c) a payment amount for the payment to the sender financial institution to cause the sender financial institution to (i) determine a funds availability of the sender account to make the funds transfer for the payment amount and (ii) send a funds transfer request to a computer-implemented funds transfer network to make the payment from the sender account at the sender financial institution to the recipient account at the recipient financial institution. The funds transfer request can include the recipient public identifier and the payment amount. The funds transfer request does not include an account number of the recipient account. The computer-implemented funds transfer network can include a first directory mapping the recipient public identifier to a recipient private identifier. The computer-implemented funds transfer network can be configured to send the recipient private identifier to the recipient financial institution to enable the recipient financial institution to map the recipient private identifier to the account number of the recipient account and make funds available to the recipient account in real-time for the payment. The computer-implemented funds transfer network can be operated by an entity that is different from the recipient financial institution and the sender financial institution. Other embodiments are disclosed.