Abstract: A method for maintaining state and event information for all of a user's devices associated in a common location using a blockchain where each block includes an event block and a device block within it, where each event and device block refers to an earlier block of the respective type, resulting in a blockchain-in-a-blockchain architecture. The device and event blocks store data regarding each device associated with a user and events related to the devices/user, respectively. Any time a new event occurs, or a device is registered or removed, a new set of blocks is created, where submissions regarding device changes or events can be made by any participant due to the decentralized and public nature of a blockchain. The result is a system where all data regarding a user's registered devices and events is kept in a common location in a manner that is auditable and verifiable.

Abstract: A method for consumer-initiated transactions with encrypted tokens includes: storing a first cryptographic key pair comprising an account public key and an account private key, a merchant public key, an account token associated with a transaction account, an account identifier, and an issuing institution identifier; receiving transaction data for a proposed payment transaction including a transaction amount; generating a transaction order including the transaction data; generating a cryptographic checksum for the generated transaction order; generating a digital signature over the cryptographic checksum using the account private key; generating a payment token including the issuing institution identifier, the account identifier, the transaction amount, and the account token; encrypting the payment token using the account private key; and transmitting the encrypted payment token and signed cryptographic checksum to a point of sale device.

Abstract: A method for consumer-initiated transactions with encrypted tokens includes: storing a first cryptographic key pair comprising an account public key and an account private key, a merchant public key, an account token associated with a transaction account, an account identifier, and an issuing institution identifier; receiving transaction data for a proposed payment transaction including a transaction amount; generating a transaction order including the transaction data; generating a cryptographic checksum for the generated transaction order; generating a digital signature over the cryptographic checksum using the account private key; generating a payment token including the issuing institution identifier, the account identifier, the transaction amount, and the account token; encrypting the payment token using the account private key; and transmitting the encrypted payment token and signed cryptographic checksum to a point of sale device.

Abstract: A method for maintaining state and event information for all of a user's devices associated in a common location using a blockchain where each block includes an event block and a device block within it, where each event and device block refers to an earlier block of the respective type, resulting in a blockchain-in-a-blockchain architecture. The device and event blocks store data regarding each device associated with a user and events related to the devices/user, respectively. Any time a new event occurs, or a device is registered or removed, a new set of blocks is created, where submissions regarding device changes or events can be made by any participant due to the decentralized and public nature of a blockchain. The result is a system where all data regarding a user's registered devices and events is kept in a common location in a manner that is auditable and verifiable.

Abstract: A method for maintaining state and event information for all of a user's devices associated in a common location using a blockchain where each block includes an event block and a device block within it, where each event and device block refers to an earlier block of the respective type, resulting in a blockchain-in-a-blockchain architecture. The device and event blocks store data regarding each device associated with a user and events related to the devices/user, respectively. Any time a new event occurs, or a device is registered or removed, a new set of blocks is created, where submissions regarding device changes or events can be made by any participant due to the decentralized and public nature of a blockchain. The result is a system where all data regarding a user's registered devices and events is kept in a common location in a manner that is auditable and verifiable.

Abstract: A payment token is generated within a token bank identification number (BIN) range, and is linked with an underlying account number of a consumer. A first instance of the token is made available in at least one of a first portable electronic device, a first mobile payment application (MPA), and a first web wallet of the consumer with an associated first primary account sequence number (PSN). A second instance of the token is made available in at least one of a second portable electronic device, a second mobile payment application (MPA), and a second web wallet of the consumer with an associated second primary account sequence number (PSN).

Abstract: A method for maintaining state and event information for all of a user's devices associated in a common location using a blockchain where each block includes an event block and a device block within it, where each event and device block refers to an earlier block of the respective type, resulting in a blockchain-in-a-blockchain architecture. The device and event blocks store data regarding each device associated with a user and events related to the devices/user, respectively. Any time a new event occurs, or a device is registered or removed, a new set of blocks is created, where submissions regarding device changes or events can be made by any participant due to the decentralized and public nature of a blockchain. The result is a system where all data regarding a user's registered devices and events is kept in a common location in a manner that is auditable and verifiable.

Abstract: Methods, apparatus and systems for permitting a cardholder to select a cardholder verification method (CVM) during a secure transaction. In an embodiment, a consumer mobile device running a mobile payment application receives, from a cardholder, selection of a payment account and an instruction to pay via one of contactless, barcode, SRC or digital secure remote payment (DSRP). The consumer mobile device then transmits a request for a secure transaction to a merchant device, receives a request for payment account data, displays a plurality of cardholder verification methods (CVMs), receives selection of a CVM, and prompts the cardholder to provide cardholder identification data in accordance with the selected CVM.

Abstract: A method for consumer-initiated transactions with encrypted tokens includes: storing a first cryptographic key pair comprising an account public key and an account private key, a merchant public key, an account token associated with a transaction account, an account identifier, and an issuing institution identifier; receiving transaction data for a proposed payment transaction including a transaction amount; generating a transaction order including the transaction data; generating a cryptographic checksum for the generated transaction order; generating a digital signature over the cryptographic checksum using the account private key; generating a payment token including the issuing institution identifier, the account identifier, the transaction amount, and the account token; encrypting the payment token using the account private key; and transmitting the encrypted payment token and signed cryptographic checksum to a point of sale device.

Abstract: A payment token is generated within a token bank identification number (BIN) range, and is linked with an underlying account number of a consumer. A first instance of the token is made available in at least one of a first portable electronic device, a first mobile payment application (MPA), and a first web wallet of the consumer with an associated first primary account sequence number (PSN). A second instance of the token is made available in at least one of a second portable electronic device, a second mobile payment application (MPA), and a second web wallet of the consumer with an associated second primary account sequence number (PSN).

Abstract: Methods, systems and apparatus for conducting secure transactions using digital barcodes. In an embodiment, a consumer mobile device launches a mobile payment application and then receives selection of a payment card account and an instruction to pay via a digital barcode by a cardholder. The consumer mobile device then generates at least one of a dynamic quick response (QR) code and a barcode, displays the QR code and/or the barcode on a display component, receives a purchase transaction confirmation request including merchant identification data and a transaction amount, and displays a confirmation notification for approval by the cardholder. After receiving a confirmation response, the consumer mobile device transmits the confirmation response to a digital enablement system (DES) computer. In some implementations, after transaction authorization, the consumer mobile device may receive and display a transaction completed confirmation message.