CBDC Card Payment Validation Without Full Blockchain Overhead
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing consumer payment infrastructure does not support token-based transactions for central bank digital currencies (CBDCs), making it difficult to use CBDCs for card-based payments at merchant points-of-sale.
Innovation Solution
A distributed ledger system with a protocol framework enables CBDC transactions by allowing parties to agree on and validate transactions without relying on a blockchain, using a decentralized approach with protocol flows, messaging, checkpoint, and deterministic virtual machine services to ensure secure and efficient transaction processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain is used to support CBDC transactions, then transaction security and decentralization are improved, but computational and storage resources required are excessive for existing payment infrastructure
Solution Approach 1:
The patent extracts the essential transaction validation functionality from the blockchain system, separating it from the full blockchain infrastructure. The protocol framework implements a simplified consensus mechanism that validates CBDC transactions without requiring the complete blockchain protocol, thereby reducing computational and storage resources while maintaining security.
Solution Approach 2:
The patent applies local quality by implementing a tailored protocol framework that is optimized specifically for CBDC transactions rather than using the general-purpose blockchain protocol. This localized approach allows the system to use only the necessary security and validation features needed for CBDC, reducing overall resource requirements.
2Reliability
If blockchain is used to support CBDC transactions, then transaction security and decentralization are improved, but computational and storage resources required are excessive for existing payment infrastructure
Solution Approach 1:
The patent extracts only the essential transaction validation and consensus functionality from the blockchain system, eliminating the need to store and process the entire blockchain ledger. The protocol framework maintains security through distributed validation without requiring full ledger replication at each node.
Solution Approach 2:
Instead of requiring full blockchain infrastructure with complete ledger replication, the patent inverts the approach by using a protocol framework where validation rules and consensus mechanisms are defined separately from the ledger storage, allowing lightweight implementation.
3Ease of operation
If existing consumer payment infrastructure is used, then ease of operation is maintained, but support for token-based CBDC transactions is lacking
Solution Approach 1:
The patent implements a protocol framework that provides multi-functionality by enabling both traditional payment processing and CBDC token-based transactions through the same infrastructure. The framework acts as a universal layer that adapts to different transaction types without requiring separate systems.
Solution Approach 2:
The patent introduces a protocol framework as an intermediary layer between the existing payment infrastructure and the CBDC token system. This mediator enables CBDC transactions to occur through conventional payment channels, maintaining ease of operation while adding CBDC capability.
Data Source
AI summary
Central bank digital currency (CBDC) tokens are used for payment in a transaction initiated by a payment card at an acquirer's point-of-sale. To facilitate these transactions, a card issuer node in a distributed ledger environment receives a payment message from a payment terminal. The payment message, comprising a request to conduct a CBDC-based transaction, contains a signature transmitted to the payment terminal by a payment card. The card issuer node generates a signature data structure that contains the signature. The card issuer node also generates a transaction message containing components of the transaction, such as a number of tokens to be transferred, a current owner of the tokens to be transferred, an intended acquirer of the tokens, a currency type of the tokens, and/or instructions for validating the transaction. The transaction is validated based at least in part on the signature data structure in the transaction message.


