Non-Native Account Processing via Intermediary Translation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing processing systems require entities to have accounts established within the system, leading to a closed system that hinders interoperability between different processing systems and prevents interactions between accounts from different systems.

Innovation Solution

The system receives an account identifier scheme from a third-party entity, assigns an entity identifier conforming to the native format, and modifies the application programming interface to recognize non-native account identifiers, enabling transactions involving non-native accounts to be processed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the processing system requires entities to have accounts established within the system, then system control and security are maintained, but interoperability with different processing systems is hindered and accounts from different systems cannot interact

Engineering Contradiction:

ImproveinteroperabilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer that translates between native account identifiers and non-native account identifiers. This intermediary mechanism enables accounts from different processing systems to interact without requiring them to be native to the same system, thereby improving interoperability while maintaining system architecture integrity

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The processing system implements a universal account identification framework that can handle both native and non-native account identifiers through a common interface. This multi-functional approach allows the system to process transactions from various account types and processing systems through unified processing logic

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If the processing system only processes native accounts, then processing simplicity is maintained, but service accessibility to external entities is limited

Engineering Contradiction:

Improveprocessing simplicityVSAvoidservice accessibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the account identification process into distinct components: native account handling and non-native account handling. By separating these functions while maintaining a unified processing interface, the system preserves processing simplicity for native accounts while adding capability to handle external accounts through the segmented non-native processing path

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12271902B2Non-native account processing

Publication Date: 2025.04.08 VISA INTERNATIONAL SERVICE ASSOCIATION

AI summary

A technique for enabling non-native accounts to be processed by a processing system may include receiving an account identifier scheme that is used by a third-party entity to provide access to accounts associated with the third-party entity, and assigning an entity identifier to the third-party entity in which the entity identifier conforms to a native format used by the processing system. An application programming interface can be modified to recognize account identifiers of the third-party entity. A transaction request can be received to execute a transaction in which the transaction request includes a resource provider identifier of the third-party entity and an account identifier of an account of the third-party entity. The entity identifier assigned to the third-party entity can be determined using the modified application programming interface, and the transaction can be processed using the entity identifier assigned to the third-party entity.