Mobile Wallet Account Linking Using Alias-Based Issuer Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Digital wallet management is unwieldy and insecure, as users often need to undergo unnecessary authorization processes and their bank-issued accounts cannot be easily added to digital wallets.
Innovation Solution
A system that allows transaction account issuers to manage digital wallets through a separate application, using aliases instead of account numbers, and validating security codes to securely add accounts to digital wallets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users provide account information and undergo authorization processes to add accounts to digital wallets, then security is improved, but user experience and ease of operation deteriorate due to unwieldy and unnecessary steps
Solution Approach 1:
The patent introduces an alias as an intermediary element that represents the account without exposing sensitive account information. The alias acts as a mediator between the user and the account details, allowing secure addition to digital wallets without requiring users to handle or transmit sensitive account numbers directly, thus improving both security and user experience
Solution Approach 2:
The patent extracts sensitive account information from the direct addition process by using aliases. Instead of requiring users to input and transmit full account numbers, the system separates the identification function (alias) from the sensitive account data, removing the security burden from the user while maintaining account security
2Reliability
If account information is transmitted over networks to validate digital wallet requests, then account validation is achieved, but security risks increase due to transmission over potentially unsecured networks
Solution Approach 1:
The alias serves as a secure intermediary that can be transmitted over networks without exposing sensitive account information. The alias validates the account linkage while maintaining security, as it does not contain the actual sensitive account data that would be at risk during network transmission
Solution Approach 2:
The system creates a copy or representation of the account linkage through the alias rather than transmitting the actual sensitive account information. This copy (alias) suffices for validation purposes while eliminating the security risks associated with transmitting real account data over networks
Data Source
AI summary
A system may be configured to perform operations and/or steps comprising querying, by an issuer server, a network server for an alias associated with a transaction account. The issuer server may receive the alias from the network server. The issuer server may also send the alias to an issuer application. The operations may also comprise validating, by the issuer server, an account validation input entered into the issuer application. The issuer server may send an issuer signature criteria that indicate whether the account validation input is valid. The issuer application may add an alias associated with the account to a digital wallet.