> 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/api-and-command-reference/dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/about.md).

# About

Pass-Through Mode is independent and separate from EMVCo Payment functions. This mode provides no access to any EMV payment kernels, and is out of scope from EMVCo certifications. 

This mode is typically used by developers that require the need for non-payment low-level APDU communications with NFC cards, tokens, and devices.

The commands in this section provide the basic capability to communicate directly with the non-payment Contactless Card. They provide control of the polling process, and exchange of application protocol data units (APDU).

Typical Use Case examples of overall sequence:

* ENTER Pass-Through Mode.
* Turn ON Polling
* Set/Use LEDs / Buzzer
* “Tap” card/device on reader.
* Engage APDU transmit/ receive activities
* Set/Use LEDs/ Buzzer
* When transaction is completed:
* Turn OFF Polling
* EXIT Pass-Through Mode.

[<mark style="color:red;">**Command 0x3001 - Pass-Through Mode Start/Stop**</mark> ](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/0x3001-pass-through-mode-start-stop)

The host uses this command to enter or exit Pass-Through Mode.&#x20;

The Host must “Enter Pass-Through Mode” prior to using any other commands in this section. Otherwise, subsequent commands will be “ignored” / “rejected”. When finished, the Host should “Exit Pass-Through Mode”. Once exited, the reader returns to its “normal state” and will accept traditional commands.


---

# 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/api-and-command-reference/dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/about.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.