Merchant Account Bank Switch Automation Using Transaction History

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Financial account holders face the challenge of having to manually update their bank account information across numerous merchant accounts when switching banks, leading to reluctance due to the hassle and difficulty of managing multiple changes.

Innovation Solution

An automated system and method that uses a remote server to access transaction history, identify relevant merchant accounts, and update bank account information across multiple databases, utilizing user authentication and machine learning to streamline the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual updating of bank account information is used for each merchant account, then data accuracy is maintained, but user convenience deteriorates and time consumption increases

Engineering Contradiction:
Improveuser convenienceVSAvoidtime consumption
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system merges multiple individual update operations into a single automated batch process. By combining transaction history analysis, merchant account identification, and information updating into one integrated workflow, the system allows users to update bank account information across numerous merchant accounts through a single initiation action, dramatically reducing time consumption while maintaining accuracy through systematic verification.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary analysis of transaction history to automatically identify all merchant accounts associated with the user before the actual update process. This preliminary identification step prepares a comprehensive list of target accounts, ensuring that no relevant merchant account is overlooked and enabling the subsequent bulk update to proceed efficiently with pre-validated information.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If automated bulk updating is implemented, then user convenience is improved and time is saved, but system complexity increases

Engineering Contradiction:
Improveupdate efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary processing layer that bridges the user's simple update request and the complex task of updating multiple merchant accounts. This intermediary automatically retrieves transaction history, identifies relevant merchant accounts, validates bank account information, and coordinates the bulk update process, shielding users from complexity while maintaining high productivity through automated workflows.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms that provide users with visibility into the automated update process. By displaying identified merchant accounts, update status, and verification results, the system allows users to monitor and control the complex bulk update operation, reducing perceived complexity while maintaining efficient automated processing through iterative validation and confirmation steps.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12530717B2System and method for facilitating bank account information changes
Publication Date: 2026.01.20 CAPITAL ONE SERVICES LLC
  • US12530717B2 patent drawing
  • US12530717B2 patent drawing
  • US12530717B2 patent drawing

AI summary

In a method for changing a user's bank account information in merchant account databases a server receives a login request including a user identification and first user authentication information. The server further receives a request to change bank account information from a first bank account to a second bank account for merchant accounts of the user and network login information for the first bank account. The server accesses an account information database for the first bank account and downloads transaction information for merchant transactions involving the first bank account. The server identifies a set of merchant user accounts involved in the merchant transactions and receives account login information for a data site associated with a selected account. The server accesses the data site and changes a bank account identification stored therein from the first bank account to the second bank account.