CBDC Transaction Integration Into Existing EMV Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing CBDC solutions require new hardware and infrastructure, making it difficult for merchants and payees to adopt CBDC transactions easily, and there is a need for a robust solution that can be deployed with minimal updates on existing payment terminals.
Innovation Solution
Integrate CBDC transactions into conventional EMV transaction flows, using EMVCo® specifications to encapsulate necessary data, allowing existing payment terminals to support CBDC transactions with minimal updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If CBDC solutions are implemented using proprietary methods, then CBDC transaction functionality is achieved, but new hardware and infrastructure must be deployed, increasing device complexity and deployment difficulty
Solution Approach 1:
The patent makes existing EMV payment terminals multi-functional by enabling them to process both traditional payment transactions and CBDC transactions through a unified architecture. The terminal includes a CBDC module that works alongside the existing EMV processing capability, allowing the same hardware infrastructure to serve multiple purposes without requiring separate dedicated CBDC terminals.
Solution Approach 2:
The patent combines CBDC transaction processing with the existing EMV payment terminal infrastructure. The CBDC module is integrated into the terminal's existing architecture, merging new CBDC functionality with proven payment processing hardware and protocols, thereby avoiding the need for entirely separate infrastructure.
2Reliability
If proprietary CBDC solutions are deployed, then CBDC transactions can be performed, but adoption by merchants and payees becomes difficult due to infrastructure requirements
Solution Approach 1:
By making payment terminals universal devices that can handle both traditional payments and CBDC transactions, the patent removes the barrier of requiring separate infrastructure. Merchants and payees can adopt CBDC using existing payment terminals they already possess, dramatically easing adoption without requiring new hardware deployment.
3Reliability
If new hardware is deployed for CBDC, then CBDC transaction security can be ensured, but deployment cost and complexity increase
Solution Approach 1:
The patent merges CBDC security requirements with existing EMV terminal security infrastructure. The CBDC module leverages the terminal's existing secure elements, cryptographic capabilities, and security protocols, combining new CBDC security needs with proven security infrastructure rather than building separate security systems.
Solution Approach 2:
The CBDC module is designed to utilize the terminal's existing security resources and capabilities, allowing the system to serve its own security needs through existing infrastructure. The terminal's built-in security mechanisms automatically support CBDC transactions without requiring external security hardware or additional security infrastructure deployment.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention is a method for performing a CBDC transaction in which a payment instrument (10) hosts a first CBDC wallet (11) and uses optional fields as defined by EMVCo® specifications when responding to commands of an EMV sequence of commands to convey to a terminal (20) a set of CBDC data and the terminal uses optional fields as defined by EMVCo® specifications of commands of said EMV sequence of commands to convey CBDC transaction data to the payment instrument. The terminal sends a CBDC payload (12) to a first entity (30), acting on behalf of an issuer of the payment instrument, which uses the CBDC payload to send to a second entity (40) a message (31) requesting that the transaction amount be transferred between the first CBDC wallet and a second CBDC wallet (41) assigned to a merchant.