Payment Aggregator Authentication Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing payment aggregator systems are cumbersome and inefficient, requiring users to input authentication data for multiple entities, making recurring payments cumbersome and time-consuming.
Innovation Solution
A computing system and method that identifies recurring transactions, stores interaction-based authentication data, and displays aggregated user interactions via a user interface, allowing users to perform optional interactions across a network without needing to log into each entity's platform separately.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users log in to each entity's website separately to perform payments, then authentication reliability is ensured, but operation time and complexity increase significantly
Solution Approach 1:
The patent introduces a payment aggregator as an intermediary system that sits between the user and multiple entity websites. The aggregator stores authentication data (passwords, security questions, etc.) for multiple entities and uses this stored data to automatically authenticate users on behalf of each entity, eliminating the need for users to manually log in to each site while maintaining authentication reliability through secure storage and transmission of credentials.
Solution Approach 2:
The system performs preliminary action by pre-storing authentication data for multiple entities in the payment aggregator's database before the user needs to make payments. When a user initiates a payment, the system retrieves the pre-stored authentication data and automatically uses it to log in to each entity's website, eliminating the need for real-time manual authentication and significantly reducing operation time.
2Measurement precision
If users manually input authentication data for each entity, then authentication accuracy is maintained, but ease of operation deteriorates
Solution Approach 1:
The payment aggregator implements self-service by automatically retrieving and using stored authentication data for each entity without requiring manual input from the user. The system autonomously handles the authentication process by accessing pre-stored credentials in its database and automatically submitting them to each entity's authentication system, making the process as easy as initiating a single payment action while maintaining authentication accuracy through secure automated credential management.
Solution Approach 2:
The system creates a copy of the authentication process by storing authentication data (passwords, security answers, etc.) in the payment aggregator's database as replicated information. Instead of requiring users to re-enter authentication data for each entity, the system uses these copied authentication records to automatically authenticate users, significantly improving ease of operation while maintaining accuracy through secure copying and transmission of authentication credentials.
3Ease of operation
If the system stores interaction-based authentication data, then ease of operation improves, but data security risks increase
Solution Approach 1:
The patent applies beforehand cushioning by implementing multiple security measures in advance to protect stored authentication data. The system uses encryption to secure authentication data in the database, employs secure transmission protocols when accessing stored data, and implements access controls to prevent unauthorized retrieval. These preventive security measures cushion against potential data breaches and protect the stored authentication information while enabling the system to automatically use this data for streamlined user authentication.
Data Source
AI summary
Systems and methods include program instructions to identify that a user is accessing, via a user interface of a user device, a user interaction aggregator of a digital platform to perform user interaction(s) across a network, each user interaction of the one or more user interactions having specific interaction-based authentication data associated therewith to perform each user interaction. Further, program instructions access a virtual aggregation table of stored recurring electronic processes, each stored recurring electronic process having associated therewith stored interaction-based authentication data. Program instructions also display, via the user interface, an aggregation of optional user interactions for the user to perform via the digital platform, each optional user interaction being selected from the stored recurring electronic processes.