Open Banking Consent Orchestration for Multi-Account Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing open services, such as open banking, require users to repeatedly authenticate and consent to data access for each account, leading to a time-consuming and vulnerable process.

Innovation Solution

A system and method for orchestrating data connections through a common sequence of enrollment, using an orchestration host to identify and aggregate consent terms across multiple accounts, enabling simultaneous data connection and access management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users authenticate and consent to data access for each account separately, then data security and compliance with individual account terms are ensured, but the process becomes time-consuming and complex

Engineering Contradiction:
Improvedata securityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the authentication and consent process into two distinct phases: (1) a single initial authentication and aggregate consent phase, and (2) subsequent individual account access phases. This segmentation allows the system to maintain security requirements while reducing redundant authentication steps, directly resolving the contradiction between security reliability and time consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary authentication and aggregate consent acquisition before individual account access is needed. By completing the authentication and consent process in advance, the system eliminates the need for repeated authentication while maintaining security and compliance, thus reducing time loss without compromising data security.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If users authenticate and consent for each account separately, then compliance with individual account terms is ensured, but the process becomes complex and user-unfriendly

Engineering Contradiction:
Improvecompliance with account termsVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent merges multiple individual authentication and consent processes into a single aggregate consent process. Users authenticate once and provide aggregate consent for multiple accounts simultaneously, rather than repeating the process for each account. This merging maintains compliance with individual account terms while dramatically simplifying the user experience and reducing operational complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system implements a universal authentication and consent mechanism that works across multiple different accounts and financial institutions. This multi-functional approach allows a single authentication event to serve multiple purposes (accessing multiple accounts), making the system both compliant and user-friendly.

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

3Reliability

If repeated authentication is required for each account, then security is maintained, but productivity and efficiency of data access are reduced

Engineering Contradiction:
ImprovesecurityVSAvoiddata access efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs authentication and consent acquisition as preliminary actions before data access is needed. By completing these security-critical steps in advance, the system enables rapid subsequent data access across multiple accounts without compromising security, thus significantly improving productivity and efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Once aggregate consent is obtained, the system enables users to access their own data across multiple accounts through self-service mechanisms without requiring repeated authentication. This maintains security while dramatically improving access efficiency and user productivity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250390942A1Systems and methods for use in orchestrating data connections
Publication Date: 2025.12.25 MASTERCARD INT INC
  • US20250390942A1 patent drawing
  • US20250390942A1 patent drawing
  • US20250390942A1 patent drawing

AI summary

Systems and methods are provided for use in orchestrating data connections. One example computer-implemented method includes receiving, by an orchestration host computing device, an access request for a user and, in response to the request, identifying, through an open service, multiple accounts issued to the user by different account hosts. The computer-implemented method also includes identifying, by the computing device, consent terms for each of the account hosts, aggregating the identified consent terms for the account hosts, and presenting, at a communication device associated with the user, the aggregate consent terms to the user. The computer-implemented method then includes, based on acceptance from the user of the aggregate consent terms, submitting, by the computing device, a data connection request to each of the account hosts.