ISO8583 Authorization
Payments Host

Pre-screening authorization
EMV and PIN verification
Card verification

Easy to start, fast to process, infinite scaling, Microservices containers

Scale in any cloud, premise, Kubernetes, orchestration

PIN MAC EMV

Security as standard, custom security easy to set up

PrePay cards, acces, fuel cards, gift cards, shopping and food cards

ISO8583 Payments Authorization Host


Request Live Demo     Details     Docs     Download    

 
Encryption and Cryptography for PIN, EMV, MAC Session

  Authorization and full security check for Cards

  Multi-connection, multi-format, ISO8583, SWIFT, ISO20022

  Configurable authorization rules with override

  Validation of limits, amounts, cards; Balance updates

  Built-in HSM: EMV, PIN, MAC, session and key exchanges

  Compatible with Base24, Postilion, Alaric

  Integrated with Message Converter and Real-Time Feed Analytics

Light and powerful, Cloud-ready

Small core with scriptable engine, easy to deploy to any cloud

Configurable format: ISO8583, ISO20022, JSON, SQL, XML

Authorization rules in scripts, ready for version control

With database and/or cached files, light and configurable

Standard ISO8583 handling, default switching rules based on BIN, amount, processing code

Cloud ready to deploy

Go to list of features

 

Features List

Customer support options

 

Support Options

Technical Architecture overview

 

Architecture

Documentation, Get started guide

 

Documentation

Payments Host for Small and Medium Business

A Host for any acquiring protocol: ISO8583, TLV, CSV, XML, JSON

Handle any switch, member bank or Institution with no code changes

Easy to integrate with HSMs, Fraud, other banks

Switch, route, log, convert on the fly any payments

Built to be Flexible, Customizable and Reliable

Customizable business logic with flexible configurable rules

A great Host for cards, balances, validation EMV, PIN, balance

Forward ISO8583 messages or settlement files to Interchanges

Incoming ISO8583 messages to custom debit systems, card management or Dispute Management

Features of the ISO8583 Authorization Host


any payments formats

any connection type

any message standard

scalable multi-threaded

all configurable

Deploy

no installation

unpack and run

platform independent

 

Run

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

 

Analytics

console output

log to files as any message

generate XML, HTML logs

superb HTML reports, graphs

 

Maintenance

version control configuration

several configuration streams possible

in-house business logic updates

no delivery dependency

 

Connectivity

files, any encoding, even binary

TCP , Web Services, HTTP

CSV files storage

databases

API, PSD2

 

Messages

XML, JSON, ISO8583, ISO20022, SWIFT, TLV, CSV, SQL in the box

fully configurable

crazy flexible: insert ISO8583 in XML

crazy powerful: send ISO8583 to file

crazy conversion: ISO8583-XML-SQL

 

Cryptography

EMV, PIN, MAC, in the box

several cryptogram methods

several PIN block methods

any encryption standard

Receive transactions, process and respond.
Iso8583, XML, JSON, fixed data, extracts.

Based on the neaPay core Engine, with authorization scripts for cards, balance, limits and rules check, the neaPay Host has unrivalled speed for limited-resource servers. It runs on any platform where you have Java, and reads JavaScript authorization scripts that specify the logic to authorize transactions.

Use cards and message configuration from any input source, starting from all databases compatible with Java, including custom binary databases like HP NSK Enscribe and even just flat files. Configure simple authorization rules in spreadsheets or use complex logic or formatting in authorizations scripts.
Do not worry about speed, all file-related configuration is loaded to memory, so it is memory-to-memory fast.

How will my project start?

For cautious customers, we have the easy sequence.
First, we set up the interface according to the specifications.
First we run something very easy, with just a few fields. No RRN, no STAN, no PIN and EMV. Something easy to check connectivity and message parsing.
Then we can start enabling more complex message handling, checks, EMV, dynamic data and encryption. It is all built in, but we can activate independently
Once all message-related functionality is confirmed, we can start working on the Authorization rules.

How do we authorize

Simplest form of authorization is done via generic rules, based on prefixes, amounts, and generic matching.
A call to the database, or to another system, is be done to check and retrieve local data. Do not worry if you have some strange binary data structures, we can match anything
Further on, we can call on business logic to calculate EMV data, MAC or HSM calls.
You have another host or fraud system? We can send a message to that one too, no matter what kind of message it is.
If required, an update of balance or card status can be sent to another system, or just send to a logging system.
Local logging and Analytics are set up for real-time overview of the system.

So, what if it does not work?

Well, we promise it will. There has not been a single interface that we encountered which we could not implement. Also, we come up with a very cautious approach which will be tailored in such a way that you have nothing to loose.

And what if we want to do a big fast implementation?

Big&fast implementations involve a lot of risk, which we assess, share, and agree upon, in advance. Usually such projects require more people, more effort and more cost, so tell us about it.


Big or small, Authorization host systems can be set up for almost any system and requirements. starting from small simulated environments

Example authorization host setups

Simple Simulated host
is usually used for members of your institution to test against a server that is always available for their testing, in case you do not want to buy another license of an expensive host system.

Small real Host
is very similar to the one above, but you can use certain features of the real system, like cards data, key data, real HSMs, balances, with or without impacting the data.

Real Host
will be set up for normal authorization, with all features, interfaces and business logic

Project Phase delivery - Authorization Host

 

Pre Project

Analysis of requirements

Free Proof of concept gurantees solution functionality

Estimate and divide into phases

Finalcial and contractual arrangements for Project and Bau

Project

Fast Proof of Concept delivery for simple sceanrio

Immediate implementation of the most used scenarios

Iterative delivery of the agreed behaviour

Project go-live threshold acheived

Live acceptance

Fast Proof of Concept delivery for simple sceanrio

Immediate implementation of the most used scenarios

Iterative delivery of the agreed behaviour

Project go-live threshold acheived

 

Request a meeting to discuss a project

 

Long Term Support delivery - Authorization Host

Long term support ensures that the delivered product and customizations are up to date with changing requirements,
up to date with technlogical updates, and of course, benefit from the newest upgrades


Post-project scope

Remaining tasks can be scheduled during bau

Mandates, updates, extra requirements as in project

Iterative delivery of scope

During License Yearly subscription

Yearly License

Just license option with no support

Company license

No restrictions in instances or individuals

White label options available

Yearly supoort scope

Support requsts and incident management

Implementation of fixes, bugs, issues and extra features

Updates and upgrades to the newest product or features

Yearly schedule and release management

neaPay payments components


Payments Authorization

T

 

Input sources

1. Directly from a user, in a secure environment, via an interactive UI or command prompt

2. From a pre-defined configuration file

3. Via commands from a web interface

Output Data

1. Database data that is used by the Authorization system. This can be a file, a direct connection to the database, or other format

2. Card Data that needs to be sent to the card printing company, in a file or via a direct connection, like a database, web host, FTP

3. Other data, like pin printing or other cardholder information, which can be sent securely to another system ro just a file

Simple Cards Generation Logic

Download ISO8583 Authorization Cards Host

Watch this deployment video before you download

Watch this test run video before your first run

 

Only Logged in users can download.

Register Sign in

Java is required to run the product. Please follow this guide to Download/Check Java version

Authorization - articles


Choose the product you need



ISO8583 Converter

Convert ISO8583 to JSON XML SQL


ISO8583 Interface

ISO8583 Interface Handler


ISO20022 Converter

Convert ISO20022 to ISO8583 ...


ISO8583 Builder

Build ISO8583 from scratch


ISO8583 Switch

ISO8583 Router by criteria


ISO8583 Authorization

Authorize cards and ledger


Payments Acquirer

Acquiring host from devices


Cards Issuing

Generate and issue cards


ISO8583 Simulator

ISO8583 generic simulator


ISO20022 Simulator

ISO20022 generic simulator


POS Simulator

POS protocols simulator


Web Api Simulator

Web API tester Performance

 

Get a free quote, Ask for details
Get help

Contact us

Try the software yourself
Download

Download software

Read Documentation and Start guides

Documentation

Online Tools Overview

Online Tools