Alias Retrieval Cache for Faster Transfer App Interactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge of efficiently searching and interacting with millions of alias identifiers across different transfer applications managed by various entities is time-consuming and difficult, hindering seamless user interactions.
Innovation Solution
A method and system that utilizes a server computer to search a database for aliases associated with potential users based on contact data from a user device, providing the aliases to the device for storage and enabling quick selection and interaction through a transfer application, using an inquiry API to enhance discoverability and facilitate cross-wallet payments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If users manually search through millions of alias identifiers in a database, then they can find the correct alias, but the process becomes time-consuming and difficult
Solution Approach 1:
The system performs preliminary actions by automatically retrieving and caching alias identifiers in the browser's memory before the user needs to conduct a transfer. When contact data is entered, the system proactively fetches corresponding aliases from the database and stores them locally, so that when the user needs to select an alias, it is already available instantly without requiring a time-consuming search through millions of identifiers.
2Reliability
If the system stores all alias identifiers in a centralized database, then data integrity is maintained, but retrieval speed decreases due to the large number of records
Solution Approach 1:
The system segments the alias data retrieval process into two parts: the centralized database maintains the complete authoritative list of aliases for data integrity, while the user's browser maintains a local cache of recently used or relevant aliases for fast retrieval. This segmentation allows the system to query the full database when necessary while providing instant access to frequently needed aliases through local storage.
Solution Approach 2:
The browser's local storage acts as an intermediary between the centralized database and the user interface. Instead of directly querying the massive database every time an alias is needed, the system first checks the local intermediary cache, which contains pre-fetched alias data. This intermediary layer significantly speeds up retrieval while the centralized database remains the ultimate source of truth for data integrity.
3Measurement precision
If the system requires users to know exact alias identifiers, then precise transfers are enabled, but user effort and complexity increase
Solution Approach 1:
The system provides self-service by automatically managing the alias retrieval and matching process. When users enter contact data (such as phone numbers or email addresses), the system automatically queries the database, retrieves the corresponding alias identifiers, and presents them to the user. This eliminates the need for users to manually know or search for exact alias identifiers, reducing user effort while maintaining transfer accuracy through automatic alias resolution.
Data Source
AI summary
A method is disclosed. The method includes receiving, by a server computer from a user device comprising a transfer application via a communications network, contact data for a plurality of potential users on the user device. The method also includes searching, by the server computer a database, for a set of aliases associated with the potential users in the contact data. The method also includes providing, by the server computer via the communications network, the set of aliases to the user device. The user device is programmed to store the set of aliases in the transfer application, receive a selection of an alias associated with a user, and initiate an interaction with the alias using the transfer application.