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 — wallet passes and verified flows handle it without making anyone create a password at the door.

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

How do wallet passes reach people?

You issue a credential from a record and send the add-to-wallet link by email or text. One tap adds it to Apple or Google Wallet; updates and revocation happen from your side afterward.

Ordering

How fast do tags arrive?

Standard catalog items typically ship within days once artwork and programming are confirmed; custom and bulk runs take longer and get a date on the quote. Every order is confirmed by a person before payment.

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.