Universal Payment App for Non-Agreed Mobile Payment Codes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile payment systems require users to install multiple applications and obtain accounts for different mobile payment platforms, leading to complicated processes.

Innovation Solution

A universal payment application that can recognize and process non-agreed payment codes, providing interfaces for universal, agreed, and financial transaction links to facilitate mobile payments across various platforms without prior agreements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple mobile payment applications are installed for different platforms, then mobile payment compatibility is improved, but device complexity and operation complexity increase

Engineering Contradiction:
Improvemobile payment compatibilityVSAvoidapplication installation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal payment code that can be recognized and processed by multiple different mobile payment applications (e.g., Apple Pay, Google Pay, Samsung Pay). This single payment code replaces the need for multiple platform-specific payment codes, allowing one application to perform multiple payment functions across different platforms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The universal payment code acts as an intermediary element between the consumer's mobile device and various payment terminals. Instead of requiring direct compatibility between each payment application and each terminal, the universal payment code mediates the transaction, enabling payments through any supported terminal regardless of the specific payment platform.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple mobile payment applications are installed, then payment platform coverage is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvepayment platform coverageVSAvoidpayment operation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The universal payment code enables a single mobile payment application to function across multiple payment platforms, eliminating the need for users to switch between different applications or remember multiple payment methods. The user simply presents the same universal payment code for any transaction.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges multiple platform-specific payment codes into a single universal payment code. This consolidation allows users to manage all their payment needs through one code rather than maintaining separate codes for different platforms, significantly simplifying the user experience.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If stores apply for multiple mobile payment codes, then customer payment options are improved, but device complexity and time consumption increase

Engineering Contradiction:
Improvepayment option availabilityVSAvoidcode application time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The universal payment code allows stores to accept payments from multiple different mobile payment applications using a single code. This eliminates the need for stores to apply for and manage separate payment codes for each platform (Apple Pay, Google Pay, Samsung Pay, etc.), reducing both time and administrative complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP4654110A1Mobile payment method and system
Publication Date: 2025.11.26 LEADOT INNOVATION
  • EP4654110A1 patent drawingFigure 1
  • EP4654110A1 patent drawingFigure 2
  • EP4654110A1 patent drawingFigure 3

AI summary

A mobile payment method, which includes steps of: starting a universal payment application; retrieving a mobile payment code, wherein the mobile payment code is a non-agreed payment code, and the non-agreed payment code is generated not corresponding to the universal payment application, and is not recognizable by the universal payment application; and the universal payment application providing a payment interface based on the retrieved mobile payment code. When the mobile payment code is the non-agreed payment code, the payment interface at least includes a financial transaction trigger link and/or a universal payment link. A mobile payment system applying the mobile payment method is also provided.