> 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/notifications/0x03nn-generic-pass-through-mode/0x0301-pass-through-mode-information-update.md).

# 0x0301- Pass-Through Mode Information Update

This notification reports information about progress and state changes that occur during a Pass-Through Mode.

For this notification, [<mark style="color:red;">**Notification Detail**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x18nn-from-user-interface/0x1805-user-interface-operation-complete#notification-detail-codes-0x1805) described in section [<mark style="color:red;">**Notification Messages**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/message-format-and-structure/message-structure#notification-message-format) contains one byte each, shown in [<mark style="color:red;">**Notification Detail Codes**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x18nn-from-user-interface/0x1805-user-interface-operation-complete#notification-detail-codes-0x1805), to indicate:

* The Payment Technology (PT) involved
* The Reason (Rsn) for the notification
* Detail (Det) about the notification that has different meanings depending on the Reason, and
* An Extra field (Ext) that has different meanings depending on the Reason.

### Notification Detail Codes - 0x0301&#x20;

{% hint style="info" %}
Payment Technology 0x20 EMV Contactless contains transaction notification detail codes involving contactless cards and contactless payment devices.

* Reason 0x01 = Card Event
* Reason 0x02 = Online PIN Event
* Reason 0x08 = Data Update
* Reason 0x10 = State Update
  {% endhint %}

<table data-header-hidden><thead><tr><th width="49.666656494140625"></th><th width="54.333343505859375"></th><th width="60.33331298828125"></th><th width="60"></th><th></th></tr></thead><tbody><tr><td><strong>PT</strong></td><td><strong>Rsn</strong></td><td><strong>Det</strong></td><td><strong>Ext</strong></td><td> <strong>Meaning</strong></td></tr><tr><td>20</td><td>01</td><td>04</td><td>10</td><td>Contactless, Card Event, Detected, ISO 14443 Type A (Contactless Only)</td></tr><tr><td>20</td><td>01</td><td>04</td><td>11</td><td>Contactless, Card Event, Detected, ISO 14443 Type B (Contactless Only)</td></tr><tr><td>20</td><td>01</td><td>04</td><td>12</td><td>Contactless, Card Event, Detected, Not Supported (Contactless Only)</td></tr><tr><td>20</td><td>01</td><td>05</td><td>00</td><td>Contactless, Card Event, Collision, Reserved (EMV Contactless Only)</td></tr><tr><td>20</td><td>08</td><td>04</td><td>02</td><td><p>Contactless, Data Update, NFC UID data, Data Attached</p><p>In this case, the device includes additional data, defined in Table 8 - Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached, in the Notification Payload portion of the Notification Message. (Contactless Only)</p></td></tr></tbody></table>

### Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached

<table data-header-hidden><thead><tr><th width="222.6363525390625"></th><th width="54"></th><th width="154"></th><th width="55"></th><th width="55"></th><th width="80.33331298828125"></th></tr></thead><tbody><tr><td>Tag</td><td>Len</td><td>Value / Description</td><td>Typ</td><td>Req</td><td>Default</td></tr><tr><td>Beginning of Notification Message </td><td></td><td></td><td></td><td></td><td></td></tr><tr><td><p>0101 = DynaPro Format Transaction Data</p><p>0301 = Generic Pass-Through Transaction Data</p></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>84</td><td>var</td><td>Transaction Data</td><td>B</td><td>R</td><td> </td></tr><tr><td>/null</td><td>(v)</td><td><br>EMV ARQC Type data blob, if the notification is an ARQC Update (Quick Chip) notification.  (MCE Only) If the notification is for manual card entry, the data blob does not contain Track 3 Data or MagnePrint Data.
<br>
<br>EMV Batch Data Type data blob, if the notification is a Batch Data notification.  (MCE Only) If the notification is for manual card entry, the data blob does not contain Track 3 Data or MagnePrint Data.
<br>
<br>Decoded raw barcode data, if the notification is a Barcode event notification.  If the barcode data is Base64 encoded, the device sends the decoded version in binary format.
<br>
<br>NFC UID Type reports the unique ID from the NFC tag (EMV Contactless Only)
<br>
<br>GPO Response Type reports the card’s GPO Response (EMV Contactless Only)
<br>
<br>– MIFARE Card Data Type reports the data reading from NFC/MIFARE tag (EMV Contactless Only)</td><td>B</td><td>O</td><td> </td></tr><tr><td>End of any wrappers, at minimum including <strong>Response Message</strong> </td><td></td><td></td><td></td><td></td><td></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/api-and-command-reference/dynafamily-programmers-manual/notifications/0x03nn-generic-pass-through-mode/0x0301-pass-through-mode-information-update.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.