Falaah Falaah AI

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.

When you’d use this

  • Donors are being asked to tap twice or three times before the card reads.
  • A checkout timed out with a card already in the donor’s hand.
  • A mounted tablet that worked on a desk has become unreliable on a wall.
  • You want to know whether to buy a reader or keep coaching tap placement.

First move: run Reader Check

In Muin Go, the Pay module’s Settings > Reader Check, which is 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
  • Your organization has accepted the Tap to Pay terms, which is an organization-level fact set once on the Stripe Connect screen
  • This device is enrolled for Tap to Pay, which is a per-device fact set in the Pay module’s Tap to Pay setup
  • In external-reader mode: the reader is paired and reachable

Those last two are deliberately separate checks and never one light. A tablet can be enrolled while the organization has not accepted, and vice versa, so collapsing them would report a station ready when it cannot take a card.

If a fact cannot be read at all, the check reports it as not confirmed rather than as accepted: “we could not confirm” is not the same answer as “yes”.

Every failed check shows its own fix. Re-run the check after each one.

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 checks this daily and alerts our operations team when an organization’s 24-hour first-tap success falls below 85% on at least twenty first-tap attempts, so do not be surprised if we reach out before you write in. The attempt floor is there so one bad tap on a quiet day is not treated as a failing station.

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.

The messages you will actually see, and what each one means

These come from the device itself, so the words below are the words on the screen. Most of them are a configuration fault the donor cannot fix, which is why the app shows you the real reason rather than a generic “payment did not go through”.

Message What to do
Turn on NFC to use Tap to Pay. Settings → Connections → NFC and contactless payments. Enable NFC in Android settings. Do this before locking a kiosk down, because afterwards you cannot reach Settings.
Developer Options is turned on, which blocks Tap to Pay. Turn it off in Settings → System → Developer options, then restart Muin. (USB debugging must also be off.) Turn both off. This is the most common cause on a tablet that was set up by a technical person.
This device cannot be used for Tap to Pay because it has been modified or rooted. Use an unmodified Android device. Use a different device. Nothing in the app will clear this.
This device does not support Tap to Pay. Use a different Android phone with NFC support. The hardware is not eligible. Pair an external reader instead.
Update Android to version 11 or later to use Tap to Pay. Update Android, or use another device.
Tap to Pay requires Android 13 or later. Update Android, or use a different device. Muin Go checks this before Tap to Pay starts. Update Android to 13 or later, or take the payment on that phone with a card reader, keyed entry or a QR code.
PIN entry is not available on this device. Use a different Android phone or a separate card reader. High-value cards may ask for a PIN this device cannot take. Use a reader.
Tap to Pay is not available for this account. Please contact support. An account-level block. Contact support.
Tap to Pay is unavailable on this build. Please contact support. The app build on the device cannot do Tap to Pay. Update Muin Go.
Setup was interrupted. Please try again. Transient. Re-run setup. Apple’s terms step can require an Apple ID sign-in and takes up to two minutes.
Setup cancelled. Somebody backed out of setup. Re-run it.
Tap to Pay on iPhone requires an iPhone. An iPad cannot do it. Use a connected reader, manual card entry or QR.
This device does not support Tap to Pay on iPhone. An iPhone XS or later is required. Use a newer iPhone.
Tap to Pay is not available on web. The browser cannot read a card. Use Muin Go.

On iPhone the feature is called Tap to Pay on iPhone, the donor taps at the top of the phone, and the terms come from Apple. On Android it is Tap to Pay, the donor taps at the back of the device, and the terms come from Stripe. Tell donors where to tap: it is different on the two platforms and invisible on both.

Quick checklist

Symptom Likely cause Fix
Reader Check says NFC is off NFC disabled in device settings Enable NFC, re-run the check
A terms error at checkout Your organization has not accepted the Tap to Pay terms An owner or admin ticks the Tap to Pay card on the Stripe Connect screen, once
A readiness error naming this device This tablet is not enrolled Run the Pay module’s Tap to Pay setup on the tablet
Taps succeed only on the second or third try, handheld Tap placement Hold the card flat against the device, steady, for a second
Mounted device, consistently below 85% Phone NFC is not built for mounted duty Pair an external reader; see the hardware guide
Everything passes and it still fails Network or provider hiccup Read the failure message, and use Try Another Way for the person in front of you

What it affects

  • Nothing about the gift already taken. A failed tap is a payment that did not happen, not one you have to reverse.
  • The Reliability tab, which records every attempt and every fallback, so a pattern is visible rather than anecdotal.
  • Your organization’s reliability alert, which is read daily against the 85% floor.

Next step