Authenticate the physical O-KEY—not just its identifier
Compare a new capture of the O-KEY with its registered physical reference and return a clear, recorded result.
From new capture to recorded result
Retrieve the registered reference
Identify the O-KEY and retrieve the physical reference recorded at registration.
Guide the new capture
Help the authorized user capture the physical O-KEY under the required operating conditions.
Compare the physical patterns
Use computer-vision models trained for O-KEY comparison to evaluate the new capture against the registered reference.
Return and record the result
Return Authentic or Not matched, keep technical errors separate and record the attempt for follow-up.
Product-level visibility to support action against unauthorized resale.
Seamless implementation gave us instant supply chain visibility.
How authentication works in practice
What is actually being compared?
A new capture of the physical O-KEY is compared with the registered reference for that item. The decision is not based only on reading a valid identifier.
What should happen after a result?
Authentic confirms that the captured O-KEY matched its registered reference. Not matched means the comparison failed and should trigger your defined follow-up, not an automatic counterfeit conclusion.
Who owns the operating policy?
Usually the team responsible for product risk, quality, safety or protection, with operations and IT where needed. We help define roles, operating conditions and follow-up.
How are security and usability validated?
Authentication settings are validated for the product, device, environment, user and required security level before wider deployment.
Start with the product you want to protect.
All content is the property of PUFIN—ID. No parts of this site including text and images, may be reproduced without prior written consent of PUFIN—ID.
