> 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/commands/user-interface-command-group-0x18nn/request-cardholder-signature-touch-only-command-0x1801.md).

# Request Cardholder Signature (Touch Only) - Command 0x1801

The host uses this command to prompt a cardholder for a signature.

The sequence of events is as follows:

{% stepper %}
{% step %}

### Transaction completed / Host may request signature

The device completes a transaction after the host invokes **Start Transaction - Command 0x1001**. At the end of the transaction, the device has provided data to the host in **Transaction Operation Complete - Notification 0x0105**. The host may send Command 0x1801 to the device to get a signature file without doing a transaction. The signature file can be encrypted if enabled.
{% endstep %}

{% step %}

### Host decides whether to request a signature

The host decides whether to request a signature from the cardholder. For example:

* If the Notification Detail in **Transaction Operation Complete**  - **Notification 0x0105** indicates Signature Capture Requested.
* If an application-specific rule requires requesting a signature.
  {% endstep %}

{% step %}

### Host composes command

If the host determines it should request a signature, it composes a command request in the format shown below.
{% endstep %}

{% step %}

### Device presents signature UI

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

{% step %}

### Device notifies host of completion or issues

The device sends **User Interface Operation Complete - Notification 0x1805** to the host to report data available, timeout, or hardware failure.
{% endstep %}

{% step %}

### Host retrieves signature file (if data available)

If the device reported data available, the host uses **Start Get File from Device - Command 0xD821** to request file type **Signature Capture File** to retrieve the data as a **Signature Capture File Type**.
{% endstep %}
{% endstepper %}

## Table RCST-1 - Request Data for Request Cardholder Signature (Touch Only) - Command 0x1801

<table><thead><tr><th>Tag</th><th width="76">Len</th><th width="264.3333740234375">Value / Description</th><th width="75.66668701171875">Typ</th><th width="75.33331298828125">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>1801 = <strong>Request Cardholder Signature (Touch Only) - Command 0x1801</strong></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>81</td><td>01</td><td>Timeout — Timeout in seconds that the device should wait for the cardholder to sign and confirm completion.</td><td>B</td><td>R</td><td></td></tr><tr><td>82</td><td>01</td><td>Encryption on signature and user data. 0=disabled, 1=enabled.</td><td>B</td><td>O</td><td>0</td></tr><tr><td>A3</td><td>var</td><td>User data parameters for item #0 to item #3. The maximum total size of 0xA3 TLV is 4,000 bytes. This TLV may be present only if encryption is enabled.</td><td>T</td><td>O</td><td></td></tr><tr><td>/81</td><td>var</td><td>User data item #0, optional</td><td>B</td><td>O</td><td></td></tr><tr><td>/82</td><td>var</td><td>User data item #1, optional</td><td>B</td><td>O</td><td></td></tr><tr><td>/83</td><td>var</td><td>User data item #2, optional</td><td>B</td><td>O</td><td></td></tr><tr><td>/84</td><td>var</td><td>User data item #3, optional</td><td>B</td><td>O</td><td></td></tr><tr><td>End of any wrappers, at minimum including <strong>Request Message</strong> </td><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

## Table RCST-2 - Response Data for Command 0x1801 - Request Cardholder Signature (Touch Only)

<table><thead><tr><th>Tag</th><th width="75">Len</th><th width="253">Value / Description</th><th width="74.66668701171875">Typ</th><th width="74">Req</th><th width="98">Default</th></tr></thead><tbody><tr><td>Beginning of any wrappers, at minimum including <strong>Response Message</strong></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>1801 = <strong>Request Cardholder Signature (Touch Only) - Command 0x1801</strong></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>No parameters.</td><td></td><td></td><td></td><td></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>

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

## Table RCST-3 - Request Example

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

```
AA 00 81 04 01 00 18 01 84 05 18 01 81 01 1E
```

{% endcode %}

## Table RCST-S - Response Example

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

```
AA 00 81 04 82 00 18 01 82 04 01 00 00 00
```

{% 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 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/commands/user-interface-command-group-0x18nn/request-cardholder-signature-touch-only-command-0x1801.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.