Abstract: A proof-of-payment system that allows smart connected devices to confirm a payment information. In one example, a smart connected device that comprises a computing device and program instructions. The program instructions, when executed by the processor, cause the computing device to at least retrieve an encrypted proof-of-payment (PoP) payload from a blockchain and decrypt the encrypted PoP payload to retrieve a first identifier from the encrypted PoP payload. The first identifier from the decrypted PoP payload is matched to a second identifier presented at the smart connected device. An action is triggered in response to the first identifier from the encrypted PoP payload matching the second identifier presented at the smart connected device.

Abstract: A proof-of-payment system may receive a payment confirmation including a transaction amount and a merchant identifier. The system may select a record from a registration repository by matching the merchant identifier to the record. The record may have a public key associated with the merchant identifier via a registration process, for example. The system may also generate a proof-of-payment payload comprising an identifier and a payment amount, and encrypt the proof-of-payment payload using the public key. The system may write the encrypted proof-of-payment payload to a blockchain maintained on a first blockchain node.

Abstract: The systems may include receiving a token request for a transaction from a merchant, the token request comprising a consumer identifier associated with a consumer and a merchant identifier (MID) associated with the merchant, matching the MID with a token requestor identifier (TRID) assigned to the merchant, matching the consumer identifier with an account identifier associated with a transaction account of the consumer, generating a digital token comprising the TRID and the account identifier, and transmitting the digital token to the merchant.

Abstract: A proof-of-payment system may receive a payment confirmation including a transaction amount and a merchant identifier. The system may select a record from a registration repository by matching the merchant identifier to the record. The record may have a public key associated with the merchant identifier via a registration process, for example. The system may also generate a proof-of-payment payload comprising an identifier and a payment amount, and encrypt the proof-of-payment payload using the public key. The system may write the encrypted proof-of-payment payload to a blockchain maintained on a first blockchain node.

Abstract: The systems may include receiving a token request for a transaction from a merchant, the token request comprising a consumer identifier associated with a consumer and a merchant identifier (MID) associated with the merchant, matching the MID with a token requestor identifier (TRID) assigned to the merchant, matching the consumer identifier with an account identifier associated with a transaction account of the consumer, generating a digital token comprising the TRID and the account identifier, and transmitting the digital token to the merchant.

Abstract: The systems may include transmitting wallet provider script to a payment service provider server, presenting an electronic wallet payment tool on a merchant checkout page, receiving a first selection of the electronic wallet payment tool, retrieving an electronic wallet comprised in a transaction account associated with the consumer, transmitting transaction account information associated with a desired transaction account in the electronic wallet to the payment service provider server, receiving a virtual token from the payment service provider server, and/or transmitting the virtual token to payment service provider script integrated in a browser used by the consumer.