← Back to the chapter · Previous detail
Technical detail · How NFC Taps Work
Diagnose a copied label that opens an unapproved host
First name the failure precisely: unreadable tag, multiple targets, unsupported record, wrong host, stale asset reference, unauthorized action, privacy issue, or installed-placement failure. These observations lead to different investigations.
If a phone reliably reads a copied gateway label but opens an unapproved host, investigate payload-to-parser and policy-to-action first. Review allowed host, schema, length, object state, session rule, audit, fallback, and copy handling. More tag capacity cannot prevent copying or enforce host restrictions. Changing phone orientation addresses intermittent reads rather than a reliably decoded, disallowed destination.
Check the closest lower proof. Inspect parsing when the wrong record opens; inspect placement and orientation when reads are intermittent. Change one variable at a time: tag type, record size, lock state, surface material, phone case, parser, session rule, or fallback flow. Record which change altered the evidence trail.
Finally, write the unsupported claim. A test covering one label, one phone fleet, or one payload schema grants approval only within that boundary. A successful tap cannot remove the need to check a decoded destination or authorize the requested maintenance action.