ISO8583 Conversion REST-API

What financial transactions to convert?

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 ISO8583 messages?

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

Payments conversion flow

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

Financial Transactions

Easily integrate financial messages other ISO8583 hosts, XML gateways, csv, database

Card File Updates

Integrate clearing, updates and refresh systems with live applications

Database financial records

Financial messages to database-based Transaction Processing systems

Webhooks, Web servers and Web Services integration

Custom clearing file based systems integration

Microservices & Containers

Separate Microservices make it easy to improve functionality, redeploy fast, and update separately

Managed Instances

Process Complex scenarios separate than high volume traffic.

Process transactions cheaper, smarter and a lot faster