Stand-In Network Authorization With Truncated Card Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In network interactions, particularly in stand-in services for transaction authorization, ensuring the security and integrity of sensitive data like card verification codes and expiration dates is challenging when multiple parties are involved, as storing this data exposes it to breaches.

Innovation Solution

The system captures and truncates specific data from authorization requests, optionally treating it with a cryptographic algorithm, and stores the encrypted output, enabling the processing network to verify transactions on behalf of the issuer institution without possessing the original data, ensuring security through truncated data verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the processing network stores complete sensitive data (CVC, expiration date) for stand-in authorization, then transaction verification capability is improved, but data security and risk of breaches worsen

Engineering Contradiction:
Improvetransaction verification capabilityVSAvoiddata breach risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent divides the sensitive data into two parts: complete data is stored only at the issuing institution, while truncated versions (with missing digits) are stored at the processing network. This segmentation allows the processing network to perform verification without storing complete sensitive data, reducing breach impact while maintaining verification capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces truncated data as an intermediary representation between the complete sensitive data and the verification process. The truncated data serves as a mediator that enables stand-in authorization functionality without exposing the full sensitive information, thus balancing verification needs with security requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If the processing network stores truncated data for stand-in services, then data security is improved, but verification precision and reliability worsen

Engineering Contradiction:
Improvedata securityVSAvoidverification reliability
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The patent performs preliminary truncation of the CVC and expiration date at the time of data capture, creating a truncated version that is then stored and used for verification. This preliminary action ensures that only truncated (less sensitive) data is stored at the processing network, maintaining security while enabling reliable verification through consistent truncation logic.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If complete data is stored at multiple parties (issuer and processing network), then verification capability is improved, but data exposure and security risks worsen

Engineering Contradiction:
Improveverification capabilityVSAvoiddata exposure
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies different data storage qualities at different locations: the issuing institution stores complete data for full verification capability, while the processing network stores only truncated data for limited verification purposes. This local quality differentiation ensures that data exposure is minimized at each location while maintaining the necessary verification capabilities where needed.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250322404A1Systems and methods for use in stand-in network services
Publication Date: 2025.10.16 MASTERCARD INT INC
  • US20250322404A1 patent drawing
  • US20250322404A1 patent drawing
  • US20250322404A1 patent drawing

AI summary

Systems and methods are provided for enabling stand-in network services based on truncated data. One exemplary method includes receiving an authorization request, the authorization request including an account number for an account, an expiration date associated with the account number, and a verification code specific to the account; scrambling the account number; retrieving, based on the scrambled account number, truncated data for the account from a memory; truncating the expiration date and verification code from the authorization request; comparing the truncated expiration date and the truncated verification code to the retrieved truncated data; and, in response to a match between the truncated expiration date, the truncated verification code, and the retrieved truncated data, compiling and transmitting an authorization response.