Enterprise Payment Solutions Secure and Compliant PCI DSS / ISO8583

Payments Cards Issuing Host

Generate, export, process card data for printing

Card data for database, PIN, cryptography generation

BIN range configurable

Import data from Excel, database

API integration, SQL, nosql, JSON, CSV, TLV

Request Consultation Details

Card Issuing and Card data generation

Card Data generation

Issue your own prefixes, generate the data needed for card printing, card authorization and validation

Card Verification

Verify PIN, Verify EMV, exchange keys, perform session and MAC verification

Card limits and account balances

Verify balance online, keep accounts balances, verify, update and check other hosts

Card Authorization

Verify balance online, keep accounts balances, verify, update and check other hosts

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

Features List

F A Q

Architecture

Documentation

Use Cases

All Products

Need a custom payments solution? Ask here

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

Cards Issuing 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

neaPay payments components

Cards Generator

The Card Data generator is used together with other products to create all data that is necesary for the Authorization system.

The simplified card data generation logic is presented below. Additionally, any variation can be configured, like more input sources, say Databases, or more output sources, for example directly to a Host via HTTP or RCP/IP

Additional encryption can be added to any of the connections, like RSA, AES or 3DES. TLS 1.2 supported.

More functionality, like integration with third party software is easy to implement vis scripting

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

Tutorials 19995 views