API Wallet Integration for Automatic Cross-Platform Data Entry

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital wallet systems lack versatility in integrating various payment sources, requiring users to manually input multiple payment details, which is time-consuming and inefficient.

Innovation Solution

A computing system utilizing application programming interface (API) integration to facilitate seamless communication between digital platforms, enabling automatic data entry and integration of new payment sources into digital wallets through cross-platform communication events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual input of payment details is used to integrate payment sources, then payment sources can be integrated into digital wallets, but the process is time-consuming and inefficient

Engineering Contradiction:
Improvepayment integration speedVSAvoidtime for manual data entry
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing API integrations between the digital wallet platform and payment source entities. Payment source data is pre-formatted and made available through standardized interfaces, so that when a user wants to add a payment source, the information is already prepared and can be transferred automatically without manual input.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses an API intermediary layer that connects the digital wallet platform with external payment source entities. This intermediary automatically handles data exchange, authentication, and integration processes, eliminating the need for users to manually input payment details while ensuring secure and standardized communication between different systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple payment sources are integrated into digital wallets, then payment versatility is improved, but the complexity of integration processes increases

Engineering Contradiction:
Improvepayment source compatibilityVSAvoidintegration system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by creating a standardized API framework that can work with multiple different payment source entities through a common interface. The digital wallet platform is designed to handle various payment types (credit cards, debit cards, bank accounts) through unified integration mechanisms, allowing the system to work with any payment provider that adheres to the standardized protocol without requiring separate complex integration processes for each.

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

3Extent of automation

If API integration is implemented for cross-platform communication, then automatic data entry is enabled, but system integration complexity increases

Engineering Contradiction:
Improvedata entry automationVSAvoidAPI integration complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent implements self-service through automated authentication and data verification processes. When a user initiates payment source integration, the system automatically handles credential verification, data format validation, and integration configuration without requiring manual intervention or complex setup procedures. The API integration process is self-configuring, reducing the perceived complexity for users while maintaining robust automated functionality.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260037935A1Application programming interface integration
Publication Date: 2026.02.05 TRUIST BANK
  • US20260037935A1 patent drawing
  • US20260037935A1 patent drawing
  • US20260037935A1 patent drawing

AI summary

Systems and methods receive, via a user interface of a user device, at a hypertext document of a first digital platform of a first entity input(s) to link to a digital program of a second entity, the receiving triggering performing a cross-platform communication event via an API with the digital program of the second entity. A digital display of the digital program of the second digital platform is automatically provided, via the user interface, the providing facilitating data entry to the digital program of the second digital platform. It is determined that a user has completed the data entry to the digital program of the second digital platform, the determining triggering a redirection to the hypertext document of the first digital platform of the first entity, and the hypertext document of the first digital platform of the first entity is displayed, via the user interface.