Recipient-Selectable Resource Transfers With Local PII and Bulk Modes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing resource transfer systems require complex setups, involve substantial recipient personal identifiable information (PII) storage, and are inefficient for ad hoc or non-bulk transfers, leading to increased computing and human resource consumption and unwanted tracking.

Innovation Solution

A system that allows senders to specify recipients and modes of transfer through customizable user interfaces on a computing device, utilizing trained machine learning models to suggest additional recipients and transfer modes, reducing the need for recipient personal information and system-initiated contact.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a third party transferor is used to facilitate resource transfers, then the sender plays little to no role in the transfer process, but the setup becomes complex and substantial recipient PII must be obtained and stored

Engineering Contradiction:
Improveease of transfer operationVSAvoidsetup complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the PII storage function from the transferor system and places it locally on the sender's device. The recipient PII is stored in a local database on the sender's computing device, eliminating the need for the transferor to obtain and store substantial amounts of recipient personal information while simplifying the setup process

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The sender's device autonomously manages recipient PII storage and transferor selection without requiring complex third-party setup. The device automatically retrieves recipient PII from local storage and selects transferors based on resource type and transfer mode, eliminating the need for complex manual configuration

Inventive Principle:
Principle #25Self-service

2Productivity

If traditional resource transfer mechanisms are used for ad hoc transfers, then only one recipient can be transferred at a time, but process efficiency is reduced and computing resources are consumed

Engineering Contradiction:
Improvetransfer efficiencyVSAvoidtime for individual transfers
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent merges multiple individual transfer operations into a single bulk transfer operation. The system allows senders to specify multiple recipients in one transaction and automatically selects an appropriate bulk transferor, enabling efficient batch processing of resources to multiple recipients simultaneously

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system dynamically adapts the transfer mechanism based on the number of recipients and resource type. When multiple recipients are specified, the system automatically transitions from individual transfer mode to bulk transfer mode, optimizing process efficiency based on the transfer scenario

Inventive Principle:
Principle #15Dynamics

3Reliability

If recipient verification is required for resource transfers, then transfer security is improved, but computing and human resources are consumed

Engineering Contradiction:
Improvetransfer securityVSAvoidtransfer processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs recipient verification in advance by storing recipient PII and transferor preferences locally on the sender's device. Recipient information including verification data is pre-collected and stored in a local database, allowing rapid transfer execution without real-time verification delays while maintaining security through local validation

Inventive Principle:
Principle #10Preliminary action

4Productivity

If bulk transfer arrangements are established with third parties, then recurring transfers are facilitated, but substantial recipient PII must be stored and tracking issues arise

Engineering Contradiction:
Improverecurring transfer efficiencyVSAvoidrecipient PII storage
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent extracts the PII storage function from the third party transferor and implements local storage on the sender's device. A local database stores recipient PII and transferor selections, eliminating the need for third parties to maintain substantial PII repositories while enabling efficient recurring transfers through pre-configured local data

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The sender's device acts as an intermediary that stores recipient PII locally and manages transferor selection. This local intermediary eliminates the need for third parties to store substantial PII while maintaining the ability to execute recurring transfers efficiently using pre-stored local information

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12572920B1Resource transfer to selectable recipients via selectable modes of transfer
Publication Date: 2026.03.10 THE HUNTINGTON NAT BANK
  • US12572920B1 patent drawing
  • US12572920B1 patent drawing
  • US12572920B1 patent drawing

AI summary

A system for facilitating transfer of a resource to a sender-selected recipient according to a sender-selected mode of resource transfer is disclosed. A group of selectable additional recipients of the resource may also be presented to the sender and one or more of the selectable additional recipients may be selected by the sender to receive the resource along with an initially specified recipient. The group of selectable additional recipients of the resource to be presented to the sender, and different modes of resource transfer from which the sender can select, may be determined in various ways, including by an output of discrete trained machine-learning models. Once a selection of a recipient(s) and a mode of resource transfer is received, a resource transfer command message can be generated and sent to a resource transfer computing system to initiate a transfer of the resource to the recipient(s).