Credit/Debit cards numbers generator and validator

Run the neaPay ISO8583 simulator

Run your ISO8583 simulator from neaPay in 3 steps

Start server; > Start client; > Run Transaction; > Check results

ISO8583 payments message format, programmers guide

There is plenty of documentation about ISO8583 out there on Wikipedia, so making that again does not make sense. However, I want to have a different approach, more pragmatic and more programmatic.

ISO8583 Message Converter JSON and XML interface specification mapping

The specification of the proposed conversion of ISO8583 messages 

Check the article for screenshots and logs of a conversion from ISO8583 to JSON

Deploy the neaPay ISO8583 simulator - video guide

When you receive a delivery from neaPay for an iso8583 simulator, 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 simulator;

3: start server;

4: start client;

5: run transaction 

ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52

A list of ISO 4217 currency codes follows. Use these values to check or load values of data elements 49 and 51, and also others (like additional amounts)

Create a new test case in the neaPay ISO8583 simulator Video guide

You have successfully run demo transactions, it is time to make your own test cases. 
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. 

MCC Codes - Merchant Category Codes to use in ISO8583 Field 18

ATM MCC: 6011

This document contains lists of valid Merchant Category Codes (MCCs). MCCs are used to identify the type of business in which a merchant is engaged.

MCC Codes (or merchant category codes) are assigned to merchant accounts during the set up process and are used to differentiate between types of business & industries. Each industry has different transaction patterns and differing levels of risk (potential for fraud). MCC codes are used by issuing bank to determine if they will accept the transaction. 

Asking for defects support for the neaPay products: converter, switch, issuer, simulator

If you need help deploying, running, configuring, customizing the payments converter, switch, Issuer, simulator or any custom product we have delivered, you can count on our support.

Paid or free users, all are welcome to ask for support. Please follow the support guidelines.

Performance testing at 500, 1000 and 1500 TPS

Taking neaPay simulator to the limits of an instance. Doing 500, 1000 and 1500 transactions per second, on one instance/core. We can start as many as we want.

Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer

Everything is working fine in the test mode, with an Acquirer and a bank host both simulated by neaPay. You want to connect your Acquirer simulator to your own Host system. 
Just follow these simple steps to change connectivity settings and make an acquirer become a host. 

Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression

A test suit is composed of different scenarios which follow in a functional (or another) way in order to cover the full, or as much as possible, of the ISO8583 Interface implementation.
Scenario 001 - Network management
Scenario 002 - POS Purchase
Scenario 003 - POS other
Scenario 004 - ATM withdrawal

Card readers supported by neaPay payments simulator, CHIP and NFC

Examples of configuration of the simulator with Card Reader support. Devices supported: Gemalto and ACS

Regression Testing in 1 click with instant Analytics and CSV report

The neaPay Payments simulator is designed from the start to follow the life of a project, and therefore, after all testing has been completed, we need to turn over to BAU the easy to use, easy to assess, regression test. 1-click easy.

Load Test enabling and performance testing at 1TPS and 100TPS

neaPay simulator performance testing. Simulator is requiring 0.02 seconds to send 100 transactions, every second.

How to enable Load /Stress test in neaPay simulator and how fast it is at 500 TPS, with Acquirer and Issuer processing, and screen recording.

Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment

Once you have received and successfully deployed your ISO8583 converter from neaPay, deploy and run is easy

1:use/deploy java 8;

2:unpack delivered converter;

3:start converter;

4:start client and server simulators;

5:run transaction 

Adding your own card to the Payments simulator to test your system

Easy steps to add a new card or copy an existing card.

The ISO8583 simulator allows setup of any number or type of cards.

Changing fields definitions in the ISO8583 simulator and message converter

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.

How the fingerprint reader works in the ISO8583 payments simulator

Step by step guide to enable and disable fingerprint reading, enrollment and verification.

Enabling traces in the payments simulator

Enabling traces in the ISO8583 Payments Simulator, just like the ISO8583 message converter and the ISO8583 Host, is a call to the system core to write additional data. This will, most of the times, show raw data (binary data is dumped as hex) for better understanding what is going on, what data is actually being used.

Most importantly, enabling traces shows dumps of TCP traffic or actual data being written to files, queries do database and so on. This is to verify that you are sending the correct data.

Deploy the neaPay ISO8583 Payments converter in a test environment

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 

Altering test cases in Excel for the ISO8583 simulator

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.

Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide

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

ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3

In this scenario the web host is not responding.

The HTTP Server will receive the JSON and reply.

Then we stop the Http host and send the message again.

The message gets declined automatically as stand-in.

ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1

In this scenario we have 3 connected parties.

An ISO8583 simulator will build ISO8583 messages real-time.

An ISO8583 converter will process the ISO8583 messages.

A HTTP Server will receive the JSON and reply

ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2

The ISO8583 message flow, via TCP/IP, to the converter.

The Converter unpacks the ISO8583 message

The Converter creates , in this case, an ISO8583 response message.

The Converter then converts this ISO8583 message to JSON, XML, SQL.

We choose to send the JSON as POST to a web host.