Mobile Payment Architecture Secure Element Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile payment systems lack a secure and efficient architecture that can be implemented across various platforms, such as mobile phones and PDAs, to manage consumer payment accounts and transaction data while allowing for updates without compromising operational functions.
Innovation Solution
A mobile payment application architecture comprising functional modules, including a secure data storage element, mobile payment module, gateway authentication module, over-the-air communication module, process message module, and multi-access module, which enables secure management and updating of payment transactions on Java Card platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If payment transaction data is stored in secure memory within the mobile device, then security of consumer payment accounts is improved, but the system requires complex architecture with multiple functional modules increasing device complexity
Solution Approach 1:
The payment system is divided into distinct functional modules: a secure element containing payment application code and data, a host application layer for user interaction, and a communication interface for transaction processing. This segmentation isolates sensitive payment data in the secure element while allowing flexible updates to the host application, thereby maintaining security without requiring complete system redesign.
Solution Approach 2:
A gateway module acts as an intermediary between the secure element and external payment networks. This gateway handles authentication, data formatting, and communication protocols, shielding the secure element from direct exposure to external systems while enabling versatile payment transactions across different networks and terminals.
2Adaptability or versatility
If the payment application architecture supports multiple platforms (mobile phones, PDAs), then adaptability is improved, but implementing secure data storage and processing across various platforms increases device complexity
Solution Approach 1:
The secure element is designed with universal interfaces and standardized communication protocols that can be integrated into multiple device types including mobile phones, PDAs, and other portable computing devices. The payment application code stored in the secure element remains platform-agnostic, while platform-specific adaptations are handled at the host application layer, enabling wide compatibility without compromising security architecture.
3Adaptability or versatility
If the system allows updates to payment application code, then adaptability and ability to implement new services is improved, but security risks increase during update processes
Solution Approach 1:
Payment application code and data are pre-loaded into the secure element through a secure provisioning process before the device is activated. The secure element maintains read-only or protected write access for these critical components, preventing unauthorized modification while allowing controlled updates through authenticated channels. This preliminary secure installation ensures that core payment functionality remains tamper-proof even as the host application evolves.
4Ease of operation
If contactless payment functionality is implemented using RF technology, then ease of operation is improved, but security vulnerabilities may arise from wireless communication
Solution Approach 1:
The secure element serves as a trusted intermediary that manages all wireless communications for contactless payments. It implements encrypted communication channels and authentication protocols between the mobile device and payment terminals, ensuring that RF transmissions cannot be easily intercepted or spoofed. This intermediary approach enables convenient contactless operation while maintaining security through cryptographic protection of wireless data exchanges.
Data Source
AI summary
A system, apparatus, and method for conducting payment transactions using a mobile device. Embodiments of the invention are directed to an architecture or system design for the functional elements residing in a mobile device that may be used to conduct a payment transaction. The inventive architecture may be implemented as a set of functional modules resident in a secure element that is embedded or otherwise incorporated into the mobile device.