Tokenized Data Exchange via Ephemeral Detokenize-Retokenize Flow
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Organizations face significant data security risks when sharing tokenized data due to the need to convert tokenized data back to plain text for transmission, as they maintain different tokenization algorithms, and this exposes data to insecure networks.
Innovation Solution
A third-party server uses temporary memory to detokenize and re-tokenize data without maintaining both tokenization schemas simultaneously, ensuring data privacy by wiping memory after each algorithm use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If tokenized data is converted back to plain text for transmission between organizations with different tokenization algorithms, then data exchange becomes possible, but data security is compromised during transmission
Solution Approach 1:
The patent introduces a third-party server as an intermediary that receives tokenized data from the sender, detokenizes it using the sender's algorithm, then re-tokenizes it using the recipient's algorithm. This mediator prevents direct exposure of plain data over networks while enabling compatibility between different tokenization schemes, thus resolving the contradiction between data exchange capability and data security
Solution Approach 2:
The patent segments the tokenization process into distinct phases: the sender's detokenization algorithm is applied first to convert tokenized data to plain data, then the third-party server's re-tokenization algorithm converts it to the recipient's token format. This segmentation allows each algorithm to operate independently and sequentially, preventing simultaneous exposure of both tokenization schemas while enabling data exchange
2Ease of operation
If a third-party server stores both detokenization and tokenization algorithms simultaneously, then data conversion is enabled, but both parties' privacy may be exposed
Solution Approach 1:
The third-party server performs the detokenization operation in advance, converting the sender's tokenized data to plain data before receiving the recipient's tokenization algorithm. This preliminary action ensures that the server never holds both algorithms simultaneously in memory, maintaining privacy protection while enabling the conversion operation
Solution Approach 2:
The server implements a periodic clearing mechanism where memory containing the detokenization algorithm is wiped after use, and only then is the tokenization algorithm loaded. This periodic action of loading and clearing algorithms ensures that both parties' privacy is maintained while the conversion capability remains functional
Data Source
AI summary
Systems, methods, and apparatuses are described for secure transfer of tokenized data from a sender to a recipient without disclosing tokenization schemas of either party. A computing device may receive a detokenization algorithm associated with a sender and tokenized data. The computing device may generate plain data by processing the first tokenized data using the detokenization algorithm. The computing device may clear memory, receive a tokenization algorithm associated with a recipient, and generate tokenized data by processing the plain data using the tokenization algorithm. The computing device may then send the tokenized data to the recipient.