ZenotiHelp

Troubleshoot payment terminal connectivity

ZTZenoti Docs Team Updated October 30, 2026 8 min readGuide

When a payment terminal cannot reach the network or loses its connection to the point of sale (POS), transactions fail and guests are left waiting. This article walks through the most common connectivity symptoms and gives step-by-step checks to restore the connection.

Audience: Front desk staff and center administrators who manage payment terminal hardware.

Before you begin

  • Confirm that the terminal is powered on and that the power cable or battery is not the source of the problem.
  • Know which network your center uses β€” including the network name (SSID), whether it operates on 2.4 GHz or 5 GHz, and whether a guest network is in use.
  • Have the terminal's serial number available in case you need to contact Zenoti Support.
  • For Adyen-connected terminals (Verifone e285, e285p, and V400m), confirm that your center's firewall allows outgoing HTTPS traffic on TCP port 443 to *.adyen.com and *.adyenpayments.com from both the POS and terminal IP addresses. This firewall requirement does not apply to the Verifone P400 Plus or to Stripe readers, which use the Stripe domains β€” see Verifone P400 Plus for those details.

Symptom index

Use the table below to jump directly to the section for your situation.

Symptom Go to section
Terminal will not reach the internet Terminal will not reach the internet
Wi-Fi keeps dropping Wi-Fi keeps dropping
Terminal is stuck on the processor screen Terminal is stuck on the processor screen
Reader and POS are on different networks Reader and POS are on different networks

Steps

Terminal will not reach the internet

Work through these checks in order. Stop when the issue is resolved.

  1. Test the network from another device. Use a phone or laptop on the same Wi-Fi network as the terminal and confirm it can load a website. If that device also cannot reach the internet, the problem is with the network itself β€” restart the router (see step 3) before continuing with the terminal.

  2. Restart the card reader. Press and hold the power button to turn the terminal off, wait 30 seconds, then press the power button again to turn it on. Allow the terminal to complete its startup sequence before testing a transaction.

  3. Restart the router. Turn the router off, wait 60 seconds, then turn it back on. Wait until the router has fully reconnected β€” all indicator lights should return to their normal steady state β€” before testing the terminal again.

  4. Confirm the correct Wi-Fi network and password. On the terminal, open the network settings and verify that the terminal is connected to the correct network. If the network name or password has changed recently, forget the network and add it again:

    • Navigate to Network > Wi-Fi > Network Forget, then select Add Network and enter the correct credentials.
    • See the device-specific article for your terminal model for the key sequence and admin PIN required to access these settings.
  5. Confirm the terminal has a valid IP address. In the terminal's network settings, check that an IP address is assigned. If your center uses a static IP address for the terminal, confirm that the static IP is still correct and does not conflict with another device on the network.

  6. Ask your IT team to check firewall rules. If the checks above do not resolve the issue, contact the center's IT team and ask them to confirm that firewall rules are not blocking the terminal from reaching the internet. For Adyen-connected terminals (Verifone e285, e285p, and V400m), the firewall must allow outgoing HTTPS (TCP port 443) to *.adyen.com and *.adyenpayments.com from the POS and terminal IP addresses. This rule does not apply to the Verifone P400 Plus or Stripe readers. To confirm whether the firewall allowlist request for your center has been submitted, share the center name and number with Zenoti Support. The Zenoti payments and engineering teams handle this configuration.

  7. For terminals with a SIM card. If your terminal uses a cellular data connection rather than Wi-Fi, confirm that the SIM card is fully inserted and that the SIM is active with an available data plan. Then toggle airplane mode on, wait five seconds, and toggle it off again to force the terminal to re-register on the cellular network.

  8. Apply any pending firmware update. An outdated firmware version can cause connectivity problems. Follow the processor's documentation to check whether a firmware update is available and apply it.

  9. Contact Zenoti Support. If the terminal still cannot reach the internet after completing all steps above, contact Zenoti Support. Have the terminal's serial number and a description of the troubleshooting steps you have already taken ready before you call or submit a ticket. If the problem cannot be resolved, ask for a replacement terminal. See Request a replacement terminal.

Wi-Fi keeps dropping

Intermittent Wi-Fi disconnections usually point to a router issue, a weak signal, or a network credential problem.

  1. Follow steps 1 through 5 in Terminal will not reach the internet to rule out the most common causes.

  2. Forget and re-add the network through the terminal's admin menu. On the terminal, navigate to Network > Wi-Fi > Network Forget, then select Add Network and enter the network name and password. See the device-specific article for your terminal model for the key sequence and admin PIN you need to access the admin menu.

Tip: To rule out a router-specific problem, temporarily connect the terminal to a mobile hotspot. If the terminal maintains a stable connection on the hotspot but not on the center Wi-Fi, the issue is with the router or access point, not the terminal itself.

  1. If dropping continues after re-adding the network, ask your IT team to check signal strength at the terminal's physical location and to confirm that the router firmware is current.

Terminal is stuck on the processor screen

A terminal that loads to the payment processor's splash screen and does not advance typically indicates a network or configuration problem that is preventing it from completing its startup handshake.

  1. Confirm the terminal is on the correct network. Open the terminal's network settings and verify that it is connected to the same Wi-Fi network β€” or the same Ethernet segment β€” as the POS. A mismatch will prevent the terminal from completing its initialization.

  2. Restart the terminal from the admin menu. On the terminal, enter 9, then press Enter, enter the admin PIN, then navigate to Power > Restart. See the device-specific article for your terminal model for the PIN.

    Important: Never publish the admin PIN in shared documents or post it at the front desk. Refer to the vendor's official documentation or contact your account representative for current credentials.

  3. Allow time for the terminal to finish loading. After restarting, wait until the terminal has fully completed its startup sequence before testing a transaction. Some terminals take two to three minutes to download configuration from the processor.

  4. Restart the POS and test a transaction. Close and reopen the Zenoti POS session, then attempt a test transaction. If the transaction completes, the terminal is working correctly.

  5. Contact Zenoti Support. If the terminal remains stuck after restarting, contact Zenoti Support. Have the terminal's serial number and a description of what you see on the screen ready before you reach out.

Reader and POS are on different networks

For network-connected terminals to communicate with the POS, both devices must be on the same network segment.

The requirement: The POS device and the terminal must be on the same network and on the same band with the same network name. A mismatch prevents pairing and blocks all communication between the two devices. Common mismatches include:

  • One device on 2.4 GHz and the other on 5 GHz (even when both SSIDs appear similar)
  • One device on the center's main network and the other on a guest network
  • One device on a staff VLAN and the other on a separate VLAN

To resolve a network mismatch:

  1. Identify which network the POS device is currently on and confirm the exact network name and band.
  2. Connect the terminal to that same network β€” see step 4 in Terminal will not reach the internet for instructions on forgetting and re-adding the network through the terminal's admin menu.
  3. Confirm both devices show the same network name before attempting to pair or process a transaction again.

Note: If your center uses the Verifone P400 Plus, you also have the option to connect the terminal via a wired Ethernet connection, which eliminates Wi-Fi band mismatches entirely. See Verifone P400 Plus for setup instructions.

Tips

  • Keep a note of the center's Wi-Fi network name, band, and credentials in a secure location accessible to authorized staff β€” this speeds up recovery when a terminal drops off the network.
  • If your center has multiple Wi-Fi networks with similar names (for example, CenterWifi and CenterWifi_5G), label the correct network clearly so staff connect terminals to the right one.
  • When a terminal is relocated to a different area of the center, re-test connectivity at the new position before resuming guest transactions β€” signal strength can vary significantly across a building.
  • Schedule firmware updates during off-peak hours so that the terminal restart required to apply the update does not interrupt guest transactions.
  • For error messages that appear on the terminal screen during a transaction, see Payment errors.

Troubleshooting

Problem Likely cause Resolution
Terminal connects to Wi-Fi but transactions still fail Firewall blocking processor domains For Adyen terminals, ask IT to allow TCP 443 to *.adyen.com and *.adyenpayments.com. For Stripe readers, confirm Stripe domains are not blocked β€” see Verifone P400 Plus.
Terminal connects to hotspot but not to center Wi-Fi Router or access point issue Restart the router, check router firmware, check signal strength at the terminal location.
Terminal shows "No network" immediately after connecting Incorrect password or IP conflict Forget the network, re-add it with the correct password, and confirm no static IP conflicts exist.
POS shows the terminal as offline even though the terminal appears connected Devices on different networks or bands Confirm both POS and terminal are on the same SSID and band, then re-pair from the POS.
Terminal restarts but returns to stuck processor screen Processor handshake failing Verify network connectivity, confirm firewall rules, and contact Zenoti Support with the serial number if the issue persists.
Cellular terminal shows no signal SIM not seated or plan inactive Remove and re-seat the SIM, confirm the plan is active, toggle airplane mode off and on.
Was this article helpful?
Your feedback helps us improve our documentation.