Initial Setup of Standard Terminal S7100

overview this article will walk through everything you need to know to collect payments with a standard terminal from unboxing to accepting payments in person, each step is outlined below some steps might have some additional information that you'd like to read up on to dive deeper into a particular step and learn about the faqs and troubleshooting, click the " suggested article " for the step instructions unbox your device and power on once you receive your terminal, you'll find the terminal and charger in the box your terminal acts like a mobile device so it can be used wirelessly without having to plug it in for use — you'll see the battery percentage on your device's screen when in use power on the device connect the terminal to the wifi network upon first boot, you'll be asked to connect to your private wifi network (it may also have you update your terminal to the latest firmware) if you have the optional ethernet dock, plug your dock into your ethernet and slide the terminal into the dock your terminal must be on the same wifi network as the computer you are selling tickets on in your ludus admin panel, or you will receive connection errors your wifi network must use wpa personal or wpa2 personal encryption and be password protected wifi is not supported for non password protected networks or enterprise networks please consult your tech department or an expert for any questions about your network generate pairing code once connected to wifi and updated, swipe right from the left side of the terminal's screen select settings on the terminal's screen and enter 07139 for the "admin pin " click generate pairing code (example below) add standard terminal to your admin panel you are now ready to connect your standard terminal to your ludus account this is done by clicking the settings (wheel icon ⚙️) in the upper right hand corner and navigating to the payments tab at the bottom of the page, click +add payment device click standard terminal s700 and insert the pairing code displayed on your terminal name your terminal and click save suggested article add payment device docid\ nouaemmlnk2g wfchwtzw sell tickets! at this point, your terminal is connected to your ludus and ready to start accepting payments when you first go to sell tickets as an admin, it'll have you connect to your terminal and then will remember which one you connected — if you have multiple terminals, you can choose and switch between them at any time via your admin cart page when selling tickets suggested article sell tickets to an event docid 0bedn7nc74ymyn8mxb9lb troubleshooting and more same wifi network it is important to note that your terminal and the computer you are selling tickets on must be connected to the same private wifi network; otherwise, you will receive connection errors one terminal can be connected to an admin cart at a time for example, if you have 2 box office computers selling tickets, each computer should have its own terminal it is best to label your terminals like "box office 1", "box office 2", etc, so you can easily tell them apart otherwise, you'll have to be aware of what the other admin seller is doing before submitting your terminal payment, and it may require you to refresh your cart page to re establish the connection consistent connection errors if you get consistent connection errors even though your terminal is connected to your wifi, this could be due to a firewall or router configuration error that is blocking the connection and ports needed please contact your it department or expert to allow the device permission or give your device access to an internal network used for internet connected devices saying not connected to the internet after saving wifi details if this happens, you may have something blocking the connection, such as a firewall to double check, try temporarily connecting to your phone's hotspot if it connects without issue, it means your wifi network is causing the issue, so you can at least have that narrowed down try connecting both the computer and your terminal to a hotspot if it connects using the hotspot on a mobile device, then this would point to there being something on your network that is blocking the communication between the two devices firewall ports if you think you may have firewall ports that need opening, here is what you'll need to open for the terminal to work tcp port 4443 tcp port 443 (https) udp port 53 (dns) whitelist fully qualified domain names (fqdns) for the terminal to communicate with stripe, the payment network, over a secure connection, it needs to access the main domains used for communication this is especially important if you are on a network, such as a school network, that has a content filter api stripe com terminal stripe com api emms bbpos com armada stripe com gator stripe com terminal events stripe com pool ntp org time android com \[random string] device stripe terminal local reader net (partially qualified) for a full list of all domains stripe uses, click here https //stripe com/docs/ips unable to connect if you are still getting an "unable to connect" error message, please open console within the chrome browser while that error message is showing this will show you an error message that may help resolve the issue in the console, there will be an error message in red also, below that, there may be a link to help with troubleshooting the network issue this is generally in yellow keyboard shortcuts to open the console windows press control + shift + j or just use f12 mac press command + option + j if you see failed to load resource net err cert date invalid , turning off your firewall can fix that if you find that corrects the issue, be sure that the ports listed above are open on both your firewall and computer dns the terminal creates a dns entry for itself of 1 1 1 1 if you are seeing an issue connecting, you may find that ensuring your computer can resolve addresses on that dns server will help you connect try a splitter in cases where wired ethernet is used on both the terminal/dock and computer, connecting both devices via a splitter may help some clients have successfully found this to get both devices to communicate at this time, stripe does not allow for the setup of a static ip on the standard terminal