If your Stripe Terminal (WisePOS E or S700) isn't connecting when trying to process a card through Walla, follow these troubleshooting steps in order. This guide walks you through the most common causes — no tech background required.
📱 iPad Users – Stripe Terminal Connection Update (March 2025)
If your Stripe terminal stopped connecting on an iPad, you're likely affected by a new Bluetooth restriction in iPadOS 17.4. This change prevents browsers like Safari and Chrome from initiating Bluetooth connections—it’s a system-level Apple update, not an issue with Walla or Stripe. 👉 Scroll to the end of this article for full details.
Step 1: Understand Business Settings Terminal Connected Status
The terminal connects for use when you select Use New Card, then choose Read Card from Terminal on the checkout page.
The terminal’s status will say Connected under Business Settings only after selecting Read Card from Terminal and while completing the transaction as pictured below.
Once the transaction is complete the terminal status under Business Settings will go back to not connected after the transaction is complete.
In other words, do not worry about if the terminal’s status says Not Connected in either of the two following places fond under Business Settings. The action that connects the Stripe terminal to Walla is selecting Read Card from Terminal on the checkout page.
Step 2: Verify Router Compatibility
⚠️ Important: T-Mobile routers and WiFi networks are not supported with Stripe terminals.
These routers often block local traffic needed for the terminal to connect to your point-of-sale system.
👉 To resolve this, switch to a standard home or business router from a different provider.
🔄 Temporary Fallback Option: Use a Mobile Hotspot
If you're currently using a T-Mobile router or aren’t sure about your setup, you can quickly test terminal functionality using a mobile hotspot:
To test:
Turn on the hotspot on your mobile phone (preferably not T-Mobile).
Connect both your Stripe terminal and your point-of-sale device (iPad, laptop, etc.) to the hotspot.
Retry the Read Card from Terminal action.
⚠️ This is a temporary testing method. Hotspots are not reliable for daily use or overnight updates, but this helps confirm whether your primary WiFi network is the issue.
Step 3: Verify Router is IPv4, Not IPv6
The following IP addresses are IPv4. They are 1–3 numbers split up into 4 sections, divided by a decimal place.
Stripe readers only support IPv4, not IPv6.
IPv4 example:
192.168.0.1IPv6 example:
2606:4708:10::6816:2868❌
If your network uses IPv6, speak with your internet provider about switching to IPv4.
Step 4: Verify Terminal Uses Same Wifi as Device
Is your terminal connected to the same wifi as the device you are using for Walla? Make sure your terminal is connected to the same wifi network as the device you are using for Walla by following these steps:
Swipe right on the reader to open Settings
Tap WiFi Settings
Make sure the terminal and the device running Walla are connected to the same network
Tap the network name to verify signal strength and assigned IP
⚠️ Joining a new WiFi network will disconnect the terminal from its current one.
Step 5: Verify Wifi is Password Protected
Your wifi network must use WPA-Personal or WPA2-Personal encryption and be password protected. Non-password-protected networks or enterprise networks are not supported.
Your network must:
Use WPA or WPA2-Personal encryption
Be password protected
❌ Public, open, or enterprise networks will not work with Stripe readers.
Step 6: Check Stripe Terminal Software Update
You can check the latest terminal software version here Reader Software Version. The reader, firmware, and configuration versions should all match the software versions of your reader.
Stripe readers update overnight when plugged in and turned on.
To check version:
Swipe left on the reader > Tap Settings
Enter admin code:
07139Review the Diagnostics page to compare current version with Stripe’s software version page
💡 If outdated, restart the terminal to trigger a manual update.
If the terminal’s software version does not match what you are seeing here Reader Software Version, then the terminal might be having trouble connecting to Stripe when it is plugged in and running through updates at midnight. Restart the device to automatically force the reader to check for software updates.
Step 7: Enable Automatic Terminal Software Updates
Follow these steps to check the terminal’s connectivity to Stripe to ensure automatic updates. Go to:
Settings > Diagnostics
Run the Stripe Connectivity test
✅ If Passed, you're good.
❌ If Failed, continue to DNS steps below.
Step 8: Update Device DNS Settings
This is the magic troubleshooting step that solves the terminal issue after everything else has been completed. And don't be intimidated by this step if you are not tech-y. Just follow the steps, it is easy!
By adding 1.0.0.1 and 1.1.1.1 to your DNS settings under your device’s network settings, it makes it easier for Walla to connect to your terminal. And usually this final step is what does the trick if you are still unable to use the terminal.
How to change DNS settings on a Mac
On the top right of your desktop select the search box
Type DNS Servers
Under DNS select the + at the bottom of the box/section titled DNS Servers IPv4 or IPv6 Servers
Choose the + under the DNS Servers column
Enter 1.1.1.1
Select the + again
Enter 1.0.0.1
Choose Save
How to change DNS settings on an iPad
Open the Settings app and tap on Wi-Fi.
Tap on “i” next to the connected Wi-Fi name or any other Wi-Fi.
Tap on Configure DNS
Tap on Manual, then choose Add Server.
Next, type 1.1.1.1
Select Add Server, type 1.0.0.1
Tap on Save
How to change DNS settings using Control Panel on Windows 11
Open Control Panel.
Click on Network and Internet.
Click on Network and Sharing Center.
Click the Change adapter settings option in the left pane.
Right-click the active network interface and select the Properties option.
Select and check the Internet Protocol Version 4 (TCP/IPv4) option.
Click the Properties button.
Select the Use the following DNS server addresses option.
Under the "Preferred DNS server" section, confirm the primary DNS address. Enter 1.1.1.1
Under the "Alternate DNS server" section, confirm the secondary DNS address the system will use if the primary is not reachable. Enter 1.0.0.1
Click the OK button.
Click the Close button.
How to change DNS settings using Settings on Windows 10
Open Settings.
Click on Network & Internet.
Click on Ethernet or Wi-Fi.
Select the connection that connects Windows 10 to the network.
Under the "IP settings" section, click the Edit button.
Use the "Edit IP settings" drop-down menu and select the Manual option.
Turn on the IPv4 toggle switch.
Under the "Preferred DNS server" section, confirm the primary DNS address. Enter 1.1.1.1
Under the "Alternate DNS server" section, confirm the secondary DNS address. Enter 1.0.0.1
Click the Save button.
Restart the device.
Step 9: Check DNS Resolution on the Terminal
Some DNS providers block local IP resolution, which Stripe uses to communicate with your reader. Stripe terminals rely on a special local address format like this:
luaCopyEdit*.[random-string].device.stripe-terminal-local-reader.net
This resolves to the local IP of your WisePOS E or S700. If your DNS provider blocks it, the terminal won’t be able to connect.
To check DNS resolution:
Go to your reader's Settings > Diagnostics
Look for DNS Resolution test results
If DNS resolution says “FAILED,” your DNS provider is likely blocking local IPs.
Fix this by changing to one of the following DNS providers:
Cloudflare DNS:
1.1.1.1and1.0.0.1Google DNS:
8.8.8.8and8.8.4.4
You can update DNS:
On your router:
If you manage your router, it’s best to update the DNS there — this applies the fix to all devices in your location.
On individual devices (POS systems):
Update DNS settings manually if you don’t have router access. You'll find instructions above under Step 8 for:
Mac / iPad
Windows 10 / 11
In browser-based setups:
Browsers like Chrome and Firefox support DNS over HTTPS.
Chrome: Go to
chrome://settings/securityFirefox: Search for DNS settings in Preferences
⚠️ Safari does not support DNS-over-HTTPS, so use device-level DNS settings.
Additional Checks
🛜 Verify DHCP Is Enabled
For the Stripe Terminal to connect successfully, your network must assign it a local IP address. This happens automatically if DHCP (Dynamic Host Configuration Protocol) is enabled on your router.
If DHCP is turned off — even by accident — your terminal won’t be able to join the network, and you'll likely see failed connection or IP assignment errors in Diagnostics.
✅ To ensure DHCP is working:
Log in to your router’s admin settings (usually via a browser at
192.168.0.1or192.168.1.1)Look for LAN Settings, DHCP Settings, or Network Settings
Make sure DHCP is turned ON and has a range of IP addresses to assign (e.g.,
192.168.1.2 – 192.168.1.254)
💡 Not sure how to check? Contact your internet service provider or IT contact and ask them to verify DHCP is enabled on your network.
🔐 Firewall, Proxy, or Content Filtering Considerations
If your business uses a managed network — such as one with an IT team, corporate firewall, or content filter (like Cisco Umbrella or Fortinet) — the reader may be blocked from resolving or communicating with Stripe’s local terminal domain.
Stripe terminals must be allowed to connect to:
luaCopyEdit*.stripe-terminal-local-reader.net
Make sure your network settings allow:
Local DNS resolution
Outbound connections to Stripe's terminal services
No interference from firewalls, VPNs, proxies, or advanced security software
💡 If you're unsure whether content filtering or firewall rules might be involved, ask your IT provider or network administrator to whitelist Stripe Terminal services.
Step 10: Still Not Working? Try Stripe’s Guide
If your reader still isn’t connecting after all steps, check out:
Keep in mind that Walla does not manufacture the Stripe terminal, Stripe does. Which means the Walla Support team uses the same information as you to troubleshoot the reader. After reading and applying relevant steps from the more advanced content, if your terminal is still not working, reach out to your friendly Walla Support team and send them a message. Be sure to mention the steps you've completed and any steps you had trouble with or did not complete!