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.
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.
The moving pieces
Behind that flow sit four parts, and the customer’s browser is the only client. There’s nothing to install on either side.
Dynamic NFC tags. Each tag emits a fresh verification URL on every tap. The material that proves authenticity lives on the tag and is checked server-side. Tags are programmed before they ship on products: either preconfigured by TAGBASE, or written by you with the TAGBASE Writer app (see your first product).
The browser. Any NFC-capable phone, any modern browser. Tapping opens the verification URL. The customer needs no app and no login.
The verification backend. It validates each tap, runs the two-scan liveness check, and records the result. Clients are never trusted with verification logic.
The brand dashboard. Brands manage products and tags, watch verifications live on a map, and review history and statistics. See using the dashboard.
Next: the security model behind this flow.