Patent classifications
G06Q20/38215
Systems and methods for smart card online purchase authentication
Systems and methods of authenticating online purchases by detecting a presence of an authorized smart card at a personal computing device of a customer are disclosed. An issuer computing system maintains a customer database of personal information and financial information for a plurality of customers with issued smart cards. An authentication logic receives an authentication request sent from a local merchant circuit at the personal computing device over a network. The authentication request comprises an authentication code provided to the local merchant circuit by a contactless chip of a smart card. The authentication logic authenticates the authentication request by comparing the authentication code with stored information in the customer database and transmits an authentication approval to the personal computing device, wherein the authentication approval enables an online purchase transaction request corresponding to the authentication request.
ENERGY RESOURCE NETWORK
An energy resource network with plurality of energy resources each capable of delivering a quantum of energy; and a plurality of energy-consuming-devices each capable of accepting a quantum of energy. Each energy resource is associated with an energy-resource-processor which is configured to issue one or more offer-messages in respect of a quantum of energy available for supply from the energy resource Each energy-consuming-device is associated with at least one energy-consuming-processor) that is configured to receive one or more offer-messages in respect of a transaction for receiving a quantum of energy from one of the energy resources The energy-resource-processor and/or the energy-consuming-processor being configured to issue a cryptographically-secured transaction record of the transaction for inclusion within a publicly-available distributed ledger.
PRIMARY ACCOUNT NUMBER (PAN) LENGTH ISSUER IDENTIFIER IN PAYMENT ACCOUNT NUMBER DATA FIELD OF A TRANSACTION AUTHORIZATION REQUEST MESSAGE
Transaction data is obtained relating to a current purchase transaction. An account indicator is retrieved. The transaction data is used to transform the account indicator. The transformed account indicator is encrypted to generate an encrypted account indicator.
CREDIT PAYMENT METHOD AND APPARATUS BASED ON MOBILE TERMINAL PEER-TO-PEER
Technologies related to mobile credit payment are disclosed. In an implementation, a first SNEP Get Request Message is generated and sent to a mobile computing device, in response to a NFC signal received from the mobile computing device. A first SNEP Response Message is received from the mobile computing device and parsed to identify an APP public key license. A pre-stored credit authorization public key is used to verify the APP public key license and an APP public key is retrieved from the APP public key license if the verification is successful. A second SNEP Get Request Message is sent to the mobile computing device and a second SNEP Response Message is received from the mobile computing device. The APP public key is then used to decrypt the second SNEP Response Message, and a transaction log is recorded if the second SNEP Response Message is successfully decrypted.
TOKENIZING A PRIMARY ACCOUNT NUMBER PRIOR TO TRANSMISSION TO A TERMINAL
In some implementations, a transaction card may receive transaction data from a transaction terminal based on initiation of a transaction with the transaction terminal; generate a tokenized primary account number, for use with the transaction, based on the transaction data and an actual primary account number of the transaction card; and transmit the tokenized primary account number to the transaction terminal for processing the transaction.
BLOCKCHAIN SYSTEM, APPROVAL TERMINAL, USER TERMINAL, HISTORY MANAGEMENT METHOD, AND HISTORY MANAGEMENT PROGRAM
A history of data can be tracked easily on a blockchain. In a blockchain system, a distributed ledger 11 includes a state database that stores a state of a smart contract for each token. A user terminal 1 includes a transaction issue unit 13 that issues a transaction that updates a token. An approval terminal 2 includes an update unit 154 that updates the token in the state database, and a block generation unit 153 that generates the block including the transaction and causes the block and the updated state database to be reflected in the distributed ledger 11. The update unit 154 sets tracking data in the token in the state database, the tracking data including an update block number and token information on the token.
INFORMATION PROCESSING DEVICE
To achieve efficient reading of data from a memory including a plurality of banks by specifying different banks and accessing the memory from a plurality of hash computation circuits simultaneously, an information processing device includes a memory 1 including a plurality of banks, a plurality of hash computation circuits 8, and an interconnect 2 respectively connecting the banks in the memory 1 and the hash computation circuits 8 to each other, wherein the hash computation circuits 8 execute control in such a manner that read requests for reading data from the memory 1 respectively include bank numbers for specifying different banks in the same cycle.
CROSS-BORDER QUICK RESPONSE (QR) PAYMENT FLOW FOR ENCRYPTED PRIMARY ACCOUNT NUMBER (PAN) PAYMENT FLOW
A computer-implemented system for streamlining encryption payload of a card transaction from a transaction code transaction via a merchant inside a restricted computer network firewall. A wallet application stores data of a payment device, and the wallet application retrieves information of a merchant and a transaction via a transaction code. In response to the retrieved information, the wallet application generates an encrypted payload. The wallet application transmits the encrypted payload to a payment facilitator within the restricted computer network firewall. After decryption of the encrypted payload, the payment facilitator transmits a decrypted payload in one payment packet to the payment processing server outside the restricted computer network firewall. The payment processing server transmits from outside the restricted computer network firewall to the merchant inside the restricted computer network firewall a notification of payment after the payment processing server validates the payment transaction.
MULTI-NETWORK TOKENIZATION PROCESSING
Systems, apparatuses, and methods are provided for enabling a transaction using a token associated with a first payment network to be conducted using a second payment network. When a transaction using a token is submitted to a payment network, the payment network can determine the payment network associated with the token. If the token is associated with a second payment network, a token verification request including the token can be sent to the second payment network. The second payment network can then return a token verification response including a primary account identifier such as a primary account number (PAN) corresponding to the token and a validation result. The transaction may then be processed using the primary account identifier.
BROWSER EXTENSION FOR LIMITED-USE SECURE TOKEN PAYMENT
Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include receiving from the first computing device an indication of a financial service account associated with the first computing device, detecting a payment field in a web page provided by the computing device through the web browser application and, in response, generating a secure token mapped to the financial service account. The operations may further include sending the second computing device an authentication request, receiving an authentication response, and populating the payment field with the secure token.