Start with a Maker account, qualified NFC tags, and registered inventory for Brand Verification or Device Control. This guide covers manufacturing preparation, then follows the detailed Device Control process for assigning a protected item to its owner.
Leather, textiles, metal casings, and packaging each affect the NFC installation. We help specify a supported ISO-DEP Type 4 tag and suitable form factor, then plan its integration during assembly, sewing, labeling, or packaging.
Qualify read performance, attachment, environmental exposure, and production handling with the finished product before scaling up.
See NFC setup for both servicesBrand Verification: register your brand and website, associate its NFC tags, and let consumers authenticate them in the app before viewing your brand's website.
Device Control: define the protected action, register the device, and prepare the owner enrollment and authorization flow described below.
The Product Brand is the Xibernetix Maker. It creates the Maker account and item records, specifies the NFC-tag requirements, imports the tag manifest, and packages each approved tag with its product, asset, or device.
Produces NFC Forum Type 4 tags that meet the Product Brand's requirements and supplies a manifest that identifies every tag and its manufacturing details.
Receives the signed-in Product Brand's tag manifest, keeps the imported inventory scoped to that Maker account, and provides the authenticated provisioning and verification path.
Installs the Xibernetix app, signs in, and makes the first tap that associates the finished product, asset, or device and its NFC tag with their verified account.
Every tag assigned to a Product Brand must appear in the manufacturer's manifest and be uploaded through the Maker-authenticated import flow before it is used in a protected product.
The tag begins with its UID and a generic factory master key. Xibernetix uses the identity to establish protected key material during provisioning. Because the generic key is shared, a rogue app that obtains it could attempt to access or provision the tag before the approved flow secures it.
The manufacturer generates an assigned master key and programs it into the tag's secure storage before delivery. When that key remains confidential and the tag is registered in the manifest, access is restricted to the Xibernetix backend and authorized mobile-app workflow.
The Maker uploads the manifest of assigned tags to Xibernetix. This records the inventory under the Maker account and lets the platform match each physical tag to its approved product, asset, or device.
The manifest import happens before the finished product, asset, or device reaches its owner. Tag personalization happens during the owner's first enrollment tap.
The Product Brand signs up and establishes its Xibernetix Maker account.
The Product Brand adds its product, asset, or device to Xibernetix with the metadata needed to identify, manage, and support it.
The Product Brand decides that NFC tags will secure the item and defines the tag, form factor, and environmental requirements.
The NFC Tag Manufacturer delivers NFC Forum Type 4 tags using the selected credential model and a JSON manifest containing each tag ID and its detailed manufacturing information.
While signed in, the Product Brand uploads the JSON manifest through the dedicated Maker-authenticated endpoint. Xibernetix validates and records the tag inventory under that Maker account.
The approved NFC tag is installed or enclosed during the qualified assembly, sewing, labeling, or packaging step before the product, asset, or device is shipped or sold.
The product documentation directs the buyer to install the Xibernetix app and create or sign in to an Operator account.
With the app installed and the Operator signed in, the Owner taps their mobile device to the finished product, asset, or device. The app reads the NFC tag and its ID.
The app requests the tag-specific cryptographic material through the authenticated backend flow. If the tag already contains the expected protected key material, the app verifies it and locks the configuration. If it is still raw, the app writes the protected material and locks it against later modification or reading.
The authenticated NFC tag and its protected product, asset, or device are assigned to the signed-in Owner. On later use, that Owner signs in and taps again; Xibernetix recognizes the authenticated tag and permits the associated item flow only for its assigned Owner.
NFC Tag Manufacturer manifest
↓
Product Brand authenticated import
↓
protected item + raw tag package
↓
first operator tap
↓
authenticated, dedicated itemIf a protected item is replaced, transferred, lost, or retired, use the authorized lifecycle process before giving it to another person. Do not treat a configured tag as raw inventory or attempt to overwrite its protected configuration.
Read the NFC guide