Central Bill Network for Single-Login Payment Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Consumers face inefficiencies and negative experiences when paying multiple bills online, as they must navigate separate payment platforms and remember multiple login credentials for each biller entity.
Innovation Solution
A central payment processing network that manages bills through a single access point, using a central network to receive and process identification parameters, authenticate transactions, and facilitate actions like bill retrieval and modification without requiring separate logins for each biller.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If consumers navigate to separate payment platforms for each biller entity, then they can access and manage each bill, but the process becomes unwieldy and requires remembering multiple logon credentials
Solution Approach 1:
The patent combines multiple separate payment platforms into a single centralized payment platform. Consumers can now access and manage bills from multiple biller entities through one unified interface, eliminating the need to navigate to separate platforms and remember multiple credentials. The system merges the functionality of multiple bill document stores into a single accessible repository.
Solution Approach 2:
The centralized payment platform provides universal access to manage bills from any biller entity. A single platform performs multiple functions: storing bills from different entities, authenticating consumers, enabling bill viewing, and processing payments across various biller types. This multi-functional approach replaces the need for separate specialized platforms for each biller.
2Reliability
If consumers use separate bill document stores for each biller, then they can access electronic bill copies, but they must remember multiple account logon credentials
Solution Approach 1:
The patent merges multiple separate bill document stores into a single centralized storage system accessible through one platform. Consumers can retrieve electronic copies of bills from any biller entity through this unified interface, eliminating the need to access separate document stores and remember multiple credentials while maintaining reliable access to all bill information.
Solution Approach 2:
The centralized payment platform acts as an intermediary between consumers and multiple biller entities. It mediates access to bill information by maintaining a consolidated repository of bills from various entities and providing a single authentication mechanism. This intermediary role simplifies consumer access while ensuring reliable retrieval of bill documents.
3Adaptability or versatility
If consumers interact with multiple merchant platforms directly, then they can manage their bills, but the system complexity and number of access points increase
Solution Approach 1:
The centralized payment platform provides universal adaptability to manage bills from any number of merchant entities through a single interface. The system is designed to accommodate multiple biller types and entities while maintaining consistent functionality. Consumers can add and manage bills from various merchants without needing separate access points or interfaces for each entity.
Solution Approach 2:
The patent combines the need to interact with multiple merchant platforms into a single centralized interaction point. The system merges access to diverse biller entities through one unified platform, reducing the number of access points from multiple separate merchant platforms to a single centralized interface while maintaining the ability to manage all bills.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A method of bill management by a central network. The method comprising the steps of: receiving, from a first system, a first message comprising: a first identification parameter; and a second identification parameter; sending, to a second system, the first identification parameter and the second identification parameter; receiving, from the second system, a first request comprising the first identification parameter, the second identification parameter, and action request data; and performing an action based on the action request data.