Shared Payment Account for Voice-Activated Group Purchases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack the ability to facilitate shared payments for group purchases via voice-activated devices, leading to inefficiencies and inconvenience, as they do not allow for the creation of a single virtual account that can automatically apply payments from multiple user accounts.
Innovation Solution
A data controller computing device creates a shared payment account linked to primary and secondary user payment accounts, enabling a voice-controlled computing device to initiate transactions using a shared payment account identifier, which is applied proportionately across the linked accounts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single payment account system is used for group purchases, then the payment process is simple, but multiple users cannot share the cost automatically
Solution Approach 1:
The patent segments the payment system into multiple independent user accounts (primary user account and secondary user accounts) that are linked to a shared payment account. Each user's payment information is kept separate and secure, while the shared account enables group purchasing functionality. This segmentation allows cost-sharing among multiple users without requiring a completely new complex payment infrastructure.
Solution Approach 2:
The patent implements a nested account structure where individual user accounts are nested within a shared payment account hierarchy. The shared payment account contains references to multiple user accounts, creating a nested relationship that enables automatic cost allocation. When a purchase is made, the system navigates this nested structure to distribute charges proportionately across the underlying user accounts.
2Ease of operation
If individual account information is shared with merchants for group purchases, then payment can be processed, but security and privacy are compromised
Solution Approach 1:
The shared payment account acts as an intermediary layer between individual user accounts and the merchant. Instead of exposing individual user account information to the merchant, the system uses the shared account as a mediator that handles the transaction. The merchant only interacts with the shared account, while the underlying user account details remain protected and are only accessed by the respective users.
3Reliability
If manual tracking of reimbursements is used, then users can be reimbursed, but the process is time-consuming and error-prone
Solution Approach 1:
The system performs preliminary actions by pre-configuring the shared payment account with multiple user accounts and their respective payment methods before any group purchase occurs. This advance setup includes establishing the relationships between accounts and configuring automatic cost allocation rules. When a purchase is made, the system already has the framework in place to automatically distribute charges, eliminating the need for manual tracking and reconciliation afterward.
Solution Approach 2:
The system implements automated feedback mechanisms that provide real-time information about payment allocations to all users. After a transaction, the system automatically notifies each user of their portion of the charge and updates their account balances accordingly. This automated feedback loop eliminates manual communication and ensures all users have accurate, up-to-date information about their financial obligations.
4Ease of operation
If voice-activated devices are used for purchases, then convenience is increased, but shared payment functionality is not available
Solution Approach 1:
The patent extends the shared payment account functionality to work with voice-activated computing devices alongside traditional payment methods. The system is designed to be universal, supporting multiple interaction modalities (voice commands, mobile app, web interface) that all access the same shared account infrastructure. This allows users to initiate group purchases through voice commands while the backend processes the shared payment through the established account relationships.
Data Source
AI summary
A data controller computing device is configured to receive, from a voice-controlled (VC) computing device, a shared payment initialization request identifying a primary user payment account associated with the VC computing device. The DC computing device creates a shared payment account linked in a database to the primary user payment account. The DC computing device also receives secondary user information, and links in the database at least one secondary user payment account to the shared payment account. Additionally, the DC computing device transmits a shared payment account identifier to the VC computing device. The DC computing device receives, via a payment network, a transaction authorization request including the shared payment account identifier, a merchant identifier, and a transaction amount. The DC computing device applies respective portions of the transaction amount against each of the primary user account and the at least one secondary user payment account.


