Tap to Pay troubleshooting — fixing flaky card taps
Fix Tap to Pay when it misses taps or times out: run the built-in Reader Check, check per-device reliability, use fallbacks, or switch to a dedicated reader.
Tap to Pay turns the phone or tablet you already own into a card terminal — no extra hardware. Most of the time it just works. When it doesn’t (card detected on the second or third tap, timeouts, donors unsure where to tap), this guide walks the exact diagnosis path built into Muin Go.
First move: run Reader Check
Muin Go → Settings → Reader Check (also offered directly on the payment-failed screen). It verifies, in one pass:
- The device has NFC hardware and NFC is turned on
- An internet connection is available
- Card payments are enabled for your organization
- Tap to Pay terms have been accepted on this device
- In external-reader mode: the reader is paired and reachable
Every failed check shows its own fix — turn NFC on in device settings, accept the terms in Tap to Pay setup, reconnect the reader, and so on. Re-run the check after each fix.
A tap still failed mid-checkout — use “Try Another Way”
The payment-failed screen has a Try Another Way button. It offers every alternative your organization has configured, with the amount and fund carried over so nobody re-enters anything:
- QR code — the customer scans and pays on their own phone
- Manual card entry — type the card on a secure payment page
- Cash — record a cash payment
The customer keeps a good experience even when the hardware has a bad moment, and each diversion is recorded so you can see how often it happens.
Reading the Tap Reliability dashboard
Muin web → Payments → Terminals → Reliability (admins only). One row per device model showing first-tap success rate, attempts, failures, and how often operators fell back to QR / manual / cash. Use it to answer one question: is this a one-off, or is this device model consistently bad?
- 95%+ first-tap success — healthy; occasional misses are normal
- 85–95% — watch it; coach tap placement (cards flat against the back of the device, hold for a second)
- Below 85% — that hardware is fighting you; see the next section
Muin also alerts our operations team automatically when an organization’s 24-hour first-tap success drops below 85% with meaningful volume — so don’t be surprised if we reach out before you write in.
Why phone NFC struggles on mounted devices
Phone and tablet NFC antennas are designed for handheld use — a person aiming the device at a card. Mounted devices invert that: the customer must find a small, invisible antenna sweet spot that differs per device model, often through a case, near metal mounting hardware. A counter or wall-mounted tablet doing dozens of taps a day is the single most common source of “Tap to Pay is flaky” reports.
If your device is mounted and the Reliability tab shows it below 85%, the fix is a dedicated card reader, not more retries. See Card readers & hardware for the recommended setup — a network-connected reader with its own antenna and customer-facing screen, mounted at eye level next to the tablet.
Quick checklist
| Symptom | Likely cause | Fix |
|---|---|---|
| “NFC is turned off” in Reader Check | NFC disabled in device settings | Enable NFC, re-run check |
| Terms-acceptance error at checkout | Tap to Pay terms not accepted on this device | Pay Settings → Tap to Pay setup |
| Taps succeed only on 2nd/3rd try, handheld | Tap placement | Hold the card flat against the device’s back, steady for one second |
| Mounted device, consistently below 85% | Phone NFC not built for mounted duty | Pair an external reader — see hardware guide |
| Everything passes, still failing | Network or provider hiccup | Check the failure message; use Try Another Way for the customer in front of you |