Terminal Data Exchange via User-Mediated Tokenized Payment Options
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data exchange systems require terminal devices to be preconfigured with third-party service provider information, leading to computational complexity and data security vulnerabilities, especially when offering non-currency payment options.
Innovation Solution
User devices communicate with a server device to obtain and confirm data exchange options directly from third-party service providers, transmitting tokenized data to terminal devices without revealing sensitive information, thus avoiding the need for terminal devices to integrate third-party service provider information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If terminal devices are preconfigured with third-party service provider information to enable alternative data exchange options, then data exchange versatility is improved, but device complexity and data security vulnerabilities increase
Solution Approach 1:
The patent introduces a user device as an intermediary between the terminal device and third-party service providers. The user device obtains alternative data exchange options from third-party service providers and communicates with the terminal device without requiring the terminal device to be preconfigured with third-party information. This mediator approach allows the terminal device to maintain simplicity while enabling versatile data exchange options through the user device's coordination with the server device.
Solution Approach 2:
The patent segments the data exchange process into separate functional components: the user device handles obtaining and confirming alternative data exchange options from third-party service providers, while the terminal device focuses on executing the data exchange using provided options. This segmentation allows each component to have specialized functionality without requiring comprehensive knowledge of all third-party service providers, thereby reducing terminal device complexity.
2Adaptability or versatility
If terminal devices integrate third-party service provider information to provide alternative payment options, then service functionality is improved, but data security vulnerabilities increase
Solution Approach 1:
The user device serves as a security intermediary by obtaining alternative data exchange options from third-party service providers and communicating these options to the terminal device without exposing sensitive third-party information to the terminal device. The terminal device only receives the necessary options for executing data exchanges, maintaining security while enabling versatile payment options.
Solution Approach 2:
The patent extracts third-party service provider information from the terminal device and relocates it to the user device. The user device obtains and stores alternative data exchange options locally, eliminating the need for terminal devices to maintain complex configurations of third-party service provider information, thereby reducing security vulnerabilities while preserving service functionality.
3Reliability
If user devices obtain data exchange options through server devices, then data security is improved, but communication overhead increases
Solution Approach 1:
The user device can pre-obtain alternative data exchange options from third-party service providers through the server device before the actual data exchange session. By performing this action in advance, the user device has the necessary options ready for quick execution during the data exchange, reducing real-time communication overhead while maintaining security through server-mediated option retrieval.
Data Source
AI summary
Techniques are disclosed for determining data exchange options during a data exchange session. An application executing on a user device can initiate a data exchange session with a terminal device and determine a data exchange account associated with a third party service provider. The application can then obtain, from a server device, a data exchange option corresponding to the data exchange account and provided by the third party service provider. The application can receive an indication that the data exchange option was selected and, responsive to the indication, transmit to the server device a confirmation request associated with the data exchange option. The application can then receive a confirmation that the data exchange option is approved by the third party service provider and responsive to the confirmation, transmit, to the terminal device within the data exchange session, a data cryptogram comprising information usable to identify the data exchange account.


