> 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/sred-settings-property-subgroup-1.1.2.nnn/sred-settings-property-subgroup-1.1.2.nnn-a.md). # SRED Settings - Property Subgroup 1.1.2.nnn - A ## Table SREDA-1 - ISO/ABA Masking Character - Property 1.1.2.2.1.2


Property Description
Property OID	1.1.2.2.1.2 / 0x010102020102
Name	ISO/ABA Masking Character
Description	The device uses this property to determine what character it should use when sending masked ISO/ABA track data. If the Property 1.1.2.2.1.5 PAN MOD 10 Check Digit Correction is enabled, the masked portions of the track will always be masked with ‘0’. For more information about masking, see the information at the bottom of this section.
Securing Key	None
Min. Len (b)	0x00
Max. Len (b)	0x01
Data Type	Character
Valid Values	Any ASCII character
Default	‘0’

## Table SREDA-2 - ISO/ABA Masking Character - Get Request Example

Example (Hex)

AA 00 81 04 01 17 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E1 08 E2 06 E2 04

E1 02 C2 00

## Table SREDA-3 - ISO/ABA Masking Character - Get Response Example

Example (Hex)

AA 00 81 04 82 17 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 E1 09 E2 07 E2 05 E1 03 C2 01 2A

## Table SREDA-4 - ISO/ABA Masking Character - Set Request Example

Example (Hex)

AA 00 81 04 01 0F D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E1 09 E2 07 E2 05

E1 03 C2 01 30

## Table SREDA-5 - ISO/ABA Masking Character - Set Response Example

Example (Hex)

AA 00 81 04 82 0F 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 E1 09 E2 07 E2 05 E1 03 C2 01 30

**When the device sends masked track data, it replaces some characters in the track data with a specified mask character. The specific characters the device masks depends on the card encode type. The device only selectively masks data that came from ISO/ABA cards (Financial Cards with *****ISO/IEC 7813***** Format code B); it sends data from all other card types entirely unmasked.** The device masks all fields from ISO/ABA cards except a number of configurable leading and trailing characters of the PAN. See Property 1.1.2.2.1.3 PAN Number of Leading Unmasked Characters and Property 1.1.2.2.1.4 PAN Number of Trailing Unmasked Characters. **For chip card transactions, masked track 2 data is contained in TLV data object DFDF4D. For magnetic stripe transactions, masked track 1, 2 and 3 data is contained in TLV data objects DFDF31, DFDF33 and DFDF35, respectively.** Table 513 below provides an example of data from tracks 1, 2, and 3 of an ISO/ABA card after it has been decrypted or if the device has sent it in the clear. Table 514 shows the same data as it might appear with a specific set of masking rules applied. ## Table SREDA-6 - Sample ISO/ABA Track Data, Clear Text / Decrypted


Sample ISO/ABA Track Data, Clear Text / Decrypted
Track 1	%B6011000995500000^ TEST CARD ^15121015432112345678?
Track 2	;6011000995500000=15121015432112345678?
Track 3	;6011000995500000=15121015432112345678333333333333333333333?

## Table SREDA-7 - Sample ISO/ABA Track Data, Masked


Sample ISO/ABA Track Data, Masked
Track 1	%B6011000020000000^0000000000^00000000000000000000?
Track 2	;6011000020000000=00000000000000000000?
Track 3	;6011000020000000=00000000000000000000000000000000000000000?

## Table SREDA-8 - PAN Number of Leading Unmasked Characters - Property 1.1.2.2.1.3


Property Description
Property OID	1.1.2.2.1.3 / 0x010102020103
Name	PAN Number of Leading Unmasked Characters
Description	The device uses this property to determine how many of the leading characters of the PAN the device sends unmasked in Masked Track x Data in ISO/ABA account information For details about ISO/ABA track masking, see Property 1.1.2.2.1.2 ISO/ABA Masking Character.
Securing Key	None
Min. Len (b)	0x01
Max. Len (b)	0x01
Data Type	Binary
Valid Values	Min 0x00 Max 0x08, if PAN length is less than 16, the number of unmasked characters will be limited to 6.
Default	0x04

## Table SREDA-9 - PAN Number of Leading Unmasked Characters - Get Request Example

Example (Hex)

AA 00 81 04 01 18 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E1 08 E2 06 E2 04

E1 02 C3 00

## Table SREDA-10 - PAN Number of Leading Unmasked Characters- Get Response Example

Example (Hex)

AA 00 81 04 82 18 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 E1 09 E2 07 E2 05 E1 03 C3 01 04

## Table SREDA-11 - PAN Number of Leading Unmasked Characters - Set Request Example

Example (Hex)

AA 00 81 04 01 10 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E1 09 E2 07 E2 05

E1 03 C3 01 04

## Table SREDA-12 - PAN Number of Leading Unmasked Characters - Set Response Example

Example (Hex)

AA 00 81 04 82 10 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 E1 09 E2 07 E2 05 E1 03 C3 01 04

## Table SREDA-13 - PAN Number of Trailing Unmasked Characters - Property 1.1.2.2.1.4


Property Description
Property OID	1.1.2.2.1.4 / 0x010102020104
Name	PAN Number of Trailing Unmasked Characters
Description	The device uses this property to determine how many of the trailing characters of the PAN the device sends unmasked in Masked Track x Data in ISO/ABA account information For details about ISO/ABA track masking, see Property 1.1.2.2.1.2 ISO/ABA Masking Character.
Securing Key	None
Min. Len (b)	0x01
Max. Len (b)	0x01
Data Type	Binary
Valid Values	Min 0x00 Max 0x04
Default	0x04

## Table SREDA-14 - PAN Number of Trailing Unmasked Characters - Get Request Example

Example (Hex)

AA 00 81 04 01 19 D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E1 08 E2 06 E2 04

E1 02 C4 00

## Table SREDA-15 - PAN Number of Trailing Unmasked Characters - Get Response Example

Example (Hex)

AA 00 81 04 82 19 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 E1 09 E2 07 E2 05 E1 03 C4 01 04

## Table SREDA-16 - PAN Number of Trailing Unmasked Characters - Set Request Example

Example (Hex)

AA 00 81 04 01 11 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E1 09 E2 07 E2 05

E1 03 C4 01 04

## Table SREDA-17 - PAN Number of Trailing Unmasked Characters - Set Response Example

Example (Hex)

AA 00 81 04 82 11 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 E1 09 E2 07 E2 05 E1 03 C4 01 04

## Table SREDA-18 - PAN MOD 10 Check Digit Correction - Property 1.1.2.2.1.5


Property Description
Property OID	1.1.2.2.1.5 / 0x010102020105
Name	PAN MOD 10 Check Digit Correction
Description	The device uses this property to determine whether it should modify one of the masked PAN digits such that the masked PAN passes the Luhn MOD-10 algorithm check. If this property is enabled, the device uses masking character ‘0’ to mask the PAN, regardless of the setting in Property 1.1.2.2.1.2 ISO/ABA Masking Character, and masks the remainder of the track data with the configured masking character.
Securing Key	None
Min. Len (b)	0x01
Max. Len (b)	0x01
Data Type	Binary
Valid Values	0x00 = Disabled 0x01 = Enabled
Default	0x01

## Table SREDA-19 - PAN MOD 10 Check Digit Correction - Get Request Example

Example (Hex)

AA 00 81 04 01 1A D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E1 08 E2 06 E2 04

E1 02 C5 00

## Table SREDA-20 - PAN MOD 10 Check Digit Correction - Get Response Example

Example (Hex)

AA 00 81 04 82 1A 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 E1 09 E2 07 E2 05 E1 03 C5 01 01

## Table SREDA-21 - PAN MOD 10 Check Digit Correction - Set Request Example

Example (Hex)

AA 00 81 04 01 12 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E1 09 E2 07 E2 05

E1 03 C5 01 01

## Table SREDA-22 - PAN MOD 10 Check Digit Correction - Set Response Example

Example (Hex)

AA 00 81 04 82 12 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 E1 09 E2 07 E2 05 E1 03 C5 01 01

## Table SREDA-23 - PAN MOD 10 Check Digit Validation (MCE Only) - Property 1.1.2.2.1.6


Property Description
Property OID	1.1.2.2.1.6 / 0x010102020106
Name	PAN MOD 10 Check Digit Validation
Description	The device uses this property to determine whether to use the Luhn MOD-10 algorithm to validate card number (PAN) digits a cardholder or operator enters in manual card entry mode during Command 0x1001 - Start Transaction. If validation is enabled, the device checks the PAN digits during entry, and until the PAN passes the check, the device disables the ENTER key, sounds an error tone when the Enter key is pressed (if the command has audio feedback enabled), and stays at the Card Number prompt until the cardholder or operator presses the Cancel button or corrects the PAN.
Securing Key	None
Min. Len (b)	0x01
Max. Len (b)	0x01
Data Type	Binary
Valid Values	0x00 = Disabled 0x01 = Enabled
Default	0x00

## Table SREDA-24 - PAN MOD 10 Check Digit Validation (MCE Only) - Get Request Example

Example (Hex)

AA 00 81 04 01 1A D1 01 84 1A D1 01 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0A E1 08 E2 06 E2 04

E1 02 C6 00

## Table SREDA-25 - PAN MOD 10 Check Digit Validation (MCE Only) - Get Response Example

Example (Hex)

AA 00 81 04 82 1A 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 E1 09 E2 07 E2 05 E1 03 C6 01 00

## Table SREDA-26 - PAN MOD 10 Check Digit Validation (MCE Only) - Set Request Example

Example (Hex)

AA 00 81 04 01 12 D1 11 84 1B D1 11 81 07 2B 06 01 04 01 F6 09 85 01 01 89 0B E1 09 E2 07 E2 05

E1 03 C6 01 01

## Table SREDA-27 - PAN MOD 10 Check Digit Validation (MCE Only) - Set Response Example

Example (Hex)

AA 00 81 04 82 12 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 E1 09 E2 07 E2 05 E1 03 C6 01 01

## Table SREDA-28 - Key Mapping of PIN-TDES (Touch Only)Key Mapping of PIN-TDES - Property 1.1.2.4.1.1


Property Description
Property OID	1.1.2.4.1.1 / 0x010102040101
Name	Key Mapping of PIN-TDES
Description	The device uses this property to determine which DUKPT Key Set and Variant shall be used for PIN-TDES.
Securing Key	None
Min. Len (b)	0x03
Max. Len (b)	0x03
Data Type	Binary
Valid Values	See DUKPT Key Mapping for detail information.
Default	0x00, 0x00, 0x01

## Table SREDA-29 - Key Mapping of PIN-TDES (Touch Only)Key Mapping of PIN-TDES - Get Request Example


Example (Hex)
AA00 81040159D101 841AD101 81072B06010401F609 850101 890AE108E206E404E102C100

## Table SREDA-30 - Key Mapping of PIN-TDES (Touch Only)Key Mapping of PIN-TDES - Get Response Example

Example (Hex)

AA00 81048259D101 820400000000 8482001DD101 81072B06010401F609 850101

890DE10BE209E407E105C1 03200701

## Table SREDA-31 - Key Mapping of PIN-TDES (Touch Only)Key Mapping of PIN-TDES - Set Request Example


Example (Hex)
AA00 8104015AD111 841DD111 81072B06010401F609 850101 890DE10BE209E407E105C1 03200701

## Table SREDA-32 - Key Mapping of PIN-TDES (Touch Only)Key Mapping of PIN-TDES - Set Response Example

Example (Hex)

AA00 8104825AD111 820400000000 8482001DD111 81072B06010401F609 850101

890DE10BE209E407E105C1 03200701

## Table SREDA-33 - Key Mapping of Account DataKey Mapping of Account Data - Property 1.1.2.4.1.2


Property Description
Property OID	1.1.2.4.1.2 / 0x010102040102
Name	Key Mapping of Account Data
Description	The device uses this property to determine which DUKPT Key Set and Variant/Usage shall be used for Account Data.
Securing Key	None
Min. Len (b)	0x03
Max. Len (b)	0x03
Data Type	Binary
Valid Values	See DUKPT Key Mapping for detail information.
Default	0x20, 0x07, 0x04

## Table SREDA-34 - Key Mapping of Account DataKey Mapping of Account Data - Get Request Example


Example (Hex)
AA00 81040159D101 841AD101 81072B06010401F609 850101 890AE108E206E404E102C200

## Table SREDA-35 - Key Mapping of Account DataKey Mapping of Account Data - Get Response Example

Example (Hex)

AA00 81048259D101 820400000000 8482001DD101 81072B06010401F609 850101

890DE10BE209E407E105C2 03200704

## Table SREDA-36 - Key Mapping of Account DataKey Mapping of Account Data - Set Request Example


Example (Hex)
AA00 8104015AD111 841DD111 81072B06010401F609 850101 890DE10BE209E407E105C2 03200704

## Table SREDA-37 - Key Mapping of Account DataKey Mapping of Account Data - Set Response Example

Example (Hex)

AA00 8104825AD111 820400000000 8482001DD111 81072B06010401F609 850101

890DE10BE209E407E105C2 03200704

## Table SREDA-38 - Key Mapping of MACKey Mapping of MAC - Property 1.1.2.4.1.3


Property Description
Property OID	1.1.2.4.1.3 / 0x010102040103
Name	Key Mapping of MAC
Description	The device uses this property to determine which DUKPT Key Set and Variant/Usage shall be used for MAC.
Securing Key	None
Min. Len (b)	0x03
Max. Len (b)	0x03
Data Type	Binary
Valid Values	See DUKPT Key Mapping for detail information.
Default	0x20, 0x07, 0x02

## Table SREDA-39 - Key Mapping of MACKey Mapping of MAC - Get Request Example


Example (Hex)
AA00 81040159D101 841AD101 81072B06010401F609 850101 890AE108E206E404E102C300

## Table SREDA-40 - Key Mapping of MACKey Mapping of MAC - Get Response Example

Example (Hex)

AA00 81048259D101 820400000000 8482001DD101 81072B06010401F609 850101

890DE10BE209E407E105C3 03200702

## Table SREDA-41 - Key Mapping of MACKey Mapping of MAC - Set Request Example


Example (Hex)
AA00 8104015AD111 841DD111 81072B06010401F609 850101 890DE10BE209E407E105C3 03200702

## Table SREDA-42 - Key Mapping of MACKey Mapping of MAC - Set Response Example

Example (Hex)

AA00 8104825AD111 820400000000 8482001DD111 81072B06010401F609 850101

890DE10BE209E407E105C3 03200702

## Table SREDA-43 - Key Mapping of Magneprint (MSR Only)Key Mapping of Magneprint - Property 1.1.2.4.1.4


Property Description
Property OID	1.1.2.4.1.4 / 0x010102040104
Name	Key Mapping of Magneprint
Description	The device uses this property to determine which DUKPT Key Set and Variant/Usage shall be used for Magneprint.
Securing Key	None
Min. Len (b)	0x03
Max. Len (b)	0x03
Data Type	Binary
Valid Values	See DUKPT Key Mapping for detail information.
Default	0x20, 0x07, 0x04

## Table SREDA-44 - Key Mapping of Magneprint (MSR Only)Key Mapping of Magneprint - Get Request Example


Example (Hex)
AA00 81040159D101 841AD101 81072B06010401F609 850101 890AE108E206E404E102C400

## Table SREDA-45 - Key Mapping of Magneprint (MSR Only)Key Mapping of Magneprint - Get Response Example

Example (Hex)

AA00 81048259D101 820400000000 8482001DD101 81072B06010401F609 850101

890DE10BE209E407E105C4 03200704

## Table SREDA-46 - Key Mapping of Magneprint (MSR Only)Key Mapping of Magneprint - Set Request Example


Example (Hex)
AA00 8104015AD111 841DD111 81072B06010401F609 850101 890DE10BE209E407E105C4 03200704

## Table SREDA-47 - Key Mapping of Magneprint (MSR Only)Key Mapping of Magneprint - Set Response Example

Example (Hex)

AA00 8104825AD111 820400000000 8482001DD111 81072B06010401F609 850101

890DE10BE209E407E105C4 03200704

## **Key Mapping of MagTek Token - Property 1.1.2.4.1.5** This OID is reserved for Mey Mapping of MagTek Token. --- # 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/sred-settings-property-subgroup-1.1.2.nnn/sred-settings-property-subgroup-1.1.2.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.