Overview
Before your terminals are installed, you and your IT provider will:
Set up a private Wi-Fi network for the terminals.
Send the network details to X-1 Support.
Make sure the network allows the terminals to reach Adyen.
Test every terminal with X-1 Support.
Tip: Share this article with your IT provider. Most of the technical steps are for them.
Step 1: Set up a private Wi-Fi network for your terminals
Use a dedicated, private Wi-Fi network for payment terminals only. Keep it separate from your public, lobby, or guest Wi-Fi.
Good news: Your existing network equipment can usually handle this. You typically don't need a separate internet service.
Important: A different Wi-Fi name alone is not enough. Your IT provider must separate payment traffic from guest traffic using network segmentation and firewall rules.
Checklist for your IT provider
Use WPA2-Personal with AES encryption and a strong password unique to your location. (Prefer Enterprise security? Coordinate it with X-1 Support first.)
Don't use a network that needs a browser login, terms acceptance, voucher code, or periodic sign-in. Terminals can't complete these.
Confirm strong Wi-Fi coverage everywhere terminals will be used, such as counters, hangars, fuel trucks, and ramp areas.
Confirm your terminal supports the network's Wi-Fi bands and channels.
Check with X-1 Support before changing the Wi-Fi name, password, or security settings. Changes made without notice can take terminals offline.
Step 2: Send your network details to X-1 Support
Send X-1 Support the details below for each FBO location and each Wi-Fi network. Your IT provider can help fill in the technical items.
What we need | What to provide |
FBO name and airport code | The location where terminals will be used. |
Onsite contact | Name, phone number, and email. |
IT contact | Your IT provider or administrator's name, phone number, and email. |
Wi-Fi network name (SSID) | The exact name, including capital letters and spaces. |
Hidden network? | Yes (the name is hidden) or No (the name is visible in Wi-Fi lists). |
Security type | Ask IT to confirm, for example WPA2-Personal or WPA2-Enterprise. |
Encryption type | Ask IT to confirm, for example AES. |
Wi-Fi password (PSK) | For Personal networks only. Do not send it in a regular request (see below). |
Wi-Fi bands | 2.4 GHz, 5 GHz, or both. |
Terminal details | Models, quantity, and serial numbers, if available. |
Payment locations | Where terminals will be used, plus any known weak spots. |
Network restrictions | Any device registration, MAC address filtering, or other access limits. |
Keep your password safe
Contact X-1 Support to arrange a secure password exchange.
Never put the Wi-Fi password in an ordinary support request or email.
Never share your router's administrator login. X-1 Support doesn't need it.
Using Enterprise security?
Tell X-1 Support before installation. Enterprise networks need extra authentication and certificate information.
Step 3: Network requirements (for your IT provider)
Terminals must be able to reach Adyen's payment servers directly. Please make sure the network meets these requirements.
All installations
Allow outbound HTTPS on TCP port 443 to
*.adyen.comand*.adyenpayments.com.Make sure DNS can resolve these domains.
Use domain-based firewall rules, not fixed Adyen IP addresses.
Let terminals connect to Adyen directly, without a proxy.
Ask X-1 Support whether your installation uses cloud or local communications before setting terminal addressing or device isolation rules.
Cloud vs. local communications
| Cloud communications | Local communications |
Terminal addressing | Dynamic DHCP addressing (Adyen recommended) | A stable address, ideally a DHCP reservation |
POS and terminal network | No special requirement | Must be on the same local network |
Port 8443 | Not needed | POS-to-terminal access on TCP 8443. Never expose 8443 to the internet. |
Client / access point isolation | No special requirement | Must not block the POS-to-terminal connection |
Step 4: Install and test with X-1 Support
X-1 Support will work with you to set up and check every terminal. Before you rely on Wi-Fi, complete these checks for each one:
Confirm Wi-Fi is the terminal's active connection.
Run the terminal's connectivity diagnostics.
Run a test payment with X-1 Support from each spot where the terminal will be used.
Restart the terminal and confirm it reconnects on its own.
Test cellular backup separately, if your terminal supports it.
Note: A Wi-Fi icon on the screen doesn't guarantee the terminal can reach X-1PAY. Only a test payment confirms that.
How X-1 Support uses your information
X-1 Support uses your details to create a Wi-Fi profile for your terminals in X-1PAY. You don't need to do anything here. This is for reference.
X-1PAY field | How it's filled in |
Name | An internal label, such as |
Authentication type | Must match your network. For WPA2-Personal, X-1 Support uses |
SSID | Your exact Wi-Fi network name. |
Hidden SSID | Selected only if your network hides its name. |
PSK | The Wi-Fi password you shared securely. |
Default | Selected if this is the preferred network. The terminal tries it first. |
Encryption | Must match your network. X-1PAY recommends |
Adyen may show starting values like wpa-psk or auto. X-1 Support checks these against your actual network settings, which is why accurate details matter.
Good to know
Can we use our guest Wi-Fi? No. Payment terminals need a private network that's separated from guest traffic.
Do we need a new internet service? Usually not. Your existing equipment can often support a separate, secure terminal network.
Will cellular backup keep everything running? Not fully. Cellular backup depends on signal strength, and it doesn't restore internet access to your POS computer.
We want to change our Wi-Fi password. What should we do? Contact X-1 Support first so your terminals are updated at the same time and stay online.
Questions? Contact X-1 Support. We're happy to coordinate directly with your IT provider.