Use any container orchestration software to ensure redundancy, performance, service uptime
Leveraging microservices to have a lightning fast time to market
Details Ask for Demo
Buy a platform which has only the functionality you need. Save money, time and infra cost and buy what you use. No need to buy a product which you use only 5% of
On-premise or in the cloud, use the newest container technologies to go to production in record time
Ensure Service uptime by leveraging the newste and best cloud computing services, simple, easy and cheap
POC takes a few hours, a running system can be up in about a week. No need to plan it all in advance, Incremental implementation is possible
Separate containers for separate functionality
In-house customizations of business logic, message format, connections
Web services and clearing formats connected to ISO8583 interfaces
Powerful scalable core: Docker, Kubernetes, any cloud
Scripting authorization logic per container instance
Configurable routing rules per container
Easy scale each microservice
out of the box Docker support
all the functionality of the Authorization host
unpack and run deploy
test and then deploy
incremental and distributed functionality
high TPS, over 1000
integrated or separate service
log to files as any message
generate XML, HTML logs
superb HTML reports, graphs
version control configuration
several configuration streams possible
in-house business logic updates
no delivery dependency
files, any encoding, even binary
TCP , Web Services, HTTP
CSV files storage
XML, JSON, ISO8583, ISO20022, SWIFT, TLV, CSV, SQL in one instance or separate services
crazy flexible: insert ISO8583 in XML
crazy powerful: send ISO8583 to file
crazy conversion: ISO8583-XML-SQL
EMV, PIN, MAC, in the box
several cryptogram methods
several PIN block methods
any encryption standard
Switch with the standard ISO8583 based package
various POS protocols, fixed message or ISO0503 based
depending on the device handler, NCR, NDC, Diebold
simple fixed formats configurable, as well as XML or JSON
usually via some form of ISO8583 implementation, easy to configure
they usually send some implementation of ISO8583
standard HTTP web service with XML or JSON data
networks usually come via ISO8583, while devices may send any API form
simplified ISO8583 or customized messages, SQL to database checks
standard SWIFT or custom inter-bank, payments, clearing, cash
Any number of scripts for separate routing logic
All scripts pre-compiled and cached
The power of our Switch 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.
Acquiring from Visa can be easily Switchd by our neaPay engine. How does it work? Load the Visa scripts in our Switch engine, the Visa message format
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.
MasterCard Acquiring is just as easy. Load the BankNet scripts, as well as the messages
Point the Switch to your system and run transactions. One by one, in batches or in full it is all a matter of choice. All messages go out in parallel and can come back in any order.
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.
Acquiring or issuing, that is just an option.
A switch of switches is ideal when dealing with many formats. Route payment transactions based on any configurable criteria
POS and e-commerce transactions work just as easily. Load the scripts, or make changes to match your custom interfaces, and then run it in the cloud or local.
Each ATM vendor comes with a different format and it may be a little more complicated. To be honest, if your vendor provides a Switch 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.
If you need help deploying, running, configuring, customizing the payments converter, switch, Issuer, simulator or any custom product we have delivered, you can count on our support.
Paid or free users, all are welcome to ask for support. Please follow the support guidelines.
Deploy then neaPay Payments switch router to easily route transactions based on BIN/prefix, amount, merchant, originating or destination insytitution, node.
1. As a container orchestration with Docker-compose
2. As separate services managed as stand-alone.
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!