Unified Login via Refresh Token Silent Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing authentication processes for online and mobile payment transactions are inconvenient, particularly on mobile devices, as they require users to manually enter login credentials, which can delay transactions and discourage the use of digital payments.
Innovation Solution
A system that implements a unified login method using a refresh token, allowing users to opt into a 'universal' login across multiple applications, where the payment provider server silently authenticates users by providing a data file with a refresh token that can be used to authenticate without requiring user input, reducing the need for repeated login credentials.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual authentication requiring login ID and password entry is implemented, then security is maintained, but transaction time increases and user convenience deteriorates
Solution Approach 1:
The system performs preliminary authentication by storing authentication results and device identifiers during initial login. This allows the system to automatically verify users in subsequent transactions without requiring them to re-enter credentials, thus reducing transaction time while maintaining security through pre-validated authentication data.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism that uses device identifiers and stored authentication tokens as a mediator between the user and the payment system. This intermediary layer enables automatic verification without direct user input, bridging the gap between security requirements and convenience needs.
2Reliability
If manual authentication requiring keyboard input is implemented, then security is maintained, but ease of operation deteriorates especially on mobile devices
Solution Approach 1:
The system implements self-service authentication by automatically using stored device identifiers and authentication tokens to verify users without requiring manual keyboard input. The device itself serves as the authentication medium, eliminating the need for users to physically enter credentials on mobile devices while maintaining security through cryptographic verification.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism that uses device identifiers and stored authentication tokens as a mediator between the user and the payment system. This intermediary layer enables automatic verification without direct user input, bridging the gap between security requirements and convenience needs.
3Reliability
If repeated login credential entry is required, then security is maintained, but productivity decreases due to multiple authentication steps
Solution Approach 1:
The system performs preliminary authentication by storing authentication results and device identifiers during initial login. This allows the system to automatically verify users in subsequent transactions without requiring them to re-enter credentials, thus reducing transaction time while maintaining security through pre-validated authentication data.
4Ease of operation
If unified login across multiple applications is implemented, then ease of operation improves, but device complexity increases
Solution Approach 1:
The patent implements a universal authentication system where a single set of stored authentication tokens and device identifiers can be used across multiple applications and transactions. This multi-functional approach allows the same authentication mechanism to serve various payment scenarios, improving ease of operation without proportionally increasing complexity.
Data Source
AI summary
A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a request to complete a transaction associated with a merchant application. The request includes a data file including an identifier from the user device. The request is from a user device. The method also includes determining whether the data file includes a refresh token and determining whether the refresh token is valid if the data file includes the refresh token. The method further includes receiving an access token from the user device if the refresh token is valid. The access token includes an authorization scope. The method also includes determining whether the transaction is within the authorization scope. The method further includes authenticating a user if the transaction is within the authorization scope.


