Test Electronic Transaction Processing via Cryptogram Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for simulating mobile device transactions are limited, failing to accurately and holistically test various transaction parameters, leading to incomplete quality control and increased reliance on real-world deployments and consumer feedback, which can be burdensome and confusing.
Innovation Solution
A computer-implemented method and system for processing test electronic transactions that includes executing a mobile application API, generating transaction data with a cryptogram, and transmitting it to a web service API, which then formats and sends the data to a payment network according to interchange standards, enabling a more realistic and scalable test environment for electronic device-initiated transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing simulation models are used for testing mobile device transactions, then testing can be conducted in a controlled environment, but the simulation is limited to particular portions of the transaction process and particular transaction types, failing to accurately and holistically simulate mobile device transactions
Solution Approach 1:
The patent creates a universal test environment that can handle multiple transaction types (contactless, in-app, online) and various device configurations through a single integrated simulation system. The system uses standardized APIs and protocols that work across different transaction scenarios, eliminating the need for separate simulation models for each transaction type.
Solution Approach 2:
The patent segments the transaction testing process into distinct modular components: device simulation layer, application layer, network layer, and payment network layer. Each layer can be independently configured and tested, allowing comprehensive coverage of transaction parameters while maintaining system manageability.
2Adaptability or versatility
If architects attempt to anticipate and simulate each significant contributing factor across nearly limitless combinations of transaction parameters, then testing coverage may be improved, but the complexity of the simulation model increases and the simulations are never perfect or complete
Solution Approach 1:
The patent introduces intermediary components including proxy servers, mock APIs, and standardized data formats that mediate between the test environment and the payment network. These intermediaries handle the complexity of parameter variations by providing standardized interfaces, allowing architects to focus on test scenarios rather than implementing every possible parameter combination.
Solution Approach 2:
The system enables dynamic parameter configuration where transaction parameters can be adjusted through standardized interfaces without modifying the core simulation model. This allows comprehensive testing of parameter combinations while maintaining a manageable base model that doesn't need to explicitly account for every possible variation.
3Adaptability or versatility
If quality control relies on real-world deployment, trial-and-error and consumer feedback, then testing can cover all transaction scenarios, but it involves increased burden on consumers to identify bugs and errors and may lead to confusion regarding the technical deficiencies
Solution Approach 1:
The patent implements preliminary automated testing of transaction scenarios in the simulation environment before real-world deployment. Common error conditions, edge cases, and failure scenarios are pre-configured in the test system, allowing bugs to be identified and resolved before consumers encounter them in production environments.
Data Source
AI summary
A computer-implemented method for processing test financial transactions that includes executing a mobile application API at an electronic device and receiving a command to initiate a transaction at the mobile application API, the command including transaction data. A payment application is executed at the electronic device to generate additional transaction data comprising a cryptogram based at least in part on the transaction data. The cryptogram and a corresponding post transaction command are transmitted. A web service API executed at a web service server receives the cryptogram and the corresponding post transaction command. A transaction request including at least some of the transaction data is generated at the web service API, according to interchange standards of a payment network, and transmitted to the payment network.


