Transaction Reversal Using Non-Sensitive Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction processing systems face security issues due to the exposure of sensitive account information, as account identifiers are often included in network communications, leading to potential security breaches.
Innovation Solution
A method where transactions are uniquely identified using a combination of a resource provider identifier and a transaction identifier, allowing for transaction reversals without exposing account information, and entities within the system store and communicate using these identifiers instead of sensitive account details.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If account information is included in network communications to identify transactions, then transaction identification is straightforward, but security risk increases due to potential exposure of sensitive data
Solution Approach 1:
The patent extracts the sensitive account information from the transaction communication process. Instead of using the full account identifier to identify transactions in communications, the system uses only a transaction identifier that does not contain sensitive account data. The account information is stored separately in secure databases, allowing transaction identification without exposing sensitive data in network communications.
Solution Approach 2:
The patent introduces an intermediary transaction identifier that mediates between the need for transaction identification and the need for security. This transaction identifier serves as a substitute that allows entities to communicate about transactions without directly exposing account information. The system uses this intermediary identifier in all communications while maintaining the ability to link back to the original account through secure stored records.
2Productivity
If multiple copies of account information are stored across databases for transaction tracking, then transaction processing is efficient, but security vulnerability increases due to multiple exposure points
Solution Approach 1:
The patent segments the information storage into two distinct parts: sensitive account information is stored in secure, limited-access databases, while transaction identifiers are stored in distributed databases across multiple entities. This segmentation allows efficient transaction processing through distributed storage of non-sensitive identifiers while protecting sensitive data by storing it in fewer, more secure locations.
Solution Approach 2:
The patent creates copies only of the non-sensitive transaction identifier portion of the account information and distributes these copies across multiple databases for efficient transaction tracking. The sensitive account information is not copied but rather referenced through the transaction identifiers, reducing the number of exposure points while maintaining processing efficiency.
3Measurement precision
If resource providers use centralized transaction identification, then transaction tracking is accurate, but system complexity and communication overhead increase
Solution Approach 1:
The patent merges the transaction identification functionality into the existing transaction authorization process. The same transaction identifier that is generated during authorization is used for subsequent tracking and reversal operations, eliminating the need for separate identification mechanisms and reducing overall system complexity while maintaining accurate transaction tracking.
Data Source
AI summary
A method is disclosed for enabling transaction reversal processes without utilizing sensitive information. Instead of being identified by sensitive information, the transaction associated with a reversal can be identified by a transaction identifier that is generated by a resource provider.