Posted on 3rd Oct 2018 5359 views
Hello and welcome to this brief guide about the standard run modes available to the neaPay ISO8583 Acquirer simulator.
4 modes are available to the user out of the box:
In detail, about each one.
Is the most commonly used mode for running transactions, by selecting them from the list and running that test case only. This is the most used because it is designed for the test phase, or test cases preparation phase.
When you select this mode, the simulator will run the test case identified by: Scenario, Number, Description.
When you click the Send button, the simulator will take the line you selected from the Transactions List and match it against the Acquirer spreadsheet (exported csv file), and then will run the first test case that matches.
It is important that each test case configured in the Acquirer spreadsheet has a unique combination of Scenario, Number, Description. If you have several rows with the same key, it will run the first combination found.
This run mode is ideal for running tests for a very specific functionality, like a suite of EMV tests that tests each tag, or for MPOS - specific certification, or just a simplified sub-set or regression.
In order to run in this mode, just select a transaction from the Scenario you want to run, from the list of transactions UI.
This mode runs all test cases that have the same scenario number/ID as the selected transaction. If you have all test cases with the same scenario number/ID, then the simulator will run them all.
This mode is used when running automated regressions, it runs all the transactions from the list.
A regression pack for an ISO8583 implementation is usually estimated to have 500-1000 test cases that run one after another and test various functionalities, like amounts, accounts, limits, pin tries and so on.
Setting up a good regression pack may cost an initial investment, but it allows you to run an automatic regression every time you make a change, in less than 15 min.
This mode is used to run load tests at a steady, fixed and measured TPS (Transactions per Second) rate.
The simulator switches to core-only mode, like a Host, ignores human interaction, like a host, and focuses on running transactions as fast as possible. While doing so, it outputs the amount of time it has to spare in a second after sending the specified number of transactions.
In simple words, if you want to run 10 transactions per second, you set the TPS rate to 10, and the neaPay Core will send 10 cached transactions, measure how much time it took, for example 0.05 seconds, write to console the remaining time in a second, in this case 0.95 seconds, so you know how much more load you can do with your device. Up to around 1000 transactions per second is the tested limit for a low-end laptop. A good server can do many thousands.
Data for running the load test must be cached before. This is enabled in the Acquirer script, and what it does is store transactions that you are running manually in the RunOne or one of the other modes (if enabled).
BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP
Read smart card chip data with APDU commands ISO 7816
ISO8583 Response Codes for Transaction processing
ISO8583 Message Types for Transaction Processing
ISO8583 Processing Codes for Transaction Processing
Run the neaPay ISO8583 simulator
Deploy, run and generate with neaPay Card Data Generator
MCC Codes - Merchant Category Codes to use in ISO8583 Field 18
ISO8583 payments message format, programmers guide
ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52
ISO8583 Message Converter JSON and XML interface specification mapping
Cards and Banks Training
Support for the neaPay products: Authorization, Switch, Converter, Simulator, Issuer
Create a new test case in the neaPay ISO8583 simulator Video guide
Log Files in BASE24 classic
Deploy the neaPay ISO8583 simulator - video guide
BASE24 documentation to read
BASE24 classic vs BASE24-eps
Performance testing at 500, 1000 and 1500 TPS
BASE24 classic interview questions
EMV explained for programmers
ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2
Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer
ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3
Adding your own card to the Payments simulator to test your system
Card readers supported by neaPay payments simulator, CHIP and NFC
ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1
BASE24 classic screens examples explained
Enabling traces in the payments simulator
Altering test cases in Excel for the ISO8583 simulator
Changing fields definitions in the ISO8583 simulator and message converter
Load Test enabling and performance testing at 1TPS and 100TPS
Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment
Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression
Deploy the neaPay ISO8583 Payments converter in a test environment
ISO8583 ATM POS Crypto API integration with exchanges like Coinbase or Binance
Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide
How the fingerprint reader works in the ISO8583 payments simulator
Regression Testing in 1 click with instant Analytics and CSV report
BASE24-eps interview questions
Deploy the Payments Switch Router in a test environment
Java version for neapay products Simulator Converter Switch Authorization Cards Issuer
Deploy the neaPay HSM simulator in a test environment
BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples
Add extra custom fields to the ISO8583 simulator
BASE24 classic cards configuration tutorial with Examples
BASE24-EPS ACI DESKTOP tutorial - Getting started
PCI compliant with neapay switch
ISO8583 Message Converter to XML SQL CSV interface specification mapping
BASE24 classic prefix configuration tutorial CPF with examples
BASE24 classic tracing of transactions. Audits, configuration, enabling and opening
ACI BASE24 classic automatic extract configuration
BASE24 classic Institution configuration Tutorial with example
BASE24 classic balance file configuration PBF with example
First steps with BASE24 Classic
Getting started with using Prognosis for BASE24 and BASE24-eps
Trace configuration in neaPay Simulator, Converter, Switch, Authorization and Cards Issuer
POS simulator format SPDH HPDH Verifone and custom
Ready to start your next project with us? Give us a call or send us an email and we will get back to you as soon as possible!
Get a free quote, Ask for details, Get guidance
Download and Use the software yourself
Read Documentation and Start guides