Aggregated Payment Interface for Multiple Transaction Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network-based payment systems are cumbersome for users who have engaged in multiple purchase transactions, as they require manual processing of multiple payment obligations across different transaction systems.

Innovation Solution

A payment system that includes a transaction identification system to aggregate multiple purchase transactions and provide an interface for automatic payment processing, utilizing a payment engine to initiate payments for selected transactions upon user election.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual payment processing is used for multiple purchase transactions, then users can maintain control over each individual payment, but the payment process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvepayment process simplicityVSAvoidtime required for payment processing
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent combines multiple individual payment processing steps into a single aggregated payment interface. The system identifies multiple purchase transactions and consolidates them into one unified payment screen, allowing users to review and process all payments simultaneously rather than handling each transaction separately. This merging approach directly reduces the time required for payment processing while maintaining user control through the aggregated review interface.

Inventive Principle:
Principle #5Merging (Combining)

2Productivity

If automatic payment processing is implemented across multiple transactions, then payment efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvepayment processing efficiencyVSAvoidpayment system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary aggregation interface that sits between the user and the multiple transaction systems. This intermediary component identifies transactions across different systems, consolidates them into a unified view, and manages the payment coordination. By placing this intermediary layer, the system achieves automatic payment processing efficiency without requiring direct complex integration between all transaction systems, thus managing system complexity while improving productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If multiple transaction systems are integrated into a single payment interface, then user convenience is enhanced, but the difficulty of detecting and measuring transaction details increases

Engineering Contradiction:
Improveuser convenienceVSAvoidtransaction detail identification
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent segments the aggregated payment interface into distinct transaction listings, where each individual purchase transaction is separately identified and displayed within the unified interface. This segmentation allows the system to maintain user convenience through aggregation while simultaneously making transaction details easily detectable through clear separation and individual listing of each transaction's specifics.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7805366B2Method and system to facilitate payments to satisfy payment obligations resulting from purchase transactions
Publication Date: 2010.09.28 PAYPAL INC
  • US7805366B2 patent drawing
  • US7805366B2 patent drawing
  • US7805366B2 patent drawing

AI summary

A payment system includes a transaction identification system to identify a plurality of purchase transactions, established utilizing one or more transaction systems that impose a plurality of corresponding payment obligations on a particular user. An interface generator generates an aggregation interface that presents the plurality of purchase transactions to the first user. The plurality of purchase transactions are presented in conjunction with a payment option to initiate an automatic payment process with respect to at least a subset of the purchase transactions. A payment engine initiates the automatic payment process with respect to the first subset of plurality of purchase transactions upon election by the first user of the payment option.