Managed EMV Kernel Pipeline for Faster Card Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing EMV transactions are slow and cumbersome, with the EMV chip needing to be inserted for extended periods, and FastEMV transactions cannot facilitate script updates to integrated circuits, particularly problematic in international markets.
Innovation Solution
Implementing a managed EMV Kernel with a pipeline of software modules that optimize transaction processing by reducing unnecessary reads of the integrated circuit, using automators to infer card brand and type, and employing a Hierarchical Option Stack to manage transaction options, allowing for faster and more secure processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional EMV transaction processing is used, then security and validation are ensured, but processing time is excessive and user experience deteriorates
Solution Approach 1:
The EMV kernel is divided into multiple software modules that can be selectively executed. The system segments the transaction processing into essential validation steps and optional steps, allowing it to bypass unnecessary operations while maintaining security requirements. This modular architecture enables the system to perform only the minimum necessary reads of the integrated circuit while still ensuring card validation.
Solution Approach 2:
The system performs partial validation by determining which software modules are actually needed for the specific transaction type and card being processed. Instead of executing the complete traditional EMV validation sequence, the system selectively activates only the necessary validation steps, reducing processing time while maintaining adequate security measures for the given context.
2Productivity
If FastEMV transaction processing is used, then processing speed is improved, but script updates to integrated circuits cannot be facilitated
Solution Approach 1:
The EMV kernel dynamically adapts its processing mode based on the specific transaction requirements and card type being processed. The system can switch between FastEMV mode for speed and traditional EMV mode for script updates, making the processing behavior flexible rather than fixed. This dynamic approach allows the same system to optimize for different priorities depending on the situation.
Solution Approach 2:
The system changes processing parameters such as the number and type of reads performed on the integrated circuit, based on the transaction context. When script updates are needed, the system adjusts its parameters to include the necessary communication sequences. When speed is the priority and updates are not needed, it reduces the parameter set to only essential operations.
3Reliability
If multiple reads of the integrated circuit are performed, then complete validation is achieved, but processing time increases
Solution Approach 1:
The system extracts and removes unnecessary read operations from the traditional EMV processing sequence. By analyzing which reads are actually required for the specific card and transaction type, the system eliminates redundant reads while retaining the essential validation checks. This extraction process reduces the total number of reads performed on the integrated circuit.
Solution Approach 2:
The system performs preliminary determination of which validation steps are necessary before executing the read operations. By pre-assessing the card type, transaction requirements, and security needs, the system can plan the minimum necessary reads in advance, avoiding unnecessary operations and optimizing the reading sequence for both completeness and speed.
Data Source
AI summary
Method and system of performing transactions with a payment card in a managed integrated payment environment comprising an integrated circuit are disclosed comprising interacting with an integrated circuit on a received payment card to obtain card data by a payment terminal and determining whether full online transaction processing of the card data is required. If full online transaction processing of the card data is required, the card data is sent to a point-of-sale terminal, which sends the card data and a transaction total for the transaction to a merchant gateway, which obtains approval or denial of the transaction. The approval or denial is provided to the PIN pad by the merchant gateway via the point-of-service terminal. The PIN pad also receives transaction data and sends the transaction data and card data to a services processor to collect metadata, perform fraud and security checks, and/or encrypt the card data.