> 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/configuration/device-settings-property-group-1.2.nnnn/transaction-settings-property-subgroup-1.2.1.nnn-a.md). # Transaction Settings - Property Subgroup 1.2.1.nnn - A ## Table TSA-1 - Device-Driven Fallback Behavior (MSR Only) - Property 1.2.1.1.1.1


Property Description
Property OID	1.2.1.1.1.1 / 0x010201010101
Name	Device-Driven Fallback Behavior
Description	The device uses this property to determine whether it should automatically implement payment brand fallback rules without host intervention when running Command 0x1001 - Start Transaction.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 = No device-driven fallback 0x01 = Device-driven fallback enabled
Default	0x01

## Table TSA-2 - Get Request Example - Property 1.2.1.1.1.1

Example (Hex)

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 C1 00

## Table TSA-3 - Get Response Example - Property 1.2.1.1.1.1

Example (Hex)

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 C1 01 01

## Table TSA-4 - Set Request Example - Property 1.2.1.1.1.1

Example (Hex)

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 C1 01 01

## Table TSA-5 - Set Response Example - Property 1.2.1.1.1.1

Example (Hex)

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 C1 01 01

## Table TSA-6 - Application Selection Behavior (Contactless Only) - Property 1.2.1.1.1.2


Property Description
Property OID	1.2.1.1.1.2 / 0x010201010102
Name	Application Selection Behavior
Description	The device uses this property to set the device’s application selection behavior for payment brand selection.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 –Card Preference. 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. 0x01 – Reserved 0x02 – Reserved 0x03 – Enhanced Prompt Cardholder. 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. 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.
Default	0x00 – Card Preference

## Table TSA-7 - Property 1.2.1.1.1.2 - Get Request Example


Example (Hex)
AA00 8104 0155D101 840F D101 8501 01 8704 02010101 8902 C200

## Table TSA-8 - Property 1.2.1.1.1.2 - Get Response Example

Example (Hex)

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

01 00

## Table TSA-9 - Property 1.2.1.1.1.2 - Set Request Example


Example (Hex)
AA00 81040155D111 8410 D111 850101 870402010101 8903 C20103

## Table TSA-10 - Set Response Example - Property 1.2.1.1.1.2

Example (Hex)

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

01 03

## Table TSA-11 - **Device-Driven MSR Fallback Retry Control (MSR Only) - Property 1.2.1.1.1.3**


Property Description
Property OID	1.2.1.1.1.3 / 0x010201010103
Name	Device-Driven MSR Fallback Retry Control
Description	For MSR Fallback case, the device uses this property to configure up to 3 retries before falling back to MSR
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 – 0x03
Default	0x00

## **Table TSA-12 - Get Request Example - Property 1.2.1.1.1.3**


Example (Hex)
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

## **Table TSA-13 - Get Response Example - Property 1.2.1.1.1.3**


Example (Hex)
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

## **Table TSA-14 - Set Request Example - Property 1.2.1.1.1.3**


Example (Hex)
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

## **Table TSA-15 - Set Response Example - Property 1.2.1.1.1.3**


Example (Hex)
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

## Table TSA-16 - Signature Capture Control - Property 1.2.1.1.2.1


Property Description
Property OID	1.2.1.1.2.1 / 0x010201010201
Name	Signature Capture Control
Description	The host can use this property to change whether the device automatically prompts the cardholder for a signature when running Command 0x1001 - Start Transaction, or leaves the triggering of signature capture prompts to the host.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 = Device-driven Signature Capture 0x01 = Host-driven Signature Capture
Default	0x00

## Table TSA-17 - Get Request Example - Property 1.2.1.1.2.1

Example (Hex)

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

E2 02 C1 00

## Table TSA-18 - Get Response Example - Property 1.2.1.1.2.1

Example (Hex)

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 E2 03 C1 01 01

Example (Hex)

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

E2 03 C1 01 01

## Table TSA-20 - Set Response Example - Property 1.2.1.1.2.1

Example (Hex)

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 E2 03 C1 01 01

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


Property Description
Property OID	1.2.1.1.2.2 / 0x010201010202
Name	Include Signature Data in EMV Batch Data
Description	The device uses this property to determine whether to include signature capture coordinate data in TLV data object DFDF3E when it returns EMV Batch Data Type while running Command 0x1001 - Start Transaction.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 = Include signature data in EMV Batch Data Type 0x01 = RESERVED. Make signature data available as file. Use Command 0xD821 - Start Get File from Device to request file type Signature Capture File to retrieve the data as a Signature Capture File Type.
Default	0x00

## Table TSA-22 - Include Signature Data in EMV Batch Data (Touch Only) - Get Request Example

Example (Hex)

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

E2 02 C2 00

## Table TSA-23 - Include Signature Data in EMV Batch Data (Touch Only) - Get Response Example

Example (Hex)

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 E2 03 C2 01 01

## Table TS-24A - Include Signature Data in EMV Batch Data (Touch Only) - Set Request Example

Example (Hex)

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

E2 03 C2 01 01

## Table TS-25A - Include Signature Data in EMV Batch Data (Touch Only) - Set Response Example

Example (Hex)

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 E2 03 C2 01 01

## Table TS-26A - Signature Timing Window (Touch Only) - Property 1.2.1.1.2.3


Property Description
Property OID	1.2.1.1.2.3 / 0x010201010203
Name	Signature Timing Window
Description	The device uses this property to determine how long to wait, in seconds, for Command 0x1801 - Request Cardholder Signature while running Command 0x1001 - Start Transaction.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 = No Wait Time. If the device uses this setting, the host must wait at least one second after receiving Notification 0x0105 - Transaction Operation Complete before performing any other operations. 0x01..0xFF = Wait the Specified Number of Seconds
Default	0x01 (second)

## Table TSA-27 - Signature Timing Window (Touch Only) - Get Request Example

Example (Hex)

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

E2 02 C3 00

## Table TSA-28 - Signature Timing Window (Touch Only) - Get Response Example

Example (Hex)

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 E2 03 C3 01 03

## Table TSA-29 - Signature Timing Window (Touch Only) - Set Request Example

Example (Hex)

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

E2 03 C3 01 01

## Table TSA-30 - Signature Timing Window (Touch Only) - Set Response Example

Example (Hex)

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 E2 03 C3 01 01

## Table TSA-31 - Contactless Low Power Card Detect (Contactless Only) - Property 1.2.1.1.3.1


Property Description
Property OID	1.2.1.1.3.1 / 0x0102010100301
Name	Contactless Low Power Card Detect
Description	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.
Securing Key	None
Min. Len (b)	1
Max. Len (b)	1
Data Type	Binary
Valid Values	0x00 = Disable 0x01 = Enable
Default	0x00 - Disabled

## Table TSA-33 - Contactless Low Power Card Detect (Contactless Only) - Get Request Example


Example (Hex)
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

## Table TSA-34 - Contactless Low Power Card Detect (Contactless Only) - Get Response Example

Example (Hex)

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

01 00

## Table TSA-35 - Contactless Low Power Card Detect (Contactless Only) - Set Request Example


Example (Hex)
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

## Table TSA-36 - Contactless Low Power Card Detect (Contactless Only) - Set Response Example

Example (Hex)

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

01 00

## Table TSA-37 - MIFARE Ultralight C 2keys3DES - Property 1.2.1.1.4.1


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

## Table TSA-38 - MIFARE Ultralight C 2keys3DES - Get Request Example

Example (Hex)

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

E4 02 C1 00

## Table TSA-39 - MIFARE Ultralight C 2keys3DES - Get Response Example

Example (Hex)

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

89 0D E2 0B E1 09 E1 07 E4 05 C1 03 29 07 96

## Table TSA-40 - MIFARE Ultralight C 2keys3DES - Set Request Example

Example (Hex)

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

07 08 09 0A 0B 0C 0D 0E 0F

## Table TSA-41 - MIFARE Ultralight C 2keys3DES - Set Response Example

Example (Hex)

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

10 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

## Table TSA-42 - MIFARE Ultralight AES DataProtKey. - Property 1.2.1.1.4.2


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

## Table TSA-43 - MIFARE Ultralight AES DataProtKey. - Get Request Example

Example (Hex)

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

E4 02 C2 00

## Table TSA-44 - MIFARE Ultralight AES DataProtKey. - Get Response Example


Example (Hex)
AA00810482D3D1018204000000008482001ED10181072B06010401F609850101890EE20CE10AE10 8E406C204763CBCDE

## Table TSA-45 - MIFARE Ultralight AES DataProtKey. - Set Request Example

Example (Hex)

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

07 08 09 0A 0B 0C 0D 0E 0F

## Table TSA-46 - MIFARE Ultralight AES DataProtKey. - Set Response Example


Example (Hex)
AA00810482E5D1118204000000008482002AD11181072B06010401F609850101891AE218E116E11 4E412C210000102030405060708090A0B0C0D0E0F

## Table TSA-47 - MIFARE Ultralight AES UIDRetrKey. - Property 1.2.1.1.4.3


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

## Table TSA-48 - MIFARE Ultralight AES UIDRetrKey. - Get Request Example

Example (Hex)

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

E4 02 C3 00

## Table TSA-49 - MIFARE Ultralight AES UIDRetrKey. - Get Response Example


Example (Hex)
AA00810482D3D1018204000000008482001ED10181072B06010401F609850101890EE20CE10AE10 8E406C304B548CFB4

## Table TSA-50 - MIFARE Ultralight AES UIDRetrKey. - Set Request Example

Example (Hex)

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

07 08 09 0A 0B 0C 0D 0E 0F

## Table TSA-51 - MIFARE Ultralight AES UIDRetrKey. - Set Response Example


Example (Hex)
AA00810482E5D1118204000000008482002AD11181072B06010401F609850101891AE218E116E11 4E412C310000102030405060708090A0B0C0D0E0F

## Table TSA-52 - MIFARE Ultralight AES OriginalityKey. - Property 1.2.1.1.4.4


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

## Table TSA-53 - MIFARE Ultralight AES OriginalityKey. - Get Request Example

Example (Hex)

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

E4 02 C4 00

## Table TSA-54 - MIFARE Ultralight AES OriginalityKey. - Get Response Example


Example (Hex)
AA00810482D3D1018204000000008482001ED10181072B06010401F609850101890EE20CE10AE10 8E406C404763CBCDE

## Table TSA-55 - MIFARE Ultralight AES OriginalityKey. - Set Request Example

Example (Hex)

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

07 08 09 0A 0B 0C 0D 0E 0F

## Table TSA-56 - MIFARE Ultralight AES OriginalityKey. - Set Response Example


Example (Hex)
AA00810482E5D1118204000000008482002AD11181072B06010401F609850101891AE218E116E11 4E412C410000102030405060708090A0B0C0D0E0F

--- # 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/configuration/device-settings-property-group-1.2.nnnn/transaction-settings-property-subgroup-1.2.1.nnn-a.md?ask=&goal= ``` `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.