> 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/0x02nn-banking-functions/0x0201-banking-functions-information-update.md).

# 0x0201 - Banking Functions Information Update

This notification reports information about progress and state changes involving the device’s Banking Functions modules.

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 [<mark style="color:red;">**Notification Message**</mark>](https://developer.magtek.com/api-and-command-reference/preliminary-documentation-scra-dynafamily-programmers-manual/preliminary-documentation-message-format-and-structure/preliminary-documentation-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 - 0x0201

<table><thead><tr><th width="69.90911865234375">PT</th><th width="75.6363525390625">Rsn</th><th width="65.45458984375">Det</th><th width="72.5455322265625">Ext</th><th>Meaning</th></tr></thead><tbody><tr><td></td><td></td><td></td><td></td><td><p>Payment Technology 0x07 Manual Card Entry (MCE) contains transaction notification detail codes involving manual card entry (MCE Only).</p><ul><li>Reason 0x01 = Card Event</li><li>Reason 0x08 = Data Update</li><li>Reason 0x10 = State Update</li></ul></td></tr><tr><td>07</td><td>01</td><td>01</td><td>00</td><td>Manual Card Entry (MCE), Card Event, Data Entered, Reserved</td></tr><tr><td></td><td></td><td></td><td></td><td><p>Payment Technology 0x08 Magnetic Stripe Reader (MSR) contains transaction notification detail codes involving magnetic stripe cards (MSR Only).</p><ul><li>Reason 0x01 = Card Event</li><li>Reason 0x08 = Data Update</li><li>Reason 0x10 = State Update</li></ul></td></tr><tr><td>08</td><td>01</td><td>01</td><td>00</td><td>MSR, Card Event, Swiped, Reserved (MSR Only)</td></tr><tr><td>08</td><td>01</td><td>02</td><td>00</td><td>MSR, Card Event, Inserted, Reserved (MSR Only)</td></tr><tr><td>08</td><td>01</td><td>03</td><td>00</td><td>MSR, Card Event, Removed, Reserved (MSR Only)</td></tr><tr><td>08</td><td>01</td><td>04</td><td>00</td><td>MSR, Card Event, Detected, Reserved (MSR Only)</td></tr><tr><td></td><td></td><td></td><td></td><td><p>Payment Technology 0x10 EMV Contact contains transaction notification detail codes involving contact chip cards (EMV Contact Only).</p><p>Reason 0x01 = Card Event</p><p>Reason 0x08 = Data Update</p><p>Reason 0x10 = State Update</p></td></tr><tr><td>10</td><td>01</td><td>02</td><td>00</td><td>EMV Contact, Card Event, Inserted, Reserved (EMV Contact Only)</td></tr><tr><td>10</td><td>01</td><td>03</td><td>00</td><td>EMV Contact, Card Event, Removed, Reserved (EMV Contact Only)</td></tr><tr><td>10</td><td>01</td><td>04</td><td>00</td><td>EMV Contact, Card Event, Detected, Reserved (EMV Contact Only)</td></tr><tr><td></td><td></td><td></td><td></td><td><p>Payment Technology 0x20 EMV Contactless contains transaction notification detail codes involving contactless cards and contactless payment devices. (EMV Contactless Only)</p><ul><li>Reason 0x01 = Card Event</li><li>Reason 0x08 = Data Update</li><li>Reason 0x10 = State Update</li></ul></td></tr><tr><td>20</td><td>01</td><td>03</td><td>00</td><td>EMV Contactless, Card Event, Removed, Reserved (EMV Contactless Only)</td></tr><tr><td>20</td><td>01</td><td>04</td><td>00</td><td>EMV Contactless, Card Event, Detected, Reserved (EMV Contactless Only)</td></tr><tr><td>20</td><td>01</td><td>05</td><td>00</td><td>EMV Contactless, Card Event, Collision, Reserved (EMV Contactless Only)</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/0x02nn-banking-functions/0x0201-banking-functions-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.