Express Credential Transaction System for Mobile Payments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile payment systems, the requirement for user authentication at wireless transit payment terminals introduces latency, which can cause delays in high-speed payment transactions, compromising the efficiency of mass transit systems, while ensuring security remains a challenge without authentication.
Innovation Solution
The system allows for the designation of an express stored value payment applet on a secure element of an electronic device, enabling contactless transactions with wireless payment terminals without manual input, while maintaining security through local and remote authentication mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user authentication is required at wireless payment terminals, then security is improved, but transaction speed deteriorates due to latency
Solution Approach 1:
The system segments payment applets into two categories: standard payment applets that require authentication and express payment applets that do not require authentication. This segmentation allows the system to maintain security for regular transactions while enabling fast transactions for express payment applets, thus resolving the contradiction between security and transaction speed.
Solution Approach 2:
Different authentication requirements are applied to different payment applets based on their designated functionality. Express payment applets are locally configured with the property of requiring no authentication, while standard payment applets maintain the property of requiring authentication. This local quality differentiation enables fast transactions for express applets while maintaining security for other applets.
2Speed
If user authentication is eliminated for fast transactions, then transaction speed is improved, but security deteriorates
Solution Approach 1:
The system creates a distinct segment of express payment applets that are specifically designated for fast, authentication-free transactions. This segmentation isolates the security risk to only those applets that are intentionally configured for express functionality, while other payment applets continue to require authentication, thus maintaining overall system security while enabling fast transactions.
Solution Approach 2:
Express payment applets are configured with self-service properties that allow them to execute transactions without requiring user authentication. The system automatically identifies and executes these pre-designated applets when activation conditions are met, eliminating the need for manual authentication while maintaining security through the pre-configured nature of these applets.
3Reliability
If manual input is required for payment transactions, then security is improved, but ease of operation deteriorates
Solution Approach 1:
Express payment applets are configured to execute automatically when their activation conditions are met, without requiring manual user input such as authentication codes or confirmation. The system self-determines whether to activate an express payment applet based on pre-configured conditions, providing both ease of operation for express transactions and security through the pre-configured nature of these applets.
Solution Approach 2:
The system performs preliminary configuration of express payment applets during setup, pre-defining which applets should execute without authentication and under what conditions. This preliminary action eliminates the need for manual input during actual transactions, improving ease of operation while maintaining security through the pre-established configuration.
4Productivity
If express payment applets are designated without authentication, then productivity is improved, but device complexity increases
Solution Approach 1:
The system uses a universal authentication mechanism that works for both standard and express payment applets. The same authentication module and transaction processing infrastructure handle both types of applets, with the only difference being the authentication requirement flag. This universality enables fast express transactions without significantly increasing system complexity, as the underlying architecture remains the same.
Data Source
AI summary
A device implementing an express credential transaction system includes at least one processor configured to receive an indication that a payment applet for a service provider has been provisioned on a secure element of the device with a first attribute indicating that the payment applet can be utilized for a transaction without authentication associated with the transaction. The processor is configured to set the first attribute of the payment applet to indicate that authentication is required to utilize the payment applet when another payment applet for the service provider provisioned on the secure element of the device has an attribute that indicates the other payment applet can be utilized for the transaction without user authentication. The at least one processor is configured to control whether the user authentication is requested when utilizing the payment applet or the other payment applet, respectively, in transactions.