Home › Knowledgebase › KB-1513

How To Secure Card Payment Terminal Wi-Fi For Restaurant Transactions

Summary

This guide helps you troubleshoot and resolve: How To Secure Card Payment Terminal Wi-Fi For Restaurant Transactions. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? đź’» Open a Ticket

Common Causes

Secure Card Payment Terminal Wi-Fi for Hospitality Transactions

Securing the Wi-Fi connection for card payment terminals is essential for protecting cardholder data and maintaining compliance with Australian payment standards. Unsecured networks can expose transaction systems to unauthorised access, putting both your customers and your organisation at risk. This guide provides step-by-step instructions to configure secure Wi-Fi connectivity for payment terminals in café, restaurant, and pub environments, including POS integration, kitchen printer/KDS considerations, and EFTPOS provider requirements.

Network Segmentation and VLANs

Payment terminals should never share a network segment with guest Wi-Fi. In hospitality environments, the business network often supports POS systems, kitchen printers, kitchen display systems (KDS), and tablets. Segmenting these devices from guest traffic reduces the risk of unauthorised devices attempting to communicate with payment systems.

Tip: Use a dedicated VLAN for payment terminals and POS hardware. This isolates cardholder data traffic from general business and guest traffic, which is a key requirement for PCI DSS compliance.

1. Create a Dedicated Business SSID

  1. Log in to your router’s administration panel using a web browser. Common gateway addresses include 192.168.1.1 or 192.168.0.1.
  2. Navigate to Wireless Settings or Wi-Fi Setup.
  3. Create a business SSID using a clear naming convention, such as Cafe-Business, Restaurant-POS, or Pub-Terminals.
  4. Connect only POS hardware, payment terminals, kitchen printers, and kitchen display systems to this network.
  5. Enable a separate guest SSID with client isolation activated to prevent guest devices from accessing business resources.

2. Configure Strong Encryption

Older encryption standards such as WEP and WPA are vulnerable to attack. Modern payment terminals require strong encryption to protect transaction data.

  1. Access the router’s Security or Wireless Security settings.
  2. Select WPA2-PSK (AES) or WPA3-Personal as the encryption method.
  3. Set a strong network password of at least 12 characters, combining upper and lowercase letters, numbers, and symbols.
  4. Save the settings and reboot the router if prompted.
Caution: Do not use WEP or WPA (TKIP) encryption. These standards are easily compromised and may fail payment industry security requirements.

3. Disable WPS

Wi-Fi Protected Setup (WPS) allows devices to connect by pressing a button or entering a PIN, but it is a known security weakness.

  1. In the router administration panel, open the WPS Setup or Wi-Fi Protected Setup section.
  2. Select Disable or Off.
  3. Apply the changes.

4. Change Default Router Credentials

Many routers ship with default administrator usernames and passwords that are publicly known. Attackers can use these to gain control of your network.

  1. Log in to the router using the current administrator credentials.
  2. Navigate to Administration, System Tools, or Management.
  3. Change the administrator password to a unique, strong passphrase.
  4. If possible, also change the default administrator username.
  5. Save the configuration.

Connecting the Payment Terminal

Once the network is secured, connect the payment terminal using the business SSID. Confirm with your EFTPOS terminal provider whether they require specific network settings, whitelisted MAC addresses, or approved router models before deployment.

  1. On the payment terminal, open Network Settings or Wi-Fi Setup.
  2. Select your business network from the available SSID list.
  3. Enter the network password.
  4. Confirm the connection and run a test transaction to verify connectivity.
  5. Record the terminal’s IP address for future troubleshooting.

Static IP vs DHCP

Most payment terminals work with DHCP, but some EFTPOS providers require a static IP address for reliable connectivity and firewall rule configuration.

  1. Contact your EFTPOS terminal provider to confirm if a static IP is required.
  2. If required, assign an IP address outside your router’s DHCP range. For example, if your router uses 192.168.1.100 to 192.168.1.199 for DHCP, assign the terminal 192.168.1.50.
  3. Configure the subnet mask as 255.255.255.0 and the default gateway as your router’s IP address (commonly 192.168.1.1).
  4. Set DNS servers to your provider’s recommended addresses, or use 8.8.8.8 and 8.8.4.4 if no specific guidance is provided.
  5. Save the settings on the terminal and restart the device.

PCI DSS Compliance for Australian Hospitality

Businesses that process, store, or transmit cardholder data must comply with the Payment Card Industry Data Security Standard (PCI DSS). For Australian cafés, restaurants, and pubs, this includes securing the network that carries EFTPOS and payment terminal traffic.

Tip: If your payment terminal supports Ethernet, a wired connection is often more stable than Wi-Fi for high-volume restaurant environments and can simplify PCI DSS scoping.

Troubleshooting

Terminal Cannot Detect the Network

Authentication Failure

Intermittent Connection or Transaction Timeouts

Unable to Access Router Settings

Maintaining a secure Wi-Fi environment for payment terminals helps protect cardholder data and supports ongoing hospitality compliance. Regularly review router settings, update firmware, and ensure only authorised devices connect to the business network.

If you need assistance configuring VLANs, static IPs, or validating your network against PCI DSS requirements, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

đź’» Open a Ticket