Trusted Internal Interface for Payment Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current payment devices require remote back-end server processing for interactions between payment applications and value-add applications, leading to inefficiencies and delays in transaction processing.
Innovation Solution
A system and method enabling direct communication and data transfer between payment applications and value-add applications within a payment device, using APIs or interfaces to reduce the need for remote processing, allowing for local data exchange and secure transfer between payment and value-add applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If remote back-end server processing is used for interactions between payment applications and value-add applications, then security and centralized control are maintained, but transaction processing efficiency deteriorates and delays occur
Solution Approach 1:
The patent segments the payment device into multiple independent application modules (payment application, value-add applications) that can operate autonomously. Each application resides in separate memory areas with defined interfaces, allowing local processing without constant remote server intervention. This segmentation enables efficient local data exchange while maintaining centralized security controls through the payment terminal's secure element.
Solution Approach 2:
The patent introduces a payment terminal as an intermediary device that hosts multiple applications and facilitates local communication between them. The terminal acts as a mediator that enables direct data exchange between payment and value-add applications without requiring remote server involvement for every interaction, thereby reducing processing time while maintaining security through the terminal's controlled environment.
2Reliability
If multiple remote data processing operations are required to complete a transaction, then centralized control and security are maintained, but device complexity and processing overhead increase
Solution Approach 1:
The patent merges multiple applications (payment application, loyalty applications, transit applications, etc.) into a single payment device, allowing them to coexist and interact locally. This consolidation reduces the need for multiple separate remote processing operations while maintaining centralized security through the payment terminal's secure element and controlled access mechanisms.
Solution Approach 2:
The payment device is designed with universal functionality to host multiple types of applications simultaneously. The device can perform payment transactions, loyalty program operations, transit fare collection, and other value-added services all within a single platform, reducing overall system complexity while maintaining centralized control through standardized security protocols.
3Reliability
If applications in payment devices are kept independent, then security and modularity are maintained, but data exchange efficiency deteriorates requiring remote processing
Solution Approach 1:
The patent implements a nested structure where value-add applications are contained within the payment device alongside the payment application, with each having its own memory space and execution environment. This nesting allows secure independent operation of each application while enabling efficient local data exchange through defined interfaces and shared access to the payment terminal's resources, eliminating the need for remote processing.
Data Source
AI summary
An interface and device architecture for a payment device. An interface between a payment application installed in a payment device and one or more value-add applications (such as loyalty programs, transit applications, etc.) that are also installed in the payment device. The API or interface design permits communications and data transfer between the payment application and one or more value-add applications. This reduces (and in some cases may prevent) the need for back-end server processing of data that may be relevant to both a payment transaction and to a function of the value-add application. Similarly, the same or another API or interface may enable communications and data transfer between a value-add application and the payment application.