> 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/0x18nn-user-interface/0x1806-personal-info-entry.md).

# 0x1806 - Personal Info Entry

The host uses this command to prompt a cardholder for customer information.

{% stepper %}
{% step %}

### Ensure device is idle

The host ensures the device is not currently running another command (for example, it is not running a transaction using [<mark style="color:red;">**0x1001 - Start Transaction**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction).
{% endstep %}

{% step %}

### Compose command

If the host determines it should request customer information, it composes a command request in the format described below.
{% endstep %}

{% step %}

### Present keypad

The device presents a keypad interface to the cardholder on the display.
{% endstep %}

{% step %}

### Device notifies host

The device sends [<mark style="color:red;">**0x1805 - User Interface Operation Complete**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x18nn-from-user-interface/0x1805-user-interface-operation-complete) to the host to report data available, or hardware failure.
{% endstep %}

{% step %}

### Host retrieves data

If the device reported data available, the host can retrieve the data as defined 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) and [<mark style="color:red;">**Notification Payload for Personal Info Entry**</mark>](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1806-personal-info-entry#host-retrieves-data).
{% endstep %}
{% endstepper %}

## Request Data for Command 0x1806 – Personal Info Entry

<table><thead><tr><th>Tag</th><th width="74">Len</th><th width="244.33331298828125">Value / Description</th><th width="72.66668701171875">Typ</th><th width="73.333251953125">Req</th><th width="98">Default</th></tr></thead><tbody><tr><td>Beginning of any wrappers, at minimum including <strong>Request Message</strong> </td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>1806 = <strong>Command 0x1806 –</strong> Personal Info Entry</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>81</td><td>01</td><td><p>Capture Type </p><p>0x01 = Phone Number: Capture the phone number<br>0x02 = Social: Capture the social security number</p><p>0x03 = Zip code: Capture the zip code<br>0x04 = Employee ID: Capture Employee ID number<br>0x05 = Birth Date: Capture birth date in USA format<br>0xFF = Cancel Capture: Cancel any of the capture commands</p></td><td>B</td><td>R</td><td></td></tr><tr><td>82</td><td>01</td><td><p>Encryption for user data (Optional) <br>00 – No Encrypt </p><p>01 - Encrypt </p></td><td>B</td><td>R</td><td></td></tr><tr><td>Beginning of any wrappers, at minimum including <strong>Request Message</strong> </td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

## Response Data for Personal Info Entry

| Tag                                                                  | Len | Value / Description | Typ | Req | Default |
| -------------------------------------------------------------------- | --- | ------------------- | --- | --- | ------- |
| Beginning of any wrappers, at minimum including **Response Message** |     |                     |     |     |         |
| 1806 = **Command 0x1806 –** Personal Info Entry                      |     |                     |     |     |         |
| No parameters.                                                       |     |                     |     |     |         |
| Beginning of any wrappers, at minimum including **Response Message** |     |                     |     |     |         |

If the request started successfully, the Request Status in the message wrapper is: OK, Started / Running, All good / requested operation was successful.

#### Request Example

{% code title="Example (Hex)" %}

```
AA00 810401031806 8405 1806 8101 01
```

{% endcode %}

#### Response Example

{% code title="Example (Hex)" %}

```
AA00 810482031806 8204 01000000
```

{% endcode %}


---

# 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/0x18nn-user-interface/0x1806-personal-info-entry.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.