Token-Based Account Association to Reduce Identity Spoofing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Establishing trusted relationships between user accounts in account-based systems is challenging due to the risk of transposition errors and identity spoofing, especially when using non-unique or easily recognizable account identifiers, which can lead to unintended transactions and data breaches.
Innovation Solution
A method involving the exchange of account identification data through secure channels, followed by the use of tokens to establish relationships between user accounts, ensuring authenticity and reducing the risk of malicious activities by requiring both parties to submit matching tokens for account association.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If unique account numbers or account number and sort code combinations are used as account identifiers, then account identification precision is improved, but the risk of transposition errors increases
Solution Approach 1:
The patent uses QR codes as visual copies of account identification data. Instead of relying solely on numeric account identifiers that are prone to transposition errors, the system creates a visual representation (QR code) that encodes the same information in a format that is much harder to misenter, thereby reducing transposition errors while maintaining identification precision.
Solution Approach 2:
The patent replaces manual entry of account identifiers (mechanical keyboard input) with optical scanning (QR code reading). This substitution eliminates the manual typing process that causes transposition errors, as the QR code data is automatically captured by the scanning device without human intervention in the data entry phase.
2Ease of operation
If generic identifiers such as user configurable display names are used, then ease of operation is improved, but the risk of identity spoofing increases
Solution Approach 1:
The patent uses QR codes as unique visual copies that represent the genuine account. The QR code contains encoded account information that serves as a verifiable copy of the account's identity, making it difficult for spoofers to create convincing fakes. The visual nature of the QR code provides an additional layer of verification beyond simple display names.
Solution Approach 2:
The patent performs preliminary verification by requiring both accounts to scan and verify each other's QR codes before establishing the association. This preliminary mutual verification action ensures that both parties confirm each other's identity before the relationship is created, preventing spoofing attempts where one party might be impersonated.
3Ease of operation
If account identification data is exchanged through manual entry, then ease of operation is improved, but manufacturing precision of data accuracy deteriorates
Solution Approach 1:
The patent replaces manual data entry (mechanical keyboard input) with optical scanning technology. The QR code scanning process automatically captures and transfers account identification data without requiring users to manually type or transcribe account numbers, thereby eliminating transcription errors and significantly improving data accuracy while maintaining ease of operation.
4Reliability
If tokens are required for account association, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent implements tokens in the form of QR codes, which are visual representations that encode the necessary authentication information. This approach maintains the security benefits of token-based verification while simplifying the user interface and interaction model, as users simply scan and display QR codes rather than manually entering or managing complex token strings.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of the present disclosure comprise methods, apparatus and computer readable instructions for establishing a relationship between user accounts. For example, the method comprises: receiving a first account association request message in relation to the a first user account in an account based system, the first account association request message comprising account identification data corresponding to the a second user account in the account based system; identifying, on the basis of the first account association request message, a first source account identifier which corresponds to the first user account and a first target account identifier which corresponds to the second user account; receiving a second account association request message in relation to the second user account, the second association message comprising account identification data corresponding to the first user account; identifying, on the basis of the second account association request message, a second source account identifier which corresponds to the second user account and a second target account identifier which corresponds to the first user account; determining that at least one of: the first source account identifier and the second target account identifier relates to the same user account in the account based system; and the second source account identifier and the first target account identifier relates to the same user account in the account based system; and responsive thereto, establishing a relationship between the first user account and the second user account.