Abstract: A system for using loyalty rewards accounts in a digital wallet may generate a mapping comprising an account mapped to a wallet token number and an indicator with the mapping stored in a database on a network of servers. The indicator may indicate an account type, and the wallet token number may be transmitted to a user device. The system may also receive a transaction request including a received wallet token number and a received indicator The indicator may be matched to the received indicator to determine the received wallet token number is associated with the account type (e.g., a loyalty rewards account). The system may route the transaction request to a loyalty settlement process in response to the account type being a loyalty rewards account.

Abstract: A system for using loyalty rewards accounts in a digital wallet may add a loyalty rewards account as a payment medium to a digital wallet application by transmitting a token that identifies the loyalty rewards account to the digital wallet application, wherein the token includes an alias account identifier that is mapped to the loyalty rewards account; and transmitting a transaction request for the transaction, wherein the transaction request includes the token that identifies the loyalty rewards account as the payment medium for the transaction, wherein the token further includes an indicator that specifies an account type for the loyalty rewards account and is configured for routing the transaction request to the loyalty settlement process during settlement processing.

Abstract: The present disclosures presents system and methods for blockchain based payment networks. One such method comprises preparing, by a payment network, a request to complete a transaction from an digital currency account associated with a payer digital wallet for entry on a blockchain ledger, wherein the request to complete the transaction includes an amount and a payee address associated with a fiat currency account; sending the request to complete the transaction to the blockchain ledger; approving the request to complete the transaction; and adjusting a balance of the payer digital wallet and a balance of the fiat currency account in response to approval of the request to complete the transaction by writing the transaction comprising the amount and the payee address to the blockchain ledger, wherein a value of the digital currency substantially matches a value of the fiat currency.

Abstract: Disclosed are various embodiments for securely conducting online in-application purchases. In one example, among others, a system comprises a computing device that is configured to identify a purchase request from a merchant application executed on the computing device and authenticate an account with a wallet provider based at least in part on a selection of the account. The computing device is configured to receive an instruction from the wallet provider to execute a security library and determine that the computing device is secure by executing a security library. The execution of the security library generates a device response for the wallet provider. A security code is determined data received from the wallet provider. A token is transmitted for the purchase request to the wallet provider based at least in part on the security code.

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 system may identify a purchase transaction request from a merchant application and generate an in-app payment cryptogram for the purchase transaction request based on a limited use payment credential (LUPC). The in-app payment cryptogram may be provided to the merchant application. The merchant application may transmit the in-app payment cryptogram to a merchant computing device. A request may be received from a payment network to update the LUPC. A security library may be executed to determine that the client device is secure. The execution of the security library may generate a device attestation response, and the device attestation response is transmitted to the payment network. An updated LUPC may be received from the payment network.

Abstract: A system may receive a request for a payment payload for a payment transaction with the request including a token and a transaction amount. The token may identify a transaction account for use in the payment transaction. The system may assess the risk of fraud associated with the transaction account and the payment transaction. The system may return the payment payload in response to a favorable risk assessment. The payment payload may be passed to a merchant and from the merchant to a payment network for evaluation. The payment transaction may be approved or declined based on the contents of received payment payload matching the contents of a generated payment payload.

Abstract: A system may receive a transaction request from a user device, and request an in-app cryptogram from a network software development kit (SDK) on the user device. The in-app cryptogram may include an unpredictable number, an application transaction counter (ATC), and a card verification result (CVR), and the ATC may be extracted from a limited use payment credential (LUPC). The system may transmit a token, a token expiry, and a token data block for an assessment by a payment network, with the token data block including the token, the token expiry, the ATC, and/or the in-app cryptogram. The system may further receive a request from the payment network to update the LUPC on the user device, and attest that the user device is secure in response to the request from the payment network to refresh the LUPC on the user device.

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 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 store a first merchant identifier in response to a registration of a first merchant and a user identifier in response to a registration of a user. The system may also store an access permission to control access by the first merchant to a first context. The access permission may be configured for retrieval by a query including at least one of the user identifier or the first merchant identifier. A user may access the system using a voice personal assistant. The system may authenticate the user based on spoken input to the voice personal assistant. The system may return the first context in response to a first application programming interface (API) call and in response to the access permission authorizing access to the first context. The system may facilitate transactions using a voice personal assistant.

Abstract: Systems and methods may comprise RFID data acquisition technology which may be embedded in a fob or tag for use in completing financial transactions. This fob may a self-contained device which includes a transponder and which may be contained on any portable form factor. For instance, the tag may be housed in a wearable transaction instrument, such as an activity tracker. The tag is configured to be used in concert with an RFID reader device.

Abstract: Systems and methods may comprise RFID data acquisition technology which may be embedded in a fob or tag for use in completing financial transactions. This fob may a self-contained device which includes a transponder and which may be contained on any portable form factor. For instance, the tag may be housed in a wearable transaction instrument, such as an activity tracker. The tag is configured to be used in concert with an RFID reader device.

Abstract: Systems and methods may comprise RFID data acquisition technology which may be embedded in a fob or tag for use in completing financial transactions. This fob may a self-contained device which includes a transponder and which may be contained on any portable form factor. For instance, the tag may be housed in a wearable transaction instrument, such as an activity tracker. The tag is configured to be used in concert with an RFID reader device.

Abstract: Systems and methods may comprise RFID data acquisition technology which may be embedded in a fob or tag for use in completing financial transactions. This fob may a self-contained device which includes a transponder and which may be contained on any portable form factor. For instance, the tag may be housed in a wearable transaction instrument, such as an activity tracker. The tag is configured to be used in concert with an RFID reader device.

Abstract: The systems may include receiving a device identifier to create a received device identifier, the received device identifier being associated with a personal POS terminal on a device associated with a consumer; matching a stored device identifier with the received device identifier; activating the personal POS terminal on the device associated with the stored device identifier; and/or receiving a payment token associated with a transaction account associated with the consumer for a transaction.

Abstract: A system for using loyalty rewards accounts in a digital wallet may generate a mapping comprising an account mapped to a wallet token number and an indicator with the mapping stored in a database on a network of servers. The indicator may indicate an account type, and the wallet token number may be transmitted to a user device. The system may also receive a transaction request including a received wallet token number and a received indicator. The indicator may be matched to the received indicator to determine the received wallet token number is associated with the account type (e.g., a loyalty rewards account). The system may route the transaction request to a loyalty settlement process in response to the account type being a loyalty rewards account.

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 regression testing system comprises an automatic test tool configured to capture a first web screen shot and a second web screen shot of a webpage, where the webpage has undergone an update or edit. The regression testing system also comprises a visual comparator configured to identify similar areas in the first web screen shot and the second web screen shot. The visual comparator receives, and compares characteristics of, the web screen shots. Furthermore, the regression testing system generates a report with marked different characteristics between the first and second web screen shots. The regression testing system identifies similar areas in the first and second web screen shots shot even if the similar areas are at different locations within the web screen shots. The comparison performed by the visual comparator includes performing a pixel comparison combined with a marking algorithm to group differences in smaller, related but separate areas.

Abstract: A system may store a first merchant identifier in response to a registration of a first merchant and a user identifier in response to a registration of a user. The system may also store an access permission to control access by the first merchant to a first context. The access permission may be configured for retrieval by a query including at least one of the user identifier or the first merchant identifier. A user may access the system using a voice personal assistant. The system may authenticate the user based on spoken input to the voice personal assistant. The system may return the first context in response to a first application programming interface (API) call and in response to the access permission authorizing access to the first context. The system may facilitate transactions using a voice personal assistant.