There is no connection with the bank terminal: Socket Error #10060, Connection timed out

Error «Socket Error #10060, Connection timed out» when working with a bank terminal

The error «Socket Error #10060, Connection timed out» means that the Torgsoft program is trying to send data (the payment amount) to the bank terminal via the network (TCP/IP), but the terminal does not respond or is unavailable on the network at the time of the request.

Most often, this is caused by a changed terminal IP address, router problems, or the terminal being disconnected from the local Wi-Fi/Ethernet network.

Step 1. Basic check and equipment restart

This is the simplest step that solves the problem in many cases when the device has simply “frozen” or temporarily lost the network connection.

1. Check the terminal connection. Make sure that the terminal is turned on and connected to the correct network (by cable to the router or via Wi-Fi to the same network as the computer).

2. Restart the terminal. Unplug it from the power outlet for a few seconds and turn it on again. Often, after a restart, the terminal restores the network connection and starts accepting commands from Torgsoft.

3. Restart the router. Sometimes the problem is caused by the router itself freezing. Restarting the router may restore access to the terminal.

4. Check the impact of power outages. If there was a power outage, the terminal (for example, Ingenico) may have automatically switched to mobile Internet (SIM card). When the power returns, it may not reconnect to Wi-Fi automatically. In this case, reconnect it to Wi-Fi or restart it.

Step 2. Checking and matching the IP address (the most common cause)

If the terminal receives its IP address from the router dynamically (via DHCP), after restarting the router or terminal, this address may have changed (for example, from 192.168.0.100 to 192.168.0.102). Since the old address is specified in Torgsoft, the program cannot find the terminal.

1. Find out the current IP address on the bank terminal itself (through the service menu or by printing a settings receipt).

2. Open the Torgsoft program and go to Settings -> Options -> Bank Terminal.

3. Compare the IP address in the program settings with the one currently shown on the terminal.

4. If they are different, enter the new IP address in Torgsoft and save the settings. After that, try to process a payment.

Step 3. Router setup for stable operation (IP reservation)

So that you do not have to repeat Step 2 constantly, the network must be configured once and properly.

1. Reserve the IP address. Open your router settings and bind the current terminal IP address to its MAC address. This will make the router always assign the same address to the terminal.

2. Check port forwarding (if Torgsoft runs on a remote server). If your program is installed on a remote RDP server, Port Forwarding to the terminal IP address must be configured on the store router for communication with the local terminal (usually port 2000, 2001, or 3000).

3. Router replacement. If you recently replaced the router or reset it to factory settings, all IP reservation and port rules have been deleted. They must be configured again.

Step 4. Checking the antivirus and firewall

Antivirus programs (for example, Avast, ESET) or Windows Firewall may block the port through which Torgsoft communicates with the terminal.

1. Temporarily disable the antivirus or firewall.

2. Check the connection to the terminal. If the connection appears, add the Torgsoft program and the terminal ports to the exceptions of your antivirus or firewall.

Step 5. Contacting bank support

If the network is stable, the IP addresses match, but there is still no connection (or the BankTerminalTest utility also cannot detect the device), the protocol settings in the terminal itself may have been changed.

1. Contact your bank’s hotline.

2. Ask them to check whether the terminal is configured to work in cash register integration mode (for example, via the BPOS, JSON, or PosApi protocol).

3. Make sure that the data exchange channel on the terminal is selected correctly (it should be Ethernet or Wi-Fi, not USB/COM, if you connect via the network).