VoIP Contact List Payment Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for transferring money between individuals, such as cash, checks, and bank transfers, are inconvenient and require additional authorization, especially for those already connected through VoIP communication systems, which have existing trust and authorization schemes.
Innovation Solution
A method and system that allows users to transfer payments directly through a VoIP communication system by displaying a contact list, retrieving and displaying payment information pages from a payment provider, and transmitting this information securely to facilitate payments between users, leveraging the existing authorization schemes within the VoIP system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional payment methods (cash, checks, bank transfers) are used, then payment security is maintained, but payment convenience and speed deteriorate due to additional authorization requirements and manual processes
Solution Approach 1:
The patent merges the communication system and payment system into a unified platform. The communication application directly integrates payment functionality, allowing users to initiate payments within the same interface where they communicate. This integration eliminates the need to switch between applications and reduces the steps required to complete a payment transaction.
Solution Approach 2:
The system performs preliminary actions by pre-establishing user identities and contact information within the communication system. Before a payment transaction occurs, the system has already verified user identities through the communication registration process and maintained contact lists. This preliminary setup eliminates the need for additional authorization steps during the actual payment process.
2Reliability
If traditional payment systems are used, then payment security is maintained through multiple authorization steps, but system complexity increases due to integration with external payment providers and additional authentication requirements
Solution Approach 1:
The communication system is designed with multi-functionality, serving both communication and payment purposes. The same user identity, contact list, and authentication mechanisms used for communication are leveraged for payment transactions. This universal approach eliminates the need for separate payment account management and reduces system complexity while maintaining security.
Solution Approach 2:
The system enables self-service by allowing users to initiate and complete payments directly through the communication application without requiring external payment provider interfaces or additional authentication systems. The communication system itself provides the payment facilitation functionality, reducing dependency on external complex systems.
3Ease of operation
If existing VoIP contact lists are used for payment initiation, then ease of operation improves by leveraging existing trust relationships, but the scope of functionality deteriorates as contact lists are currently limited to communication events only
Solution Approach 1:
The contact list is enhanced to serve multiple functions beyond just initiating communication events. The same contact list now supports both communication initiation and payment initiation. This multi-functional use of the contact list improves ease of operation while expanding versatility, allowing users to seamlessly transition between communication and payment actions with the same interface element.
Data Source
AI summary
In one embodiment, transferring payment between a first user and a second user of a communication system includes displaying a contact list in a user interface of a client executed at a user terminal of the first user, the contact list including the second user. The client retrieves and displays at least one page from a payment provider responsive to the first user selecting the second user from the contact list. The client transmits, to the payment provider, information related to the payment entered into the page by the first user, which causes the payment provider to transfer the payment from an account of the first user to an account of the second user.