Iso8583 simulator
You will love having the same simulator for all your connections:
Visa, MasterCard, Bank host, ATM, POS, e-commerce.
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!