Integrate banking ISO8583 transactions with Web interfaces, Databases, Mobile
and handle in an easy, friendly format
Make HTTP POST or GET requests from EFT financial messages
Database records easy to manipulate, interpret and analyze
Microservices or standalone server, logging, reporting
TCP/IP to HTTP Web services, or any API CSV, binary files
Delivered as Commercial off the shelf solution or as integrated framework
We handle binary complex ISO8583 data
You handle
user-friendly JSON payments
or any server can be used to process converted JSON
in case the web host is down
with a HSM or built-in
Technical run of an ISO8583 conversion to JSON REST API in under 2 minutes with ISO8583 simulator Acquirer and web Host simulator (JSON host)
Configure message mapping and automatic formatting to convert ISO8583 fields in data for web and back into ISO8583
Pack ISO8583 fields in a JSON, XML, or any custom body you want
All Mapping and business logic is controllable via JavaScript, so any small changes can be made on the spot
Achieve high performance, NON-STOP availability, easy maintenance by deploying in containers
By default you get a JSON of the ISO8583 data to play with. From here on, it is up to your imagination what to do with it.
Architecture simplified diagram
Easy convert from ISO8583 to another ISO8583 message
Convert ISO8583 authorizations to clearing records
Convert any EFT, either XML, fixed format, ISO8583, CSV
Connect your Web services to clearing files and online payments
Online ISO8583 message to Visa, MasterCard, Amex, etc.
Your proprietary format to settlement for Switches
Custom POS, ATM, ISO8583 messages, even XML or fixed formats
HTTP XML Bill presentments to TCP ISO8583 and flat settlement
Incoming ISO8583 messages to custom debit systems, card management or Dispute Management
Configure the Inbound custom ISO8583 format as a JSON message
Configuration of the Outbound converted ISO8583 message is done the same way
Set up the inbound/Acquiring connection as a server with the format defined above
Set-up the outbound/Issuer connection as a client with the other format
Customize parsing and conversion in javascript files
The acquired transaction Comes from the predefined inbound (Acquirer) server
The converter uses the configured iso8583 definition to parse the message
The converter receives the JSON message for applying business logic (user-defined JavaScript)
Once formatted, the transaction is given back to the neapay Core for sending
The core uses the Outbound (Issuer) JSON definition to pack the message and send it to the Issuer connection
Any number of connections can be defined
Any number of messages and message types can be used
Easily integrate financial messages parsing with XML entries, csv, database or any ISO8583 format.
Convert your ISO8583 messages and integrate host with switches, fraud systems with warehousing and Card systems;
Or, convert financial messages to database entries for logging also!
Since you are at it, why not generate some web content with some statistics?
Also convert and forward the message to another ISO8583 format for the fraud system;
Do not forget to generate a clearing file. The same mechanism applies.
Because we define all connections and all messages in scripts, they are all easy to change. Easy to customize and fast to deploy, for inbound and outbound.
We also implement the parsing of messages in scripts, so those are also easy to change. You can have field-by-filed parsing of define a generic behaviour for parsing all fields. All in scripts.
Need something specific? New features are added all the time to our product, so ask us about what you need.
The bank uses a processing company that runs BASE24 classic or Base24-eps to process transactions, and the processor sends all transactions to the bank as HISO93
The Bank needs to convert these messages to its own legacy Host systems
The Converter receives all incoming traffic and convert each of them to ISO8583 Host custom format
The Converter converts all responses back to Base24 HISO93
neaPay Switch Router can be used to send messages to a database or web host as well
neaPay The Converter can be used to generate clearing files
The bank acquires all ISO8583 payments of ATM and POS through a partner Acquirer, and receive transactions for final approval.
The Bank chooses neaPay's ISO8583 Converter to interface with the online Web system (as example);
neaPay Payments Switch sends all transactions to the host and to neaPay Message Converter
neaPay ISO8583 to JSON Converter receives all incoming traffic and converts it all to JSON
The neaPay Converter makes HTTP POST requests with the JSON body above
If the WEB API responds to the POST call, the converter can notify the Router, otherwise another part;
In case of no response, the Converter can log the request to a database, and retry later.
The bank uses a processing company that runs Postilion to process transactions, and the processor sends all transactions to the bank as PostBridge Messages
The Bank needs to convert these messages to its own Warehouse or Oracle Database processing system
neaPay Converter receives all incoming traffic and convert each of them to SQL and JSON
then converts all responses back to Postilion and auto populate responses
neaPay Switch Router can be used to send messages to a BLOB Warehouse as JSON
Features
no installation
unpack and run
platform independent
very simple User Interface
server mode with no-UI
move to local, test mode
high TPS, low impact
small footprint
all memory run
no database required
Console / container output
Integrated Analytics service
Log to files any message
TXT CSV XML HTML logs
HTML reports service
Version control software
Siple Archive delivery or GIT
Configuration GIT or DB
In-house business logic updates
No delivery dependency
Files binary ASCII EBCDIC
TCP/IP Web Services HTTP API
CSV files storage
Databases SQL NoSQL Oracle
API PSD2 Rest SOA
XML JSON ISO8583 ISO20022 SWIFT TLV CSV SQL
One instance or separate micorservices
Independently configurable
Flexible ISO8583 with XML CSV TLV
Powerful ISO8583 binary file
Conversion included ISO8583-XML-SQL-CSV
EMV PIN MAC
Configurable cryptogram methods
Configurable PIN block methods
TLS SHA and other encryption standards
On the felt side we have transactions coming in
The connection type is defined in .js files
Each connection is configurable independently
The script engine asks the connection to read data into a message
The connection reads information into a message
Message structures are defined independently from connections
Messages are also defined in .js files
The message is returned to the script engine
The script engine calls scripts to validate, alter information
Additional business logic can be applied via the scripts
We can then convert this information and create an output message
We take the way back and the script engine can send the new message to a connection
The connection actually sends the message out
All components work independently
Watch this deployment video before you download
Watch this test run video before your first run
Only Logged in users can download.
Register Sign inJava is required to run the product. Please follow this guide to Download/Check Java version
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!