User-Level Token Identity Verification via Payment Channels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current identity verification systems often require additional non-financial information, which can complicate processes and lack seamless integration with financial transactions, especially in online and mobile environments, where secure and efficient exchange of both financial and non-financial data is needed.
Innovation Solution
A computer-implemented method and system that generates a user-level token (ULT) associated with a user's profile, allowing non-financial data to be verified and integrated with financial transactions through existing payment channels, using contextual information to provide relevant non-financial data to entities, enhancing security and simplifying transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If additional non-financial information is required for identity verification, then verification completeness is improved, but process complexity increases
Solution Approach 1:
The patent combines non-financial data verification with existing financial transaction processing channels. The identity verification system integrates multiple data types (financial and non-financial) into a unified verification process that occurs through the same payment card network infrastructure, reducing overall process complexity while maintaining verification completeness.
Solution Approach 2:
The system creates a universal user-level profile that can serve multiple verification purposes across different contexts. The profile stores various non-financial data elements (membership numbers, frequent flier miles, age, etc.) that can be selectively retrieved based on the specific verification needs, allowing a single system to handle diverse verification requirements without increasing complexity.
2Adaptability or versatility
If non-financial data is integrated into identity verification, then data utility is improved, but information security requirements increase
Solution Approach 1:
The system applies different security and access control measures to different types of data within the user-level profile based on their sensitivity and usage requirements. Non-financial data elements are stored and retrieved with appropriate security controls matched to their specific nature, allowing high data utility while maintaining targeted security measures rather than applying uniform restrictive security across all data.
Solution Approach 2:
The patent introduces an intermediary identity verification computing system that mediates between the payment card network and various data sources. This intermediary securely manages the integration of non-financial data, controlling access and ensuring security requirements are met while still enabling broad data utility for verification purposes.
3Loss of information
If user-level profiles store multiple data types, then information completeness is improved, but data management complexity increases
Solution Approach 1:
The user-level profile is segmented into distinct data categories (personal identifying information, non-financial data, financial information) with structured organization. Each segment can be independently managed, retrieved, and updated based on specific verification needs, reducing data management complexity while maintaining overall information completeness.
Data Source
AI summary
A method includes verifying the identity of an individual. The method further includes receiving non-financial data from the individual and generating a user-level profile. The user-level profiles include the non-financial data received from the individual. The method further includes generating a user-level token unique to the individual. The user-level token is associated with the generated user-level profile. The method also includes provisioning the user-level token to a device associated with the individual. The method further includes receiving an identity verification request comprising the user-level token, wherein the identity verification request is structured as a financial transaction card-originated message, validating the user-level token, and analyzing a context of the received user-level token to determine a relevant non-financial data element included in the non-financial information within the user-level profile. The method also includes transmitting an identity verification approval including the relevant non-financial data element.