> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/linux/idevice.md).

# IDevice

Create an instance of the IDevice from CoreAPI::getDeviceList(). Then use the functions described in this chapter.

## getName <a href="#id-4.1_getname" id="id-4.1_getname"></a>

This function retrieves the name of the device.&#x20;

{% code overflow="wrap" %}

```
IDeviceControl* IDevice->getName() 
```

{% endcode %}

Return Value: IDeviceControl\*

## getConnectionInfo <a href="#id-4.2_getconnectioninfo" id="id-4.2_getconnectioninfo"></a>

This function retrieves the connection info of the device.&#x20;

{% code overflow="wrap" %}

```
ConnectionInfo IDevice->getConnectionInfo() 
```

{% endcode %}

Return Value: ConnectionInfo

## getConnectionState <a href="#id-4.3_getconnectionstate" id="id-4.3_getconnectionstate"></a>

This function retrieves the connection state of the device.&#x20;

{% code overflow="wrap" %}

```
ConnectionState IDevice->getConnectionState() 
```

{% endcode %}

Return Value: ConnectionState

## getDeviceInfo <a href="#id-4.4_getdeviceinfo" id="id-4.4_getdeviceinfo"></a>

This function retrieves the information class of the device.&#x20;

{% code overflow="wrap" %}

```
DeviceInfo IDevice->getDeviceInfo() 
```

{% endcode %}

Return Value: DeviceInfo

## getDeviceCapabilities <a href="#id-4.5_getdevicecapabilities" id="id-4.5_getdevicecapabilities"></a>

This function retrieves the device capabilities class of the device.&#x20;

{% code overflow="wrap" %}

```
DeviceCapability IDevice->getDeviceCapabilities() 
```

{% endcode %}

Return Value: DeviceCapability

## getDeviceControl <a href="#id-4.6_getdevicecontrol" id="id-4.6_getdevicecontrol"></a>

This function retrieves the device control class of the device.&#x20;

{% code overflow="wrap" %}

```
IDeviceControl* IDevice->getDeviceControl() 
```

{% endcode %}

Return Value: DeviceCapability

## getConfiguration <a href="#id-4.7_getconfiguration" id="id-4.7_getconfiguration"></a>

This function retrieves the device configuration class of the device.

{% code overflow="wrap" %}

```
IDeviceConfiguration* IDevice->getConfiguration()
```

{% endcode %}

Return Value: IDeviceConfiguration\*

## subscribeAll <a href="#id-4.8_subscribeall" id="id-4.8_subscribeall"></a>

This function allows the host to be notified of all events sent by the device.

{% code overflow="wrap" %}

```
bool IDevice->subscribeAll(IEventSubscriber* eventCallback)
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="137.18182373046875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top">eventCallback</td><td valign="top">Name of a class that implements the IEventSubscriber interface event.</td></tr></tbody></table>

Return Value: Truth of successful. Otherwise, returns false.

## unsubscribeAll <a href="#id-4.9_unsubscribeall" id="id-4.9_unsubscribeall"></a>

This function allows the host to no longer receive any events sent by the device.

{% code overflow="wrap" %}

```
bool IDevice->unsubscribeAll(IEventSubscriber* eventCallback)
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="138.09100341796875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top">eventCallback</td><td valign="top">Name of a class that implements the IEventSubscriber interface event.</td></tr></tbody></table>

Return Value: Truth of successful. Otherwise, returns false.

## startTransaction <a href="#id-4.10_starttransaction" id="id-4.10_starttransaction"></a>

This function starts a transaction. This function will automatically handle the opening and closing of a device. The transaction will be processed through multiple calls to the event OnEvent(). See API Walk Through for how to process an EMV transaction.

{% code overflow="wrap" %}

```
bool IDevice->startTransaction(ITransaction& transaction)
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="151.72735595703125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top">eventCallback</td><td valign="top">Name of a class that implements the IEventSubscriber interface event.</td></tr></tbody></table>

Return Value: Truth of successful. Otherwise, returns false.

## cancelTransaction <a href="#id-4.11_canceltransaction" id="id-4.11_canceltransaction"></a>

This function cancels a transaction. A transaction can only be canceled before a card is presented.

{% code overflow="wrap" %}

```
bool IDevice->cancelTransaction();
```

{% endcode %}

Return Value: True if canceled. Otherwise, returns false.

## sendSelection <a href="#id-4.12_sendselection" id="id-4.12_sendselection"></a>

This function sends a user selection to the device. The response data will be returned in the event OnEvent().

{% code overflow="wrap" %}

```
bool IDevice->sendSelection(IData data);
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="177.1817626953125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter for data</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p>Byte 0</p></td><td valign="top"><p>Status of User Selection:</p><ul><li>0x00 = User Selection Request completed, see Selection Result </li><li>0x01 = User Selection Request aborted, cancelled by user</li><li>0x02 = User Selection Request aborted, timeout</li></ul></td></tr><tr><td valign="top">Byte 1</td><td valign="top">The menu item selected by the user. This is a single byte zero based binary value.</td></tr></tbody></table>

Return Value: True if successful. Otherwise, returns false.

## sendAuthorization <a href="#id-4.13_sendauthorization" id="id-4.13_sendauthorization"></a>

This function sends the Authorization Response Code (ARPC) blob to the device. The response data will be returned in the event OnEvent(). See API Walk Through for how to process an EMV transaction.

{% code overflow="wrap" %}

```
bool IDevice->sendAuthorization(IData data);
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="144.45452880859375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top">data</td><td valign="top">Contains ARPC blob.</td></tr></tbody></table>

Return Value: True if successful. Otherwise, returns false.

## requestPAN <a href="#id-4.14_requestpan" id="id-4.14_requestpan"></a>

This function prompts the user to present their card and enter a PIN. A card is presented so that the device can retrieve the PAN, which is used for Format blocks requiring a PAN. The encrypted PIN block (EPB) will be returned in the event OnEvent().

For DynaFlex devices, this function starts a PIN session on the first call and shall be called again to send the PIN status to the device for completing the PIN session.

{% code overflow="wrap" %}

```
bool IDevice->requestPAN( 
    PANRequest Request, 
    PINRequest* pinRequest = NULL);
```

{% endcode %}

**PANRequest:**

<table data-header-hidden><thead><tr><th width="132" valign="top"></th><th width="174.818115234375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Type</td><td valign="top">Description</td></tr><tr><td valign="top">Timeout</td><td valign="top">unsigned char</td><td valign="top">Wait time in seconds.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="164.72723388671875" valign="top"></th><th width="118.727294921875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Type</td><td valign="top">Description</td></tr><tr><td valign="top">PaymentMethods</td><td valign="top">enum</td><td valign="top"><p>PaymentMethod enumeration.</p><p> </p><p>Usage:</p><ul><li>MSR = 1         - For magnetic stripe cards.</li><li>Contact = 2     - For EMV chip cards.</li><li>Contactless = 4 - For NFC contactless cards. </li><li>ManualEntry = 8 - For user to manually enter transaction data without any card access. When set to ManualEntry, the other payment methods do not apply.</li><li>BARCODE = 16    - For barcode transaction.</li><li>APPLE_VAS = 32 - For Apple VAS support.</li></ul></td></tr></tbody></table>

**PINRequest:**

<table data-header-hidden><thead><tr><th width="132.90911865234375" valign="top"></th><th width="147.45452880859375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Type</td><td valign="top">Description</td></tr><tr><td valign="top">Timeout</td><td valign="top">unsigned char</td><td valign="top">Wait time in seconds.</td></tr><tr><td valign="top">PINMode</td><td valign="top">unsigned char</td><td valign="top"><p>PIN mode.</p><p>Usage:</p><ul><li>0x00 - Enter PIN</li><li>0x01 - Enter PIN Amount </li><li>0x02 - Reenter PIN Amount </li><li>0x03 - Reenter PIN</li><li>0x04 - Verify PIN</li></ul><p> </p><p>For DynaFlex devices this is the User Interface Sequence:</p><ul><li>0x01 - Present Card / Enter PIN (start session)</li><li>0x04 - Present Card / Enter PIN / Enter PIN Again (start session)</li></ul><p> On the second call to requestPAN(), send the PIN status:</p><ul><li>0xFD - Cancel PIN Session (end session) </li><li>0xFE - PIN Entry Failed (end session) </li><li>0xFF - PIN Entry Successful (end session)</li></ul></td></tr><tr><td valign="top">MinLength</td><td valign="top">unsigned char</td><td valign="top">Minimum length of accepted PIN (>= 4).</td></tr><tr><td valign="top">MaxLength</td><td valign="top">unsigned char</td><td valign="top">Maximum length of accepted PIN (=&#x3C; 12).</td></tr><tr><td valign="top">Tone</td><td valign="top">unsigned char</td><td valign="top"><p>Tone to play when prompting for the PIN. Usage:</p><ul><li>0x00 - No sound </li><li>0x01 - One beep </li><li>0x02 - Two beeps</li></ul></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="132" valign="top"></th><th width="169.3636474609375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Type</td><td valign="top">Description</td></tr><tr><td valign="top">Format</td><td valign="top">unsigned char</td><td valign="top"><p>ISO format for the PIN block.</p><ul><li>0x00 - ISO Format 0 </li><li>0x01 – Reserved / Invalid </li><li>0x03 - ISO Format 3 </li><li>0x04 - ISO Format 4</li></ul></td></tr><tr><td valign="top">PAN</td><td valign="top">string</td><td valign="top">First 12 digits of the Primary Account Number. Leave blank if not required by the ISO format for the PIN block.</td></tr></tbody></table>

Return Value: True if successful. Otherwise, returns false.

## requestPIN <a href="#id-4.15_requestpin" id="id-4.15_requestpin"></a>

This function prompts the user to enter a PIN. The host must supply the PAN if the Format block selected requires a PAN. The encrypted PIN block (EPB) will be returned in the event OnEvent().

For DynaFlex devices, this function starts a PIN session on the first call and shall be called again to send the PIN status to the device for completing the PIN session.

{% code overflow="wrap" %}

```
bool IDevice->requestPIN(PINRequest Request); Request:
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="122.9090576171875" valign="top"></th><th width="163.3636474609375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Type</td><td valign="top">Description</td></tr><tr><td valign="top">Timeout</td><td valign="top">unsigned char</td><td valign="top">Wait time in seconds.</td></tr><tr><td valign="top">PINMode</td><td valign="top">unsigned char</td><td valign="top"><p>PIN mode.</p><p>Usage:</p><ul><li>0x00 - Enter PIN</li><li>0x01 - Enter PIN Amount </li><li>0x02 - Reenter PIN Amount </li><li>0x03 - Reenter PIN</li><li>0x04 - Verify PIN </li></ul><p>For DynaFlex devices this is the User Interface Sequence:</p><ul><li>0x00 - Enter PIN (start session)</li><li>0x02 - PIN Incorrect, Try Again (continue session) </li><li>0x03 - Enter PIN / Enter PIN Again (start session) </li><li>0x05 - Enter PIN Again (continue session)</li></ul><p> </p><p>On the second call to requestPIN(), send the PIN status:</p><ul><li>0xFD - Cancel PIN Session (end session) </li><li>0xFE - PIN Entry Failed (end session) </li><li>0xFF - PIN Entry Successful (end session)</li></ul></td></tr><tr><td valign="top">MinLength</td><td valign="top">unsigned char</td><td valign="top">Minimum length of accepted PIN (>= 4).</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="125.6363525390625" valign="top"></th><th width="163.272705078125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Type</td><td valign="top">Description</td></tr><tr><td valign="top">MaxLength</td><td valign="top">unsigned char</td><td valign="top">Maximum length of accepted PIN (=&#x3C; 12).</td></tr><tr><td valign="top">Tone</td><td valign="top">unsigned char</td><td valign="top"><p>Tone to play when prompting for the PIN. Usage:</p><ul><li>0x00 - No sound </li><li>0x01 - One beep </li><li>0x02 - Two beeps</li></ul></td></tr><tr><td valign="top">Format</td><td valign="top">unsigned char</td><td valign="top"><p>ISO format for the PIN block.</p><ul><li>0x00 - ISO Format 0 </li><li>0x01 - ISO Format 1 0x03 - ISO Format 3 </li><li>0x04 - ISO Format 4</li></ul></td></tr><tr><td valign="top">PAN</td><td valign="top">string</td><td valign="top">First 12 digits of the Primary Account Number. Leave blank.</td></tr></tbody></table>

Return Value: True if successful. Otherwise, returns false.

## requestSignature <a href="#id-4.16_requestsignature" id="id-4.16_requestsignature"></a>

This function prompts the user to enter a signature. The response data will be returned in the event OnEvent().

{% code overflow="wrap" %}

```
bool IDevice->requestSignature(unsigned char timeout);
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="168.09100341796875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top">timeout</td><td valign="top">Time in seconds for the operation to complete. 0x01 – 0xFF</td></tr></tbody></table>

Return Value: True of successful. Otherwise, returns false.

## sendNFCCommand <a href="#id-4.17_sendnfccommand" id="id-4.17_sendnfccommand"></a>

This function sends a command to an NFC tag type 2. The NFC tag must first be activated by calling startTransaction() with NFC enabled.

{% code overflow="wrap" %}

```
bool IDevice-> sendNFCCommand( 
    IData data,
    bool lastCommand, 
    bool encrypt);
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="139.9090576171875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>data</p></td><td valign="top"><p>Command to send to the NFC tag.</p><ul><li>Get Version</li><li>Read</li><li>Fast Read</li><li>Write</li><li>Compatibility Write</li><li>Read_Cnt</li><li>PWD_Auth</li><li>Read_Sig</li></ul><p> </p><p>For details of the command see the NFC commands table below or</p><p><mark style="color:red;"><strong>DynaFlex Family Programmer’s Manual</strong></mark></p></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p>lastCommand</p></td><td valign="top"><p>Determines if this is the last NFC command to complete the operation.</p><p> </p><p>true = This is the last command. Device will provide a single beep after receiving a successful response from the NFC tag. To send subsequent commands, the NFC tag must be activated by calling startTransaction() with NFC enabled.</p><p> </p><p>false = Expect more commands (Default).</p><p> </p><p>Either set to true or false, if the NFC tag command fails, device will provide a double beep.</p></td></tr><tr><td valign="top"><p> </p><p>encrypt</p></td><td valign="top"><p>Determines if data returned is to be encrypted.</p><p>true = Encrypt data</p><p>false = Do not encrypt data (Default)</p></td></tr></tbody></table>

Return Value: True of successful. Otherwise, returns false.

## **NFC Commands**

<table data-header-hidden><thead><tr><th width="130.18182373046875" valign="top"></th><th width="97.54547119140625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Command</td><td valign="top">Length</td><td valign="top">Field Value</td></tr><tr><td valign="top"><p> </p><p> </p><p>Get Version</p></td><td valign="top"><p> </p><p> </p><p>1</p></td><td valign="top"><p>The GET_VERSION command is used to retrieve information on the NTAG family, the product version, storage size and other product data required to identify the specific NTAG21x.</p><p> </p><p>Byte 0 = 0x60</p></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="120.18182373046875" valign="top"></th><th width="104.36358642578125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Command</td><td valign="top">Length</td><td valign="top">Field Value</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>Read</p></td><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>2</p></td><td valign="top"><p>The READ command requires a start page address, and returns the 16 bytes of four NTAG21x pages. For example, if address is 03h then pages 03h, 04h, 05h, 06h are returned. Special conditions apply if the READ command address is near the end of the accessible memory area. The special conditions also apply if at least part of the addressed pages is within a password protected area.</p><p> </p><ul><li>Byte 0 = 0x30</li><li>Byte 1 = Start Page Address</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p>Fast Read</p></td><td valign="top"><p> </p><p> </p><p> </p><p>3</p></td><td valign="top"><p>The FAST_READ command requires a start page address and an end page address and returns the all n*4 bytes of the addressed pages. For example, if the start address is 03h and the end address is 07h then pages 03h, 04h, 05h, 06h and 07h are returned.</p><p> </p><ul><li>Byte 0 = 0x3A</li><li>Byte 2 = Start Page Address </li><li>Byte 3 = End Page Address</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p>Write</p></td><td valign="top"><p> </p><p> </p><p>6</p></td><td valign="top"><p>The WRITE command requires a block address, and writes 4 bytes of data into the addressed NTAG21x page.</p><ul><li>Byte 0 = 0xA2</li><li>Byte 1 = Address to Write</li><li>Byte 2 to 5 = 4 Bytes of Data to Write</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>Compatibility Write</p></td><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>18</p></td><td valign="top"><p>The COMPATIBILITY_WRITE command is implemented to guarantee interoperability with the established MIFARE Classic PCD infrastructure, in case of coexistence of ticketing and NFC applications. Even though 16 bytes are transferred to NTAG21x, only the least significant 4 bytes (bytes 0 to 3) are written to the specified address. Set all the remaining bytes, 04h to 0Fh, to logic 00h.</p><p> </p><ul><li>Byte 0 = 0xA0</li><li>Byte 1 = Address to Write</li><li>Byte 2 to 17 = 16 Bytes of Data to Write (only least significant 4 bytes are written)</li></ul><p>Note: This command is sent in 2 steps, which the Firmware will handle</p><ol><li>&#x3C;CMD>&#x3C;Address to Write>&#x3C;CRCH>&#x3C;CRCL></li><li>&#x3C;16 Bytes of Data to Write>&#x3C;CRCH>&#x3C;CRCL></li></ol></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="120.1817626953125" valign="top"></th><th width="86.18182373046875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Command</td><td valign="top">Length</td><td valign="top">Field Value</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>READ_CNT</p></td><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>2</p></td><td valign="top"><p>The READ_CNT command is used to read out the current value of the NFC one-way counter of the NTAG213, NTAG215 and NTAG216. The command has a single argument specifying the counter number and returns the 24-bit counter value of the corresponding counter. If the NFC_CNT_PWD_PROT bit is set to 1b the counter is password protected and can only be read with the READ_CNT command after a previous valid password authentication</p><ul><li>Byte 0 = 0x39</li><li>Byte 1 = 0x02 (NFC Counter Address)</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>PWD_AUTH</p></td><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>5</p></td><td valign="top"><p>A protected memory area can be accessed only after a successful password verification using the PWD_AUTH command. The AUTH0 configuration byte defines the protected area. It specifies the first page that the password mechanism protects. The level of protection can be configured using the PROT bit either for write protection or read/write protection. The PWD_AUTH command takes the password as parameter and, if successful, returns the password authentication acknowledge, PACK. By setting the AUTHLIM configuration bits to a value larger than 000b, the number of unsuccessful password verifications can be limited. Each unsuccessful authentication is then counted in a counter featuring anti-tearing support. After reaching the limit of unsuccessful attempts, the memory access specified in PROT, is no longer possible.</p><p> </p><ul><li>Byte 0 = 0x1B</li><li>Byte 1..4 = password (4 bytes)</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p>READ_SIG</p></td><td valign="top"><p> </p><p> </p><p> </p><p>2</p></td><td valign="top"><p>The READ_SIG command returns an IC specific, 32-byte ECC signature, to verify NXP Semiconductors as the silicon vendor. The signature is programmed at chip production and cannot be changed afterwards.</p><p> </p><ul><li>Byte 0 = 0x3C</li><li>Byte 1 = 0x00, RFU</li></ul></td></tr></tbody></table>

## **Response Data For NFC Tag Type 2**

<table data-header-hidden><thead><tr><th width="74.6363525390625" valign="top"></th><th width="68.1817626953125" valign="top"></th><th width="152.6363525390625" valign="top"></th><th width="96.818115234375"></th><th></th></tr></thead><tbody><tr><td valign="top">Tag</td><td valign="top">Len</td><td colspan="3" valign="top">Value / Description</td></tr><tr><td valign="top"><p> </p><p>81</p></td><td valign="top"><p> </p><p>01</p></td><td colspan="3" valign="top">Tag Response Code 0x00 = Success 0x01 = Failed</td></tr><tr><td rowspan="8" valign="top">82</td><td rowspan="8" valign="top">var</td><td colspan="3" valign="top"><p>Encryption Control Payload</p><p> </p><p>If unencrypted:</p></td></tr><tr><td valign="top">Tag</td><td>Len</td><td>Value / Description</td></tr><tr><td valign="top">FC</td><td>var</td><td>NFC Data Container</td></tr><tr><td valign="top">/DF7A</td><td>var</td><td>NFC Data</td></tr><tr><td colspan="3" valign="top"><p> </p><p>If encrypted:</p></td></tr><tr><td valign="top">/DFDF59</td><td>var</td><td>Encrypted Data Primitive to be decrypted.</td></tr><tr><td valign="top">/DFDF50</td><td>var</td><td>Encrypted Data KSN</td></tr><tr><td valign="top">/DFDF51</td><td>01</td><td>Encrypted Data Encryption Type</td></tr></tbody></table>

**Example Unencrypted Payload for Fast Read**

{% code overflow="wrap" %}

```
81	0100 (Tag Respons Code)
82	82036D (Encryption Control)
        FC 820369 (NFC Data Container) 
                DF7A 820364 (NFC Data)
                        031391010F55047777772E6D616774656B2E636F6DFE00. . .
                                        www.magtek.com
```

{% endcode %}

**Example Encrypted Payload for Fast Read**

{% code overflow="wrap" %}

```
81	0100 (Tag Response code)
82	820389 (Encryption Control)
        DFDF59 820370 (Encrypted Data Primitive) 
                03679DC03B4CA607E3A7D2B52C8E9F1B5CD3D85E7368425. . .
        DFDF50 0A (Encrypted Data KSN) 
                FFFF9876543210200047
        DFDF51 01 (Encrypted Data Type) 
                80
```

{% endcode %}

## sendClassicNFCCommand <a href="#id-4.18_sendclassicnfccommand" id="id-4.18_sendclassicnfccommand"></a>

This function sends a command to a Mifare Classic NFC tag type 2. The NFC tag must first be activated by calling startTransaction() with NFC enabled.

{% code overflow="wrap" %}

```
bool IDevice-> sendClassicNFCCommand ( 
    IData data,
    bool lastCommand, 
    bool encrypt);
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="129.90911865234375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>data</p></td><td valign="top"><p>Command to send to the NFC tag.</p><ul><li>Get Version</li><li>Read</li><li>Fast Read</li><li>Write</li><li>Compatibility Write</li><li>Read Cnt</li><li>PWD Auth</li><li>Read Sig</li></ul><p> </p><p>For details of the command see NFC commands table below or</p><p><mark style="color:red;"><strong>DynaFlex Family Programmer’s Manual</strong></mark> </p></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p>lastCommand</p></td><td valign="top"><p>Determines if this is the last NFC command to complete the operation.</p><p> </p><p>true = This is the last command. Device will provide a single beep after receiving a successful response from the NFC tag. To send subsequent commands, the NFC tag must be activated by calling startTransaction() with NFC enabled.</p><p> </p><p>false = Expect more commands (Default).</p><p> </p><p>Either set to true or false, if the NFC tag command fails, device will provide a double beep.</p></td></tr><tr><td valign="top"><p> </p><p>encrypt</p></td><td valign="top"><p>Determines if data returned is to be encrypted.</p><p>true = Encrypt data</p><p>false = Do not encrypt data (Default)</p></td></tr></tbody></table>

Return Value: True of successful. Otherwise, returns false.

## **NFC Commands**

<table data-header-hidden><thead><tr><th width="120.18182373046875" valign="top"></th><th width="109.81817626953125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Command</td><td valign="top">Length</td><td valign="top">Field Value</td></tr><tr><td valign="top"><p> </p><p> </p><p>Get Version</p></td><td valign="top"><p> </p><p> </p><p>1</p></td><td valign="top"><p>The GET_VERSION command is used to retrieve information on the NTAG family, the product version, storage size and other product data required to identify the specific NTAG21x.</p><p> </p><p>Byte 0 = 0x60</p></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="126.54547119140625" valign="top"></th><th width="90.45458984375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Command</td><td valign="top">Length</td><td valign="top">Field Value</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>Read</p></td><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>2</p></td><td valign="top"><p>The READ command requires a start page address, and returns the 16 bytes of four NTAG21x pages. For example, if address is 03h then pages 03h, 04h, 05h, 06h are returned. Special conditions apply if the READ command address is near the end of the accessible memory area. The special conditions also apply if at least part of the addressed pages is within a password protected area.</p><p> </p><ul><li>Byte 0 = 0x30</li><li>Byte 1 = Start Page Address</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p>Fast Read</p></td><td valign="top"><p> </p><p> </p><p> </p><p>3</p></td><td valign="top"><p>The FAST_READ command requires a start page address and an end page address and returns the all n*4 bytes of the addressed pages. For example, if the start address is 03h and the end address is 07h then pages 03h, 04h, 05h, 06h and 07h are returned.</p><p> </p><ul><li>Byte 0 = 0x3A</li><li>Byte 2 = Start Page Address </li><li>Byte 3 = End Page Address</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p>Write</p></td><td valign="top"><p> </p><p> </p><p>6</p></td><td valign="top"><p>The WRITE command requires a block address, and writes 4 bytes of data into the addressed NTAG21x page.</p><ul><li>Byte 0 = 0xA2</li><li>Byte 1 = Address to Write</li><li>Byte 2 to 5 = 4 Bytes of Data to Write</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>Compatibility Write</p></td><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>18</p></td><td valign="top"><p>The COMPATIBILITY_WRITE command is implemented to guarantee interoperability with the established MIFARE Classic PCD infrastructure, in case of coexistence of ticketing and NFC applications. Even though 16 bytes are transferred to NTAG21x, only the least significant 4 bytes (bytes 0 to 3) are written to the specified address. Set all the remaining bytes, 04h to 0Fh, to logic 00h.</p><p> </p><ul><li>Byte 0 = 0xA0</li><li>Byte 1 = Address to Write</li><li>Byte 2 to 17 = 16 Bytes of Data to Write (only least significant 4 bytes are written)</li></ul><p>Note: This command is sent in 2 steps, which the Firmware will handle</p><ol><li>&#x3C;CMD>&#x3C;Address to Write>&#x3C;CRCH>&#x3C;CRCL></li><li>&#x3C;16 Bytes of Data to Write>&#x3C;CRCH>&#x3C;CRCL></li></ol></td></tr></tbody></table>

## sendDESFireNFCCommand <a href="#id-4.19_senddesfirenfccommand" id="id-4.19_senddesfirenfccommand"></a>

This function sends a command to an NFC Mifare DESFire Light Tag Type 4. The NFC tag must first be activated by calling startTransaction() with NFC enabled.

{% code overflow="wrap" %}

```
bool IDevice-> sendDESFireNFCCommand ( 
        IData data,
        bool lastCommand, 
        bool encrypt);
```

{% endcode %}

<table data-header-hidden><thead><tr><th width="112.6363525390625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Parameter</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p> </p><p>data</p></td><td valign="top"><p>Command to send to the NFC tag. See DESFire Data Sheet (MF2DLHX0). Should follow ISO 7816-4 APDU format.</p><p> </p><p>For details of the command see</p><p><mark style="color:red;"><strong>DynaFlex Family Programmer’s Manual</strong></mark> </p></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p>lastCommand</p></td><td valign="top"><p>Determines if this is the last NFC command to complete the operation.</p><p> </p><p>true = This is the last command. Device will provide a single beep after receiving a successful response from the NFC tag. To send subsequent commands, the NFC tag must be activated by calling startTransaction() with NFC enabled.</p><p> </p><p>false = Expect more commands (Default).</p><p> </p><p>Either set to true or false, if the NFC tag command fails, device will provide a double beep.</p></td></tr><tr><td valign="top"><p> </p><p>encrypt</p></td><td valign="top"><p>Determines if data returned is to be encrypted.</p><p>true = Encrypt data</p><p>false = Do not encrypt data (Default)</p></td></tr></tbody></table>

Return Value: True of successful. Otherwise, returns false.

## **Response Data For NFC Mifare DESFire Light Tag Type 4**

<table data-header-hidden><thead><tr><th width="65.6363525390625" valign="top"></th><th width="78.727294921875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Tag</td><td valign="top">Len</td><td valign="top">Value / Description</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p>81</p></td><td valign="top"><p> </p><p> </p><p> </p><p>02</p></td><td valign="top"><p>Tag Response (SW1 SW2). See DESFire Data Sheet (MF2DLHX0). Should follow ISO 7816-4 APDU format.</p><ul><li>SW1 and SW2 of R-APDU</li></ul><p>If card is not able to respond:</p><ul><li>SW1 = 0x64, SW2 = 0x00</li></ul></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="66.45452880859375" valign="top"></th><th width="64.727294921875" valign="top"></th><th width="166.181884765625" valign="top"></th><th width="96.3636474609375"></th><th></th></tr></thead><tbody><tr><td valign="top">Tag</td><td valign="top">Len</td><td colspan="3" valign="top">Value / Description</td></tr><tr><td rowspan="9" valign="top">82</td><td rowspan="9" valign="top">var</td><td colspan="3" valign="top"><p>Encryption Control Payload tag data</p><ul><li>Data of R-APDU</li></ul><p>If unencrypted:</p></td></tr><tr><td valign="top">Tag</td><td>Len</td><td>Value / Description</td></tr><tr><td valign="top">FC</td><td>var</td><td>NFC Data Container</td></tr><tr><td valign="top">/DF7A</td><td>var</td><td>NFC Data</td></tr><tr><td colspan="3" valign="top"><p> </p><p>If encrypted:</p></td></tr><tr><td valign="top">Tag</td><td>Len</td><td>Value / Description</td></tr><tr><td valign="top">/DFDF59</td><td>var</td><td>Encrypted Data Primitive to be decrypted.</td></tr><tr><td valign="top">/DFDF50</td><td>var</td><td>Encrypted Data KSN</td></tr><tr><td valign="top">/DFDF51</td><td>01</td><td>Encrypted Data Encryption Type</td></tr></tbody></table>

**Example Unencrypted Payload**

{% code overflow="wrap" %}

```
81	0100 (Tag Respons Code)
82	82036D (Encryption Control)
        FC 820369 (NFC Data Container) 
        DF7A 820364 (NFC Data)
                031391010F55047777772E6D616774656B2E636F6DFE00. . .
                        www.magtek.com
```

{% endcode %}

**Example Encrypted Payload**

{% code overflow="wrap" %}

```
81	0100 (Tag Response code)
82	820389 (Encryption Control)
        DFDF59 820370 (Encrypted Data Primitive)
                03679DC03B4CA607E3A7D2B52C8E9F1B5CD3D85E7368425. . .
        DFDF50 0A (Encrypted Data KSN) 
                FFFF9876543210200047
        DFDF51 01 (Encrypted Data Type) 
        80
```

{% endcode %}

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/linux/idevice.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
