Frequently Asked Questions

Is CID supported?

CID is and optional feature of cards and readers, using the T4T/ISO-DEP protocol. It was designed to communicate with multiple cards simultaneously. The PTX1K does not support CID. Communication with such cards will work using the data exchange function, but CID will have no effect, even if the card supports it.

Is AID supported?

AID stands for Application Identifier. The function ptxNSC_RoutingTable_AddEntryAid()  is a left-over piece from an early release of the 1K SDK, when connection to secure elements was supported. This is not the case any more however and this function is not to be used, especially not above the NSC level.

Routing tables are not related to reader mode at all. In that case, AID is purely and application payload. If you wish to use AID, it needs to be encapsulated in the application-specific command, and transmitted using the ptxPOS_Data_Exchange()  function.

In card emulation mode, only Host Card Emulation is supported, which means all traffic from the reader is forwarded to the host.

Is CCID supported?

Chip Card Interface Device is a USB protocol, which is designed to connect a smart card to a computer using a smart card reader. Since it is not NFC, it has nothing to do with the PTX reader or the SDKs.

Is RFCA supported?

RF Collision Avoidance means, that the reader should stop polling as long as an external field is detected (i. e. another reader is polling in the immediate vicinity). This is supported by the IOT Reader SDK, where listening while polling can be done inside the discovery loop. In case listening for Type-A tags is enabled, and an external field is detected, polling is stopped, and a Type-4 tag is emulated. The external reader can then exchange data with the emulated tag. This is called Host Card Emulation.

In case of the POS SDK, polling and listening are mutually exclusive. If ListenTypeA  (listening) is enabled in ptxEMVCO_LOOPBACK.c , there will be no polling at all, but HCE will be run. The EMVCo loopback app will only work, if listening is disabled. The reason is, that listening would be problematic with the Polling Loop as defined by the EMVCo v3.2 specifications. Introducing listening mode while polling would also require major changes to the POS API.

If RFCA is required, the IOT Reader SDK must be used.