How does FirstScanIt work?
FirstScanIt has four parts: the maker signs, the pack travels, the buyer scans, and the answer comes back. Only the first part needs any work from the manufacturer.
From factory to phone
The journey of one pack
What makes a FirstScanIt code hard to fake?
When a code is created, the product details (product, batch, serial and dates) are signed with a key that belongs to the maker. Any phone can check that signature, but nobody can create a new valid one without the maker’s key. It is the same kind of mathematics that protects online banking.
Change one character and the check fails. If a counterfeiter edits the batch number, the expiry date or anything else in the code, the signature no longer matches and the buyer sees a red warning.
How are photocopied codes caught?
A counterfeiter’s easiest trick is to buy one real pack and copy its code onto many fakes. The copy carries a real signature, so FirstScanIt also looks at each code’s scan history. A real pack is sold once and scanned in one place. A copied code keeps appearing in new places.
Where one code is scanned over 30 days
What happens when a batch is recalled?
The maker marks the batch as recalled in the dashboard. From the next scan onward, every pack from that batch shows a red recall warning on the buyer’s phone, wherever the pack is.
What results can a scan show?
The five results
The maker signed this code and its history looks normal. Safe to buy.
A real code that was checked before. Look at the count and first-scan city.
The maker did not create this code, or it was altered. Do not buy.
The maker has pulled this batch. Do not use it.
Genuine, but past its expiry date. The date is shown.
Next steps
FirstScanIt provides technology-assisted verification based on the maker’s digital signature and scan records. Plain-text version