> 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/enumerations.md).

# Enumerations

## BarCodeFormat

This enum refers to the type of barcodes to display.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">BARCODE_FORMAT_BLOB</td><td valign="top">Data is binary format</td></tr><tr><td valign="top">BARCODE_FORMAT_COMMAND</td><td valign="top">Data is a command in binary format</td></tr><tr><td valign="top">BARCODE_FORMAT_BLOB_BASE64</td><td valign="top">Data is Base64 encoded format</td></tr><tr><td valign="top">BARCODE_FORMAT_COMMAND_BASE64</td><td valign="top">Data is a command in Base64 format</td></tr></tbody></table>

## BarCodeType <a href="#id-13.2_barcodetype" id="id-13.2_barcodetype"></a>

This enum refers to the type of barcodes to display.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">QRCODE</td><td valign="top">QR code</td></tr></tbody></table>

## ConnectionState <a href="#id-13.3_connectionstate" id="id-13.3_connectionstate"></a>

This enum refers to the readiness of the SDK to communicate with the device. This is not the physical attachment to a host system.

<table data-header-hidden><thead><tr><th width="312.6363525390625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">CONNECTION_STATE_Unknown</td><td valign="top">Device is in an unknown connection state.</td></tr><tr><td valign="top">CONNECTION_STATE_Disconnected</td><td valign="top">Device is disconnected.</td></tr><tr><td valign="top">CONNECTION_STATE_Connecting</td><td valign="top">Device is in the process of connecting. The next state is to be Connected.</td></tr><tr><td valign="top">CONNECTION_STATE_Error</td><td valign="top">There was an error either connecting or disconnecting the device.</td></tr><tr><td valign="top">CONNECTION_STATE_Connected</td><td valign="top">Device is connected and ready for transacting.</td></tr><tr><td valign="top">CONNECTION_STATE_Disconnecting</td><td valign="top">Device is in the process of disconnecting. The next state will is to be Disconnected.</td></tr></tbody></table>

## DeviceEvent <a href="#id-13.4_deviceevent" id="id-13.4_deviceevent"></a>

This enum refers to a change in the device status.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_DEVICE_EVENT_None</td><td valign="top">No event to report.</td></tr><tr><td valign="top">MTU_DEVICE_EVENT_DeviceResetOccurred</td><td valign="top">A device reset had occurred.</td></tr><tr><td valign="top"><p> </p><p>MTU_DEVICE_EVENT_DeviceResetWillOccur</p></td><td valign="top">A device reset will occur soon. Host application may uses this as a warning to take appropriate actions.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_DEVICE_EVENT_DeviceBondingFailure</td><td valign="top"> </td></tr><tr><td valign="top">MTU_DEVICE_EVENT_DeviceTemperatureLow</td><td valign="top"> </td></tr><tr><td valign="top">MTU_DEVICE_EVENT_DeviceTemperatureHigh</td><td valign="top"> </td></tr></tbody></table>

## DeviceFeature <a href="#id-13.5_devicefeature" id="id-13.5_devicefeature"></a>

This enum refers to a featured supported by the device.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_None</td><td valign="top">No feature</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_SignatureCapture</td><td valign="top">Supports signature capture</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_PINEntry</td><td valign="top">Supports PIN entry</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_PANEntry</td><td valign="top">Supports PAN entry</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_ShowBarCode</td><td valign="top">Supports display of a barcode</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_ScanBarCode</td><td valign="top">Supports scanning a barcode</td></tr><tr><td valign="top">MTU_DEVICE_FEATURE_DisplayMessage</td><td valign="top">Supports display of a messsage</td></tr></tbody></table>

## EventType <a href="#id-13.6_eventtype" id="id-13.6_eventtype"></a>

This enum refers to the type of event triggered by the device.

<table data-header-hidden><thead><tr><th width="331.727294921875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">EVENT_TYPE_Invalid</td><td valign="top">Invalid</td></tr><tr><td valign="top">EVENT_TYPE_ConnectionState</td><td valign="top">There was a change in the connection state of the device.</td></tr><tr><td valign="top">EVENT_TYPE_DeviceResponse</td><td valign="top">Device has responded to a command.</td></tr><tr><td valign="top">EVENT_TYPE_DeviceExtendedResponse</td><td valign="top">Device has responded to an extended command.</td></tr><tr><td valign="top">EVENT_TYPE_DeviceNotification</td><td valign="top">Device has sent a notification.</td></tr><tr><td valign="top">EVENT_TYPE_DeviceTransferCancelled</td><td valign="top">Device has cancelled data transfer.</td></tr><tr><td valign="top">EVENT_TYPE_CardData</td><td valign="top">Device has sent magnetic stripe data from a card swipe.</td></tr><tr><td valign="top">EVENT_TYPE_TransactionStatus</td><td valign="top">There was a change in transaction status.</td></tr><tr><td valign="top">EVENT_TYPE_DisplayMessage</td><td valign="top">Device has a message to display for the user.</td></tr><tr><td valign="top">EVENT_TYPE_InputRequest</td><td valign="top">Device is requesting input from the user.</td></tr><tr><td valign="top"><p> </p><p>EVENT_TYPE_AuthorizationRequest</p></td><td valign="top">Device has sent the Authorization Request Cryptogram and associated block of EMV tags for a transaction. This block is meant to be sent to the transaction processor.</td></tr><tr><td valign="top">EVENT_TYPE_TransactionResult</td><td valign="top">Device has sent the result of the transaction.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="265.3636474609375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">EVENT_TYPE_PINBlock</td><td valign="top">Device has sent the PINBlock after the user has entered a PIN on the device.</td></tr><tr><td valign="top">EVENT_TYPE_Signature</td><td valign="top">Device has sent data which represents a signature from a user.</td></tr><tr><td valign="top">EVENT_TYPE_DeviceDataFile</td><td valign="top">Device has sent a data file.</td></tr><tr><td valign="top">EVENT_TYPE_OperationStatus</td><td valign="top">Device has sent an operation status of a command.</td></tr><tr><td valign="top">EVENT_TYPE_DeviceEvent</td><td valign="top">Device has sent change of device state.</td></tr><tr><td valign="top">EVENT_TYPE_UserEvent</td><td valign="top">Device has sent a notification related to user interaction with the device.</td></tr><tr><td valign="top">EVENT_TYPE_FeatureStatus</td><td valign="top">Device has sent data related to a feature.</td></tr><tr><td valign="top">EVENT_TYPE_PINData</td><td valign="top">Device has sent data related to a PIN.</td></tr><tr><td valign="top">EVENT_TYPE_PANData</td><td valign="top">Device has sent data related to a PAN.</td></tr><tr><td valign="top">EVENT_TYPE_BarCodeData</td><td valign="top">Device has sent barcode data.</td></tr><tr><td valign="top">EVENT_TYPE_NFCEvent</td><td valign="top">Device has sent an NFC event.</td></tr><tr><td valign="top">EVENT_TYPE_NFCData</td><td valign="top">Device has sent data related to NFC tag.</td></tr><tr><td valign="top">EVENT_TYPE_NFCResponse</td><td valign="top">Device has sent an NFC response.</td></tr></tbody></table>

## FeatureStatus <a href="#id-13.7_featurestatus" id="id-13.7_featurestatus"></a>

This enum refers to the status of a specific feature reported from DeviceFeature.

<table data-header-hidden><thead><tr><th width="325.3636474609375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_NoStatus</td><td valign="top">No change in status</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_Success</td><td valign="top">Success</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_Failed</td><td valign="top">Failed</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_TimedOut</td><td valign="top">Timed out</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_Cancelled</td><td valign="top">Cancelled</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_Error</td><td valign="top">Error</td></tr><tr><td valign="top">MTU_FEATURE_STATUS_HardwareNA</td><td valign="top">Featured hardware not applicable for a status</td></tr></tbody></table>

## ImageType <a href="#id-13.8_imagetype" id="id-13.8_imagetype"></a>

This enum refers to the type of image.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">IMAGE_TYPE_BITMAP</td><td valign="top">BMP file</td></tr></tbody></table>

## InfoType <a href="#id-13.9_infotype" id="id-13.9_infotype"></a>

This enum refers to the type of specific information to retrieve from the device.

<table data-header-hidden><thead><tr><th width="279.9090576171875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">INFOTYPE_DeviceSerialNumber</td><td valign="top">Device serial number.</td></tr><tr><td valign="top">INFOTYPE_FirmwareVersion</td><td valign="top">Firmware version of the device.</td></tr><tr><td valign="top">INFOTYPE_DeviceCapabilities</td><td valign="top">Capabilities of the device delimited by a comma.</td></tr><tr><td valign="top">INFOTYPE_Boot1Version</td><td valign="top">Boot 1 firmware version of the device.</td></tr><tr><td valign="top">INFOTYPE_Boot0Version</td><td valign="top">Boot 0 firmware version of the device.</td></tr><tr><td valign="top">INFOTYPE_FirmwareHash</td><td valign="top">Firmware hash comprised of part numbers, versions, and timestamps.</td></tr><tr><td valign="top"><p> </p><p>INFOTYPE_TamperStatus</p></td><td valign="top"><p>Tamper status of the device. 0x00 = Not Tampered</p><p>0x01 = Tampered</p></td></tr><tr><td valign="top"><p> </p><p>INFOTYPE_OperationStatus</p></td><td valign="top"><p>Operation status of the device. 0x01 = Offline</p><p>0x02 = Online</p></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>INFOTYPE_OfflineDetail</p></td><td valign="top"><p>Details of why the device is offline.</p><p>·         Bit 0 = Tamper problem present</p><p>·         Bit 1 = Master Key problem present</p><p>·         Bit 2 = Keys and Certificates problem present</p><p>·         Bit 3 = Real Time Clock problem present</p><p>·         Bit 4 = Random Number Generator problem present</p><p>·         Bit 5 = Cryptography Engine problem present</p><p>·         Bit 6 = Magnetic Stripe Reader Hardware problem present</p><p>·         Bit 7 = Reserved</p></td></tr><tr><td valign="top">INFOTYPE DeviceModel</td><td valign="top">Device model.</td></tr></tbody></table>

## MTU\_DEVICE\_CONNECTION\_TYPE <a href="#id-13.10_mtu_device_connection_type" id="id-13.10_mtu_device_connection_type"></a>

This enum refers to the communication interface type of MagTek reader which the SDK will control.

<table data-header-hidden><thead><tr><th width="161.727294921875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_USB</td><td valign="top">Universal Serial Bus supported devices:</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="176.27276611328125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top"> </td><td valign="top"><ul><li>eDynamo</li><li>mDynamo</li><li>DynaPro</li><li>Dynamag</li><li>DynaPro Go</li><li>DynaMax</li><li>DynaPro Mini</li><li>tDynamo</li><li>DynaFlex</li><li>kDynamo</li><li>DynaFlex Pro</li><li>cDynamo</li><li>DynaProx</li><li>iDynamo 6</li></ul></td></tr><tr><td valign="top">MTU_BLE</td><td valign="top"><p>Bluetooth Low Energy devices:</p><ul><li>DynaMax</li></ul></td></tr><tr><td valign="top">MTU_BLE_EMV</td><td valign="top"><p>Bluetooth Low Energy with EMV supported devices:</p><ul><li>eDynamo</li></ul></td></tr><tr><td valign="top">MTU_BLE_EMVT</td><td valign="top"><p>Bluetooth Low Energy with EMV supported devices:</p><ul><li>tDynamo</li></ul></td></tr><tr><td valign="top">MTU_TCP</td><td valign="top"><p>Transmission Control Protocol supported devices:</p><ul><li>DynaPro</li></ul></td></tr><tr><td valign="top"><p> </p><p>MTU_TLS12</p></td><td valign="top"><p>Transmission Control Protocol with Transport Layer Security supported devices:</p><ul><li>DynaPro Go</li></ul></td></tr><tr><td valign="top"><p> </p><p>MTU_TLS12_TRUST</p></td><td valign="top"><p>Transmission Control Protocol with Transport Layer Security supported devices:</p><ul><li>DynaPro Go</li></ul></td></tr><tr><td valign="top">MTU_SERIAL</td><td valign="top">UART supported devices</td></tr><tr><td valign="top">MTU_WS</td><td valign="top"><p>WebSocket supported devices:</p><ul><li>DynaFlex II PED</li></ul></td></tr><tr><td valign="top"><p> </p><p>MTU_WS_TRUST</p></td><td valign="top"><p>WebSocket supported devices. This will TLS connection to device without requirement for name match.</p><ul><li>DynaFlex II PED</li></ul></td></tr><tr><td valign="top">MTU_LIGHTNING</td><td valign="top"><p>Audio devices:</p><ul><li>iDynamo 6</li></ul></td></tr></tbody></table>

## MTU\_DEVICE\_TYPE <a href="#id-13.11_mtu_device_type" id="id-13.11_mtu_device_type"></a>

This enum refers to the type of MagTek reader which the SDK will control.

<table data-header-hidden><thead><tr><th width="120.81817626953125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p>SCRA</p></td><td valign="top"><p>Secure Reader Authenticator devices. List includes but not limited to:</p><ul><li>eDynamo</li><li>mDynamo</li><li>Dynamag</li><li>DynaMax</li><li>tDynamo</li><li>kDynamo</li><li>cDynamo</li><li>iDynamo 6</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p>PPSCRA</p></td><td valign="top"><p>PIN Pad Secure Reader Authenticator devices. List includes but not limited to:</p><ul><li>DynaPro</li><li>DynaPro Go</li><li>DynaPro Mini</li></ul></td></tr><tr><td valign="top"><p> </p><p>CMF</p></td><td valign="top"><p>Common Message Structure devices. List includes but not limited to:</p><ul><li>oDynamo</li></ul></td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p>MMS</p></td><td valign="top"><p>MMS class devices. (MagTek Message Scheme) List includes but not limited to:</p><ul><li>DynaFlex</li><li>DynaFlex Pro</li><li>DynaProx</li><li>DynaFlex II PED (USB-C)</li><li>DynaFlex II Go (USB-C)</li></ul></td></tr></tbody></table>

## MTU\_OPERATION\_STATUS <a href="#id-13.12_mtu_operation_status" id="id-13.12_mtu_operation_status"></a>

This enum refers to the operation status of the device.

<table data-header-hidden><thead><tr><th width="193.54547119140625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_OS_NoStatus</td><td valign="top">No update for the operation.</td></tr><tr><td valign="top">MTU_OS_Started</td><td valign="top">Device has started an operation.</td></tr><tr><td valign="top">MTU_OS_Warning</td><td valign="top">Device has sent a warning about the operation.</td></tr><tr><td valign="top">MTU_OS_Failed</td><td valign="top">Device has failed an operation.</td></tr><tr><td valign="top">MTU_OS_Done</td><td valign="top">Device has completed an operation.</td></tr></tbody></table>

## TransactionStatus <a href="#id-13.13_transactionstatus" id="id-13.13_transactionstatus"></a>

This enum refers to the status of the transaction.

<table data-header-hidden><thead><tr><th width="194.45452880859375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">NoStatus</td><td valign="top">Set before the start of a transaction and before a card is presented to the device.</td></tr><tr><td valign="top">NoTransaction</td><td valign="top">No transaction in progress.</td></tr><tr><td valign="top">CardSwiped</td><td valign="top">A card was swiped into the device.</td></tr><tr><td valign="top">CardInserted</td><td valign="top">A card was inserted into the device.</td></tr><tr><td valign="top">CardRemoved</td><td valign="top">A card was removed from the device.</td></tr><tr><td valign="top">CardDetected</td><td valign="top">A card was detected by the device.</td></tr><tr><td valign="top">CardCollision</td><td valign="top">A card collision was detected by the device.</td></tr><tr><td valign="top">TimedOut</td><td valign="top">The transaction was not completed before a timeout period.</td></tr><tr><td valign="top">HostCanceled</td><td valign="top">The host software sent a cancel.</td></tr><tr><td valign="top">TransactionCanceled</td><td valign="top">The transaction was canceled.</td></tr><tr><td valign="top">TransactionInProgress</td><td valign="top">The transactions is in progress.</td></tr><tr><td valign="top">TransactionError</td><td valign="top">There is an error during the transaction.</td></tr><tr><td valign="top">TransactionApproved</td><td valign="top">The transactions is approved.</td></tr><tr><td valign="top">TransactionDeclined</td><td valign="top">The transactions is declined.</td></tr><tr><td valign="top">TransactionCompleted</td><td valign="top">The transaction is completed.</td></tr><tr><td valign="top">TransactionFailed</td><td valign="top">The transaction failed.</td></tr><tr><td valign="top">TransactionNotAccepted</td><td valign="top">The transaction was not accepted by the device.</td></tr><tr><td valign="top">SignatureCaptureRequested</td><td valign="top">A signature capture is requested by the device.</td></tr><tr><td valign="top">TechnicalFallback</td><td valign="top">Due to technical reasons, the chip transaction cannot be completed by the reader.</td></tr><tr><td valign="top">QuickChipDeferred</td><td valign="top">Device has sent a “Z3” response code to the chip card.</td></tr><tr><td valign="top">DataEntered</td><td valign="top">Data has been entered on the device for a manual card entry transaction.</td></tr><tr><td valign="top">TryAnotherInterface</td><td valign="top">Due to removal of the chip card or error with contactless card, the transaction cannot be completed by the reader.</td></tr><tr><td valign="top">BarCodeRead</td><td valign="top">A barcode is read.</td></tr><tr><td valign="top">VASError</td><td valign="top">Apple VAS error occurred.</td></tr></tbody></table>

## UserEvent <a href="#id-13.14_userevent" id="id-13.14_userevent"></a>

This enum refers to the type of user event reported by the device. These events relate to user interaction.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_USER_EVENT_None</td><td valign="top">No events yet to occur.</td></tr><tr><td valign="top">MTU_USER_EVENT_ContactlessCardPresented</td><td valign="top">Contactless card has been presented.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTU_USER_EVENT_ContactlessCardRemoved</td><td valign="top">Contactless card has been removed.</td></tr><tr><td valign="top">MTU_USER_EVENT_CardSeated</td><td valign="top">Card is seated into the chip station.</td></tr><tr><td valign="top">MTU_USER_EVENT_CardUnseated</td><td valign="top">Card was removed from the chip station.</td></tr><tr><td valign="top">MTU_USER_EVENT_CardSwiped</td><td valign="top">Magnetic stripe card was swiped.</td></tr><tr><td valign="top">MTU_USER_EVENT_TouchPresented</td><td valign="top">Touch screen sensor press detected.</td></tr><tr><td valign="top">MTU_USER_EVENT_TouchRemoved</td><td valign="top">Touch screen sensor release detected.</td></tr><tr><td valign="top">MTU_USER_EVENT_ BarcodeRead</td><td valign="top">Barcode read detected.</td></tr><tr><td valign="top"><p>MTU_USER_EVENT_</p><p>NFCMifareUltralightPresented</p></td><td valign="top">Mifare Ultralight presented.</td></tr><tr><td valign="top"><p>MTU_USER_EVENT_</p><p>MifareClassic1KPresented</p></td><td valign="top">Mifare Classic 1K presented.</td></tr><tr><td valign="top"><p>MTU_USER_EVENT_</p><p>MifareClassic4KPresented</p></td><td valign="top">Mifare Classic 4K presented.</td></tr><tr><td valign="top">MTU_USER_EVENT_MifareDESFirePresented</td><td valign="top">Mifare DESFire presented.</td></tr><tr><td valign="top"><p>MTU_USER_EVENT_</p><p>NFCMifareUltralightRemoved</p></td><td valign="top">Mifare Ultralight removed.</td></tr><tr><td valign="top"><p>MTU_USER_EVENT_</p><p>MifareClassic1KRemoved</p></td><td valign="top">Mifare Classic 1K removed.</td></tr><tr><td valign="top"><p>MTU_USER_EVENT_</p><p>MifareClassic4KRemoved</p></td><td valign="top">Mifare Classic 4K removed.</td></tr><tr><td valign="top">MTU_USER_EVENT_MifareDESFireRemoved</td><td valign="top">Mifare DESFire removed.</td></tr></tbody></table>

## NFCEvent <a href="#id-13.15_nfcevent" id="id-13.15_nfcevent"></a>

This enum refers to NFC events.

<table data-header-hidden><thead><tr><th width="309.9091796875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">MTUSDKNFCE_None</td><td valign="top">No events yet to occur.</td></tr><tr><td valign="top">MTUSDKNFCE_TagRemoved</td><td valign="top">Tag removed.</td></tr><tr><td valign="top">MTUSDKNFCE_NFCMifareUltralight</td><td valign="top">Mifare Ultralight.</td></tr><tr><td valign="top">MTUSDKNFCE_MifareClassic</td><td valign="top">Mifare Classic.</td></tr><tr><td valign="top">MTUSDKNFCE_CommandFailed</td><td valign="top">NFC command failed.</td></tr><tr><td valign="top">MTUSDKNFCE_Failed</td><td valign="top">Failed.</td></tr><tr><td valign="top">MTUSDKNFCE_IOFailed</td><td valign="top">IO failed.</td></tr><tr><td valign="top">MTUSDKNFCE_MifareClassic1K</td><td valign="top">Mifare Classic 1K.</td></tr><tr><td valign="top">MTUSDKNFCE_MifareClassic4K</td><td valign="top">Mifare Classic 4K.</td></tr><tr><td valign="top">MTUSDKNFCE_MifareDESFire</td><td valign="top">Mifare DESFire.</td></tr><tr><td valign="top">MTUSDKNFCE_AuthenticationFailed</td><td valign="top">Authentication failed.</td></tr></tbody></table>

## PaymentMethods <a href="#id-13.16_paymentmethods" id="id-13.16_paymentmethods"></a>

This enum refers to which card type the device will perform a transaction.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">PAYMENT_METHOD_MSR</td><td valign="top">For magnetic stripe cards.</td></tr><tr><td valign="top">PAYMENT_METHOD_CONTACT</td><td valign="top">For EMV chip cards.</td></tr><tr><td valign="top">PAYMENT_METHOD_CONTACTLESS</td><td valign="top">For NFC contactless cards.</td></tr><tr><td valign="top">PAYMENT_METHOD_MANUALENTRY</td><td valign="top">For user to manually enter transaction data without any card access.</td></tr><tr><td valign="top">PAYMENT_METHOD_BARCODE</td><td valign="top">For Barcode.</td></tr><tr><td valign="top">PAYMENT_METHOD_BARCODE_Encrypted</td><td valign="top">For encrypted Barcode.</td></tr><tr><td valign="top">PAYMENT_METHOD_APPLE_VAS</td><td valign="top">For Apple VAS.</td></tr><tr><td valign="top">PAYMENT_METHOD_NFC</td><td valign="top">For NFC tag.</td></tr><tr><td valign="top">PAYMENT_METHOD_GOOGLE_VAS</td><td valign="top">For Ggoogle Wallet Smart Tap VAS.</td></tr></tbody></table>

## StatusCode <a href="#id-13.17_statuscode" id="id-13.17_statuscode"></a>

This enum refers to the operation status of the SDK.

<table data-header-hidden><thead><tr><th width="164.45452880859375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">SUCCESS</td><td valign="top">The operation completed successfully.</td></tr><tr><td valign="top">TIMEOUT</td><td valign="top">The operation timed out.</td></tr><tr><td valign="top">ERROR</td><td valign="top">Error attempting the operation.</td></tr><tr><td valign="top">UNAVAILABLE</td><td valign="top">Status currently unavailable.</td></tr></tbody></table>

## VASMode <a href="#id-13.18_vasmode" id="id-13.18_vasmode"></a>

This enum refers to the Apple VAS mode. This controls how the Apple VAS data is returned in the transaction ARQC. For details on Apple VAS data structure returned in a transaction see <mark style="color:red;">**DynaFlex Family Programmer’s Manual.**</mark>

<table data-header-hidden><thead><tr><th width="96.272705078125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p> </p><p>Single</p></td><td valign="top">The device reads only Apple VAS data from a tapped smartphone, or reads EMV payment data from a tapped card. When the device sends ARQC to conclude the transaction, it only includes either EMV payment data in container FC for cards, or includes VAS data in container FE for smartphones.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="120.81817626953125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top"><p> </p><p> </p><p>Dual</p></td><td valign="top">The device reads both Apple VAS data and EMV payment data from a tapped smartphone, or reads EMV payment data from a tapped card. When device sends ARQC to the host to conclude the transaction, it includes EMV payment data in container FC and includes VAS data, if available, in container FE.</td></tr><tr><td valign="top"><p> </p><p> </p><p>VASOnly</p></td><td valign="top">The device reads only Apple VAS data from a tapped smartphone, and does not read data from a tapped card. If the tapped smartphone does not support VAS, the device does not detect or read from the smartphone. When the device send ARQC to conclude the transaction, it includes VAS data in container FE and does not include EMV payment data in container FC.</td></tr></tbody></table>

## VASProtocol <a href="#id-13.19_vasprotocol" id="id-13.19_vasprotocol"></a>

This enum refers to the Apple VAS protocol. For details on Apple VAS data structure returned in a transaction see <mark style="color:red;">**DynaFlex Family Programmer’s Manual.**</mark>

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Enum</td><td valign="top">Description</td></tr><tr><td valign="top">URL</td><td valign="top">URL VAS protocol</td></tr><tr><td valign="top">Full</td><td valign="top">Full VAS protocol</td></tr></tbody></table>


---

# 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/enumerations.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.
