Merchant Table Location Identifier for Transaction Data Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service platforms that handle electronic transactions face complexity in analyzing and reporting due to large amounts of data and data entry errors, making it cumbersome to configure and manage transaction records from multiple sources for merchants.

Innovation Solution

The system generates a unique location identifier (LID) based on normalized merchant addresses, allowing for the organization and grouping of transaction records by location, and applies rules to identify merchant accounts associated with a defined location, facilitating accurate analysis and reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If transaction records are stored with detailed merchant information from multiple sources, then data completeness is improved, but analysis and reporting complexity increases

Engineering Contradiction:
Improvedata completenessVSAvoidanalysis complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments merchant information into standardized fields (merchant_id, merchant_name, address, location_identifier) and organizes transaction records into a structured table format. This segmentation allows comprehensive data storage while enabling efficient querying and analysis through the standardized structure and location-based grouping.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a location_identifier as an intermediary element that links merchant addresses to geographic locations. This intermediary simplifies analysis by providing a direct connection between transaction records and location-based metrics, avoiding complex address parsing and geographic calculations during analysis.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If merchant addresses are stored in detailed formats, then location accuracy is improved, but data processing complexity increases

Engineering Contradiction:
Improvelocation accuracyVSAvoiddata processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent performs preliminary normalization of merchant addresses during data entry, converting various address formats into a standardized structure with separate fields for street address, city, state, and ZIP code. This preliminary action maintains location accuracy while simplifying subsequent processing by eliminating the need for complex address parsing operations.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If transaction records are organized by multiple merchant attributes, then query flexibility is improved, but storage and retrieval complexity increases

Engineering Contradiction:
Improvequery flexibilityVSAvoidstorage complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal merchant table structure that serves multiple functions: it stores detailed merchant information, enables location-based analysis through location_identifier, supports hierarchical merchant relationships, and facilitates various query types. This single standardized structure replaces multiple specialized data structures, reducing overall system complexity while maintaining query flexibility.

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

Data Source

PatentUS11615054B2Merchant table and associated processes
Publication Date: 2023.03.28 FIRST DATA CORP
  • US11615054B2 patent drawing
  • US11615054B2 patent drawing
  • US11615054B2 patent drawing

AI summary

Tables and techniques to configure the same are provided. In some embodiments, configuration of one or more memory devices can permit or otherwise facilitate including transaction records in a table or another type of data structure, where the transaction records can be organized based at least on a defined location for a merchant or another type of organization associated with the transaction records.