Visa Acquirer Issuer Simulator

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 Simulator

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, CUP

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, ATM e-comm Simulator

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.

So easy to configure!

• All test data is in Excel spreadsheets!
• Card data is easy to configure and import in Excel!
• If you want to copy a transaction, just copy-paste a row in excel!
• A terminal is also a row in Excel!
• Define message validation fields in Excel also!
• Message definition in JSON messages with Graphical interface!
• Connections configuration also in JSON with Graphical interface!

Built to be customized!

• All test data is in Excel spreadsheets!
• Card data is easy to configure and import in Excel!
• If you want to copy a transaction, just copy-paste a row in excel!
• A terminal is also a row in Excel!
• Define message validation fields in Excel also!
• Message definition in JSON messages with Graphical interface!
• Connections configuration also in JSON with Graphical interface!

Any Bank simulator

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 use for beginners

• Run transactions from the Graphical interface with 1 click!
• Run automatic regressions from the Graphical interface with 1 click!
• Start a load test with 1 click also!
• Edit test data like amounts and card numbers in Excel!
• Edit messages and connections from the Graphical interface or JSON files
• Save logs in any format with a virtual printing function.
• If needed alter behaviour in house with javascript files!

Built to handle heavy customization

• Authorization message validation of fields and verification
• transaction validation of amounts and responses
• Business decisions based on test data, like amounts of filed presence!
• Full PIN validations, PIN block generation and validation.
• Full EMV support for all brands, validation and verification
• ARQC, ARPC generation and validation
• Issuer script generation
• Any ISO8583-based protocol supported!
• Many connections types: TCP/IP, files, Web Service, NSK Enscribe
• Singe or dual message systems, clearing

Suitable for Agile teams

• Anyone can make a copy of the repository and make changes
• Works with a common versioning system
• Can cope with different levels of skills in the team
• Senior testers and developers make the business changes
• Test engineers can make and run test cases
• Junior testers can run the tests and assess the results
• Even the cleaning lady can run a regression
• Real-time display of message building, parsing and validation!
• Various running modes selectable with 1 click: Single Test, Scenario, Regression, Load Test

Follows the project plan

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!

From beginning to the end

• Set it up for any POC by overwriting any field in the Interface
• Customize message formats, connection type and scripts in parallel with the development phase
• Prepare test cases in advance based on the design
• run the test in many modes
• Single test mode
• Test scenario mode
• Full regression mode
• Load test mode
• Prepare for BAU with automatic regressions
• Switch back to functional mode any time you want

Iso8583 simulator

Visa simulator

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 simulator

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 simulator

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.

Iso8583 simulator

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 simulator

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.

ATM simulator

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.

Regression Testing

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.

Automatic Regression Testing

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.

Performance Testing

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!