Identification Card Transaction Security via Secondary Data Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Despite conventional security measures, a significant volume of unauthorized uses of identification cards occurs, leading to fraudulent transactions and associated losses for card users, issuers, and vendors.

Innovation Solution

The method involves storing secondary security data associated with account information on identification cards, requiring users to provide both the card and a secondary identifier at the point of sale, with the issuer verifying the correlation of transaction secondary ID data to the stored secondary security data to approve or refuse transactions, and issuing post-transaction confirmation requests to ensure legitimate use.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional security measures (signature verification, PIN entry, picture ID) are used, then basic identity verification is achieved, but a significant volume of unauthorized uses still occurs

Engineering Contradiction:
Improvetransaction securityVSAvoidunauthorized transactions
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The security verification process is divided into multiple independent components: primary card data verification, secondary security data verification, and post-transaction confirmation. Each component independently verifies a specific aspect of identity, and all must align for transaction approval. This segmentation prevents unauthorized transactions by requiring multiple verification layers that must all succeed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Secondary security data is collected and stored in advance during account setup, before any transactions occur. This preliminary action creates a reference database of verified security characteristics that can be quickly compared against transaction data, enabling rapid verification without requiring real-time physical presence or complex verification procedures.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple security verification steps are implemented, then transaction security is improved, but the complexity of the verification process increases

Engineering Contradiction:
Improvetransaction securityVSAvoidverification process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of requiring physical presence or complex biometric verification, the system creates and stores copies of security characteristics (secondary security data) during account setup. These copied data can be quickly transmitted and compared during transactions, simplifying the verification process while maintaining security. The system copies security traits into a digital format that can be efficiently processed and compared.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements post-transaction confirmation requests that provide feedback to the cardholder about the transaction details. This feedback mechanism allows the cardholder to verify the transaction and report any unauthorized uses, creating a feedback loop that enhances security without adding complexity to the initial transaction verification process.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9508074B2Method for secure use of identification cards
Publication Date: 2016.11.29 ADVANCED PLATFORM SOLUTIONS LLC
  • US9508074B2 patent drawing
  • US9508074B2 patent drawing
  • US9508074B2 patent drawing

AI summary

A method for approving or refusing a transaction is based on the use of an identification card having card data thereon, the card data identifying account information pertaining to the authorized user of the identification card. The method includes storing issuer secondary security data in association with the account information. A transaction approval request is received from a vendor, the transaction approval request including the card data and transaction secondary identifier (secondary ID) data. The transaction is refused if the transaction secondary ID data does not correlate properly to the stored issuer secondary security data. Optionally, a post-transaction confirmation request is issued if the transaction is not refused.