Subaccount Authentication Segmentation for Fraud Mitigation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional authentication methods for transaction accounts are inadequate as they rely on a single method of authentication for multiple subaccounts, making the entire account vulnerable if a single subaccount is compromised.

Innovation Solution

Implementing customized authentication rules and values for each subaccount, allowing different authentication methods (e.g., PIN, signature, biometric) and values for each subaccount, stored in an account database, ensuring that compromising one subaccount does not expose the others.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional single authentication method is used for multiple subaccounts, then device complexity is reduced, but account security deteriorates

Engineering Contradiction:
Improveaccount securityVSAvoidauthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the authentication system into separate authentication methods for each subaccount. Each subaccount can have its own authentication method (PIN, signature, or both), so that compromising one subaccount does not compromise others. This segmentation isolates security risks to individual subaccounts while maintaining overall system security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different authentication requirements to different subaccounts based on local needs. Each subaccount can be configured with specific authentication methods appropriate to its usage pattern and risk profile, rather than applying a uniform authentication approach across all subaccounts.

Inventive Principle:
Principle #3Local quality

2Reliability

If customized authentication rules are implemented for each subaccount, then account security is improved, but device complexity increases

Engineering Contradiction:
Improveaccount securityVSAvoidauthentication management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments authentication management into individual subaccount configurations, allowing customized authentication rules for each subaccount while maintaining separate management of authentication values. This segmentation enables security customization without requiring complex inter-subaccount authentication relationships.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system establishes authentication rules and values for each subaccount in advance, during account setup. This preliminary configuration of authentication methods and values eliminates the need for complex real-time authentication management decisions, simplifying ongoing system operation.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If different authentication values are used for each subaccount, then loss of information is reduced upon compromise, but ease of operation decreases

Engineering Contradiction:
Improveexposure of authentication valuesVSAvoidauthentication process convenience
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent segments authentication values into separate, subaccount-specific credentials. Each subaccount has its own PIN and/or signature stored independently in the account database. This segmentation ensures that compromise of one subaccount's authentication values does not expose values for other subaccounts, limiting information loss while maintaining straightforward authentication operations.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10706420B2Method and system for fraud mitigation via account security
Publication Date: 2020.07.07 MASTERCARD INT INC
  • US10706420B2 patent drawing
  • US10706420B2 patent drawing
  • US10706420B2 patent drawing

AI summary

A method for customized authentication of a subaccount includes: storing an account profile, wherein the account profile includes a structured data set related to a transaction account including a plurality of subaccounts, each subaccount including an associated account number, authentication rules, and authentication values; receiving a transaction message related to a payment transaction, wherein the transaction message includes a transaction account number and authentication data; identifying a specific subaccount in the account profile where the included associated account number corresponds to the transaction account number; and authenticating the authentication data based on the authentication rules and the authentication values included in the identified specific subaccount.