BASE24 classic vs BASE24-eps

PCI compliant with neapay switch. Steps and procedure.

The payments converter has the capability to convert any payment messages to API requests to exchanges.

Integrate crypto payments or crypto purchase from within your system, ATM or Host for Bitcoin, Ether, and many other cryptocurencies.

Adding extra, custom fields to the ISO8583 simulator in 3 simple steps: Edit the spreadsheet and save, edit the message that reads the test data, alter the ISO8583 message.

Deploy then neaPay Payments switch router to easily route transactions based on BIN/prefix, amount, merchant, originating or destination insytitution, node.

1. As a container orchestration with Docker-compose

2. As separate services managed as stand-alone.

In this post we explain how to change individual fields settings so they match your specification. All configurable via GUI or by altering the configuration files directly.

Method 1.  Alter settings via UI (User Interface)

Method 2.  Alter settings via configuration files. This is great for versioning of settings.

4 modes are available to the user out of the box:

1. RunOne - runs only the selected Test Case
2. RunScenario - runs only the selected Scenario
3. RunAll - runs all test cases in the list
4. RunLoad - runs the core in Load mode

When you receive a delivery from neaPay for an iso8583 convertor, you will get 1 zip file. 

This step by step guide will guide you through the deployment process, which is as simple as using the software. 

1: use/deploy java 8;

2: unpack delivered convertor;

3: start server;

4: start client;

5: run transaction 

When you need to customize your own test case, you need to follow some simple steps all the time.
In order to obtain this, you need to alter test data in Excel, save your new test data, export for the simulator, restart simulator with new test cases.

Changing test cases with the neaPay ISO8583 simulator is really easy because you just need to work with Excel.