Third-Party Authentication for Mobile-Free Financial Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
User authentication in online services can be difficult for users without a mobile device, preventing them from completing transactions.
Innovation Solution
A system that allows users to authenticate using a third-party device or entity, where authentication is facilitated through linking user accounts and utilizing third-party devices or entities to verify user identity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional mobile device-based authentication is required, then security is improved, but accessibility deteriorates for users without mobile devices
Solution Approach 1:
The patent introduces a third-party service as an intermediary that facilitates authentication between users and financial institutions. Instead of requiring direct mobile device authentication, the third-party service acts as a mediator that can verify user identity through alternative means (such as email verification, SMS codes sent to non-mobile devices, or knowledge-based questions), thereby enabling users without mobile devices to complete transactions while maintaining security through the trusted third-party verification process
2Reliability
If multiple authentication factors are required, then security is improved, but user convenience deteriorates
Solution Approach 1:
The patent implements dynamic authentication requirements where the number and type of authentication factors are adjusted based on the transaction context and user profile. For low-risk transactions, fewer authentication factors are required, while high-risk transactions trigger additional verification steps. This dynamic approach allows the system to maintain high security for critical transactions while providing user convenience for routine transactions, avoiding the need for users to consistently provide multiple authentication factors
Data Source
AI summary
Systems and techniques may generally be used to authenticate users. An example technique may include receiving a selection to execute a first financial transaction on a first user account of a first user at a financial institution, the first financial transaction having an authentication level requirement, and determining that the first user completed a selected authentication option that satisfies the authentication level requirement. The example technique may include, in response to the determination, authorizing the first financial transaction to execute using the first user account.