Issue with Custom HCE AID Routing on Samsung Device (ISO 18013-5 mdoc)

Mobile
1

Hello,

We are developing a mobile identity (mdoc) solution based on the ISO 18013-5 standard, which requires our application to emulate a Type 4 NFC Tag using the Application Identifier (AID) A0 00 00 02 48 04 00.

During our tests, we noticed that Samsung devices do not route SELECT commands for this specific AID to our Host Card Emulation (HCE) service, even though it is correctly declared in the HCE manifest XML. The same implementation works as expected on other Android devices (such as Google Pixel), where the SELECT command is properly received and handled by our app.

Steps to reproduce:

  1. Register an HCE service with the AID A0 00 00 02 48 04 00 in the manifest.
  2. Deploy the app on a Samsung device with NFC.
  3. Use an external NFC reader to send a SELECT command with this AID.
  4. Observe that the SELECT is not routed to the HCE service (no callback is triggered).

Request:
We kindly ask for clarification on the handling of custom AIDs for HCE on Samsung devices, and whether it is possible to have this specific AID whitelisted or supported for mobile identity solutions as described in ISO 18013-5.

This AID is defined by the ISO standard for digital documents and is required for interoperability across devices.

3

Hello.
Please create a support request in the Samsung Developer Technical Support Portal with more details about the issue and affected device.

Best Regards,
Ahsan