Contactless Card Verification Using Dual NDEF and EMV Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing use of credit and debit cards for transactions has led to increased risks of fraud and theft due to the difficulty in verifying the user's identity remotely and the availability of sensitive data on the card, making it easier for malicious parties to misuse credentials.
Innovation Solution
A system and method for user verification using a contactless card that reads two types of data, such as NDEF and EMV data, through a client device, and compares these identifiers with stored information to enhance verification, involving a contactless card with a processor and memory, a server, and a database to determine if the card is being used by an authorized user.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If card data is stored on the card for transaction processing, then transaction convenience is improved, but fraud risk increases due to misappropriation of credentials
Solution Approach 1:
The card data is segmented into two distinct types: first type data (e.g., NDEF format) and second type data (e.g., EMV format). Each type serves a specific verification purpose, and neither alone is sufficient for authentication. This segmentation prevents fraudsters from using partial data replication to commit fraud, as both data types must be present and verified.
Solution Approach 2:
The system changes the verification parameter from checking single data type to checking multiple data types with different formats and structures. The server is configured to determine user identifiers from both first and second type data, requiring multiple parameter validations rather than a single data check, thereby increasing security against credential misappropriation.
2Device complexity
If single data type verification is used, then verification process is simple, but user identification reliability is insufficient
Solution Approach 1:
The system performs excessive verification by checking more data types than the minimum single type. While this increases verification steps, it significantly enhances reliability by requiring multiple independent data types to match, making it computationally infeasible for fraudsters to replicate all required data types simultaneously.
3Reliability
If multiple data types are read from the card, then verification security is improved, but data processing time increases
Solution Approach 1:
The card is pre-configured with both first and second type data in specific formats (NDEF and EMV) before the transaction occurs. This preliminary preparation allows the verification system to quickly read and process the data without needing to generate or convert data during the transaction, minimizing processing time while maintaining high security through multiple data type verification.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
Systems, methods, and computer-accessible mediums for user verification through the interaction of a short-range transceiver, such as a contactless card, with a client device are presented. User verification may be provided in the context of reading two types of data from the short-range transceiver, such as a contactless card, using a client device, sending the data to a server, obtaining identifiers from each data type and comparing with stored user identifier data. Matching stored user identifier data to two forms of identification data obtained from a short-range transceiver, such as a contactless card, provides an enhanced ability to verify that the short-range transceiver is being used by an authorized user.