Devices

Will your phones
actually work?

Almost certainly yes — and we will not guess. Every handset model in your fleet is bench-tested against real cards before rollout, because weak antennas read perfectly in a lab and fail at a doorstep with someone waiting.

Check a handset

Four conditions, all of them hard

Toggle any of them off to see what happens. TapProof fails closed by design: it will refuse a session rather than take a payment it cannot vouch for.

Check a handset

This handset qualifies

It can be enrolled and start taking cards. We still bench-test each model in your fleet before rollout.

Fleet

One handset in a hundred is the one that fails at a doorstep

Which is why we bench-test every model you run, rather than publishing a list and hoping.

Qualification

Why we bench-test rather than publish a list

Antenna placement varies

Two handsets on the same chipset can put the NFC coil in different places. The one that reads at 15mm in a lab is the one that fails on a counter.

Cases and covers matter

A thick case, a metal ring holder or a card sleeve behind the phone will kill a read. We test the phone as your people actually carry it.

Round-trip time is the tell

We record read success and time-to-read per model. Anything slow or inconsistent is excluded before the pilot, not after.

Why placement matters

Two phones on the same chipset read differently

The antenna coil sits in a different place on almost every model, and a case, a metal ring holder or a card tucked behind the phone will kill a read outright.

We test the handset as your people actually carry it, case and all, and record read success and time-to-read per model. Anything slow or inconsistent is excluded before the pilot — not discovered during it.

NFC field, at the phone's edge

Lifecycle

Enrolment, monitoring and revocation

Enrolment

The device generates a hardware-backed keystore key, StrongBox where the handset has it. Its identity is the hash of that key — it cannot be spoofed by copying a file, and it dies with a factory reset.

Once per device

Heartbeat

Continuous attestation, not a check only at transaction time. A device that stops heart-beating stops being able to transact, hard-failed at twenty-four hours.

Every 4 hours

Distribution

Shipped as a private app under Android Enterprise. Play Integrity gives strong verdicts to Play-installed apps and weak ones to sideloads, and we fail closed on weak.

Managed Play

Revocation

One call kills a lost or compromised handset. Managed Play adds remote wipe and forced updates across the fleet.

Immediate

Bring your own app

The same enrolment and attestation applies when TapProof runs inside your app rather than ours.

SDK

Send us your handset list How attestation works