Mobile Wallet Alternate Currency Selection via Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Third-party mobile wallets are inflexible regarding user payment preferences, limiting the ability to easily select and utilize alternate payment currencies, such as paying with points, during transactions.
Innovation Solution
A method for mobile wallet payments that allows a mobile application to receive a selection of an alternate payment currency, decode payment payloads, and communicate this selection to a merchant host, enabling the use of alternate currencies like points through cryptographic data and Near-Field Communication (NFC) protocols, with authentication via SDK or API, and retrieval from customer profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party mobile wallets are used, then payment transactions can be conducted, but user payment preferences and alternate payment currency selections are not supported
Solution Approach 1:
The patent segments the payment data structure by separating payment token information from customer preference information. The payment token container holds transaction-specific data, while customer preferences (including alternate payment currency selections) are stored separately in customer profile data. This segmentation allows third-party wallets to maintain their existing transaction processing while adding preference flexibility without increasing overall system complexity.
Solution Approach 2:
The patent introduces a merchant host as an intermediary that receives both the payment token container from the mobile device and customer preference data, then combines them during transaction processing. The merchant host acts as a mediator that integrates the rigid third-party wallet system with flexible customer preferences, allowing alternate payment currencies to be applied without modifying the wallet application itself.
2Adaptability or versatility
If alternate payment currencies are supported, then user flexibility is improved, but transaction processing complexity increases
Solution Approach 1:
The patent implements preliminary action by storing customer preference data, including alternate payment currency selections, in advance in the customer profile before the actual transaction occurs. The mobile application retrieves these pre-stored preferences during the transaction and includes them in the payment request to the merchant host. This eliminates the need for complex real-time processing of preference selections during the transaction itself.
Solution Approach 2:
The patent creates a universal payment token container structure that can accommodate multiple types of payment instruments and alternate currencies through a standardized format. The same token container and communication protocol work for traditional payments, points-based payments, and other alternate currencies, allowing the system to handle diverse payment types without increasing processing complexity for each specific case.
3Adaptability or versatility
If payment preferences are stored and retrieved, then payment flexibility is improved, but data security requirements increase
Solution Approach 1:
The patent extracts sensitive payment preference data from the transaction processing flow and stores it separately in the customer profile database. Only non-sensitive payment token information is included in the mobile application's payment container, while the actual preference data (including alternate currency selections) remains securely stored on the server side and is retrieved only when needed for transaction processing, minimizing exposure of sensitive data.
Data Source
AI summary
Systems and methods for mobile wallet payments are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for conducting a payment using an electronic wallet may include: (1) a mobile application receiving a selection of an alternate payment currency; the mobile application receiving a payment payload from an issuer; the mobile application providing the selection of the alternate payment currency and an identifier to the issuer; and the mobile application providing the payment payload and the identifier to a merchant host. The merchant host may communicate the identifier to the issuer, and the issuer may identify selection of the alternate payment currency based on the identifier.


