Search content or go to documentation , tutorials

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.

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.

From BINs to brands, from POS terminals to the Bank, cards and card data is travelling from one place to another and everything is working in connection. This connected way of working is vital for your experience in the world of transaction processing. 

We can show you the way card information travels from the terminal to the Bank that issued it, how your balance works and how you find out how much money you have available to spend.

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.

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