Virtual Payments Environment Simulation for Transaction Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current payment system testing lacks the ability to simulate actual transactional volumes and project future performance, making it difficult to identify faults and root causes of failures effectively.

Innovation Solution

A virtual payments environment is created using a user interface that allows users to configure scenarios with specific payment environment characteristics, including hardware components and transactional paths, utilizing activity engines and blockchains to model and process payment information, thereby generating performance data for analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If historical data is used for payment system testing, then testing can be performed with existing data, but the ability to simulate actual transactional volumes and project future performance is lost

Engineering Contradiction:
Improveability to simulate actual transactional volumesVSAvoidcomplexity of testing environment
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a virtual copy of the payment system environment that replicates real-world transaction flows, hardware components, and processing paths. This virtual environment allows testing with simulated transactional volumes that mirror actual usage patterns without requiring access to real payment data or live systems, thus achieving adaptability while maintaining manageable complexity through abstraction.

Inventive Principle:
Principle #26Copying

2Measurement precision

If real payment data is accessed for testing, then accurate performance evaluation is possible, but security and regulatory compliance challenges arise

Engineering Contradiction:
Improveaccuracy of performance evaluationVSAvoidsecurity and compliance assurance
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The virtual payment system environment acts as an intermediary layer between test evaluators and real payment systems. It generates synthetic transaction data that preserves the statistical characteristics and processing behaviors of real payments while eliminating security risks. This intermediary approach maintains measurement precision by accurately modeling real-world scenarios without requiring access to sensitive actual payment data.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Difficulty of detecting and measuring

If the payment system is tested under various scenarios, then potential faults can be identified, but the complexity of configuring and managing test scenarios increases

Engineering Contradiction:
Improveease of fault identificationVSAvoidcomplexity of scenario configuration
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent segments the payment system into distinct virtual components representing different hardware and processing stages (POS devices, payment gateways, processors, networks). Each segment can be independently configured and tested under specific scenarios. This segmentation allows systematic fault identification by isolating issues to particular components while simplifying scenario management through modular configuration of individual segments rather than managing monolithic complex test setups.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10698795B2Virtual payments environment
Publication Date: 2020.06.30 TOTAL SYST SERVICES
  • US10698795B2 patent drawing
  • US10698795B2 patent drawing
  • US10698795B2 patent drawing

AI summary

A virtual payments environment can be used to simulate and test performance of a payments system. A plurality of characteristics and settings can be used to generate and/or determine one or more scenarios associated with a payments environment. The one or more scenarios associated with the payments environment can comprise a plurality of activity engines that simulate real-word components of a payments environment. Payment information can be introduced to the one or more scenarios and activity engines can be used to test and/or verify the integrity of the payment information as it traverses a transactional path through the payments environment. Performance data associated with the payment information can be accessed and review in order to determine a number or successes and/or failures associated with processing the payment information as it transverses the payments environment.