Registry-Based Transaction Data Access System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current standards for exchanging financial transactional information do not support detailed transactional data access and require point-to-point connections, leading to bottlenecks and overhead in authentication and data collection, especially when dealing with multiple service providers.
Innovation Solution
A system utilizing secure identifiers generated from user identifiers to facilitate the storage and access of detailed transactions through a registry, allowing entities to push transactions to a data store without pre-existing connections, with an access controller managing security and access rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a point-to-point connection architecture is used to exchange transactional data between users and financial institutions, then direct data exchange is enabled, but the system becomes unwieldy and creates bottlenecks when the number of participating organizations increases
Solution Approach 1:
The patent introduces a registry as an intermediary component that mediates between users and financial institutions. The registry stores mappings between user identifiers and data store locations, allowing entities to discover and access transaction data without requiring direct point-to-point connections. This intermediary approach maintains reliable data exchange while eliminating the complexity of mesh networking among multiple organizations.
2Ease of operation
If point-to-point connections are established between multiple service providers and users, then direct access to transactional data is achieved, but substantial overhead is required to authenticate numerous participants and maintain participant accounts
Solution Approach 1:
The patent extracts the authentication and account management functions from the point-to-point connection model and consolidates them into a centralized registry. The registry maintains participant credentials and performs authentication centrally, eliminating the need for each entity to independently manage authentication with every other participant. This reduces authentication overhead and simplifies account maintenance while preserving direct access capabilities.
3Loss of information
If detailed transactional information is accessed using a pull model driven by explicit requests, then transaction data can be retrieved, but it is difficult or impossible to collect detailed transactions in a timely manner when dispersed across multiple service providers
Solution Approach 1:
The patent implements preliminary action by having service providers push transaction data to user data stores in advance, rather than waiting for pull requests. The registry enables this push model by storing the mapping between user identifiers and data store locations, allowing transactions to be proactively delivered to the appropriate destination. This eliminates the delays inherent in pull-based collection across multiple dispersed providers.
4Quantity of substance
If current standards for exchanging financial transactional data are used, then aggregate-level transactional information is accessible, but detailed transactional information such as line items purchased is typically unavailable
Solution Approach 1:
The patent segments the transactional data architecture into multiple layers: aggregate-level summaries and detailed-line-item data are separated and stored in appropriate locations. The registry enables selective access to different data granularities, allowing users to retrieve either aggregate information or detailed transactions depending on their needs. This segmentation preserves aggregate information while making detailed information accessible without requiring changes to existing aggregate data exchange standards.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A system may include transaction storage devices. Each transaction storage device may include a data store configured to receive, from a first entity, a request to push a detailed transaction corresponding to a secure identifier. The secure identifier may be generated, using an encoding function, from a user identifier of a user. The data store may be further configured to store the detailed transaction based on a first determination to trust the first entity. The system may further include an access controller configured to perform the first determination by applying a first security rule corresponding to a type of the secure identifier to the request to push the detailed transaction, and a registry configured to store at least the first security rule.