A guest walks up to your machine, pulls out their phone, and the QR code just won't scan. They try twice, give up, and move on. You lose the sale and potentially the repeat visit. QR scan failures are one of the most common support issues for cashless payment systems—and most of them are fixable in minutes if you know where to look.
This guide walks through the most common causes and how to resolve them, in order from simplest to most complex.
Start with the Obvious: Is the Screen Clean?
The single most frequent cause of scan failures is a dirty QR display. Smudged glass, fingerprints, dust, and condensation all scatter the light that a phone camera needs to read the code. Wipe the QR screen with a clean microfiber cloth—not a paper towel, which can scratch—and test again before doing anything else.
This step resolves roughly 40% of scan issues in high-traffic environments. Make it part of your weekly site visit routine.
Check Screen Brightness
If the QR display is set too dim, phone cameras struggle to get enough contrast to decode the pattern—especially in bright environments or under direct overhead lighting. Check your reader's brightness setting and push it to maximum. Most cashless readers support brightness adjustment through the device settings or a management portal.
Outdoor or window-adjacent installations are especially prone to brightness issues. If the machine is in a bright spot and scan rates are consistently low, a screen shade or repositioning the unit slightly can make a significant difference.
Confirm the Reader Is Online
A QR code that loads but doesn't process a payment is different from one that fails at the scan step. If the code loads and the guest can scan it but gets an error or no response, the issue is likely connectivity, not the reader hardware. Check your dashboard to confirm the machine is showing as online. If it's offline, check the local Wi-Fi or cellular connection at the site.
Tip: set up transaction alerts on your machines so you know quickly if a unit has gone silent—zero transactions in a multi-hour window during business hours is a reliable offline signal.
Test with Multiple Phones
Some older phone cameras struggle with certain QR display types, especially e-ink or low-refresh screens. If a guest's phone can't scan but your phone can, the issue is likely on the guest device side—camera permissions for the browser, low-quality camera, or a protective screen filter.
When testing, also try the scan from slightly different angles and distances. Most QR readers are optimized for a 12–24 inch scan distance. Very close or very far scans sometimes fail.
Inspect the Mount and Physical Position
A reader that was installed cleanly but has shifted over time—from vibration, cleaning, or accidental bumps—can end up at an angle that makes scanning awkward. The QR display should be roughly at chest height, facing the direction guests approach from, and level. If it's tilted or facing at an odd angle, reposition it.
Also check that the unit hasn't been partially covered by a sticker, a price tag, or promotional material that someone placed over the reader face.
Restart the Reader
If all the physical checks pass and the machine is online but scans still fail consistently, a soft restart of the payment reader is the next step. Most cashless readers can be restarted through the device management interface. After the restart, wait 60 seconds and test again.
A restart resolves software glitches, memory issues, and connection state problems that can accumulate over time, especially on readers that run 24/7 without interruption.
When to Escalate
If you've cleaned the screen, confirmed connectivity, tested with multiple phones, checked the physical mount, and restarted the reader—and scans are still failing—it's time to contact support. When you reach out, include:
- Machine ID or reader serial number
- Location name and address
- What you've already tried
- Whether the failure is intermittent or consistent
- Any error messages the guest sees after scanning
Good support teams can often diagnose hardware or configuration issues remotely when they have this information upfront. It cuts resolution time significantly.
Build a Quick-Reference Card
If you manage multiple sites and have staff or contract technicians, create a laminated quick-reference card with these steps for each location. Most scan issues are resolvable without a service call. Empowering the person on-site to run through the checklist saves time, money, and guest frustration.
Prevention Is Better Than Troubleshooting
Add a 2-minute scan test to every site visit. Wipe the reader, do a test payment, confirm it completes. Catching a degrading reader early—before it fails completely—is far better than discovering the problem when a frustrated guest reports it. Your dashboards and transaction logs are your first line of defense. Use them.