Mobile Wallet Token Authentication and QR Code Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for mobile transactions using mobile devices lack efficient authentication and integration methods for facilitating payments and fund transfers between users and merchants, often requiring cumbersome login credentials and manual account management.
Innovation Solution
A computer system that authenticates users for mobile wallet transactions using device and customer tokens, generating substitute card numbers for secure payment processing, and automatically provisioning accounts to the mobile wallet without manual entry, utilizing QR codes or other transmission methods for authentication and payment verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional authentication methods using full login credentials are used for mobile transactions, then security can be maintained, but user convenience and transaction speed deteriorate due to cumbersome manual entry requirements
Solution Approach 1:
The authentication system is segmented into multiple components: device tokens stored on the mobile device, customer tokens stored on the server, and QR code visual authentication. This segmentation allows the system to verify device identity and user identity separately, eliminating the need for manual credential entry while maintaining security.
Solution Approach 2:
The system uses QR codes as a visual copy or representation of authentication data. Instead of manually entering login credentials, users present a QR code generated on their mobile device, which contains encoded authentication information that can be scanned and verified by the merchant system.
2Productivity
If manual account provisioning is required for mobile wallet integration, then account security and verification can be ensured, but productivity and user experience deteriorate due to time-consuming setup processes
Solution Approach 1:
The system performs preliminary actions by pre-generating device tokens and customer tokens before actual transactions occur. During account provisioning, the system pre-establishes the association between device tokens and customer accounts, and pre-generates QR codes that encode this authentication data, enabling immediate use without additional setup time.
Solution Approach 2:
The mobile device autonomously generates and stores device tokens, and automatically creates QR codes for authentication. The system enables self-service account provisioning where users can independently complete wallet integration without manual verification steps, as the device itself manages token storage and presentation.
3Reliability
If substitute card numbers are generated for each transaction, then payment security is improved through tokenization, but device complexity increases due to additional token management requirements
Solution Approach 1:
The system introduces tokens as intermediary elements between the actual card data and the transaction processing system. Device tokens and customer tokens serve as mediators that represent the user's payment credentials without exposing the actual card information, enabling secure transactions while simplifying the management burden on the mobile device.
Data Source
AI summary
A computer system receives an indication from a user that the user wishes to perform a mobile wallet transaction to transfer funds to a recipient using a mobile device. The transaction is authenticated by the computer system. The authentication includes receiving login credentials manually entered by the user and determining that the login credentials match stored login credentials for the user. The authentication further includes determining that the mobile device has a device token stored thereon that matches a device token stored in a database of the computer system. The device token uniquely identifies the mobile device in the computer system. The authentication further includes determining that the mobile device has a customer token stored thereon that matches the customer token stored in the database. The customer token uniquely identifying the customer in the computer system. The computer system transmits the funds to the recipient responsive to the authenticating step.