Transaction Status Access With Role-Based Contingency Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex financial transactions, such as mortgage loan origination, are difficult to monitor due to the involvement of multiple parties and limited access to information, leading to missed deadlines and suboptimal experiences.

Innovation Solution

An electronic computing device system that authenticates third parties and provides status information for financial transactions, including contingency updates, based on authorization levels, using a data store and communication module to notify third parties through existing software applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If status information is made accessible to multiple third parties, then communication efficiency improves, but information security and access control become more complex

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidaccess control complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements differentiated access control where different third parties receive different levels of status information based on their authorization. The processor determines what information each third party can access, allowing broad distribution of information while maintaining security through localized, role-based access rights.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes the parameter of information accessibility by dynamically adjusting what status information is returned to each third party based on their authorization level. This allows the same system to serve multiple parties with different needs without requiring complex manual access control configurations.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If real-time status information is provided to all parties, then coordination improves, but system complexity and data management increase

Engineering Contradiction:
Improvecoordination easeVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system automatically queries the data store for status information and determines what to return based on authorization, without requiring manual intervention. The processor self-manages the complexity of data retrieval and filtering, providing real-time information to authorized parties while keeping the system manageable through automated processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system serves multiple third parties with different authorization levels through a single unified interface. The same computing device handles authentication, authorization determination, data querying, and information delivery for all parties, reducing overall system complexity despite serving diverse needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of information

If comprehensive status information is returned to third parties, then transparency improves, but information security risks increase

Engineering Contradiction:
Improveinformation transparencyVSAvoidsecurity risks
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The system applies different levels of information transparency to different third parties based on their authorization. Each party receives comprehensive information appropriate to their role, while the system locally filters what is returned to prevent unauthorized access to sensitive data, balancing transparency with security.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12567043B2Status information for financial transactions
Publication Date: 2026.03.03 WELLS FARGO BANK NA
  • US12567043B2 patent drawing
  • US12567043B2 patent drawing
  • US12567043B2 patent drawing

AI summary

An electronic computing device receives a request from a third party for status information for a financial transaction. The request includes an identifier for the third party and an identifier for the financial transaction. The third party is authenticated using the identifier for the third party. A data store is queried using the identifier for the financial transaction to determine the status information for the financial transaction. Any contingency information associated with the financial transaction is updated. The status information and contingency information are returned to the third party.