Transaction Deconflicting Using Network Names and User Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic payment systems, designed independently without centralized standards, face challenges in deconflicting data from multiple sources due to proprietary encoding and display formats, leading to duplicate entries and incorrect account reporting by aggregation services.
Innovation Solution
A system that compares transactions based on consistent data like payment amount and time stamp, uses network names generated by credit card networks, and generates user queries to resolve conflicts, potentially with automated assistance, ensuring accurate account information aggregation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary encoding methods and formats are used by each payment system to increase internal efficiency, then system reliability and error prevention are improved, but data matching and deconflicting between different sources become more difficult
Solution Approach 1:
The patent introduces an aggregation service as an intermediary component that receives data from multiple proprietary payment systems. This service acts as a mediator that translates and harmonizes data from different encoding formats into a unified representation, enabling deconflicting without requiring changes to the underlying proprietary systems. The aggregation service maintains the reliability of individual systems while resolving the complexity of cross-system data matching.
Solution Approach 2:
The patent transforms the approach to data comparison by changing the parameters used for matching. Instead of attempting to match all proprietary data fields directly, the system identifies and compares key invariant parameters (such as transaction amounts, timestamps, and merchant identifiers) that remain consistent across different encoding formats. This parameter transformation enables effective deconflicting despite format differences.
2Adaptability or versatility
If each system uses independent proprietary formats without centralized standards, then system adaptability and independence are improved, but duplicate transaction detection and conflict resolution deteriorate
Solution Approach 1:
The aggregation service is designed with universal functionality to handle multiple proprietary formats simultaneously. It implements a multi-functional architecture that can adapt to different payment systems (Visa, Mastercard, American Express, etc.) while maintaining a single unified interface for conflict resolution. This universality allows the system to preserve the adaptability of individual proprietary systems while achieving precise duplicate detection through standardized comparison protocols.
3Productivity
If aggregation services attempt to match transactions from multiple sources, then comprehensive account monitoring is improved, but false duplicates and incorrect reporting increase due to format variations
Solution Approach 1:
The system performs preliminary actions by pre-processing and normalizing data from different payment sources before attempting to match transactions. The aggregation service implements preliminary validation, formatting standardization, and key parameter extraction prior to the matching process. This preliminary preparation significantly reduces false duplicates and improves matching accuracy by ensuring that comparisons are made between equivalent data representations.
Solution Approach 2:
The patent implements feedback mechanisms where the aggregation service continuously learns from matching results and adjusts its deconflicting algorithms. When duplicate transactions are identified or conflicts arise, the system uses feedback loops to refine its matching criteria and improve future detection accuracy. This adaptive feedback process enhances both the efficiency of comprehensive monitoring and the precision of transaction matching over time.
Data Source
AI summary
Methods and systems are described for verifying an identity of a user through contextual knowledge-based authentication. The system described uses contextual knowledge-based authentication. By verifying an identity of a user through contextual knowledge-based authentication, the verification is both more secure and more intuitive to the user. For example, by relying on confidential and/or proprietary information, the system may generate verification questions, the answers to which are known only by the user.