Service-Hosted Payment Request for Messaging Channels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional digital wallet systems require a vendor's front-end application to run on the user's client device for payment transactions, limiting their functionality in communication channels that do not support such applications, such as chatbots or messaging platforms, where dynamic updates of payment amounts or shipping details are not possible.
Innovation Solution
A service-hosted payment request system that allows vendors to generate and cache payment requests with a digital wallet service, enabling users to interact with these requests via a messaging channel, allowing for dynamic updates and secure payment token generation without requiring the vendor's application to run on the client device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a vendor's front-end application runs on the user's client device, then dynamic updates of payment amounts and shipping details are possible, but the system cannot function in communication channels that do not support such applications (e.g., chatbots, messaging platforms)
Solution Approach 1:
The patent introduces a service-hosted payment request system that acts as an intermediary between the vendor and the digital wallet service. Instead of requiring the vendor's application to run on the client device, the system hosts the payment request service on the vendor's server, which generates and manages payment requests that can be accessed through various communication channels including chatbots and messaging platforms. This intermediary approach enables compatibility with channels that cannot host applications while maintaining dynamic update capabilities through server-side management.
2Adaptability or versatility
If the vendor's application runs locally on the client device, then direct communication between the digital wallet and vendor application is enabled, but the system loses functionality in channels like chatbots where applications cannot run
Solution Approach 1:
The patent extracts the payment request hosting functionality from the client device and relocates it to the vendor's server. By taking out the service-hosted payment request component from the local application environment and hosting it remotely, the system eliminates the requirement for vendor applications to run on client devices while maintaining full payment functionality through server-side request generation and management.
3Ease of operation
If static fund-transfer methods are used in communication channels without application support, then transactions can occur, but dynamic updates of payment amounts and shipping details are not possible
Solution Approach 1:
The patent implements preliminary action by having the vendor's server pre-generate and host payment requests with all possible payment amounts, shipping details, and transaction parameters before the user initiates a payment. The service-hosted payment request system prepares multiple potential transaction scenarios in advance, allowing the digital wallet to dynamically select and update payment details based on user choices without requiring real-time server communication during the payment flow.
Data Source
AI summary
Systems and methods are provided that enable a vendor to utilize a digital wallet service to complete an online transaction with a user via a messaging channel (e.g., a chat channel), in a scenario where the vendor does not have a front end application running on the user's client device (i.e., there is no mechanism for the vendor's web-based application, such as a bot, to communicate with a digital wallet application running on the user's device). An online digital wallet service generates and caches a payment request (which can be rendered at a later time by the digital wallet service for interaction with the user) which is requested by the vendor, and provides the vendor with a reference to the cached payment request. The vendor provides the reference to the user such that the user can access the payment request via the link.