Tokenized Refund Authentication for Secure Transaction Reversal
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction systems face challenges in managing secure transactions and reversals, particularly in environments where sensitive client data needs protection, and there are concerns about fraud, regulatory compliance, and efficient data management across multiple merchants and lenders.
Innovation Solution
Implementing a tokenized account number system that keeps sensitive client data separate from merchant systems, using a shared authentication structure for both transactions and reversals, and enabling batch processing with a parent merchant account for efficient refund settlement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sensitive client data is kept separate from merchant systems using tokenization, then data security is improved, but transaction reversal complexity increases
Solution Approach 1:
The patent introduces an account security system as an intermediary between merchant systems and client data. This mediator holds and manages tokenized account numbers, allowing merchants to process transactions and reversals without direct access to sensitive client information. The intermediary resolves the contradiction by enabling transaction reversal functionality while maintaining data security through tokenization.
2Productivity
If batch processing with parent merchant account is used, then processing efficiency is improved, but authentication structure complexity increases
Solution Approach 1:
The patent merges multiple child merchant accounts under a single parent merchant account for batch processing operations. This consolidation allows multiple transactions to be processed together in a single batch, improving efficiency. The parent account serves as a unified authentication structure that simplifies the overall system while enabling efficient batch operations across multiple merchant entities.
3Loss of energy
If shared authentication structure is used for transactions and reversals, then resource usage is reduced, but system complexity increases
Solution Approach 1:
The patent implements a universal authentication structure where the same account security system and authentication mechanisms serve both transaction authorization and transaction reversal functions. This multi-functional approach eliminates the need for separate authentication systems, reducing resource usage and eliminating redundancy while maintaining security across different operation types.
4Loss of information
If tokenized account numbers are used instead of actual account numbers, then client data privacy is improved, but transaction processing complexity increases
Solution Approach 1:
The patent extracts sensitive client information (actual account numbers) from the transaction processing system and stores it securely in an account security system. Tokenized account numbers are used in place of actual account numbers throughout the transaction process. This extraction removes sensitive data from the processing path, improving privacy while the tokenization mechanism handles the increased processing complexity.
Data Source
AI summary
Examples describe data security for communication systems. One example includes validating a merchant system using merchant data and generating a set of merchant credentials. The set of merchant credentials is then used in authentication to facilitate a secure transaction, which involves automatically generating transaction data with a tokenized client account number associated with the secure transaction. A refund request associated with the secure transaction is received with the set of merchant credentials that are used for automatically authenticating the merchant system. The example then involves accessing a database that includes the transaction data for automatically facilitating settlement of a refund payment using the authenticated merchant system and the transaction data.