Mobile Carrier Payment Authentication via One-Time Token
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile payment processes are time-consuming and inconvenient due to the need for user authentication and additional input, such as credit card information, which slows down the payment processing time.
Innovation Solution
A mobile payment application that uses a one-time token generated by the service provider, sent to the user's mobile device, which communicates with the mobile carrier to process payments without requiring additional user input, allowing for quick and easy transactions by linking the payment to the user's mobile phone number.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional mobile payment processes require user authentication and additional input, then security is improved, but processing time increases and convenience deteriorates
Solution Approach 1:
The system performs preliminary authentication by linking the mobile device to the carrier account before the payment transaction. The carrier pre-approves the device identity, so when a payment occurs, authentication is already complete and no additional user input is needed during the transaction itself.
Solution Approach 2:
The mobile device automatically uses its own carrier account credentials to authenticate and process payments without requiring the user to manually enter authentication information. The device serves itself by leveraging the existing carrier relationship to complete the payment process automatically.
2Reliability
If traditional mobile payment processes require multiple steps of authentication and funding source selection, then security is improved, but ease of operation deteriorates
Solution Approach 1:
The system extracts and removes the authentication step from the payment process by using the carrier account linkage. Instead of requiring authentication during payment, the system extracts the authentication mechanism to the account setup phase, leaving the payment process clean and automatic.
Solution Approach 2:
The mobile device's carrier account serves multiple functions: it provides wireless communication services and also serves as the authentication and funding mechanism for payments. This multi-functionality eliminates the need for separate authentication and payment processes.
3Adaptability or versatility
If payment processing involves multiple providers and steps, then functionality is improved, but device complexity increases
Solution Approach 1:
The mobile carrier acts as an intermediary that simplifies the payment architecture. Instead of the device needing to directly manage complex interactions with multiple payment providers, the carrier mediates by using its existing infrastructure to handle authentication and payment processing.
Solution Approach 2:
The system merges the authentication function with the payment processing function by using the carrier account as both the identity verification mechanism and the funding source. This consolidation reduces the number of separate components and simplifies the overall system.
Data Source
AI summary
A user makes a purchase request through a merchant app on a mobile device, such as by selecting an item for purchase. A mobile SDK of a payment provider is installed in the merchant app. The payment request includes the phone number for the mobile device. The payment provider verifies the phone number of the user and requests approval of the payment from a mobile operator providing wireless communication services on the mobile device. If the request is approved, the payment is charged to the user mobile operator account. The user simply taps a button to select an item to purchase and selects another button to confirm the purchase. Once processing is done, the user is notified on the mobile device of a successful payment.