Modern acquiring systems are increasingly abandoning cumbersome wired connections in favor of mobile solutions that allow payment acceptance anywhere in the retail space or even outdoors. Connecting the terminal to Wi-Fi It's becoming the de facto standard for small businesses, courier services, and mobile retailers, providing essential mobility and transaction speed. However, despite its apparent simplicity, the initial setup process often presents difficulties for users unfamiliar with the specifics of network protocols.
Connection stability directly impacts payment processing speed, which is critical during peak hours when technical glitches shouldn't cause queues to swell. In this article, we'll cover not only the basic steps for entering a password but also examine the fine-grained router settings that often serve as a hidden barrier to successful device authorization. You'll learn how to avoid common mistakes, ensure the security of transmitted data, and what to do if the terminal detects the network but can't connect.
Implementing wireless technologies into the payment infrastructure requires careful attention to configuration details. POS systems Point of Sale (POS) devices have specific signal requirements that differ from those of typical smartphones or laptops. Understanding these nuances will allow you to resolve 90% of connection issues yourself, without calling a technician.
Wireless network requirements for payment devices
Before setting up the terminal itself, you need to ensure that your infrastructure is ready to work with financial equipment. Most modern models, such as Ingenico, PAX or Verifone, support safety standards WPA2-PSK And WPA3, which are mandatory for PCI DSS compliance. Using open networks or outdated WEP encryption is not only unsafe but is often blocked by the firmware of the devices themselves.
A critical parameter is the frequency range. Many payment terminals still operate exclusively in the frequency range. 2.4 GHz, ignoring 5 GHz networks. If your router broadcasts a single shared network (Smart Connect) or hides the SSID, the terminal may simply not see the access point. You should assign a separate SSID for the guest network or IoT devices, operating strictly at the 2.4 GHz frequency.
⚠️ Attention: Some corporate routers have a client isolation feature that prevents devices within the same Wi-Fi network from exchanging data. This feature must be disabled for the terminal to function, as the device must send requests to the processing gateway.
Channel bandwidth is also worth considering. Although transmitting a payment transaction requires minimal data, collisions are possible in areas with high wireless network density (shopping centers, markets). It is recommended to use Wi-Fi analyzers to select the least congested channel (1, 6, or 11) in the 2.4 GHz band.
Equipment preparation and initial inspection
The configuration process begins well before entering the password. Ensure the terminal's battery is charged to at least 30-40%, as the communication module's power consumption increases sharply when searching for a network and establishing a secure connection. A discharged battery may interrupt the configuration process and prevent the settings from being written.
Visually inspect the device for damage to the antenna (if it's external) and ensure that the SIM card (if the terminal is a combination device) is removed or deactivated in the menu to prevent the device from prioritizing mobile data over Wi-Fi. In the menu of some models, for example: PAX A920 or A800, you need to explicitly select the preferred connection type.
- 🔋 Check the battery charge level and, if necessary, connect the terminal to the power supply.
- 📡 Make sure your router is turned on, working reliably, and transmitting a signal at the correct frequency.
- 📝 Prepare your network details in advance: the exact name (SSID) and password, checking the case of letters and special characters.
- 🔄 Restart the terminal before starting the configuration to clear any temporary network module errors.
It is important to know the exact model of your device, as menu interfaces may vary significantly. Instructions for Ingenico Move/5000 will differ from the menu of Android terminals Sunmi or EvotorIf you're unsure of the model, look at the sticker on the back or under the battery.
Step-by-step instructions: connecting to Wi-Fi
The procedure may vary depending on the terminal's operating system, but the general logic remains the same. First, you need to access the settings menu. On classic push-button terminals, this is often a key combination (e.g., Fn + Enter or log in via the administrator menu with a password 12345678 or 00000000). On Android devices, this is the standard menu. Settings → Wi-Fi.
After activating the wireless module, the device will scan for available networks. Find your SSID in the list. If the network is hidden, select "Add network" or "Other" and enter the name manually. Be extremely careful when entering the password: the system is case-sensitive, and some terminals have low-resolution screens, making it difficult to distinguish similar characters.
☑️ Connection setup checklist
After entering the data, the terminal will attempt to obtain an IP address from the router's DHCP server. A successful connection is usually indicated by the appearance of the Wi-Fi icon at the top of the screen and the signal strength display. If the status changes to "Obtaining IP address..." and then resets, the problem lies in the router settings or incompatible encryption protocols.
| Status on screen | Probable cause | Action |
|---|---|---|
| Searching networks... | The Wi-Fi module is disabled or there is a driver error. | Reboot the device, check if the module is enabled in the menu |
| Incorrect password | Input error, incorrect case | Delete the network from memory and re-enter the data. |
| Obtaining IP... | The DHCP address pool is full | Reboot your router or set a static IP |
| Limited | Gateway or DNS issues | Check your router settings and internet access |
In some cases, manual IP address configuration is required. This is done through the menu. Network settings → TCP/IPHere you need to switch the mode from DHCP to Static and enter the address, mask, gateway, and DNS. The address must be in the same subnet as the router, but not the same as the addresses of other devices.
Router setup: hidden settings
Often, the cause of unstable terminal operation lies not in the device itself, but in the aggressive security settings of a modern router. Protocol WPA3, although the most secure, may not be supported by older terminal models. In this case, you need to set the router's wireless network settings to mixed mode. WPA2/WPA3 or force selection WPA2-PSK (AES).
Another important parameter is channel width. For the 2.4 GHz band, the optimal and most compatible width is 20 MHzSetting the value to 40 MHz or "Auto" may result in the terminal seeing the network but being unable to establish a handshake connection due to interference or chipset incompatibility. It is also recommended to fix the channel by selecting 1, 6, or 11 to prevent the router from "jumping" between them.
⚠️ Attention: Router interfaces (Keenetic, TP-Link, Asus, Mikrotik) are constantly being updated. The location of channel width and encryption type settings may change. If you don't find the described settings, refer to the documentation for your router model or the "Wireless Network/WLAN" section.
The function deserves special attention MAC filteringIf the router has the "Whitelist" mode enabled (allow only known devices), you need to find the MAC address of the terminal (usually indicated on a sticker or in the Status -> About the device) and add it to the list of allowed clients on the router. Without this, the terminal will be denied access immediately after entering the correct password.
What is a static IP and why is it needed?
A static IP address is a permanent digital address for a device on a local network. Using a static IP address for a terminal is beneficial because the router will always assign it the same address, simplifying diagnostics and setting up port forwarding if remote maintenance is required. However, a dynamic address (DHCP) is sufficient for basic operation.
Diagnosing and troubleshooting common errors
If the terminal is connected to Wi-Fi but transactions are not going through, you need to troubleshoot the connection. First, check if the terminal has access to the outside world. Many devices have a "Connection Test" or "Ping" function in their menu. Try pinging the gateway (router) address and an external address, such as Google's DNS (8.8.8.8).
A common problem is time desynchronization. For SSL certificates used to encrypt payments to function correctly, the time on the terminal must match the actual time. If the time is out of sync after being turned off, the internal battery may be dead, preventing the terminal from establishing a secure connection with the acquiring bank. In this case, manually setting the time or replacing the battery will help.
- 📉 Low signal level: If the signal strength is below two bars, use a Wi-Fi repeater or move the router closer to the checkout. Metal structures around the checkout counter can shield the signal.
- 🔒 Certificate Error: Check the date and time. If they are incorrect, update them manually in the terminal settings.
- 🌐 No internet access: Check if the internet is working on other devices on the same network. Your router may be out of power or your ISP may be performing maintenance.
If the connection is constantly interrupted, try forgetting the network on the terminal (Forget the network) and reconnect. This will clear old configuration files and the error cache. A complete network settings reset is also an effective method (Network Reset), but remember that this will delete all saved Wi-Fi profiles.
Security Considerations When Using Wi-Fi
Using wireless networks for financial transactions imposes increased security requirements. Never connect your terminal to public Wi-Fi networks in cafes or shopping malls, even if they're free. Attackers can use such networks to intercept traffic (a Man-in-the-Middle attack), despite the encryption of the payment protocol itself.
It's recommended to create a separate guest network on your router specifically for payment terminals and IoT devices. This will isolate them from the main network, which may contain accounting computers or employee smartphones. If one of the devices is compromised, the attacker will not gain access to critical infrastructure.
Update your terminal's firmware regularly. Manufacturers release updates that patch vulnerabilities in Wi-Fi modules and the operating system. You can check for updates through the menu. Service -> Software update, choosing the Wi-Fi update method. Before updating, make sure the terminal is connected to a stable network and charged.
Is it possible to use a mobile hotspot from a phone instead of a Wi-Fi router?
Technically, this is possible if the terminal supports the required frequencies. However, for regular use in a store, this is a poor solution: the phone will get very hot, the battery will drain quickly, and mobile internet is less stable and has data limits. Use a hotspot only as an emergency solution.
The terminal says "No connection to host" even though Wi-Fi is connected. What's wrong?
This means there's a physical connection, but the terminal can't reach the bank's server. Check the date and time settings, the correct APN (if using the GSM portion), or any blocking issues on the provider's side. The issue could also be on the processing center's end.
How to find the IP address of a terminal on a Wi-Fi network?
This can usually be found in the menu: Settings -> Net -> Status or About the deviceThe IP address is also often displayed in the top status bar next to the Wi-Fi icon after a successful connection.
Does the distance to the router affect the payment speed?
Yes, it does. A weak signal increases the time it takes to establish a connection and transfer a data packet. If the signal is too weak, the transaction may be interrupted mid-process, resulting in an error and the need to re-scan the receipt, creating queues.