Location-Agnostic Payment Code Caching for Offline Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile payment systems require multiple steps and a network connection to make payments at merchant locations, which can be inconvenient and unreliable, especially in areas with weak network coverage.
Innovation Solution
A location-agnostic payment code system that caches payment codes on the user's mobile device, allowing for one-time or limited-use payments without the need for constant network connectivity, with features like gesture-activated code generation and location-based accessibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a customer uses a mobile device to make payments at merchant locations, then payment functionality is enabled, but multiple steps and network connection requirements cause inconvenience and reduce reliability
Solution Approach 1:
The system pre-generates payment codes and caches them on the user's mobile device before actual payment is needed. This preliminary action allows the payment code to be ready for immediate use without requiring network connection at the moment of payment, thus simplifying the payment process and improving reliability in areas with weak network coverage.
Solution Approach 2:
The patent extracts the payment code from the network-dependent payment process and stores it locally on the user's device. By separating the payment code generation and storage from the real-time network connection requirement, the system enables payments without constant network connectivity, reducing operational complexity and improving reliability.
2Reliability
If payment codes are cached on the user's mobile device for offline use, then payment reliability is improved in areas with weak network coverage, but security risks increase due to potential device compromise
Solution Approach 1:
The system changes the parameters of the cached payment codes by implementing expiration times and usage limits. Payment codes are set to expire after a certain period or after a specific number of uses, transforming them from permanent, high-risk credentials to temporary, limited-use tokens. This reduces the impact of potential device compromise while maintaining offline payment capability.
Solution Approach 2:
The patent treats payment codes as disposable, short-living objects that are generated, used, and then invalidated. Each payment code has a limited lifespan and can only be used once or a limited number of times, similar to single-use tokens. This approach minimizes security risks associated with caching payment information while ensuring payment reliability offline.
3Reliability
If the system requires check-in to merchant location before obtaining payment code, then payment security is improved, but payment process complexity increases
Solution Approach 1:
The system performs the location verification and payment code generation as preliminary actions that are cached on the user's device. Once the user has checked in to a merchant location and obtained a payment code, the code is stored locally for immediate use without requiring repeated location verification or network connections, thus simplifying the actual payment process while maintaining security.
Solution Approach 2:
The patent introduces a payment code as an intermediary between the user's mobile device and the payment processing system. The payment code encapsulates the result of location verification and authorization, allowing the user to complete payments without repeatedly interacting with the complex check-in process or network infrastructure, thus reducing operational complexity while maintaining security.
Data Source
AI summary
A payment processing apparatus and a system or a method are provided that have a location-agnostic payment code, where the user does not have to check in to the merchant's location. Further, the reliance on the network connection is reduced by caching or storing payment codes at the user's mobile device. The payment codes may have expiration and may be used once. The payment codes may be revoked or canceled if the user's mobile device is compromised or stolen. In an embodiment, the payment codes may be generated and provided to the user's mobile device when the payment application at the user's mobile device is refreshed. For example, the payment application is refreshed based on user's payment history or payment habits. In another embodiment, the payment codes may be generated and provided to the user's mobile device when the user is within a predetermined distance from a merchant.