Mobile Wallet Third-Party Service Integration via Intermediary Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile wallets face challenges in providing a secure, efficient, and integrated experience for consumers to utilize multiple services from various service providers, while also enabling targeted and consistent communication from service providers to consumers, due to security risks and fragmented user experiences.
Innovation Solution
The system integrates a mobile wallet with third-party services by authenticating service provider information, establishing a communication session, and invoking a servicing environment, allowing users to access and manage payment products, receive notifications, and interact with service provider websites or applications securely and efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mobile wallets integrate multiple service provider accounts and communication channels, then the user experience becomes more comprehensive and convenient, but the system complexity and security risks increase
Solution Approach 1:
The patent introduces a wallet server as an intermediary component that mediates between mobile devices and service provider systems. The wallet server manages authentication, stores service provider information, and coordinates communications, thereby reducing the complexity burden on individual mobile devices while enabling comprehensive service integration across multiple providers
Solution Approach 2:
The system is segmented into distinct functional components: mobile devices for user interaction, wallet servers for centralized management, and service provider systems for specific services. This segmentation allows each component to specialize in specific tasks, reducing overall system complexity while maintaining versatile service integration capabilities
2Adaptability or versatility
If mobile wallets store and process sensitive service provider information, then service integration functionality improves, but security vulnerabilities and exposure to exploitation increase
Solution Approach 1:
The wallet server acts as a secure intermediary that stores and manages sensitive service provider information centrally rather than on individual mobile devices. This centralization enhances security through dedicated security measures at the server level while still enabling comprehensive service integration functionality through controlled access
Solution Approach 2:
The system performs preliminary authentication and validation of service provider information before storing or processing it. The wallet server verifies service provider credentials and establishes secure communication channels in advance, preventing unauthorized access and reducing security vulnerabilities before they can be exploited
3Adaptability or versatility
If service providers use multiple different communication means with consumers, then service coverage is expanded, but the user experience becomes fragmented and inconsistent
Solution Approach 1:
The wallet client is designed as a universal interface that consolidates multiple communication channels (push notifications, emails, SMS, in-app messages) into a single unified application. This allows consumers to access all service provider communications through one consistent interface, maintaining ease of operation while expanding communication coverage across multiple providers and channels
Solution Approach 2:
The patent merges multiple disparate communication channels and service provider interfaces into a unified wallet application. By combining push notifications, emails, SMS, and in-app messages into a single consolidated interface, the system maintains consistent user experience while achieving broad communication coverage across multiple service providers
Data Source
AI summary
Systems, methods, and computer program products are provided for providing a third party service via a wallet client. Service provider information is received from a service provider and stored in a wallet client database. Based on the service provider information, a wallet client is authenticated with a service provider system, a communication session is established, and a servicing environment is invoked.


