Software Transaction Control Module for Contactless Payment Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current payment and access control systems require physical interaction with terminals, leading to ergonomic and security issues, especially for users in vehicles or with reduced mobility, and incur significant costs for providers due to hardware-based terminals.
Innovation Solution
A method allowing communicating objects to perform transactions without physical terminals by receiving requests from transaction control modules, reading identification data, and transmitting it for validation, enabling dynamic pairing and reducing the need for hardware-based devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If physical terminals are used for transactions, then transaction control and validation can be performed, but user convenience deteriorates due to the need for physical interaction
Solution Approach 1:
The patent replaces the mechanical/physical terminal system with a software-based transaction control module that runs on communicating objects like smartphones. The reader on the communicating object reads identification data from means of access (cards, badges) and transmits it to the software-based module for validation, eliminating the need for physical terminals while maintaining transaction control reliability.
Solution Approach 2:
The patent introduces an intermediary communication protocol and data transmission mechanism between the reader on the communicating object and the software-based transaction control module. This intermediary layer enables seamless interaction without physical terminals, allowing the system to maintain control functionality while improving user convenience through wireless or contactless communication.
2Productivity
If physical terminals are deployed, then transaction processing is enabled, but device complexity and cost increase due to hardware requirements
Solution Approach 1:
The patent extracts the transaction control functionality from physical terminals and relocates it to software-based modules that run on communicating objects. The hardware reader component is retained on the communicating object (which users already possess), while the complex terminal infrastructure is eliminated, reducing overall device complexity and deployment costs.
Solution Approach 2:
The patent makes the communicating object (smartphone, tablet) universal by equipping it with both a reader capability and software-based transaction control module. This single device can handle multiple transaction types (payment, access control, ticketing) without requiring separate physical terminals for each function, thereby reducing hardware complexity while maintaining productivity.
3Productivity
If physical terminals are used in public spaces, then transactions can be processed, but security deteriorates due to exposure to interception and hacking
Solution Approach 1:
The patent inverts the traditional architecture where the terminal is stationary and the user approaches it. Instead, the reader is on the user's communicating object and they approach the service provider's software-based module. This inversion allows the security-sensitive reading operation to occur on the user's secure device, while the validation happens in a controlled software environment, reducing exposure to public space security risks.
Solution Approach 2:
The patent creates a virtual copy of the terminal functionality within the software-based transaction control module on the communicating object. Rather than relying on physical terminals in public spaces, the system uses software-based validation that can operate securely in distributed environments, reducing the attack surface for interception and hacking while maintaining transaction processing capability.
Data Source
AI summary
A method for establishing a transaction using a communicating object in which the object receives a request containing data relating to the transaction from a device for providing a product or a service or from a transaction control module associated with the device. The object carries out the following: receiving, from the module or the device, a message asking whether a reader of a means for accessing a service for implementing the transaction is associated with the object; a reader being associated with the object, reading identification data of a means for accessing the service, using the reader; and transmitting the identification data to the module to validate the transaction.


