Transaction Status Security With Tokenized Validation and Data Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing transaction systems face barriers due to lack of integrated data security and secure client account validation, leading to concerns over fraud, regulatory compliance, and privacy issues, which hinder seamless network communications and data management.

Innovation Solution

A modular data security system is implemented within merchant systems, enabling tokenized client data access through a secure interface element, allowing real-time account lookup and validation while isolating sensitive information from the merchant system, using both push and pull systems for enhanced security and flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If client data is shared with merchant systems for transaction processing, then transaction functionality is enabled, but data security and privacy are compromised

Engineering Contradiction:
Improvetransaction functionalityVSAvoiddata security risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an account security system as an intermediary between the merchant system and client data. This mediator validates client accounts and provides verification information to merchants without exposing actual client data, thus enabling transaction functionality while maintaining data security and privacy

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts sensitive client data from the transaction flow by implementing account validation that provides verification information without exposing actual account details. The system takes out the essential validation function while removing the harmful exposure of client data to merchant systems

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If account validation is performed without integrated security systems, then transaction speed is maintained, but fraud risk and regulatory compliance issues increase

Engineering Contradiction:
Improvetransaction speedVSAvoidfraud protection
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary account validation through the account security system before transactions are completed. By performing validation in advance and providing verification information to merchants, the system enables fraud protection without compromising transaction speed, as the validation occurs as part of the transaction flow rather than as a separate blocking step

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If client account data is accessed by merchant systems, then account validation is enabled, but regulatory compliance and privacy concerns arise

Engineering Contradiction:
Improveaccount validation capabilityVSAvoidregulatory compliance risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The account security system serves as an intermediary that enables account validation capability while preventing direct access to client account data by merchant systems. This mediator approach allows merchants to validate accounts for regulatory compliance without handling sensitive data, thus maintaining versatility while reducing regulatory compliance risk

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250272675A1Status system with data security for transactions
Publication Date: 2025.08.28 SYNCHRONY BANK
  • US20250272675A1 patent drawing
  • US20250272675A1 patent drawing
  • US20250272675A1 patent drawing

AI summary

Examples described herein include systems, methods, instructions, and other implementations for data security. One example includes receiving a status inquiry associated with a secure transaction, a merchant system, and a client device. The status inquiry is processed to determine that the merchant system associated with the status inquiry has been previously validated and that the status inquiry is from the merchant system. Then, in response to the determination that the merchant system has been previously validated, postback data including a tokenized client account number associated with client information is accessed and the tokenized client account number is transmitted. The tokenized client account number facilitates processing the secure transaction without the merchant system having access to the client information.