> 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/properties/1.2.nnnn-device-settings/1.2.1.nnn-transaction-settings-a.md).

# 1.2.1.nnn - Transaction Settings - A

## Device-Driven Fallback Behavior (MSR Only) - Property 1.2.1.1.1.1&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.1.1 / 0x010201010101</td></tr><tr><td valign="top">Name</td><td>Device-Driven Fallback Behavior</td></tr><tr><td valign="top"><p> </p><p>Description</p></td><td>The device uses this property to determine whether it should automatically implement payment brand fallback rules without host intervention when running <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction"><mark style="color:red;"><strong>Command 0x1001 - Start Transaction.</strong></mark></a></td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>1</td></tr><tr><td valign="top">Max. Len (b)</td><td>1</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td><p>0x00 = No device-driven fallback </p><p>0x01 = Device-driven fallback enabled</p></td></tr><tr><td valign="top">Default</td><td>0x01</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA0081040104D101841AD10181072B06010401F609850101890AE208E106E104E102C100</td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA0081048204D1018204000000008482001BD10181072B06010401F609850101890BE209E107E105E103C10100</td></tr></tbody></table>

#### Set Request Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA0081040102D111841BD11181072B06010401F609850101890BE209E107E105E103C10101</td></tr></tbody></table>

#### Set Response Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA0081048202D1118204000000008482001BD11181072B06010401F609850101890BE209E107E105E103C10101</td></tr></tbody></table>

## Property 1.2.1.1.1.2  - Application Selection Behavior (Contactless Only)&#x20;

<table data-header-hidden><thead><tr><th width="196.727294921875" valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.1.2 / 0x010201010102</td></tr><tr><td valign="top">Name</td><td>Application Selection Behavior</td></tr><tr><td valign="top">Description</td><td>The device uses this property to set the device’s application selection behavior for payment brand selection.</td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>1</td></tr><tr><td valign="top">Max. Len (b)</td><td>1</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>Valid Values</p></td><td><p>0x00 –Card Preference.</p><p>The device automatically chooses the application that is mutually supported by the card and the terminal, based on the priority order specified by the card. This is the default and is standard EMV transaction flow behavior.</p><p> </p><p>0x01 – Reserved 0x02 – Reserved</p><p> </p><p>0x03 – Enhanced Prompt Cardholder.</p><p>The device sends the host Notification 0x1803 – 02 02 00 00 (Display Cardholder, Data Attached, Reserved) to request that the cardholder select from a list of available applications. Each application may include additional tags such as - priority indicator, Issuer Country Code and Issuer Identification Number. After the cardholder selects an application, the host passes the selection to the device using Command 0x1802 - Report Cardholder Selection to device to return the cardholder’s selection to the device.</p><p> </p><p>Note that if the device is configured to use this option, the cardholder must hold the card or contactless payment device in contact with the device for until cardholder application selection is complete, otherwise the device will report the transaction failed. For this reason, MagTek does not recommend using this setting.</p></td></tr><tr><td valign="top">Default</td><td>0x00 – Card Preference</td></tr></tbody></table>

#### Get Request Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 8104 0155D101 840F D101 8501 01 8704 02010101 8902 C200</td></tr></tbody></table>

#### Get Response Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 55 D1 01 82 04 00 00 00 00 84 82 00 10 D1 01 85 01 01 87 04 02 01 01 01 89 03 C2</p><p>01 00</p></td></tr></tbody></table>

#### &#x20;Set Request Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 81040155D111 8410 D111 850101 870402010101 8903 C20103</td></tr></tbody></table>

#### Set Response Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 55 D1 11 82 04 00 00 00 00 84 82 00 10 D1 11 85 01 01 87 04 02 01 01 01 89 03 C2</p><p>01 03</p></td></tr></tbody></table>

## **Property 1.2.1.1.1.3 &#x20;**<mark style="color:$danger;">**-**</mark>**&#x20;Device-Driven MSR Fallback Retry Control (MSR Only)**&#x20;

<table data-header-hidden><thead><tr><th width="182.18182373046875"></th><th></th></tr></thead><tbody><tr><td>Property Description</td><td></td></tr><tr><td>Property OID</td><td>1.2.1.1.1.3 / 0x010201010103</td></tr><tr><td>Name</td><td>Device-Driven MSR Fallback Retry Control</td></tr><tr><td>Description</td><td>For MSR Fallback case, the device uses this property to configure up to 3 retries before falling back to MSR</td></tr><tr><td>Securing Key</td><td>None</td></tr><tr><td>Min. Len (b)</td><td>1</td></tr><tr><td>Max. Len (b)</td><td>1</td></tr><tr><td>Data Type</td><td>Binary</td></tr><tr><td>Valid Values</td><td>0x00 – 0x03</td></tr><tr><td>Default</td><td>0x00</td></tr></tbody></table>

#### **Get Request Example**&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA 00 81 04 01 04 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04 E1 02 C3 00</td></tr></tbody></table>

#### **Get Response Example**&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA 00 81 04 82 04 D1 01 82 04 00 00 00 00 84 82 00 1B D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E2 09 E1 07 E1 05 E1 03 C3 01 00</td></tr></tbody></table>

#### **Set Request Example**&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA 00 81 04 01 02 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E2 09 E1 07 E1 05 E1 03 C3 01 03</td></tr></tbody></table>

#### **Set Response Example**&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA 00 81 04 82 02 D1 11 82 04 00 00 00 00 84 82 00 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E2 09 E1 07 E1 05 E1 03 C3 01 03</td></tr></tbody></table>

## Property 1.2.1.1.1.1C - CDOL Zero Filled Tags Enable

This property controls whether missing CDOL tags are zero-filled when building ARQC (CDOL1 / tag 8C) and Batch (CDOL2 / tag 8D) Dynapro payloads. When disabled (default), firmware still merges CDOL tag IDs into the request tag list, but does not synthesize zero-filled TLVs for CDOL slots that have no value in context. When enabled, missing CDOL tags are appended as Tag + Length + zero-filled Value using the CDOL-declared length.

<table data-header-hidden><thead><tr><th width="201.6666259765625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td valign="top">Property Description</td></tr><tr><td valign="top">Property OID</td><td valign="top">1.2.1.1.1.1C / 0x01010101011C</td></tr><tr><td valign="top">Name</td><td valign="top">CDOL Zero Filled Tags Enable</td></tr><tr><td valign="top">Description</td><td valign="top"><p>Enables or disables zero-fill of missing CDOL tags in ARQC and Batch output.</p><p>0 = Disable: Do not synthesize zero-filled TLVs for missing CDOL tags (default).</p><p>1 = Enable: For each CDOL slot not present in the built TLV stream, append a TLV with value bytes set to 0x00 using the length declared in CDOL (8C for ARQC, 8D for Batch).</p></td></tr><tr><td valign="top">Securing Key</td><td valign="top">None</td></tr><tr><td valign="top">Min. Len (b)</td><td valign="top">1</td></tr><tr><td valign="top">Max. Len (b)</td><td valign="top">1</td></tr><tr><td valign="top">Data Type</td><td valign="top">Binary</td></tr><tr><td valign="top">Valid Values</td><td valign="top">0x00 = Disable 0x01 = Enable</td></tr><tr><td valign="top">Default</td><td valign="top">0x00 - Disabled</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 81040191 D101 840F D101 850101 870401010101 8902 DC00</td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA0081048291D10182040000000084820010D1018501018704010101018903DC0100</td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 81040155 D111 8410 D111 850101 870401010101 8903 DC0100</td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA0081048255D11182040000000084820010D1118501018704010101018903DC0100</td></tr></tbody></table>

## Property 1.2.1.1.2.1  - Signature Capture Control

<table data-header-hidden><thead><tr><th width="221.272705078125" valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.2.1 / 0x010201010201</td></tr><tr><td valign="top">Name</td><td>Signature Capture Control</td></tr><tr><td valign="top"><p> </p><p>Description</p></td><td>The host can use this property to change whether the device automatically prompts the cardholder for a signature when running <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction"><mark style="color:red;"><strong>Command 0x1001 - Start Transaction</strong></mark></a>, or leaves the triggering of signature capture prompts to the host.</td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>1</td></tr><tr><td valign="top">Max. Len (b)</td><td>1</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td>0x00 = Device-driven Signature Capture 0x01 = Host-driven Signature Capture</td></tr><tr><td valign="top">Default</td><td>0x00</td></tr></tbody></table>

#### Get Request Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 04 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E2 02 C1 00</p></td></tr></tbody></table>

#### Get Response Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 04 D1 01 82 04 00 00 00 00 84 82 00 1B D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0B E2 09 E1 07 E1 05 E2 03 C1 01 01</p></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 02 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E2 09 E1 07 E1 05</p><p>E2 03 C1 01 01</p></td></tr></tbody></table>

#### Set Response Example&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 02 D1 11 82 04 00 00 00 00 84 82 00 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0B E2 09 E1 07 E1 05 E2 03 C1 01 01</p></td></tr></tbody></table>

## Property 1.2.1.1.2.2  - Include Signature Data in EMV Batch Data (Touch Only)

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.2.2 / 0x010201010202</td></tr><tr><td valign="top">Name</td><td>Include Signature Data in EMV Batch Data</td></tr><tr><td valign="top"><p> </p><p>Description</p></td><td>The device uses this property to determine whether to include signature capture coordinate data in TLV data object DFDF3E when it returns <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects/emv-batch-data-type"><mark style="color:red;"><strong>EMV Batch Data Type</strong></mark></a> while running <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction"><mark style="color:red;"><strong>Command 0x1001 - Start Transaction</strong></mark></a><mark style="color:red;"><strong>.</strong></mark></td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>1</td></tr><tr><td valign="top">Max. Len (b)</td><td>1</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top"><p> </p><p>Valid Values</p></td><td><p>0x00 = Include signature data in EMV Batch Data Type</p><p>0x01 = RESERVED. Make signature data available as file. Use <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd821-start-get-file-from-device"><mark style="color:red;"><strong>Command 0xD821 - Start Get File from Device</strong></mark></a> to request file type Signature Capture File to retrieve the data as a Signature Capture File Type.</p></td></tr><tr><td valign="top">Default</td><td>0x00</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 04 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E2 02 C2 00</p></td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 04 D1 01 82 04 00 00 00 00 84 82 00 1B D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0B E2 09 E1 07 E1 05 E2 03 C2 01 01</p></td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 02 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E2 09 E1 07 E1 05</p><p>E2 03 C2 01 01</p></td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 02 D1 11 82 04 00 00 00 00 84 82 00 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0B E2 09 E1 07 E1 05 E2 03 C2 01 01</p></td></tr></tbody></table>

## Property 1.2.1.1.2.3 - Signature Timing Window (Touch Only)

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.2.3 / 0x010201010203</td></tr><tr><td valign="top">Name</td><td>Signature Timing Window</td></tr><tr><td valign="top"><p> </p><p>Description</p></td><td>The device uses this property to determine how long to wait, in seconds, for <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1801-request-cardholder-signature-touch-only"><mark style="color:red;"><strong>Command 0x1801 - Request Cardholder Signature</strong></mark></a> while running <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction"><mark style="color:red;"><strong>Command 0x1001 - Start Transaction</strong></mark></a>.</td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>1</td></tr><tr><td valign="top">Max. Len (b)</td><td>1</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top"><p> </p><p>Valid Values</p></td><td><p>0x00 = No Wait Time. If the device uses this setting, the host must wait at least one second after receiving <a href="https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/0x01nn-transactions/0x0105-transaction-operation-complete"><mark style="color:red;"><strong>Notification 0x0105 - Transaction Operation Complete</strong></mark></a> before performing any other operations.</p><p>0x01..0xFF = Wait the Specified Number of Seconds</p></td></tr><tr><td valign="top">Default</td><td>0x01 (second)</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 04 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E2 02 C3 00</p></td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 04 D1 01 82 04 00 00 00 00 84 82 00 1B D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0B E2 09 E1 07 E1 05 E2 03 C3 01 03</p></td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 02 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E2 09 E1 07 E1 05</p><p>E2 03 C3 01 01</p></td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 02 D1 11 82 04 00 00 00 00 84 82 00 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0B E2 09 E1 07 E1 05 E2 03 C3 01 01</p></td></tr></tbody></table>

## Property 1.2.1.1.3.1 - Contactless Low Power Card Detect (Contactless Only)&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.3.1 / 0x0102010100301</td></tr><tr><td valign="top">Name</td><td>Contactless Low Power Card Detect</td></tr><tr><td valign="top"><p> </p><p>Description</p></td><td>The device uses this property to enable/disable contactless low power card detect (Proximity Detection Mode). When disabled, device will read a contactless card as soon as the card is detected. If enabled, device will track and delay reading a contactless card, allowing user to use Contact or MSR card slots.</td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>1</td></tr><tr><td valign="top">Max. Len (b)</td><td>1</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td>0x00 = Disable 0x01 = Enable</td></tr><tr><td valign="top">Default</td><td>0x00 - Disabled</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA 00 81 04 01 55 D1 01 84 0F D1 01 85 01 01 87 04 02 01 01 03 89 02 C1 00</td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 55 D1 01 82 04 00 00 00 00 84 82 00 10 D1 01 85 01 01 87 04 02 01 01 03 89 03 C1</p><p>01 00</p></td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA 00 81 04 01 55 D1 11 84 10 D1 11 85 01 01 87 04 02 01 01 03 89 03 C1 01 00</td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 55 D1 11 82 04 00 00 00 00 84 82 00 10 D1 11 85 01 01 87 04 02 01 01 03 89 03 C1</p><p>01 00</p></td></tr></tbody></table>

## Property 1.2.1.1.4.1 - MIFARE Ultralight C 2keys3DES&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.4.1 / 0x0102010100401</td></tr><tr><td valign="top">Name</td><td>MIFARE Ultralight C 2keys3DES</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>Description</p></td><td><p>The device uses this property to set 16-byte of the 2keys 3DES for MIFARE Ultralight C authentication.</p><p> </p><p>On an example of Key1 = 0001020304050607h and Key2 = 08090A0B0C0D0E0Fh, the setting should be 000102030405060708090A0B0C0D0E0F</p><p>For security, the Get request for this property will always return 3-MSB of KCV. This key will be encrypted and stored in KPM.</p></td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>16</td></tr><tr><td valign="top">Max. Len (b)</td><td>16</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td> </td></tr><tr><td valign="top">Default</td><td>49454D4B 41455242 214E4143 554F5946</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 06 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E4 02 C1 00</p></td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 06 D1 01 82 04 00 00 00 00 84 82 00 1D D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01</p><p>89 0D E2 0B E1 09 E1 07 E4 05 C1 03 29 07 96</p></td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 55 D1 11 84 1F D1 11 85 01 01 87 04 02 01 01 04 89 12 C1 10 00 01 02 03 04 05 06</p><p>07 08 09 0A 0B 0C 0D 0E 0F</p></td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 82 55 D1 11 82 04 00 00 00 00 84 82 00 1F D1 11 85 01 01 87 04 02 01 01 04 89 12 C1</p><p>10 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F</p></td></tr></tbody></table>

## Property 1.2.1.1.4.2 - MIFARE Ultralight AES DataProtKey.

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.4.2 / 0x0102010100402</td></tr><tr><td valign="top">Name</td><td>MIFARE Ultralight AES DataProtKey.</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>Description</p></td><td><p>The device uses this property to set 16-byte of the AES_DataProtKey for MIFARE Ultralight AES authentication.</p><p> </p><p>On an example of ASE Key = 000102030405060708090A0B0C0D0E0Fh, the setting should be 000102030405060708090A0B0C0D0E0F</p><p>For security, the Get request for this property will always return 4-MSB of KCV. This key will be encrypted and stored in KPM.</p></td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>16</td></tr><tr><td valign="top">Max. Len (b)</td><td>16</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td> </td></tr><tr><td valign="top">Default</td><td>00000000 00000000 00000000 00000000</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 06 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E4 02 C2 00</p></td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00810482D3D1018204000000008482001ED10181072B06010401F609850101890EE20CE10AE10 8E406C204763CBCDE</td></tr></tbody></table>

#### MIFARE Ultralight AES DataProtKey. - Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 55 D1 11 84 1F D1 11 85 01 01 87 04 02 01 01 04 89 12 C2 10 00 01 02 03 04 05 06</p><p>07 08 09 0A 0B 0C 0D 0E 0F</p></td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00810482E5D1118204000000008482002AD11181072B06010401F609850101891AE218E116E11 4E412C210000102030405060708090A0B0C0D0E0F</td></tr></tbody></table>

## Property 1.2.1.1.4.3 - MIFARE Ultralight AES UIDRetrKey.

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.4.3 / 0x0102010100403</td></tr><tr><td valign="top">Name</td><td>MIFARE Ultralight AES UIDRetrKey.</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>Description</p></td><td><p>The device uses this property to set 16-byte of the AES UIDRetrKey for MIFARE Ultralight AES authentication.</p><p> </p><p>On an example of the ASE Key = 000102030405060708090A0B0C0D0E0Fh, the setting should be 000102030405060708090A0B0C0D0E0F</p><p>For security, the Get request for this property will always return 4-MSB of KCV. This key will be encrypted and stored in KPM.</p></td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>16</td></tr><tr><td valign="top">Max. Len (b)</td><td>16</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td> </td></tr><tr><td valign="top">Default</td><td>00000000 00000000 00000000 00000000</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 06 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E4 02 C3 00</p></td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00810482D3D1018204000000008482001ED10181072B06010401F609850101890EE20CE10AE10 8E406C304B548CFB4</td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 55 D1 11 84 1F D1 11 85 01 01 87 04 02 01 01 04 89 12 C3 10 00 01 02 03 04 05 06</p><p>07 08 09 0A 0B 0C 0D 0E 0F</p></td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00810482E5D1118204000000008482002AD11181072B06010401F609850101891AE218E116E11 4E412C310000102030405060708090A0B0C0D0E0F</td></tr></tbody></table>

## Property 1.2.1.1.4.4 - MIFARE Ultralight AES OriginalityKey.&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>1.2.1.1.4.4 / 0x0102010100404</td></tr><tr><td valign="top">Name</td><td>MIFARE Ultralight AES OriginalityKey.</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p>Description</p></td><td><p>The device uses this property to set 16-byte of the AES OriginalityKey for MIFARE Ultralight AES.</p><p> </p><p>On an example of the ASE Key = 000102030405060708090A0B0C0D0E0Fh, the setting should be 000102030405060708090A0B0C0D0E0F</p><p>For security, the Get request for this property will always return 4-MSB of KCV. This key will be encrypted and stored in KPM.</p></td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>16</td></tr><tr><td valign="top">Max. Len (b)</td><td>16</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td> </td></tr><tr><td valign="top">Default</td><td>00000000 00000000 00000000 00000000</td></tr></tbody></table>

#### Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 06 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E2 08 E1 06 E1 04</p><p>E4 02 C4 00</p></td></tr></tbody></table>

#### Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00810482D3D1018204000000008482001ED10181072B06010401F609850101890EE20CE10AE10 8E406C404763CBCDE</td></tr></tbody></table>

#### Set Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top"><p>AA 00 81 04 01 55 D1 11 84 1F D1 11 85 01 01 87 04 02 01 01 04 89 12 C4 10 00 01 02 03 04 05 06</p><p>07 08 09 0A 0B 0C 0D 0E 0F</p></td></tr></tbody></table>

#### Set Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00810482E5D1118204000000008482002AD11181072B06010401F609850101891AE218E116E11 4E412C410000102030405060708090A0B0C0D0E0F</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/properties/1.2.nnnn-device-settings/1.2.1.nnn-transaction-settings-a.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.
