Payment Processing System Update Code Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing payment processing systems face challenges in updating configuration settings without overwriting customer-specific customizations, particularly when sending configuration files, which can be cumbersome and complex, affecting both sophisticated and unsophisticated users.

Innovation Solution

Generating update code that includes validation or mapping code, configured to replace executable code files, allowing for customization while ensuring that customer-specific mappings are retained, and sent as a configuration code file to the payment processing system, enabling seamless integration and minimal impact on existing configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a configuration file is sent to update the payment processing system, then the system can be updated to conform with new standards, but customer-specific customizations (local mapping changes) may be overwritten or lost

Engineering Contradiction:

Improvesystem update conformityVSAvoidcustomer customization retention

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the update configuration file into distinct components: standard mapping definitions and customer-specific customization sections. This segmentation allows the system to apply updates to standard configurations while preserving customer-specific modifications, preventing overwriting of local changes.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary processing layer that compares the incoming update configuration with existing customer customizations. This intermediary mechanism identifies conflicts and resolves them by merging standard updates with customer-specific changes, ensuring both conformity and customization retention.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If a configuration file is sent to update the system, then new payment standards can be implemented, but the update process becomes cumbersome and complex for users

Engineering Contradiction:

Improvestandard complianceVSAvoidupdate process simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service functionality where the payment processing system automatically detects, processes, and integrates configuration updates without requiring manual user intervention. The system autonomously handles conflict resolution between standard updates and customer customizations, simplifying the update process for users.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-processing the update configuration file to identify applicable changes and potential conflicts before applying updates. This preliminary analysis prepares the system for seamless integration, reducing complexity and user burden during the actual update process.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10503488B2Updating a payment processing system to conform with a standard

Publication Date: 2019.12.10 NCR VOYIX CORP

AI summary

Examples of a system and method for updating a payment processing system to conform with a standard are generally described. A method may include generating an update code configured to replace or be inserted into an executable code file. The method may include sending the update code to a payment processing system for implementation in the payment processing system. The update code may include validation code or mapping code. The payment processing system may include validation rules or mapping rules.