Automated Transaction Account Update via Merchant Portal Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods require users to manually update transaction account information with merchants, which is time-consuming and insecure, especially when transaction account information expires or is breached, leading to potential fraud and increased security risks.
Innovation Solution
A transaction management platform that automatically updates transaction account information by navigating a merchant portal using stored login credentials and a navigation model, such as robotic process automation (RPA), to manage and secure transaction account information without user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users manually update transaction account information with merchants, then transaction account information can be updated, but it is time-consuming and increases security risks
Solution Approach 1:
The system performs preliminary actions by automatically detecting when transaction account information needs updating and proactively navigating to merchant portals to complete the update before the user would need to manually do so. The navigation model pre-identifies required updates and executes them in the background.
Solution Approach 2:
The transaction management platform enables self-service by autonomously managing the update of transaction account information without requiring user intervention. The system uses stored login credentials and a navigation model to automatically access merchant portals and update information.
2Ease of operation
If transaction account information is exposed to merchant portals and user devices for manual updates, then updates can be performed, but security risks and fraud potential increase
Solution Approach 1:
The navigation model acts as an intermediary between the transaction management platform and merchant portals. It automatically navigates to merchant portals using stored credentials and updates transaction account information in the background, eliminating the need for users to expose sensitive information across multiple devices and interfaces.
Solution Approach 2:
The system extracts the update function from manual user operations and transfers it to an automated background process. The navigation model separates the sensitive credential management from user interaction, storing credentials securely and using them only for automated updates.
3Extent of automation
If a navigation model with stored login credentials is used to automatically update transaction settings, then user intervention is minimized and security is improved, but device complexity increases
Solution Approach 1:
The navigation model serves multiple functions: it stores login credentials securely, navigates to various merchant portals automatically, detects when updates are needed, and executes the updates. This multi-functional approach consolidates what would otherwise require separate systems for each task.
Solution Approach 2:
The navigation model is nested within the transaction management platform, which itself operates within the broader payment ecosystem. The model contains embedded logic for credential management, portal navigation, and update detection, creating a hierarchical structure that manages complexity through organization.
Data Source
AI summary
A device may determine that transaction account information, associated with a transaction account associated with a user, is to be updated. The device may identify a merchant account that is configured to use the transaction account for a transaction associated with the user and a merchant, and navigate, using a navigation model, a merchant portal associated with the merchant, to access the merchant account. The device may perform, using the navigation model and login credentials for the merchant account, a login operation to access the merchant account via the merchant portal, wherein the login credentials are stored in a credential mapping that indicates an authorization to update the transaction account information to permit the transaction account information to be used in association with the merchant account. The device may update, using the navigation model, a transaction setting of the merchant account to include updated transaction account information for the transaction account.