NFC Implementation
Last updated
Was this helpful?
Last updated
Was this helpful?
If you already have a native app, you can also leverage native NFC reading capabilities within the app to read NFC tags programmed by Legitimate. To do so, please refer to the standard documentation to trigger the NFC reading capabilities of the mobile app operating system that you are developing for.
For further clarity, your application must be able to read NFC tags programmed to emit data in NDEF format. This is a fairly standard capability, with support from all major mobile operating systems and frameworks. We've included links to some standard libraries and resources below:
(multiple libraries exist)
After successfully setting up NFC read support in your native application, you should be able to trigger an NFC reading session on your phone. Scanning a Legitimate NFC tag should yield data in the following format:
The URL parameters can then be used to call the tag related APIs.
Each time an NFC tag is scanned, a new set of verification parameters will be generated. Therefore, if you are intending to use the Tag URL Redirect features, it is extremely important to note that . This is meant to protect the connected products from counterfeit and ensure that each scan is unique.
User opens Native App and triggers an NFC read action
iOS applications will trigger a native OS-level user NFC prompt
The NFC tag is read and NDEF data is returned to the mobile app
The uid, ctr, and cmac is used to verify the tag's authenticity and get information about the content for the tag.
You can call a set of APIs to obtain the NFT and blockchain information associated with the tag. With the given information about the NFT, you can then call our APIs to transfer the NFT to a given wallet or reset ownership when the item is sold or given away.