Mobile Payment via Third-Party Server Tokenization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile payment methods require the installation of a payment application (APP) on a mobile device to facilitate transactions, limiting flexibility and convenience, especially when payments need to be made between devices without a payment APP installed.
Innovation Solution
A method and system that allows mobile payment between devices by sending payment information, including a unique identifier and account details, to a third-party server, enabling transactions even when the first mobile device lacks a payment APP, using device authentication and token generation for secure processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a payment APP is installed on a mobile device to enable mobile payment, then payment functionality is achieved, but device complexity and installation requirements increase
Solution Approach 1:
The patent introduces a server as an intermediary that stores account information and processes payment requests. Instead of requiring the mobile device to have payment APP installed, the server acts as a mediator between the mobile device and the payment system, handling authentication and transaction processing remotely.
Solution Approach 2:
The patent extracts the payment processing functionality from the mobile device itself and relocates it to a remote server. The mobile device only needs to communicate payment requests, while the server handles the complex authentication, account verification, and transaction processing, thereby reducing device complexity.
2Adaptability or versatility
If payment processing is centralized on a server, then payment can be made without payment APP on first device, but system complexity increases
Solution Approach 1:
The server is designed to handle multiple functions including authentication, account information storage, payment request processing, and transaction execution. This multi-functional design consolidates what would otherwise require separate systems, reducing overall system complexity while enabling versatile payment capabilities.
3Reliability
If account information is stored and processed on a third-party server, then security is improved, but data transmission requirements increase
Solution Approach 1:
The server stores copies of account information and uses these copies for processing payment requests. When a payment request is received, the server retrieves the relevant account information copy, verifies it, and processes the transaction without requiring the original device to have the payment APP or sensitive data.
Data Source
AI summary
The present specification relates to a mobile payment method, device, and system. One example method includes enabling, by the payee device, a device authorization function using a third-party server; receiving, by the payee device, identity authentication information from a payor device, wherein the identity authentication information includes an identifier of the payor device, and wherein the payor device does not have a payment application (APP) installed; forwarding, by the payee device, the received identity authentication information to the third-party server; receiving, by the payee device, token information from the third-party server, wherein the token information corresponds to the identifier; receiving, by the payee device, a payment request from the payor device, wherein the payment request includes the identifier of the payor device and the generated token; and sending, by the payee device, payment information including the generated token and the to the third-party server for verification.