Transaction Processing Using Global Unique Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The reliance on account identifiers for transaction processing in payment systems exposes consumers to risks of unauthorized access, fraud, and credit damage, as these identifiers are stored and used to distinguish transactions within the system.
Innovation Solution
Implementing a Globally Unique Identifier (GUID) associated with each transaction, which is unique within the payment processing system and independent of the account identifier, to secure authorization and remittance processes, ensuring that transactions are distinguished without relying on account identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If account identifiers are used to distinguish transactions, then transaction processing can be performed, but consumer security is compromised due to storage and transmission of sensitive account information
Solution Approach 1:
A GUID (Globally Unique Identifier) is introduced as an intermediary element that replaces the account identifier in transaction data. The GUID serves as a mediator that maintains transaction distinguishability without exposing sensitive account information. The system generates a GUID for each transaction, stores it with transaction details, and uses it throughout the authorization and clearing processes instead of the actual account number, thus eliminating fraud risk while preserving transaction processing reliability
Solution Approach 2:
The sensitive account identifier is extracted and removed from the transaction data stream. Instead of transmitting or storing the account number, the system extracts only the necessary transaction information and replaces the account identifier with a non-sensitive GUID. This extraction eliminates the harmful factor (exposure of account information) while maintaining the functional capability of transaction processing
2Ease of operation
If account identifiers are stored and transmitted, then transactions can be matched and cleared, but the system becomes vulnerable to unauthorized access and credit damage
Solution Approach 1:
The system uses a disposable GUID that is generated for each transaction and does not need to be stored long-term or reused. Unlike the permanent account identifier, the GUID is a temporary, single-use element that serves its purpose for matching and clearing the specific transaction then becomes obsolete. This disposable approach maintains transaction matching capability while eliminating the risk of unauthorized access to persistent sensitive data
3Productivity
If the system uses account identifiers for clearing and settlement, then payment routing is enabled, but consumer information security is compromised
Solution Approach 1:
Instead of using the original account identifier, the system creates a copy in the form of a GUID that replicates the functional role of the account number without containing sensitive information. The GUID copy enables all necessary operations (routing, matching, clearing, settlement) while the original sensitive account information remains protected and is never transmitted or stored in the transaction processing system
Data Source
AI summary
A Globally Unique IDentifier (GUID) is used to match an authorization request with an authorization response for a transaction between a merchant and a consumer upon an account within a payment processing system where the payment amount is unknown until after the merchant receives the authorization response that includes the GUID. After receiving the authorization response and when the payment amount is known, the merchant forms a transmission that has information for delivery to an issuer of the account. This information is sufficient for the issuer to forward the payment amount from the account to pay the merchant for the transaction. While including the GUID and the payment amount, the information does not include an identifier of the account.