Network requirements for a bank POS terminal: IP, ports, firewall
This guide describes the minimum network requirements for stable operation of a banking POS terminal together with Torgsoft software. It applies to local operation, remote access (RDP), and the use of terminal servers.
This guide involves changing the network settings of the terminal, router, firewall, and antivirus software, so it should be followed carefully and only if you understand how your connection scheme is built. Mistakes in IP addresses, port forwarding, or access rules can completely stop the operation of the banking terminal, cash register, or remote access to the server. Before making changes, we recommend recording the current network settings, and if access to the router, server, or security policies is restricted — contact your system administrator or technical support.
When you need to check the terminal's network settings
-
The terminal is connected via Ethernet or Wi-Fi (TCP/IP).
-
The cash register or database is running on a remote server (RDP).
-
After restarting the router or a power outage, the connection to the terminal disappears.
-
Cash register and terminal integration (ECR) is being used.
How to understand that the problem is in the network or access to the terminal
-
Messages «No connection to terminal» or «Device not found».
-
Card payment does not go through, and timeouts appear.
-
The terminal works locally, but does not respond from the server.
-
The connection disappears after each restart of network equipment.
-
«Error No. 3» appears or a receipt «CANCELED» is printed (especially with RDP connection via USB/COM).
Why Torgsoft cannot see the banking terminal
-
The terminal has a dynamic IP address — after reboot, the internal IP changes.
-
There is no external (white) static IP address on the store router — the server cannot initiate a connection to the terminal.
-
Ports are not open or not forwarded on the router or in the firewall.
-
Different subnets without VPN — the cash register and the terminal cannot «see» each other.
-
Ports are blocked or Torgsoft executable files are deleted/quarantined by antivirus software (Avast, Windows Defender, 360 Total Security).
How to configure the network for a banking terminal
1. Static IP address
-
Internal (LAN, mandatory). In the router settings, reserve an IP address for the terminal using DHCP reservation (binding the MAC address to the IP). An alternative is to set a static IP directly in the terminal menu (for example, for PAX or Verifone). Please note that after a full router reset to factory settings, this binding disappears.
-
External (Public / White IP). Required on the store side if the server initiates the connection to the terminal. If the internet works through a mobile 3G/4G router (for example, LifeCell, Kyivstar), the provider issues a «gray» (internal) IP address by default. Port forwarding will not work in this case, and the service «External static (white) IP address» must be ordered separately from the provider.
2. Port forwarding and protocols
Configure forwarding on the store router from the external port to the terminal's reserved internal IP. The settings depend on the protocol:
-
BPOS (PrivatBank, Oschadbank, etc.). The typical port is 2000. Sometimes the bank may switch operation to port 2100.
-
JSON (WebSocket). A local server is used (the file genericDriverJsonETH.exe or genericDriverJsonUSB.exe), which always runs on port 3000.
-
JSON (COM/TCP). Torgsoft connects directly to the terminal's IP address, usually using port 2000 or 2100.
-
PosApi (Verifone Sense/Alfa-Bank). The typical Ethernet connection port is 5001.
-
InpasEcrCom (MR Bank, PUMB, TAS, etc.). The protocol feature is that the terminal searches for the cash register, not the other way around. The terminal settings must contain the IP address of the computer (cash register), and the incoming port 5555 must be opened on the PC itself (router).
Several terminals in one network
A separate internal IP address is reserved for each terminal, and a separate external port is configured on the router (for example: external 2001 → to the internal IP of the first terminal (port 2000), external 2002 → to the internal IP of the second terminal (port 2000)).
3. Firewall and antivirus
On the computer or server with Torgsoft:
-
Create Inbound and Outbound rules in Windows Firewall to allow traffic over the TCP/UDP protocol.
-
Open the terminal ports (2000, 3000, 5555, etc.) and the ports required for the program itself: 1433, 1434 (SQL Server), 6001 (Torgsoft application server).
-
Allow RDP connections (by default TCP 3389 or a changed port).
-
Add the entire Torgsoft program folder and executable files (torgsoft.exe, TorgsoftLicenseService.exe) to antivirus exceptions (Avast, Defender, 360 Total Security), because they may mistakenly block services or move files to quarantine.
4. Bank network requirements
-
The cash register and the terminal must be in the same subnet.
-
If they are physically in different locations — be sure to use a VPN.
-
For stability, a wired connection (Ethernet) is recommended. Wi-Fi is allowed only if the signal is stable and the configuration is correct.
5. USB / COM and RDP (limitations)
-
When using a USB/COM connection through Remote Desktop (RDP), «Error No. 3» often appears or a receipt «CANCELED» is printed.
-
Banks do not guarantee correct operation in this setup.
-
Solution: for stable operation, the terminal should be switched to a network connection (TCP/IP) and you should contact the bank's support to configure the protocol (for example, BPOS Ethernet).
How to check that the terminal is accessible over the network
-
Ping: run ping <IP_terminal> — there should be a response from the device.
-
Port check: telnet <IP> <PORT> — checks whether the port is open and whether the connection is established without errors.
-
Bank utilities: always check the terminal operation independently of Torgsoft. For the BPOS, PosApi, SSIAxECR protocols, use the BankTerminalTest utility. For WebSocket — open http://localhost:3000/ in the browser, where the WEB interface «Generic PoS driver» should appear. For InpasEcrCom, use InpasEcrComTest.exe.
-
Test in Torgsoft: Settings → Parameters → Additional functions → Banking terminal → click «Get information about the banking terminal».
-
Payment test: perform a test payment for UAH 1 (or $0.01) and then process a refund.
How to avoid losing connection to the terminal
-
Always reserve the IP addresses of the equipment (through the router settings or the terminal itself).
-
Do not use Wi-Fi for critical cash registers without backup; if you do use it — make sure there are no network conflicts.
-
Document the ports, IP addresses, and MAC addresses for each store location.
-
After replacing or fully resetting the router — be sure to check IP reservation (DHCP reservation) and port forwarding, because these settings are lost.
What is important to remember
If the POS terminal periodically «drops off» — first check whether there is a white static IP address and whether the terminal's internal IP is reserved, then the correctness of forwarded ports, the operation of banking utilities, and the presence of permissions in the firewall/antivirus. Without these settings, stable terminal operation over the network (especially with RDP) is impossible.
-
29.01.2026
Exceeded number of workstations" error when working with a banking POS terminal
How to fix the license error when connecting a banking POS terminal to Torgsoft. Guide on clearing old workstation bindings.
-
28.01.2026
Setting up the PAX A930 bank terminal (JSON / Wi-Fi)
Guide on connecting and configuring the PAX A930 Android banking terminal in the Torgsoft program via the JSON (COM/TCP) protocol over Wi-Fi
-
22.01.2026
The bank terminal check slip is not printing
The bank terminal slip check is not printed: how to check the printer, template, terminal and transfer of details to the fiscal check









Go back to the previous step