Mobile Wallet Tokenized Account Balance Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for mobile device-based fund transfers and payments lack efficient and secure methods for facilitating transactions between users and merchants, particularly in integrating tokenized card systems for authentication and reward processing.
Innovation Solution
A computer system that accesses a database to retrieve account balance information, generates a screen display for users on their mobile devices, and enables transactions by transmitting funds using tokenized card numbers, which are validated through a network of servers and payment systems, including QR codes and NFC for authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional credit card systems are used for mobile payments, then transaction security is maintained through card networks, but device complexity and user operation convenience deteriorate due to manual card entry and authentication processes
Solution Approach 1:
The patent uses tokenized copies of card numbers instead of actual card numbers for mobile payments. The mobile device stores a tokenized version of the card number, which is then used for transactions. This copying approach maintains security while simplifying the user interface, as users only need to provide their mobile device and authentication credentials rather than manually entering card numbers.
Solution Approach 2:
The patent introduces a mobile device as an intermediary between the user and the payment system. The mobile device holds the tokenized card number and facilitates the transaction through wireless communication with the point-of-sale system. This intermediary approach eliminates the need for direct card insertion or manual entry, improving ease of operation while the server-side tokenization manages the system complexity.
2Ease of operation
If account balance information is displayed on mobile devices, then user accessibility and transaction visibility are improved, but security risks increase due to exposure of account information on personal devices
Solution Approach 1:
The patent displays tokenized account balance information on mobile devices rather than actual card numbers or sensitive account details. The mobile device receives and displays tokenized versions of account information, which are sufficient for the user to see balances and manage accounts without exposing sensitive data. This copying approach maintains accessibility while minimizing security risks.
Solution Approach 2:
The patent implements different levels of information exposure based on the context and user needs. The mobile device displays sufficient account information for usability (balances, recent transactions) while the actual sensitive data remains protected on secure servers. The quality and sensitivity of displayed information varies based on the transaction context, authentication level, and device security state.
3Reliability
If tokenized card numbers are used for authentication, then transaction security is improved by protecting actual card numbers, but system complexity increases due to tokenization infrastructure requirements
Solution Approach 1:
The patent uses a server-based tokenization system as an intermediary that manages the complexity of token generation, storage, and validation. The mobile device simply stores and transmits tokenized card numbers without needing to implement complex tokenization logic locally. This intermediary approach shifts the computational complexity to a centralized secure system while keeping the mobile device simple and secure.
Solution Approach 2:
The patent creates and uses tokenized copies of card numbers that contain sufficient information for authentication and transaction processing without exposing the actual card numbers. These tokenized copies are generated by a secure system and used throughout the transaction process, maintaining security while the tokenization infrastructure manages the complexity through standardized protocols and server-side processing.
Data Source
AI summary
A computer system selects a default payment account based on at least one of (a) account balance information for a plurality of accounts of a user or (b) user preferences received from the user. The computer system receives a request for a transaction to transfer funds to a recipient and determines that the transaction causes the account balance of the default payment account to decrease below a user-defined threshold minimum value. The computer system generates a screen display including a link associated with a second account and provides the screen display to a mobile device of the user. The computer system receives a selection of the link associated with the second account, generates an optical code associated with the second account that incorporates a tokenized account number of the second account, and transmits the optical code to the mobile device for the transaction.