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

# .NET (Windows)

### Universal SDK Documentation (.NET/Windows)

The .NET edition of the MagTek Universal SDK (MTUSDK), giving developers a single managed interface for connecting to and controlling MagTek card readers and PIN pad devices — including the DynaFlex family — from Windows .NET applications. The complete API reference is available as a PDF download below.

### In This Section

<table data-header-hidden><thead><tr><th width="237.66668701171875" valign="middle"></th><th></th></tr></thead><tbody><tr><td valign="middle"><strong>Reference Section</strong></td><td><strong>Information Available</strong></td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/introduction"><mark style="color:red;"><strong>Introduction</strong></mark></a></td><td>SDK scope and supported device classes, package contents (MTUSDKNET.dll and the MTUSDKDemo sample), nomenclature (device, host, user), and Windows host requirements, including the certificates needed for TLS Trust and secure WebSocket connections.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/how-to-set-up-the-sdk"><mark style="color:red;"><strong>How to Set Up the SDK</strong></mark></a></td><td>Steps to download the SDK package, reference the MTUSDKNET library in Visual Studio, and build, run, and debug the MTUSDKDemo sample on x86 or x64.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/coreapi"><mark style="color:red;"><strong>Core API</strong></mark></a></td><td>Static entry points for finding and creating devices (getDeviceList, createDevice with the address format for each transport, and device-specific factory functions), API version lookup, MQTT broker, topic, QoS, client ID, certificate, and discovery settings, and system status callback registration.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/idevice"><mark style="color:red;"><strong>IDevice</strong></mark></a></td><td>The primary device object: start and cancel transactions, request PIN, PAN, signature, and user selections, send the processor’s ARPC with sendAuthorization, send NFC tag, Mifare Classic, DESFire, and Plus commands, get the device’s capability, control, configuration, and connection objects, and subscribe to device events.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/idevicecapabilities"><mark style="color:red;"><strong>IDeviceCapabilities</strong></mark></a></td><td>Read-only properties for checking hardware support before you call a feature: display, PIN pad, signature capture, automatic signature capture, battery-backed clock, MSR power saver, SRED, and the list of supported payment methods.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/idevicecontrol"><mark style="color:red;"><strong>IDeviceControl</strong></mark></a></td><td>Direct device control, both synchronous and asynchronous: open and close the connection, reset the device, end a session, send raw, extended, and synchronous commands, show messages, images, barcodes, and custom UI pages, run the barcode reader, NFC pass-through, polling, and card emulation, set the card latch and LEDs, and capture personal info entry.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/connectioninfo"><mark style="color:red;"><strong>ConnectionInfo</strong></mark></a></td><td>Connection details for a device: its address, connection type, device type, and certificate information for TLS and secure WebSocket connections.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/deviceinfo"><mark style="color:red;"><strong>DeviceInfo</strong></mark></a></td><td>Device identity properties: model, name, and serial number.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/ideviceconfiguration"><mark style="color:red;"><strong>iDeviceConfiguration</strong></mark></a></td><td>Configuration and maintenance: read and write device settings by OID, retrieve device info, key info, and challenge tokens, send, retrieve, and delete files and images, send secured files, set the idle-screen image, update keys, and update main and wireless firmware. Asynchronous operations report through IConfigurationCallback.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/classes"><mark style="color:red;"><strong>Classes</strong></mark></a></td><td>Objects passed to and returned from the API, and the Builder helpers that parse raw OnEvent payloads into them. These include ITransaction (amount, payment methods, QuickChip, tip and tax, and VAS settings), IData, CertificateInfo, ConnectionStateBuilder, InputRequest and EnhancedInputRequest for application selection, and the barcode, NFC, R-APDU, and personal info entry data classes.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/ieventsubscriber-delegates"><mark style="color:red;"><strong>IEventSubscriber Delegates</strong></mark></a></td><td>The OnEvent callback, which delivers nearly all device output (card data, transaction status, ARQC requests, PIN blocks, NFC and barcode data) after you register with subscribeAll.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/iconfigurationcallback-delegates"><mark style="color:red;"><strong>IConfigurationCallback Delegates</strong></mark></a></td><td>Callbacks for asynchronous configuration operations: OnProgress for percent complete, OnResult for completion status and data, and OnCalculateMAC for requests that must carry a MAC.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/imqttdevicestatuscallback-delegates"><mark style="color:red;"><strong>IMQTTDeviceStatusCallback Delegates</strong></mark></a></td><td>OnConnected and OnDisconnected callbacks that report MQTT-connected devices coming online or going offline while device status monitoring is running.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/isystemstatuscallback-delegates"><mark style="color:red;"><strong>iSystemStatusCallback Delegates</strong></mark></a></td><td>The OnError callback, which reports errors in MQTT communication once registered with setSystemStatusCallback.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/~/revisions/7gQMuwvu8JKvxaHJDCR8/universal-sdk-documentation/.net-windows/enumerations"><mark style="color:red;"><strong>Enumerations</strong></mark></a></td><td>Enumerated values used across the SDK: device and connection types, connection and transaction states, event types, payment methods, capture and data entry types, device events and features, NFC events and modes, image and info types, error types, and Apple VAS modes and protocols.</td></tr><tr><td valign="middle"><mark style="color:red;"><strong>Appendices</strong></mark></td><td>Status codes and the supported-function list, an API walkthrough with sample code, the EMV transaction flow, and Apple VAS and Google Wallet Smart Tap integration.</td></tr></tbody></table>

### Need More Help

{% hint style="info" %}
**Need Help?**

For additional support, please contact MagTek Support:

**Technical Support:**

* 📧 **Email:** [support@magtek.com](mailto:support@magtek.com?subject=Support%20Request)
* 📞 **Phone:** 1-562-546-6800 (US)
* 🕐 **Hours:** Monday-Friday, 5:30 AM - 5:00 PM Pacific

**Online Resources:**

* 🌐 **Support Portal:** developer.magtek.com
* 🌐 **Official Site:** [https://www.magtek.com](https://www.magtek.com/)

**Documentation Feedback:**

Help us improve this documentation! [feedback@magtek.com](mailto:feedback@magtek.com?subject=Feedback)
{% endhint %}


---

# 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/.net-windows.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.
