Payment Processing Eligibility Checks for Owed Balance Points

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing payment processing systems fail to incentivize users to pay owed balances, such as credit card or loan balances, using accounts managed by the same financial entity, thereby missing opportunities for generating user points.

Innovation Solution

Implementing systems and methods that track eligibility conditions for users to generate user points by using eligible payment accounts to pay owed balances, managed by the same financial entity, through notifications, deep links, and user interfaces that facilitate efficient payment actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually navigate through payment processing systems to pay owed balances, then payment actions can be completed, but the number of clicks and selections required increases, reducing user efficiency and engagement

Engineering Contradiction:
Improvenumber of clicks and selections for payment actionsVSAvoiduser points accumulation rate
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system pre-identifies eligible payment accounts and owed balances before the user initiates a payment action. By performing eligibility checks and preparing payment options in advance, the system reduces the number of clicks and selections required during the actual payment process, while ensuring user points can be generated from qualifying transactions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically determines which payment accounts are eligible for generating user points and which owed balances qualify for such rewards. This self-service approach eliminates the need for users to manually check eligibility criteria or navigate through multiple selection screens, streamlining the payment process while maintaining points generation capabilities.

Inventive Principle:
Principle #25Self-service

2Loss of information

If the system provides comprehensive information about payment eligibility and user points, then user decision-making is improved, but the complexity of the user interface increases

Engineering Contradiction:
Improveinformation about payment eligibility and user pointsVSAvoiduser interface complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system provides detailed eligibility information and user points details only in the contexts where they are most relevant - specifically in notifications and at the point of payment action. Rather than displaying all information simultaneously throughout the interface, the system delivers targeted information locally where users need it, reducing overall interface complexity while maintaining comprehensive information availability.

Inventive Principle:
Principle #3Local quality

3Reliability

If the system tracks and monitors eligibility conditions for user points, then accurate rewards can be provided, but the processing overhead and system complexity increase

Engineering Contradiction:
Improveaccuracy of user points generationVSAvoidsystem processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs eligibility tracking and monitoring in advance, before payment actions are executed. By pre-establishing the rules for user points generation and continuously monitoring eligibility conditions, the system ensures accurate rewards can be provided without adding complex processing steps during the actual payment transaction.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250238833A1Generating User Points for Payment Actions in Payment Processing Systems
Publication Date: 2025.07.24 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC
  • US20250238833A1 patent drawing
  • US20250238833A1 patent drawing
  • US20250238833A1 patent drawing

AI summary

Disclosed are various embodiments for generating user points for payment actions applied to an owed balance from eligible payment accounts or source accounts associated with an entity. In some examples, a system comprises a client device that is configured to receive payment action data from a client device associated with a user identifier. A payment action is identified for an owed balance assigned to the user identifier. The payment action comprises a first identifier for a source account and a second identifier for the owed balance. A common attribute is identified between the first identifier and the second identifier. A payment amount for the payment action is determined to have been held for a threshold time period. The payment amount for the payment action is determined to have been cleared. A user point amount for the user identifier is generated.