Multisystem Identity Verification via Validation Number Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identity verification systems for electronic transactions lack robustness in authenticating users, particularly when account information is provided through webpages, as they rely on traditional methods that consume processing and networking resources and do not effectively prevent impersonation.
Innovation Solution
A multisystem cooperation approach involving a first subsystem associated with an institution and a second subsystem associated with an entity, where a validation number is randomly generated and transmitted to a second user device, which the user enters into a webpage, allowing the institution to authenticate the user and authorize or decline transactions based on matching validation numbers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional identity verification methods are used, then the system structure remains simple, but the authentication efficiency and security are insufficient
Solution Approach 1:
The verification system is divided into three independent components: the merchant system (first subsystem), the user device (second subsystem), and the institution system (third subsystem). Each component performs specific functions - the merchant system initiates verification, the user device receives validation numbers and displays them, and the institution system generates and validates the numbers. This segmentation improves authentication efficiency while keeping each individual component relatively simple.
Solution Approach 2:
The validation number serves as an intermediary element that transfers information between the institution system and the user device. Instead of direct complex communication between all systems, the validation number acts as a mediator that simplifies the verification process. The institution system generates the validation number, transmits it to the user device, and later verifies it, reducing the complexity of direct system-to-system authentication.
2Reliability
If validation numbers are transmitted to user devices, then impersonation is prevented, but processing and networking resources are consumed
Solution Approach 1:
The user device automatically performs several functions without requiring additional processing from the institution system: receiving the validation number, displaying it to the user, and transmitting it back to the merchant system. The user simply needs to view and enter the validation number, making the system self-sufficient in handling the verification process and reducing the processing burden on the institution system.
Solution Approach 2:
The validation number is generated and transmitted to the user device before the actual transaction occurs. This preliminary action of sending the validation number in advance allows the user to have it ready for immediate entry during the transaction, reducing the overall processing time and networking resource consumption compared to real-time verification.
3Reliability
If validation numbers are randomly generated, then security is improved, but processing time increases
Solution Approach 1:
The validation number is generated as a simple copy or representation of the user's identity information rather than requiring complex cryptographic operations. The institution system creates a validation number that can be easily transmitted and verified, prioritizing speed and simplicity over complex security mechanisms. This copying approach maintains security while minimizing processing time.
Data Source
AI summary
A system includes first and second subsystems. The first subsystem receives a validation number request, transmitted by a first device in response to the entry of an account number into a first field of a webpage. In response to receiving the request, the first subsystem randomly generates the validation number, stores a copy in memory, and transmits it to a second device. The second subsystem receives a transaction request that includes the validation number from the first device, and transmits the received number to the first subsystem. The first device transmitted the request in response to the second device receiving the validation number and its subsequent entry into a second field of the webpage displayed on the first device. In response to receiving the validation number, the first subsystem determines that it matches the stored copy and transmits a message to the second subsystem authorizing the transaction.