Merchant Identity Validation via Unique Key-Hash Pairs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current merchant system identity validation methods in electronic transactions rely on shared login credentials, which are outdated and insufficient, leading to security concerns when a compromised merchant system is detected, requiring the entire group to be taken down, and do not provide precise identification and isolation of compromised systems.

Innovation Solution

Implementing a method where each merchant system is assigned a unique primary key and hash value, which are included in transaction data sent to an access management system for validation, allowing it to pinpoint and block traffic from compromised systems without affecting others, using a key-hash pair for identity verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If shared login credentials are used for merchant system validation, then ease of operation is improved, but security is worsened because a compromised system requires taking down the entire group

Engineering Contradiction:
Improvevalidation processVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the validation process by assigning unique identifiers (primary key and hash value) to each individual merchant system instead of using shared credentials. This allows the access management system to validate and isolate specific compromised systems without affecting others, resolving the contradiction between ease of operation and security by maintaining simple validation procedures while enabling precise security control at the individual system level

Inventive Principle:
Principle #1Segmentation

2Reliability

If unique primary key and hash value are assigned to each merchant system, then security is improved by isolating compromised systems, but device complexity is worsened

Engineering Contradiction:
ImprovesecurityVSAvoidvalidation system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-generating and storing the primary key and hash value for each merchant system in a database before validation is needed. During transaction processing, the access management system simply retrieves and compares these pre-stored values, maintaining low complexity despite the enhanced security model. The complexity is front-loaded during system setup rather than during ongoing validation operations

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If shared credentials are used, then device complexity is reduced, but measurement precision is worsened because compromised systems cannot be precisely identified

Engineering Contradiction:
Improvevalidation systemVSAvoididentification precision
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent applies local quality by making each merchant system's identification data unique and specific to that individual system through the primary key and hash value assignment. This enables the access management system to precisely identify and validate each system individually, achieving high measurement precision in identifying compromised systems while maintaining relatively simple validation logic through direct comparison of unique identifiers

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20240422008A1Methods and systems for enhanced endpoint identity validation in electronic transactions
Publication Date: 2024.12.19 WORLDPAY LLC
  • US20240422008A1 patent drawing
  • US20240422008A1 patent drawing
  • US20240422008A1 patent drawing

AI summary

Methods and systems are disclosed for merchant system identity validation. One method comprises generating, by an access management system, a primary key associated with an integrator system and transmitting the primary key to the integrator system. The access management system may also generate a hash value associated with a merchant system, and may transmit the hash value to the merchant system. When a payment transaction is initiated at the merchant system, the access management system may receive an authorization request comprising a key-hash pair. The key-hash pair may be validated against a validation database. Upon successful validation, the access management system may transmit the authorization request to an acquirer processor.