Authorization Flow Interface for Merchant-Free Payment Path Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing authorization systems require integration into merchant websites, which is cumbersome, insecure, and costly, and often solicit customers for incentives after transactions, reducing effectiveness.

Innovation Solution

A standalone authorization flow management system that provides multiple interaction paths to users during transactions without integrating with merchant systems, allowing options like rewards points or equal payments through a pop-up window on the user's device, using a plug-in that operates independently of the merchant's software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If the authorization system integrates with merchant website code, then the authorization process can be implemented on the merchant website, but the implementation becomes cumbersome, burdensome, insecure, and costly

Engineering Contradiction:
Improveease of implementationVSAvoidintegration complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent extracts the authorization functionality from the merchant website integration and places it in a standalone authorization system. The system communicates with the merchant website through standardized APIs rather than requiring code integration, thereby eliminating the complex integration process while maintaining authorization capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary layer between the user and the merchant website. The authorization system acts as a mediator that handles authentication and authorization decisions independently, communicating with the merchant website through standardized interfaces without requiring direct integration of authorization logic into the merchant's codebase.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the authorization system solicits customers for incentives after transactions, then the system can offer rewards programs, but the customer must initiate a new interaction and the process is not effective

Engineering Contradiction:
Improveincentive program flexibilityVSAvoidinteraction time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by presenting authorization options and incentive programs to the customer during the authorization flow itself, before the transaction is completed. The system proactively offers rewards points, cashback, or other incentives as part of the authorization process, eliminating the need for customers to initiate separate interactions afterward.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If the authorization system provides multiple authorization options during the authorization event, then user experience is enhanced and processing efficiency is improved, but the system complexity increases

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamics by making the authorization interface adaptive and responsive. The system dynamically presents different authorization options based on real-time factors such as customer preferences, transaction amount, merchant capabilities, and available rewards programs. This dynamic approach allows the system to handle multiple authorization paths efficiently without requiring complex static infrastructure.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250356352A1Authorization flow management system
Publication Date: 2025.11.20 CITIBANK N A
  • US20250356352A1 patent drawing
  • US20250356352A1 patent drawing
  • US20250356352A1 patent drawing

AI summary

An authorization flow management system provides multiple authorization options to a user when conducting an authorization event. The system provides options to a user during an authorization event to select a preferred interaction path without integrating the process into a merchant system. The system receives a request from a merchant computing device to authorize an interaction with a user and provides instructions to a user computing device to open a window on a user interface to receive a security code and to display options to select from one of at least two interaction paths, such as paying with rewards points or with an equal payment plan. When the user communicates a response to the opened window that selects one of the interaction paths and the communicated code, the system conducts the interaction utilizing the selected interaction path and communicates an authorization for the interaction to the merchant computing device.