In short
Verified authentic tags prove that a product is the real one. They are NTAG 424 DNA chips that make a new one-time code every time they are tapped. Linxy checks the code, so a copied tag or a copied link fails. Anyone can tap one with a phone, with or without the Linxy App, and sees Verified authentic or This tag could not be verified.
Write them in the Linxy App: More Tools › NFC Tags › Write Verified authentic tags, or choose Verified authentic on the TouchPoint Purpose step with NFC Tag.
On this page
What makes them different
An ordinary NFC tag, including a secure Linxy tag, always gives the same link. Anyone can read it and write that link onto another tag, and the copy works just as well. A Verified authentic tag adds a code that changes on every tap:
| Verified authentic tag | Linxy tag or standard tag | |
|---|---|---|
| The link it opens | Changes on every tap | The same every time |
| A copy of the tag or the link | Fails the check and shows a warning | Works like the original |
| The chip | NTAG 424 DNA only | Any NFC tag |
| Needs the Linxy App to tap | No | No |
| Point it somewhere else later | Yes | Linxy tag yes, standard tag no |
Each tag gets its own keys, made and kept by Linxy. While a tag is being written, the phone only passes messages between the tag and Linxy, so the keys never sit on the phone, and nobody can read them off the tag.
What you need
- NTAG 424 DNA tags, new and unused. Other chips, and tags already set up by someone else, are refused
- A phone that writes NFC tags: an iPhone XS or newer, or an Android phone with NFC turned on
- The record or page the tags will open: one of your Linxy records, a landing page or a bio page
Writing the tags
- Open the setupMore Tools › NFC Tags › Write Verified authentic tags. Or tap Create, choose NFC Tag, then Verified authentic.
- What it opensTap Choose, then One of my Linxy records or One of my pages.
- After a good tapShow the check, then open it shows Verified authentic first, with one tap to continue. Open it right away checks in the background and goes straight there. Copies get the warning page either way.
- Tell me about copiesOn, you get a push when a tap fails the check, with where it happened.
- WriteTap Continue to write tags and hold a tag to the phone for about 2 seconds while the four steps tick off: Read the chip, Lock in its own keys, Turn on the one-time code, Check a test tap. On iPhone, tap Write the next tag for each new tag. On Android, just hold the next tag to the phone.
Each tag gets a number (Tag No. 0001, 0002 and so on) for its record. Tap Done writing to see your tags.
What people see when they tap
| Result | What they see |
|---|---|
| Verified authentic | A gold card, the product, the tag number and how many times it has been tapped, then Continue. With Open it right away, they go straight to the content |
| Code already used | “This tag could not be verified. The code from this tap was already used.” Usually a copied link, or a copy of the tag |
| Code doesn’t match | “The code from this tap does not match this tag.” The tag or the link may be a copy |
| Tag turned off | “The owner turned this tag off. It may have been lost or stolen.” |
The warning page tells people to tap the tag again, because a real tag makes a new code each time, and not to trust it if it fails again.
Your tags, failed checks and lost tags
More Tools › NFC Tags › My Verified authentic tags shows how many tags you have, verified taps and failed checks, then each tag with its taps and its last tap. A tag whose last tap failed is shown in red, with where it happened.
- Lost or stolen tag: tap it in the list, then Turn off. Its taps then show the warning page. Turn it back on the same way
- More tags for the same product: tap Write more
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| “This tag is already set up, or it is not an NTAG 424 DNA” | The tag is another kind of chip, or was set up before | Use a new NTAG 424 DNA tag |
| “The tag moved away” | The tag left the phone part way through | Hold it still, flat against the phone, and write it again |
| “This setup timed out” | More than three minutes passed | Start again with the same tag |
| A real tag fails when tapped from a saved link or a screenshot | The saved link carries an old code | Expected. Tap the tag itself |
| Verified authentic is dimmed in the Create wizard | Linxy Mark or Short link was chosen in step 1 | Go back and choose NFC Tag |
| No push about a failed check | Tell me about copies is off, or app notifications are off | Turn them on. Failed checks still show in your list |
Things people commonly get wrong
Related reading: Secure NFC tags and standard NFC tags, Writing an NFC tag and Landing pages.