Terminal connectivity
What Should I Do If a Terminal Cannot Connect?
Treat a connection failure as an isolation problem: protect pending payment records, identify which link is failing, compare the terminal with another device, and escalate with useful evidence. The correct settings and recovery steps depend on the terminal, payment application, network, and provider program.
Protect transactions first
Check for pending or offline records before disruptive steps
Before signing out, changing locations, removing an application, or factory-resetting hardware, review the terminal and provider portal for pending, incomplete, or offline transactions. Reconnect and upload them according to the provider's current instructions. A destructive reset can remove unsent records or local settings.
Find the boundary
Identify what “cannot connect” actually means
A terminal may fail to join Wi-Fi, reach the internet, contact payment services, pair with a POS device, or communicate with an accessory. Test one layer at a time instead of changing several settings together.
Power and physical links
Confirm the approved power supply, dock, hub, and cables are seated and undamaged. Check network-port activity where applicable.
Local network
Confirm the expected network name and signal. Test the same connection near the terminal with another authorized device.
Internet and service reachability
If other devices also fail, investigate the router, internet service, firewall, DNS, or wider service path before replacing the terminal.
POS or reader pairing
For paired or mobile readers, confirm the POS device is online and follow the provider's documented Bluetooth, USB, or local-network workflow.
Controlled checks
Use a short diagnostic sequence
Observe and compare
- Write down the exact error and time it occurred.
- Check power, connection indicators, and cable seating.
- Test the network with another approved device nearby.
- Check whether one terminal or every station is affected.
Change one variable
- Verify the device date, time, and network selection.
- Try a known-good approved cable or connection path.
- Restart only under model-specific instructions.
- Retest and record the result before the next change.
Network requirements
Look beyond signal strength
A strong Wi-Fi icon does not prove that a payment terminal can reach every required service. Managed networks can block required domains, ports, DNS, time synchronization, or local-device communication. Captive portals and unsupported authentication methods may also prevent connection. Give the network administrator the current requirements published for the exact payment platform and hardware.
Escalation
Send support evidence that narrows the problem
Contact the party responsible for the failing layer: the internet provider or network administrator when multiple devices are offline; the POS or integration provider when pairing fails; or the processor, terminal program, or manufacturer support path for device-specific errors. Include the model, asset identifier, connection type, software version, timestamps, exact error, affected stations, and sanitized transaction references.
Before calling
- Confirm whether other devices and sites are affected.
- Note recent network, software, or equipment changes.
- Preserve pending payment records and reports.
- Keep authorized account contacts available.
Before resetting
- Confirm the official recovery sequence.
- Verify credentials and configuration can be restored.
- Upload provider diagnostics when available.
- Understand whether local payment records may be removed.
Related resources
Continue troubleshooting the payment workflow
Common questions
Terminal connection FAQ
Should I factory-reset the terminal?
Only after pending records are protected and the responsible provider's model-specific instructions call for it. A reset can remove local settings or unsent records.
Does working Wi-Fi prove the terminal can process?
No. The device must also reach required payment services, and managed-network rules, DNS, time, or provider availability can still affect that path.
What if every terminal is offline?
Check shared power, router, internet, network policy, and provider-status channels before treating multiple terminals as simultaneous hardware failures.
What if only one terminal fails?
Compare its cables, signal, network selection, software state, and configuration with a working approved station, changing one variable at a time.
Last editorial review: August 12, 2026. Sources reviewed: current official Square terminal/network support and Stripe Terminal network documentation.
Next step
Isolate the failed layer before replacing equipment
Protect pending records, test one connection boundary at a time, and bring precise evidence to the provider responsible for that layer.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US