Transaction Confirmation via User Attribute Similarity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application software lacks effective security measures to prevent user mistakes during payment transactions, leading to potential losses due to incorrect input of user identification information.
Innovation Solution
A risk control method and device that determines user attribute similarity between the first user and the second user based on their respective user attributes stored in a database, using this similarity to perform risk control on payment requests, thereby verifying the accuracy of identification information and preventing incorrect transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the server directly pushes sensitive information to the user corresponding to the account information based on the received account information (Method 2), then the operations are simpler and more convenient, but the security risk increases due to potential user input errors
Solution Approach 1:
The patent performs preliminary verification of user identity before executing the payment transaction. The server obtains authentication information from the first user and verifies it against pre-stored authentication information associated with the second user's account. This preliminary action prevents incorrect transactions due to user input errors while maintaining a relatively simple operation flow.
Solution Approach 2:
The patent implements a feedback mechanism where the server verifies the authentication information provided by the first user against the pre-stored authentication information. If the verification fails, the server does not proceed with the transaction and can notify the user of the error. This feedback loop ensures security without significantly complicating the user interface.
2Reliability
If the server verifies user identity through additional authentication steps (Method 1 with verification), then the security is improved, but the operations become more complex and time-consuming
Solution Approach 1:
The patent utilizes authentication information that the first user already possesses (such as passwords, PINs, or biometric data) and has previously set up in their account settings. The verification process leverages these self-service authentication credentials rather than requiring additional manual verification steps, thereby maintaining security while minimizing operational complexity.
3Productivity
If no verification mechanism is implemented and the server directly processes the payment request, then the operation is fastest and simplest, but user mistakes can cause financial loss
Solution Approach 1:
The patent applies preliminary anti-action by preemptively verifying the user's authentication information before the payment transaction is executed. This prevents harmful actions (incorrect payments) from occurring in the first place, rather than attempting to correct errors after they happen. The verification step is integrated into the transaction flow in a way that minimizes delay while ensuring accuracy.
Data Source
AI summary
Techniques for providing a risk control method and device for resolving the issue of low application software security are described. A transaction request is received from a first user, and the transaction request comprises transaction data, data identifying the first user, and data identifying a second user. An attribute of the first user is determined from the data identifying the first user. An attribute of the second user is identified using the data identifying the second user. In response to the attribute of the first user being determined and the attribute of the second user being identified, an attribute similarity between the first user and the second user is determined. The attribute similarity is compared to a threshold. In response to determining the attribute similarity is less than the threshold, a notification is transmitted to the first user requesting a confirmation of the identified attribute of the second user.