Multi-point Payment Authentication via Randomized Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current payment card security systems are vulnerable to fraud and breaches, as they rely solely on physical cards and signatures, which can be easily compromised, leading to significant financial losses and loss of trust for consumers and merchants.
Innovation Solution
Implementing a multi-point authentication system that requires both a physical payment card and a mobile device associated with the cardholder, using randomized transaction and authentication identifiers to validate transactions, ensuring that even if card information is stolen, hackers cannot complete transactions without the mobile device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multi-point authentication is implemented requiring both physical card and mobile device, then transaction security is improved, but device complexity and operation steps increase
Solution Approach 1:
The authentication system is segmented into multiple independent verification points: physical card verification at the POS terminal, mobile device verification through the application, and centralized validation at the payment association server. Each segment handles a specific aspect of authentication, distributing complexity across multiple components rather than concentrating it in a single system.
Solution Approach 2:
The payment association server acts as an intermediary that receives authentication requests from both the POS terminal and mobile device, validates the randomized identifiers, and coordinates the multi-point verification process. This intermediary manages the complexity of cross-device validation without requiring direct complex communication between the POS terminal and mobile device.
2Reliability
If multiple authentication points are required, then fraud prevention is improved, but transaction processing time increases
Solution Approach 1:
The mobile device application performs preliminary authentication setup by generating and storing the randomized identifier in advance, before the actual transaction occurs. This preliminary action ensures that when a transaction takes place, the verification process can proceed quickly by simply comparing the presented identifier against the pre-stored valid identifier, rather than performing complex validation during the transaction itself.
Solution Approach 2:
The system uses randomized identifiers that change for each transaction or authentication cycle, providing strong fraud prevention. However, these identifiers are designed to be simple comparison values rather than complex cryptographic proofs, allowing rapid validation. The parameter of identifier complexity is optimized to provide sufficient security while enabling fast processing.
3Reliability
If randomized identifiers are used for each transaction, then security against replay attacks is improved, but system complexity and computational overhead increase
Solution Approach 1:
The system uses simplified copied identifiers rather than complex cryptographic tokens. The mobile device receives a copy of the randomized identifier from the payment association server and stores it locally. During authentication, the device simply presents this copied identifier for verification, avoiding the need for complex real-time cryptographic computation while maintaining security against replay attacks through the use of unique randomized values.
Data Source
AI summary
Authentication includes receiving an indication of physical possession of a payment card by a merchant and receiving a purchase request for an authorization of an exchange from the payment account of the cardholder to the merchant. Authentication includes assigning a randomized transaction identifier to the request for the authorization of the exchange. The method also includes transmitting the request for the authorization of the exchange from the payment account of the cardholder to the merchant and receiving the assigned randomized transaction identifier and a randomized authentication identifier associated with the randomized transaction identifier from a payment association, the payment association determining whether the request for the authorization of the exchange is valid. Authentication includes transmitting a copy of the randomized authentication identifier to the mobile device and receiving validation that the transmitted copy of the randomized authentication identifier from the mobile device matches the randomized authentication identifier.