> 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/scra-dynafamily-programmers-manual/notifications/notifications-from-banking-functions-banking-functions-only-notification-0x02nn/banking-functions-operation-complete-notification-0x0205.md).

# Banking Functions Operation Complete - Notification 0x0205

This notification reports information about progress and state changes that occur during interaction with the Banking Functions modules.

For this notification, **Notification Detail** described in section **3.2.2.3 Notification Message** contains one byte each to indicate:

* The **User Interface Module** (UI) involved
* The **Reason** (Rsn) for the notification (UI Event)
* **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.

## Table - Notification Detail Codes

<table><thead><tr><th width="65.81817626953125">UI</th><th width="75.54541015625">Rsn</th><th width="72.6363525390625">Det</th><th width="71.727294921875">Ext</th><th>Meaning</th></tr></thead><tbody><tr><td></td><td></td><td></td><td></td><td><p>Module <strong>0x01 Touchscreen</strong> contains UI notification detail codes that are specific to the touchscreen module (Touch Only)</p><ul><li>Reason 0x01 = Signature Capture</li><li>Reason 0x02 = PIN Entry (Banking Functions Only)</li></ul></td></tr><tr><td>01</td><td>02</td><td>01</td><td>01</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Success, Data Attached — In this case, the device includes additional data defined in <strong>Table XXX</strong>, or in <strong>Table XXX</strong> if the device is including account data with PIN data.</td></tr><tr><td>01</td><td>02</td><td>02</td><td>01</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Timeout</td></tr><tr><td>01</td><td>02</td><td>02</td><td>02</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Hardware Not Available</td></tr><tr><td>01</td><td>02</td><td>02</td><td>03</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Canceled</td></tr><tr><td>01</td><td>02</td><td>02</td><td>04</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Error</td></tr><tr><td>01</td><td>02</td><td>02</td><td>05</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, PIN Verify Failed</td></tr><tr><td>01</td><td>02</td><td>02</td><td>06</td><td>(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Account Data Capture Failed</td></tr></tbody></table>

## Table BFOC-1 - Notification Payload for Touchscreen, PIN Entry, Success, Data Attached without Account Data (Banking Functions Only)

<table><thead><tr><th width="247.45452880859375">Tag</th><th width="72.27276611328125">Len</th><th>Value / Description</th><th width="75.727294921875">Typ</th><th width="79.0909423828125">Req</th><th width="96.181884765625">Default</th></tr></thead><tbody><tr><td>Beginning of <strong>Notification Message</strong></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>0205 = User Interface Operation Complete</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>84</td><td>var</td><td>Notification Payload</td><td>B</td><td>R</td><td></td></tr><tr><td>/F5</td><td>var</td><td>Container for Encrypted PIN Data</td><td>B</td><td>R</td><td></td></tr><tr><td>//DF71</td><td>01</td><td><p>PIN Block Format</p><ul><li>0x00 = ISO Format 0</li><li>0x01 = ISO Format 1</li><li>0x03 = ISO Format 3</li><li>0x04 = ISO Format 4</li></ul></td><td>B</td><td>R</td><td></td></tr><tr><td>//99</td><td>var</td><td>Encrypted PIN Block — ISO Formats 0, 1, and 3 are 8 bytes; ISO Format 4 is 16 bytes</td><td>B</td><td>R</td><td></td></tr><tr><td>//DFDF41</td><td>var</td><td>PIN Key Serial Number (KSN)</td><td>B</td><td>R</td><td></td></tr><tr><td>//DFDF42</td><td>01</td><td>PIN Encryption Type — See section <strong>4.4 Encryption Type</strong> for a list of valid values.</td><td>B</td><td>R</td><td></td></tr><tr><td>End of <strong>Notification Message</strong> </td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

## Table BFOC-2 - Notification Payload for Touchscreen, PIN Entry, Success, Data Attached with Account Data (Banking Functions Only)

<table><thead><tr><th width="116.8182373046875">Tag</th><th width="79.0909423828125">Len</th><th>Value / Description</th><th width="74.8182373046875">Typ</th><th width="77.272705078125">Req</th><th width="98">Default</th></tr></thead><tbody><tr><td>Beginning of <strong>Notification Message</strong></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>0205 = User Interface Operation Complete</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>84</td><td>var</td><td>Notification Payload</td><td>B</td><td>R</td><td></td></tr><tr><td>/DFDF59</td><td>var</td><td>Encrypted Data Primitive — Decrypt the value of this TLV data object using the algorithm and variant specified in the <strong>Encrypted Data KSN</strong> parameter and the <strong>Encrypted Data Encryption Type</strong> parameter to read its contents. The format of the decrypted data is shown in <strong>Table XXX</strong>.</td><td>B</td><td>R</td><td></td></tr><tr><td>/DFDF56</td><td>var</td><td>Encrypted Data KSN</td><td>B</td><td>R</td><td></td></tr><tr><td>/DFDF57</td><td>01</td><td>Encrypted Data Encryption Type — See <strong>Encryption Type</strong> for a list of valid values.</td><td>B</td><td>R</td><td></td></tr><tr><td>/F5</td><td>var</td><td>Container for Encrypted PIN Data</td><td>TC</td><td>R</td><td></td></tr><tr><td>//DF71</td><td>01</td><td><p>PIN Block Format</p><ul><li>0x00 = ISO Format 0</li><li>0x01 = ISO Format 1</li><li>0x03 = ISO Format 3</li><li>0x04 = ISO Format 4</li></ul></td><td>B</td><td>R</td><td></td></tr><tr><td>//99</td><td>var</td><td>Encrypted PIN Block — ISO Formats 0, 1, and 3 are 8 bytes; ISO Format 4 is 16 bytes</td><td>B</td><td>R</td><td></td></tr><tr><td>//DFDF41</td><td>var</td><td>PIN KSN</td><td>B</td><td>R</td><td></td></tr><tr><td>//DFDF42</td><td>01</td><td>PIN Encryption Type — See <strong>Encryption Type</strong> for a list of valid values.</td><td>B</td><td>R</td><td></td></tr><tr><td>End of <strong>Notification Message</strong> </td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

## Table BFOC-3 - Account Data DFDF59 Decrypted Contents (Banking Functions Only)

<table><thead><tr><th>Tag</th><th width="74.18182373046875">Len</th><th>Value / Description</th><th width="74.818115234375">Typ</th><th width="76.3636474609375">Req</th><th width="96.1817626953125">Default</th></tr></thead><tbody><tr><td>FC</td><td>var</td><td>Decrypted Data Container</td><td>T</td><td>R</td><td></td></tr><tr><td>/DF42</td><td>var</td><td>MSR Track 2 Clear Text Data</td><td>B</td><td>O</td><td></td></tr><tr><td>/57</td><td>var</td><td>Track 2 Equivalent Data</td><td>B</td><td>O</td><td></td></tr><tr><td>/5A</td><td>var</td><td>Primary Account Number</td><td>B</td><td>O</td><td></td></tr><tr><td>Padding to force DFDF59 plus padding to be a multiple of 8 bytes</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/notifications/notifications-from-banking-functions-banking-functions-only-notification-0x02nn/banking-functions-operation-complete-notification-0x0205.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.