The reader worked fine at 9 a.m. By 11 it shows as offline in Altru, the cashier is holding a guest’s card, and the only fix anyone knows is to unplug the device and wait for it to boot. Then it happens again after lunch.
Card readers that drop off and need a reboot are almost never “broken” readers. In nearly every case the cause sits somewhere between the device, your network, and the payment processor’s servers. Rebooting works because it forces the reader to rejoin the network and start a fresh connection, which hides the real problem instead of fixing it. Below is how to find what’s actually going on.
How the connection works, in plain terms
An EMV smart reader such as a WisePOS-style device isn’t just a keypad wired to your PC. It is a small networked computer. It needs a working network connection, it has to reach the processor’s servers over the internet, and Altru has to be able to find it when a cashier starts a card transaction. Anything that interrupts one of those links shows up at the desk as “reader not connected.”
The exact connection model (whether the workstation and reader must sit on the same local network, which ports and addresses need to be open) is set by Blackbaud and its payment partner, and it has changed over time. Get the current network requirements from Blackbaud support or the Blackbaud Merchant Services documentation before you start changing firewall rules. Don’t rely on a forum post from three years ago.
The usual causes, roughly in order of how often they turn up
1. Wi-Fi that’s good enough for phones but not for a payment device
Readers on Wi-Fi are the most common source of drops. Front desks are often at the far edge of coverage, near glass, metal turnstiles, or a gift shop full of shelving. A phone tolerates a weak signal; a reader holding a payment session open often doesn’t. If your reader has a wired dock or Ethernet option, use it at fixed stations. That one change clears up a large share of these complaints.
2. Guest or isolated networks
Many organizations put readers on the guest Wi-Fi because it was the easiest password to find. Guest networks commonly use client isolation (devices can’t see each other), captive portals that expire, and aggressive filtering. Any of those can block a reader. Put payment devices on a staff or dedicated payments network, ideally a separate VLAN your IT team manages, and keep them off anything with a splash page.
3. Changing IP addresses
When the router hands the reader a new address after a lease expires or a power blip, anything that was pointing at the old address loses it. That’s why problems often appear mid-morning or after a weekend. Ask your IT team to set a DHCP reservation for each reader so it always gets the same address.
4. Firewalls, content filters, and security appliances
If readers connect fine at home but fail on-site, look at your firewall or web filter. Rules that inspect encrypted traffic, block unfamiliar outbound ports, or time out idle connections can quietly cut a reader off. Give IT the processor’s published list of required domains and ports and have them exempt the reader’s traffic from inspection.
5. Sleep, power, and pending updates
Readers can go to sleep after a period of inactivity, run low on battery when left off the dock, or sit half-way through a firmware update. Check each device’s power and sleep settings, keep fixed readers on their charging base, and let updates finish before opening (a morning update that stalls is a classic “it needs a reboot” moment).
6. Workstation-side problems
Sometimes the reader is fine and the Altru workstation is the one losing track of it: a laptop that roams between access points, a VPN that kicks in, a browser session that’s been open for days. If only one register has trouble, swap the reader to a different workstation before blaming the device.
A quick way to narrow it down
- Keep a simple log for a week. Time, which reader, which workstation, what fixed it. Patterns (same time each day, one location, only on Wi-Fi) point straight at the cause.
- Swap things one at a time. Move a reader to a wired connection, or to a different station, and see if the drops follow the device or stay with the location.
- Check the network side when it fails. Before rebooting, see whether the reader still shows a network connection on its own screen. If it has no network, it’s local. If it has network but Altru can’t reach it, look at firewall, addressing, or the workstation.
- Open a ticket with evidence. Blackbaud support can do much more with “reader 3, Wi-Fi, drops roughly every 90 minutes, IP changes each time” than with “the readers keep disconnecting.”
Keep a fallback ready
Even a well-configured setup will fail sometimes, usually when the internet connection itself goes down. Decide ahead of time what the desk does: a spare reader already paired and charged, a second station to send guests to, and a clear rule for when to stop taking cards and call a supervisor. Whether Altru supports any offline or deferred card processing for your setup is something to confirm with Blackbaud directly; don’t assume it does.
Quick answers
Is rebooting the reader harmful?
Not usually, but avoid doing it mid-transaction, and check in Altru afterward that the interrupted sale didn’t post twice or not at all.
Should we just buy new readers?
Only after you’ve ruled out the network. A new device on the same weak Wi-Fi or filtered guest network will disconnect just as often.
Who owns this problem, IT or the Altru admin?
Both. The Altru admin knows when and where it fails; IT controls the network that’s usually causing it. Get them looking at the same log.
