Abstract: A system and method for facilitating electronic commerce over a network, according to one or more embodiments, includes communicating with a user via a user device and a business entity via a business entity device over the network, monitoring user navigation events over the network, determining a mood of the user based on user navigation behavior, marketing to the user based on the mood of the user, and storing user information related to the user navigation events and the mood of the user.

Abstract: A system may generate a seed one-time password (OTP). The system may also perform steps including transmitting the seed OTP to a user device, receiving a response OTP from the user device, and calculating an expected response OTP by applying a function to the seed OTP. The system may then compare the response OTP to the expected response OTP and send a result in response to comparing the response OTP to the expected response OTP.

Abstract: A payment network is operated with a blockchain-based ledger. In one embodiment, a request is prepared to complete a transaction from an account associated with a payer digital wallet for entry on a blockchain. The request includes an amount and a payee identifier associated with a payee digital wallet. The request is sent to the blockchain and approved. A balance of the payer digital wallet and a balance of the payee digital wallet are adjusted in response to approval of the request to complete the transaction by at least writing a portion of data associated with the transaction comprising the amount and the payee identifier to the blockchain. A reputation ledger associated with the account is recorded in the blockchain in association with the transaction. The reputation ledger includes at least one reputation score associated with at least one previous transaction conducted by the account.

Abstract: A user who is authorizing a delegate to make a purchase using funds from an account of the user sends information to a payment provider. The information includes a picture of the delegate, along with information such as a merchant name, a maximum amount, a type of purchase, item information, and/or any other transaction limitations/restrictions. The payment provider then transmits this information to the merchant. A one-time code or number may be communicated to the delegate. When the delegate is ready to make a payment with the user account, the delegate gives the delegate's name and/or other identifying information to the merchant, along with the payment code. The merchant enters the information and is shown a picture of the delegate. If there is a match, the payment may be submitted for processing. In one embodiment, a photo of the delegate may be taken by the merchant and the image transmitted to the user. The user may then be requested to confirm the delegate as an authorized delegate.

Abstract: A system for operating a payment network with a blockchain-based ledger may prepare a request to complete a transaction from an account associated with a payer digital wallet for entry on the blockchain. The request may include an amount and payee address associated with a payee digital wallet. The system may also send the request to the blockchain using a blockchain interface. The system may approve or decline the request. The system may further adjust a balance of the payer a balance of the payee to reflect approval of the request. The adjustment may include writing the transaction to the blockchain.

Abstract: A system may receive a primary image containing a first set of facial feature data. The primary image may be sent by a facial recognition device for association with a user account. The system may also retrieve a secondary image from a secondary image source. The secondary image may contain a second set of facial feature data. The secondary image may further depict a user associated with the user account. The system may then compare the first set of facial feature data to the second set of facial feature data to determine whether the primary image depicts the user associated with the user account.

Abstract: Systems and methods for the calculation of a dynamic trust score are disclosed. The dynamic trust score may indicate a likelihood that the consumer will complete the transaction in a positive manner. The system may calculate the dynamic trust score based on various static and dynamic variables including digital identity data, internal data, third-party data, private data, and/or data from the transaction initiated by the consumer.

Abstract: Systems and methods for facilitating financial transactions over a network include a merchant device, a client device and a payment processing device. The merchant device is adapted to allow a merchant to provide items for purchase via the network. The client device is adapted to allow a user to access the merchant device via the network and view the items for purchase. The client device is adapted to provide a payment mechanism to the user. The user generates a purchase request for an item by selecting the one item, dragging the item to the payment mechanism, and dropping the item over the payment mechanism. The payment processing device is adapted to receive the purchase request from the client device via the network and authorize the user to purchase the item from the merchant based on information passed with the purchase request.

Abstract: A system for conducting transactions without a debit card or credit card may receive a request to complete a transaction including authentication data associated with a transaction account and a captured biometric template. The transaction request may lack information contained on a typical debit card or credit card. The system may identify the transaction account using the authentication data associated with the transaction account. The transaction account may be associated with a stored biometric template stored in a biometric data store. The system may also compare the stored biometric template with the captured biometric template. In response to the stored biometric template conflicting with the captured biometric template, the system may decline the transaction.

Abstract: A user may apply for an account on an account registration page. The account issuer may receive a phone number of a mobile device used to apply for the account. The account issuer may transmit the phone number to a carrier integration server which may obtain user information from the wireless carrier for the mobile device. The account issuer may autofill fields on the account registration page with the user information. The user may upload a photograph of the user and an identification card. The account issuer may perform facial recognition to verify the identity of the user.

Abstract: A hybrid identity service system is disclosed. The system may receive a transaction request. The system may generate a first passcode and a second passcode. The system may decrypt a first encrypted private key with the first passcode to recover a private key. The system may sign the transaction request with the private key and may encrypt the private key with the second passcode to generate a second encrypted private key.

Abstract: A system receives a source and a metadata layer that describes the source. The source may comprise source records with fields containing source data, and the metadata layer may include metadata comprising at least one of a field data type, a field data length, a field description, or a record length. The processor may further validate the metadata layer against the source and write results to a log. The processor may further be configured for transforming the source records into transformed records for a load ready file. The processor may further balance a number of records in the source against a number of transformed records in the load ready file to generate a transformation failure rate.

Abstract: Embodiments of the invention are directed to methods, systems and devices for providing sensitive user data to a mobile device using an encryption key. For example, a mobile application on a mobile device may receive encrypted sensitive user data from a mobile application server, where the user sensitive data is encrypted with a key from a token server computer. The mobile application may then request that the encrypted payment information be sent to the token server. The mobile device may then receive a payment token associated with the payment information from the token server.

Abstract: Embodiments of the invention relate to efficient methods for authenticated communication. In one embodiment, a first computing device can generate a key pair comprising a public key and a private key. The first computing device can generate a first shared secret using the private key and a static second device public key. The first computing device can encrypt request data using the first shared secret to obtain encrypted request data. The first computing device can send a request message including the encrypted request data and the public key to a server computer. Upon receiving a response message from the server computer, the first computing device can determine a second shared secret using the private key and the blinded static second device public key. The first computing device can then decrypt the encrypted response data from the response message to obtain response data.

Abstract: Systems, methods, and computer program products for providing secure messaging communications are disclosed. For example, a computer-implemented method may include receiving an encrypted message and a key from a sender associated with a first computing device where the encrypted message is generated by the first computing device, verifying the received key at least in part based on a comparison with a pre-determined key, processing one or more unique factors associated with the sender in view of verifying the received key, decrypting the encrypted message, re-encrypting a result of the decrypting using a key of a receiver associated with a second computing device, and sending the re-encrypted result to the receiver associated with the second computing device.

Abstract: Embodiments of the invention relate to efficient methods for authenticated communication. In one embodiment, a first computing device can generate an ephemeral key pair comprising an ephemeral public key and an ephemeral private key. The first computing device can generate a first shared secret using the ephemeral private key and a static second device public key. The first computing device can encrypt request data using the first shared secret to obtain encrypted request data. The first computing device can send a request message including the encrypted request data and the ephemeral public key to a server computer. Upon receiving a response message from the server computer, the first computing device can determine a second shared secret using the ephemeral private key and the blinded static second device public key. The first computing device can then decrypt the encrypted response data from the response message to obtain response data.

Abstract: Systems, methods, and computer program products for providing secure messaging communications are disclosed. For example, a computer-implemented method may include receiving an encrypted message and a key from a sender associated with a first computing device where the encrypted message is generated by the first computing device, verifying the received key at least in part based on a comparison with a pre-determined key, processing one or more unique factors associated with the sender in view of verifying the received key, decrypting the encrypted message, re-encrypting a result of the decrypting using a key of a receiver associated with a second computing device, and sending the re-encrypted result to the receiver associated with the second computing device.

Abstract: Embodiments of systems and methods for client and/or server authentication are provided. In one embodiment, a method includes sending information from a mobile network device to a server, wherein the information comprises a seed that is used by both the mobile network device and the server to compute a series of one time passwords. The method also includes receiving, by the mobile network device, a succession of one time passwords generated by the server throughout a session. And the method further includes comparing the received one time passwords generated by the server throughout the session to corresponding one time passwords generated at the mobile network device. In this manner, the server can be authenticated. In various embodiments, the process may be reversed to facilitate client, e.g., mobile network device, authentication.

Abstract: A system for conducting transactions without a debit card or credit card may receive a request to complete a transaction including authentication data associated with a transaction account and a captured biometric template. The transaction request may lack information contained on a typical debit card or credit card. The system may identify the transaction account using the authentication data associated with the transaction account. The transaction account may be associated with a stored biometric template stored in a biometric data store. The system may also compare the stored biometric template with the captured biometric template. In response to the stored biometric template conflicting with the captured biometric template, the system may decline the transaction.

Abstract: Systems and methods for fraud management using a distributed database are disclosed. The system may receive a payment request and generate a payment request hash by cryptographically processing the payment request using a hashing algorithm. The system may invoke a fraud reporting smart contract by passing the payment request hash and a public blockchain address to the fraud reporting smart contract. The system may query a local blockchain database to locate a fraud report matching the payment request hash to determine whether the payment request has been previously reported as fraud. In response to the payment request hash not matching the fraud report, the fraud reporting smart contract is configured to write the payment request hash to the blockchain as a second fraud report.