Data Mapping System for Merchant Identifier Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Payment processing systems face challenges in accurately matching and utilizing non-validated merchant identifiers with validated data, leading to potential fraudulent transaction declines and incomplete transaction reports due to format and identifier discrepancies.
Innovation Solution
A data mapping system that compares and maps non-validated merchant identifiers from user messages to validated identifiers in authorization messages, storing these mappings in a linked identifier table to facilitate accurate matching and integration during the authorization process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-validated merchant identifiers are used in transactions, then merchants can submit flexible data formats, but the data cannot be automatically considered accurate and may not be in standard format causing system incompatibility
Solution Approach 1:
The patent introduces an intermediary mapping system that sits between non-validated merchant identifiers and the payment processing system. This mapping system translates and validates merchant identifiers, allowing the system to accept flexible non-validated formats while ensuring data accuracy through mapping to standardized validated identifiers before processing.
2Reliability
If merchant identifiers are strictly validated against authorization messages, then data accuracy is maintained, but legitimate transactions may be incorrectly declined due to format discrepancies
Solution Approach 1:
The patent implements preliminary mapping of merchant identifiers before the authorization process. By pre-establishing mappings between non-validated and validated merchant identifiers, the system prepares the data in advance, ensuring accuracy is maintained while preventing false declines. This preliminary action allows the authorization process to proceed efficiently with already-matched identifiers.
3Reliability
If non-validated data is excluded from authorization messages, then data quality is maintained, but useful merchant-submitted data is lost and transaction analysis becomes incomplete
Solution Approach 1:
The patent merges non-validated merchant data with validated authorization message data through the mapping system. Instead of excluding non-validated data, the system combines both data sources by mapping merchant identifiers to their validated counterparts, preserving all useful information while maintaining data quality standards. This allows complete transaction analysis with both merchant-submitted and system-validated data.
Data Source
AI summary
A data mapping (DM) computing device including a processor and a memory in communication with the processor is provided. The processor receives a plurality of validated data messages associated with a plurality of transactions through a first communication channel and receives a non-validated data message associated with a first transaction through a second communication channel. Each validated data message includes a plurality of validated data elements with a validated merchant identifier. The non-validated data message includes a plurality of non-validated data elements with a non-validated merchant identifier. The processor further compares the validated data messages and the non-validated data message, identifies a validated data message that is associated with the first transaction based on the comparison, maps the non-validated merchant identifier and the validated merchant identifier of the identified validated message, and stores the mapped merchant identifiers in a linked identifier table within the memory.