Questions and answers

Straight answers before you commit.

Straight answers about hardware, security, and what happens when ten thousand people start tapping.

Compatibility

What phones can tap a tag?

Basically all of them: iPhones and Android phones read NFC tags natively — a tap opens the browser, no app installed. Every tag can also carry a printed QR code as a camera-scan fallback.

Visitors

Do people need an account?

No. A tap opens a public form or link in the browser. Where you want identity — memberships, credentials — verified credential flows handle it without making anyone create a password at the door, and Apple/Google Wallet passes are coming soon.

Security

What if someone screenshots or shares the link?

Secure NFC tags generate a one-time cryptographic code per tap, so copied URLs fail on replay. Fresh-scan windows add a timer: the action must run within seconds of the physical tap, or it expires.

Data

What ends up in the scan log?

Time, approximate location, device info, the resolved action, and the outcome — success, expired, disabled, or blocked. Successful form actions also update the actual records they touch.

Wallet

When do Wallet passes arrive?

Apple Wallet and Google Wallet passes are coming soon: you will issue a credential from a record and send an add-to-wallet link by email or text, with updates and revocation from your side afterward. They will be included in managed-Action capacity — no separate Wallet fee. Contactless tap-to-reader presentation stays a custom pilot.

Ordering

How fast do tags arrive?

Fast — you buy directly from TapTag, and most custom items ship the next business day (large runs take about a business day per hundred items). If we design for you, add the design round first; the hardware still ships from TapTag on their clock.

Put an action in the world.

Start with a handful of tags and one workflow — most teams find the second use case within a week.