Verified Device Authentication for Remote Access Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems struggle to accurately authenticate user devices in remote transactions, particularly in card-not-present scenarios, where verifying the association between a user and their devices is challenging.
Innovation Solution
A system and method for user authentication that involves identifying verified devices associated with a user, presenting device options to the user, and allowing selection of an authentication device for transactions, utilizing tokenization services to associate devices with payment accounts, and implementing challenge requests for secure authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication methods are used in remote transactions, then device verification is simpler, but authentication accuracy and security are insufficient
Solution Approach 1:
The system performs preliminary device verification by maintaining a registry of verified devices associated with user accounts. Before completing a remote transaction, the system checks whether the initiating device is in the verified device registry, thereby performing authentication preparation in advance to ensure security without complicating the actual transaction process.
Solution Approach 2:
The system introduces an intermediary authentication mechanism that mediates between the user and the transaction system. This intermediary layer verifies device associations through challenge requests and response validation, enhancing authentication accuracy while maintaining a clear separation between device management and transaction processing functions.
2Adaptability or versatility
If multiple verified devices are associated with a user account, then authentication flexibility improves, but device identification and selection becomes more complex
Solution Approach 1:
The system segments the authentication process into distinct phases: device verification (registering devices with the system), device identification (retrieving the list of verified devices), and device selection (user choosing which device to use). This segmentation allows multiple devices to be associated with a single account while maintaining operational simplicity through clear procedural separation.
Solution Approach 2:
The system enables users to self-manage their verified devices by allowing them to view their registered devices and select which device to use for authentication. This self-service capability enhances authentication flexibility while keeping the interface simple, as users independently handle device selection without requiring complex system intervention.
3Productivity
If device verification is performed expeditedly, then transaction speed improves, but verification thoroughness may be compromised
Solution Approach 1:
Device verification is performed expeditedly by relying on preliminary device registration and verification. Devices are pre-verified and registered in the system before transactions occur, allowing the actual transaction process to proceed quickly while maintaining thorough verification standards that were applied during the initial registration phase.
Solution Approach 2:
The system uses feedback mechanisms where previously verified device information is stored and reused. When a transaction is initiated, the system quickly retrieves pre-verified device data rather than performing complete verification again, thereby maintaining both speed and accuracy through intelligent use of historical verification feedback.
Data Source
AI summary
Some embodiments may provide systems, methods and computer program code to method to facilitate an interaction involving a user which include determining that a user authentication is required to complete the interaction, identifying at least a first verified device associated with the user, and transmitting an authentication message to the at least first verified device.