Falaah Falaah AI
payments

Making tap-to-pay reliable on every device — what we shipped

Phone NFC is great in the hand and flaky on a wall. Here's how Muin Go now diagnoses reader problems, falls back gracefully mid-checkout, measures per-device tap reliability, and supports dedicated card readers for mounted stations.

FT
Falaah Team
· · 4 min read
Making tap-to-pay reliable on every device — what we shipped

Draft — pending founder review before publish.

“Tap to pay is flaky on our mounted tablet” is one of the most common pieces of feedback we hear from organizations running fixed payment stations. The card reads on the second or third try. Donors hover the card, unsure where to tap. The operator apologizes. Everyone loses a little confidence.

The root cause isn’t the software — it’s physics. Phone and tablet NFC antennas are designed for handheld use, where a person aims the device at the card. Mount that device on a wall or counter and the geometry inverts: now the customer has to find an invisible antenna sweet spot that sits in a different place on every device model, often through a case and next to metal mounting hardware. Handheld, the same hardware is excellent. Mounted, it fights you.

We just shipped four things in Muin that attack this end to end.

1. Reader Check — diagnosis built into the app

Muin Go now has a one-tap Reader Check (Settings → Reader Check, and offered right on the payment-failed screen). It verifies NFC hardware and whether NFC is enabled, network connectivity, your organization’s card-payment capability, and Tap to Pay terms acceptance — each with its own plain-language fix. If the device is paired with an external reader, it checks the pairing and reachability instead.

No more guessing which of five preconditions is the broken one.

2. “Try Another Way” — graceful fallback mid-checkout

When a tap fails with a customer standing there, retrying isn’t always the right move. The failure screen now offers Try Another Way: a QR code the customer scans to pay on their own phone, secure manual card entry, or a cash record — with the amount and fund carried over. The options shown are exactly the ones your organization has enabled.

3. Tap Reliability — per-device-model measurement

You can’t fix what you can’t see. Muin now records every tap outcome — success, failure, retry, fallback diversion — and rolls it up per device model in Payments → Terminals → Reliability. A Samsung tablet at 72% first-tap success sticks out next to an iPhone at 98%, and the decision (“that mounted tablet needs a real reader”) makes itself. Our operations team also gets alerted automatically when any organization’s daily first-tap success drops below 85%, so we often know before you write in.

4. External card readers — first-class support for fixed stations

For counters and wall-mounted tablets, Muin Go now supports dedicated Stripe-certified network readers (BBPOS WisePOS E) as a per-device setting. Pair the reader once in Pay Settings; from then on, every checkout on that device sends the customer to the reader’s own screen — its own antenna, designed for thousands of taps, mounted at eye level where the customer expects it. The tablet keeps doing what tablets are good at: amount entry, fund selection, receipts.

Stripe doesn’t sell a wall-mount reader — every certified model ships handheld or countertop — so our hardware guide covers the third-party-bracket route: positioning (within ~30 cm of the tablet, NFC face toward the customer), power and Ethernet routing, and what to verify after installation.

The honest recommendation

  • Handheld use — phone or tablet Tap to Pay is excellent. Use it.
  • Mounted, high-volume stations — pair a dedicated reader. Software can diagnose, measure, and fall back gracefully, but it cannot move an antenna.

Reliability work is rarely glamorous. But payments are the moment your supporters trust you most — and the bar is “first tap, every time.”