Cross-Card Wallet Authentication Using Transaction History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a trade-off between security measures and customer convenience in online transactions, as excessive authentication steps can lead to transaction abandonment, while merchants and issuers need to combat fraud effectively.
Innovation Solution
An authentication service that records successful user authentication processes, allowing for the skipping of subsequent authentication steps for a pre-set period if the user is using the same digital wallet, leveraging a biometric system and history server to determine when user authentication is not necessary, thus enhancing convenience while maintaining security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user authentication procedures are implemented to combat fraud, then security is improved, but customer convenience deteriorates due to additional authentication steps
Solution Approach 1:
The system performs biometric authentication in advance and stores the authentication result. When a subsequent transaction occurs within a predetermined time period, the system retrieves and reuses this pre-performed authentication result, eliminating the need for repeated authentication and thereby improving convenience while maintaining security.
Solution Approach 2:
The system applies different authentication requirements to different transaction scenarios. For transactions within the predetermined time period following successful authentication, no additional authentication is required. For transactions outside this period or with suspicious characteristics, full authentication is enforced, thus locally optimizing the balance between security and convenience.
2Ease of operation
If authentication steps are reduced to improve convenience, then customer convenience is improved, but security deteriorates due to increased fraud risk
Solution Approach 1:
The system continuously monitors transaction characteristics and compares them against stored authentication results and transaction history. Based on this feedback loop, the system dynamically determines whether to reuse previous authentication results or require new authentication, ensuring security is maintained while allowing convenience optimizations when appropriate.
Solution Approach 2:
The authentication requirement is made dynamic rather than static. The system adjusts authentication requirements based on the time elapsed since the last authentication, transaction amount, merchant category, and other variables. This dynamic approach allows the system to reduce authentication friction when risk is low while maintaining strong security when risk increases.
3Reliability
If biometric authentication is required for every transaction, then security is improved, but transaction processing time increases
Solution Approach 1:
Biometric authentication is performed in advance and the result is stored for reuse. This preliminary action eliminates the need to repeat the time-consuming biometric scanning and verification process for subsequent transactions within the valid time period, thereby significantly reducing transaction processing time while maintaining security through the stored authentication result.
4Reliability
If transaction monitoring and authentication history tracking are implemented, then fraud detection capability is improved, but system complexity increases
Solution Approach 1:
The authentication service performs multiple functions using a unified architecture: it conducts biometric authentication, stores authentication results, monitors transaction characteristics, retrieves historical data, and determines whether to require re-authentication. This multi-functional approach avoids the need for separate complex systems for each function, thereby improving fraud detection capability while limiting the increase in overall system complexity.
Data Source
AI summary
A method includes performing a first transaction using a first payment account. The first transaction includes a successful authentication of a holder of the first payment account. A record is stored of the first transaction. The record indicates that the successful authentication occurred. A request is received for a second transaction using a second payment account. The indication of the successful authentication is detected in the stored record of the first transaction. The second transaction is completed without requiring authentication of the account holder.