Token-Based Device Binding for Faster Secure Merchant Checkout
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic transaction systems require users to repeatedly log in and input financial information at each merchant or service provider, leading to inefficiencies and increased transaction times.
Innovation Solution
A system that authenticates users using a single personal identification credential, performs a hashing operation, and generates a token for device and browser binding, allowing seamless transactions without the need for repeated login or financial information input.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users log in repeatedly at each merchant or service provider, then security is maintained through authentication, but transaction time increases and user convenience deteriorates
Solution Approach 1:
The system performs preliminary authentication by binding the user's device and browser during the initial login. This binding creates a persistent secure session that eliminates the need for repeated logins during the same browsing session, thereby reducing transaction time while maintaining security through the pre-established authenticated state
Solution Approach 2:
The patent introduces a binding mechanism as an intermediary between the user's credentials and the authentication system. This binding stores authentication tokens in the user's browser, acting as a mediator that automatically validates subsequent requests without requiring the user to re-enter credentials, thus reducing transaction time while preserving security through token-based verification
2Reliability
If users input financial information at each transaction, then transaction security is ensured, but ease of operation deteriorates and user convenience is reduced
Solution Approach 1:
The system implements self-service by automatically retrieving and using the user's financial information from previously stored payment methods. The binding mechanism enables the system to automatically complete transactions using stored credentials without requiring the user to manually input financial information, thereby improving ease of operation while maintaining security through the pre-authenticated binding
Solution Approach 2:
The patent creates a copy of the user's financial information and authentication credentials during the initial binding process. This copied information is stored securely in the user's browser and automatically used for subsequent transactions, eliminating the need for repeated manual input while maintaining security through the use of authenticated copies rather than requiring re-entry of sensitive data
3Reliability
If the system requires initial account creation, then user financial information can be securely stored, but device complexity and onboarding difficulty increase
Solution Approach 1:
The system performs the account creation and information storage actions preliminarily during the initial binding process. Once the user's device and browser are bound with their credentials, the secure storage infrastructure is already in place, eliminating the need for repeated account creation or information entry in subsequent transactions, thereby reducing the perceived complexity while maintaining secure storage capabilities
Data Source
AI summary
Systems and methods are disclosed herein for real-time digital authentication. According to some embodiments, receiving a hashed user credential from the third party entity, performing a matching operation between the received hashed user credential and a stored hashed credential stored in the non-transitory memory, the received hashed user credential and the stored hashed credential being hashed using the same hashing algorithm, and in response to detecting a match between the received hashed user credential and the stored hashed user credential, performing a user eligibility operation associated with the first transaction. The authentication method may further include in response to determining that the user is eligible for the first transaction, generating an authentication challenge to the user, in response to the user successfully completing the authentication challenge, retrieving payment credentials of the user and authenticating the user, and authorizing a checkout operation associated with the first transaction.