Freedom = free forever.
Performance = over 1000 TPS.
Start
your journey with us.
Download below or follow the documentation
NOT for commercial
use
Watch this test run video before your first run
For very small companies for POC ONLY , individuals and non-profit organizations
Simulates POS, ATM, VISA, MasterCard, with Full EMV support
Test POS devices, Bank Host, Clearing systems, anything
Customize yourself: you are free to alter all behavior and learn yourself
Not licensed for commercial use, may come with ads and limited functionality
222
Happy Clients
222
Hours Of Support
222
Successful Projects
222
Hard Workers
Acquiring from Visa can be easily simulated by our neaPay engine.
How does it work? Load the Visa scripts in our simulator engine,
the Visa message format, and do not forget the test cases. Make
sure you point to the IP and port you need and start firing away
those transactions like they came from Visa. Authorize in your
system and our scripts will wait for the response to validate.
Visa Issuer is loaded the same way, just use authorization scripts
for issuing, and select the connection type to be a server. The
scripts know what messages to wait for, process and respond. It is
the best way to test your system before going to certification with
Visa. You do not want to keep the certification open for too long.
MasterCard Acquiring is just as easy. Load the BankNet scripts, as well as the messages and test cases, point the simulator to your system and run transactions. One by one, in batches or in full regression mode, it is all a matter of choice. All messages go out in parallel and can come back in any order. Just like a real authorization system.
MasterCard Issuing works with the same scripts, but uses the issuer part of them. The logic in the scripts decides that when you select the option to listen as a server.
Diners, Amex, JCB, China Union Pay? For the engine it is a matter
of loading a different script and formatting messages differently.
For the tester it is just a difference of test cases. And IP/port.
Acquiring or issuing, that is just an option.
Pre-certification tests with any switch will give you confidence
and you will have the flexibility to test beyond the certification
test cases.
If you are a switch , you can use our simulator
to certify member banks with your switch!
POS and e-commerce transactions work just as easily. Load the scripts, the transactions and start testing. Or make changes to match your custom interfaces, and then test as much as you want.
Each ATM vendor comes with a different format and it may be a little more complicated. To be honest, if your vendor provides a simulator for the ATM, use that one. If you need something heavily customized, then neaPay's engine will definitely be able to do it. Contact us and tell us what device you have, we might have the scripts for it already. If not, it is never too late to write a new one.
Simulates all your formats and all your connection types because it is all easy to define
We used Java, so it runs on any platform, and you can can disable the User Interface for server use.
Simulator for functional, regression and load testing, all in one, because we wanted only one tool
In-house Configurable Business logic, Message formats and Connections. Fully customizable.
Back-end systems, host, fraud, cards and balances systems
Web services, XML, csv, clearing and NSKL enscribe files support
TCP/IP, HTTP, flat files and SQL connections
And for all you can customize the business logic in-house
Easy to set up for Proof of Concept
Configure in parallel with the design and development phase
Thorough for all test phases: Unit test, System Test, Acceptance test
Resuse all testing scenarios in Automatic regressions
Reuse test cases for load tests!
Features
Windows, Mac, Linux, CICD
No installation
Unpack and run
Could/platform independent
Java / Javascript
Very simple User Interface
One-click Run of Test cases
One-click Run regression
High TPS (Transactions Per Second) Load test over 1000
Automatic validation
Automatic pass/fail assessment
Automatic comparison
ISO8583 validation for mandatory, Optional, Conditional
Console output to UI
Log to files as any message
Generate XML, HTML logs
Superb HTML reports, graphs
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
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 ISO8583-XML-SQL-CSV
EMV PIN MAC
EMV PIN MAC
Configurable cryptogram methods
Configurable PIN block methods
TLS SHA and other encryption standards
Acquiring from Visa can be easily simulated by our neaPay engine. How does it work? Load the Visa scripts in our simulator engine, the Visa message format, and do not forget the test cases. Make sure you point to the IP and port you need and start firing away those transactions like they came from Visa. Authorize in your system and our scripts will wait for the response to validate.
Visa Issuer is loaded the same way, just use authorization scripts for issuing, and select the connection type to be a server. The scripts know what messages to wait for, process and respond. It is the best way to test your system before going to certification with Visa. You do not want to keep the certification open for too long.
MasterCard Acquiring is just as easy. Load the BankNet scripts, as well as the messages and test cases, point the simulator to your system and run transactions. One by one, in batches or in full regression mode, it is all a matter of choice. All messages go out in parallel and can come back in any order. Just like a real authorization system.
MasterCard Issuing works with the same scripts, but uses the issuer part of them. The logic in the scripts decides that when you select the option to listen as a server.
Diners, Amex, JCB, China Union Pay? For the engine it is a matter of loading a different script and formatting messages differently. For the tester it is just a difference of test cases. And IP/port. Acquiring or issuing, that is just an option.
Bank host interfacing starts with a standard Iso8583 script. Then we apply the customizations. Message fields are activated or deactivated via GUI, and data type and length is also visual. Add or remove fields as you please. Then add or remove those fields from the test cases. In the end, we need to check that those fields are loaded and populated, so we need to add script logic for them. A mini authorization system you might say it is, and you would be right. No wonder it can do so many things, if it is built the same way. Just more customizable.
POS and e-commerce transactions work just as easily. Load the scripts, the transactions and start testing. Or make changes to match your custom interfaces, and then test as much as you want.
Each ATM vendor comes with a different format and it may be a little more complicated. To be honest, if your vendor provides a simulator for the ATM, use that one. If you need something heavily customized, then NeaPay's engine will definitely be able to do it. Contact us and tell us what device you have, we might have the scripts for it already. If not, it is never too late to write a new one.
A new code release comes and you need to make sure your system did not lose any functionality. You want to check that limits are working just as fine as before, that the accounts are debited and usages are updated. Each of them. A good regression pack can detect whether your limits are working fine, your balances are fine, all your fields are formatted correctly, for each transaction type, and your transactions are approved or declined as before. With that peace of mind, you can proceed to test the enhancements. Our simulators are designed with a regression approach from the beginning, therefore, any new functionality can be easily added to the regression pack, so next time you apply changes, these enhancements will be tested as part of the regression. After a few years, you will have a nice regression pack of a few hundred or thousand transactions, which can be run in less than an hour to check the status of the system, any day or night. You want this, we know you do, and our simulator can do it very well.
We know that you need the functionality above and you know you want it executed as soon as possible. What is your estimate for running a complete regression for the system, that covers everything, with 1000 test cases? You may say a week, you may say maybe two, or you may dare to estimate 2 days. We say that takes an hour. Because that is the estimate we wanted in our test plans and we made the simulator that can do that. Once all is set up properly, click the Run and go for a coffee. When you come back, you have your answer.
Your system must do all the processing at very high speed, so we built a matching simulator, which can run just as fast. We believe that 60 transactions need to be run in 3 seconds, not 30. We hope you agree. So our simulator can run fast enough to be used for performance testing, even without caching features. We have in plan to add a caching feature, which can release hundreds of transactions per second, it will be here soon!
We have cards configured in our files, we have terminals, we have message fields definition, we have keys for encryption, and we have authorization logic. At a smaller scale, it behaves like an authorization system, and therefore it can be configured to do one or several of the tasks of the authorization system. So, what part do you need?
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 is
responsible to make it all pleasant for you to configure
connections, messages and fields.
The Engine 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.
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!
