Verifying a product takes two taps and happens entirely in the browser.
Tap-to-verify flow
- A customer taps the product’s NFC tag with their phone.
- The tag produces a fresh, single-use verification URL.
- The browser opens it and asks the TAGBASE backend to verify the tag.
- The backend confirms the tag is genuine and tracks the verification.
- The page shows a result (authentic or not), optionally with product content.
Why two scans
The first tap starts a short-lived verification and shows a “tap again” prompt. The second tap is a liveness proof. A genuine tag produces new material on the second tap, while a static clone can only replay the first. Comparing the two taps is what separates live hardware from a captured snapshot.
Tap 1 → fresh URL → pending (backend records the first tap)
Tap 2 → fresh URL → valid (backend confirms the tag is live)
A single captured URL written to a cheap tag passes the first tap but fails the second, so it never reaches a valid result.
What the customer sees
- They tap a product, say a luxury perfume.
- A browser page opens instantly, with no app.
- They tap once more to confirm.
- They see a clear result: authentic or not authentic.
When valid, the page can also show the product name, image or video, the brand’s domain, and optional documents such as a warranty, manual, or certificate. The brand configures all of it.
See the security model for the threat model behind this flow.