Test Data
All test cases are stored in Excel sheets. So does card data, key
data, validation data and authorization rules. Other sources are
possible.
Connections
Easy UI configuration, stored in JSON format in javascript file,
easy version control.
Messages
Easy to configure via UI, but also via javascript JSON editing
directly, so easy to deliver, store and massively update.
Business logic
javascript is key here. We use it to user menus for transactions,
build transaction data, call core features and of course, handle
message contents. The user can see all its work.
Authorization logic
Configurable authorization rules and validation are available in
Excel, but more logic is built into javascript authorization, like
when to do cryptogram checks and PIN validation, or when to
override default response codes
neaPay Core
The power of our simulator comes from its script engine, with
support for connections, message building and formatting, its look
and feel are the UI which makes it all easy, but its heart is the
controller which manages it all.
The UI
It is responsible to make it all pleasant for you to configure
connections, messages and fields.
The Engine
It is responsible for running the scripts and do the processing.
The Controller
handles the connections, provides and handles data to and from the
script engine and UI, as well as files, databases or TCP/IP.
Get a quote and a live demo