Offline Tap-to-Pay Validation Tokens for Secure Store-and-Forward
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge of securing sensitive data on user devices that are offline or disconnected from networks, where data exposure and tampering risks are heightened due to the inability to immediately transmit data to third-party systems, is addressed by implementing an offline processing session that encrypts and stores sensitive data locally, using a daemon to maintain data integrity and authenticity.
Innovation Solution
A user device enters an offline session, encrypts sensitive data, and stores it in a daemon inaccessible to the user, generating validation data that is later verified by a second computing system to generate a validation token, ensuring the integrity and authenticity of the data before transmission to a first computing system for processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If sensitive data is stored locally on user devices, then data availability and processing capability are improved, but data security and integrity are worsened due to increased exposure to tampering and compromise
Solution Approach 1:
The patent segments data into two categories: validation data (stored locally in the daemon for availability) and sensitive data (encrypted and transmitted to remote systems for security). This segmentation allows the system to maintain both local processing capability and remote security oversight.
Solution Approach 2:
The patent introduces a validation token as an intermediary mechanism. The token is generated by a remote system after validating data integrity and is then stored locally. This intermediary allows the system to verify data authenticity without permanently storing the sensitive data itself, thus maintaining both availability and security.
2Reliability
If sensitive data is transmitted immediately to third-party systems, then data security is improved, but processing delay and operational continuity are worsened when network connection is unavailable
Solution Approach 1:
The patent performs preliminary validation by generating a validation token before data transmission. The token is created in advance and stored locally, enabling the system to proceed with operations even when network connection is unavailable. This preliminary action ensures that validation can occur without immediate network dependency.
Solution Approach 2:
The system performs self-validation by using the validation token to verify data integrity locally without requiring continuous remote verification. The daemon uses the token to validate data exchanges independently, enabling the system to serve itself during offline periods without constant external intervention.
3Reliability
If validation data is stored in the background application, then data integrity is improved through centralized management, but user accessibility and data retrieval are worsened
Solution Approach 1:
The patent extracts validation data from the background application's centralized storage and makes it accessible through the validation token mechanism. The token is generated and stored in a way that allows the application to retrieve and use validation data when needed, separating the centralized integrity management from the accessibility requirement.
Data Source
AI summary
A method may include receiving, by an application executed on a user device, sensitive data associated with one or more data exchanges. The method may include generating, by a background application executed on the user device, validation data. The method may include retrieving, by the application executed on the user device, the validation data from the background application. The method may include transmitting, by the application executed on the user device, the validation data, and the sensitive data to a first computing system. The method may include receiving, by a second computing system, the validation data from the first computing system. The method may include generating, by the second computing system, the token, digitally signed by the second computing system. The method may include transmitting, by the second computing system, the token to the first computing system. The method may include receiving the token from the first computing system.