Short answer: First identify which side of the NFC exchange the handheld must occupy. Reading an asset tag requires a reader role; presenting a credential to another terminal requires a supported card-emulation path. A successful tag read does not establish card-emulation compatibility.
Draw the two endpoints
For asset inspection, the handheld reads the tag attached to the item and the app uses the returned data. In a credential-presentation workflow, another terminal acts as the reader and the handheld must respond with the expected application protocol.
List the counterpart tag or terminal, data format and security method. If both workflows are required, test them separately. UHF inventory capability concerns a different radio technology and does not establish either NFC role.
Distinguish HCE from secure-element emulation
Android’s host-based card emulation documentation distinguishes exchanges routed to an Android service from those handled by a secure element. HCE is an ISO-DEP/APDU path, not a general method for reproducing every existing credential.
Confirm the application identifier and protocol expected by the terminal. For an HCE design, check the required feature on the actual build and demonstrate service selection. If a secure element is required, obtain evidence for that specific hardware and provisioning arrangement.
Test the required device and credential states
Use a controlled sample with an authorized credential, then repeat with a revoked credential, the required lock state and the intended screen-on or screen-off condition. Record terminal exchange, application response and the system’s accepted or rejected decision.
If nothing is detected, check the roles and radio technology. If the terminal detects the device but selects no application, inspect protocol and application identifier. If the exchange works but the system refuses it, investigate provisioning and authorization rather than repeatedly changing tap position.
Keep identity and purchase evidence separate
Android’s HCE documentation says the presented UID should be assumed random. Do not use it as a permanent employee or asset key. Tag-to-record mapping and credential authorization require their own application rules.
Send the counterpart specification, exact device and OS build, required role, credential application, provisioning owner and operating states through Integration & Support. Keep asset-reading results separate from credential-presentation results, and retain secrets outside the review report.
Device options for this task
The AIDC GO HX-21 and AIDC GO HX-24 specifications list 13.56 MHz NFC. For a proposed tag or credential workflow, request the exact protocol, supported role and application evidence for the chosen build of these Android PDA Barcode Scanners.
Devices for this workflow
