For the complete documentation index, see llms.txt. This page is also available as Markdown.

EMV Types

The device formats ARQC messages as shown in Table 19. The default is an EMV standard list of ARQC message tags. The host may also customize the contents of ARQC messages by setting Property 1.1.1.1.1.2 EMV ARQC Message Tag List.

EMV ARQC (DynaPro Format) Type

Table - EMV ARQC (DynaPro Format) Type

Tag

Len

Value / Description

Typ

Req

Default

2-byte MSB message length excluding padding and CBC-MAC

F9

var

Container for MAC structure and generic data

T

R

/DFDF54

var

MAC KSN

B

R

/DFDF55

01

MAC Encryption Type

See section 4.4 Encryption Type for a list of valid values.

B

R

/DFDF25

var

Device Serial Number (IFD Serial Number)

B

R

/FA

var

Container for generic data

T

R

//70

var

Container for ARQC

T

R

///82

02

Application Interchange Profile

Available on:

DynaFlex I FW Ver CA1 or newer DynaProx FW Ver A8 or newer DynaFlex II FW Ver A6 or newer

B

O

///9F6E

var

Third Party Data

Available on:

DynaFlex I FW Ver CA1 or newer DynaProx FW Ver A8 or newer DynaFlex II FW Ver A6 or newer

B

O

///DFDF53

01

Fallback Indicator

· 0x00 = No Fallback

· 0x01 = Technical Fallback

· 0x81 = MSR Fallback

B

R

///DFDF33

var

Masked Track 2 MSR Data

If the payment method presented by the cardholder provides it

AN

O

///DFDF4D

var

Masked Track 2 ICC Data

If the payment method presented by the cardholder provides it

AN

O

///DFDF52

01

Card Type

· 0x00 = Other

· 0x01 = Magnetic Stripe ISO/ABA Financial (MSR)

· 0x02 = Magnetic Stripe AAMVA (MSR)

· 0x03 = Manual Entry

· 0x04 = Unknown

· 0x05 = Contact Chip Card (ICC)

· 0x06 = Contactless Chip Card (PICC), EMV

· 0x07 = MSR Financial and Contact Chip Card (ICC)

B

R

Table - EMV ARQC (DynaPro Format) Type

Tag

Len

Value / Description

Typ

Req

Default

· 0x08 = Contactless PICC, Magnetic Stripe Data (MSD)

///FF42

var

Container for Selectable Encrypted Card Data Set up OID 1.1.2.6.1.1 to enable this container.

T

O

////DFDFDF37

var

Selectable Encrypted Data Primitive

Decrypt the value of this TLV data object using the algorithm and variant specified in the Selectable Encrypted Data KSN parameter and the Selectable Encrypted Data Encryption Type parameter. See Table 21 - EMV ARQC (DynaPro Format) DFDFDF37 Decrypted Contents for the data structure as it should appear after decryption.

(This item will be present if 0xFF42 is enabled)

B

O

////DFDFDF38

0C

Selectable Encrypted Data KSN

(This item will be present if 0xFF42 is enabled)

B

O

////DFDFDF39

01

Selectable Encrypted Data Encryption Type (This item will be present if 0xFF42 is enabled)

B

O

///DF2A

06

Tip Mode Sale Amount Entered

B

O

///DF2B

06

Tip Mode Total Amount

B

O

///DF5D

06

Tip Amount

B

O

///DF5E

06

Tax Amount

B

O

///F8

var

Container for Encrypted Data

T

R

////DFDF59

var

Encrypted Data Primitive

Decrypt the value of this TLV data object using the algorithm and variant specified in the Encrypted Transaction Data KSN parameter and the Encrypted Transaction Data Encryption Type parameter to read its contents. See Table 20 for the data structure as it should appear after decryption.

B

R

////DFDF56

var

Encrypted Transaction Data KSN

B

R

////DFDF57

01

Encrypted Transaction Data Encryption Type

See section 4.4 Encryption Type for a list of valid values.

B

R

////DFDF58

01

Number of Padding Bytes

Number of bytes added to DFDF59 value to force its length to a multiple of 8 bytes for TDES, or 16 bytes for AES.

B

R

/FE

Var

VAS Data Container

See Table 25 – VAS Data Container Payload

T

O

/FF40

Var

Fleet Data Container (Common Kernel Only)

See Table 4.5 9 – Fleet Data Container Payload

T

O

Table - EMV ARQC (DynaPro Format) Type

Tag

Len

Value / Description

Typ

Req

Default

Padding to ensure the length of data, starting with the message length at the very beginning, and ending with any additional padding, is a multiple of 8 bytes for TDES, or 16 bytes for AES. This is a requirement of using the CBC-MAC algorithm.

Four-byte CBC-MAC. The host should calculate the CBC-MAC and verify that it matches. For details about calculating a CBC-MAC, see About Message Authentication Codes (MAC).

The device encrypts the value inside the Encrypted Data Primitive container using the Encrypted Transaction Data Encryption Type parameter and working key associated with the keyset number currently active in the device’s configuration. As a requirement for using DUKPT encryption algorithms, the device pads it so the length of its value is a multiple of 8 bytes for TDES, or 16 bytes for AES. The device uses container DFDF58 to report how many bytes of data object DFDF59 are padding. Data object DFDF59 itself is formatted like Table 20 after the host decrypts it.

Table - EMV ARQC (DynaPro Format) DFDF59 Decrypted Contents

Tag

Len

Value / Description

Typ

Req

Default

FC

var

Decrypted Data Container

Inside this container, the device inserts all EMV TLV data objects specified by the setting in Property 1.1.1.1.1.2 EMV ARQC Message Tag List. The remainder of this table shows the basic structure and content of MagTek custom tags. For definitions of all other standard EMV tags that can be included directly under container FC, see EMV 4.3 Book 3.

T

R

/DF29

08

Only if tag DF29 is included in Property 1.1.1.1.1.2 EMV ARQC Message Tag List.

Outcome Parameter Set Byte 1 - Outcome

0x10 = Approved

0x20 = Declined

0x30 = Online Request 0x40 = End Application

0x50 = Select Next Application 0x60 = Try Another Interface 0x70 = Try Again

0xF0 = N/A

Byte 2 – Entry Point Start 0x00 = Start A

0x10 = Start B 0x20 = Start C 0x30 = Start D 0xF0 = N/A

Byte 3 – Entry Point Online Response

B

O

Table - EMV ARQC (DynaPro Format) DFDF59 Decrypted Contents

Tag

Len

Value / Description

Typ

Req

Default

0x00 = EMV Data 0x10 = Any

0xF0 = N/A

Byte 4 – CVM 0x00 = No CVM

0x10 = Obtain Signature 0x20 = Online PIN

0x30 = Confirmation Code Verified 0xF0 = N/A

Byte 5 – UI/Data/Receipt

0x80 = UI Request on Outcome Present 0x40 = UI Request on Restart Present 0x20 = Data Record Present

0x10 = Discretionary Data Present 0x08 = Provide Receipt

Byte 6 – Alternate Interface Preference 0x10 = Contact

0x20 = MSR

0xF0 = N/A

Byte 7 – Field Off Request FF = N/A

Byte 8 – Removal Timeout

/F4

var

Container for encrypted MSR data (MSR Only)

T

O

//DFDF36

01

Encrypted Track 1 Status (MSR Only)

· 0x00 = OK

· 0x01 = Empty

· 0x02 = Error

· 0x03 = Disabled

B

O

//DFDF37

var

Encrypted Track 1 Data (MSR Only)

B

O

//DFDF38

01

Encrypted Track 2 Status (MSR Only)

· 0x00 = OK

· 0x01 = Empty

· 0x02 = Error

· 0x03 = Disabled

B

O

//DFDF39

var

Encrypted Track 2 Data (MSR Only)

B

O

//DFDF3A

01

Encrypted Track 3 Status (MSR Only)

· 0x00 = OK

· 0x01 = Empty

· 0x02 = Error

· 0x03 = Disabled

B

O

Table - EMV ARQC (DynaPro Format) DFDF59 Decrypted Contents

Tag

Len

Value / Description

Typ

Req

Default

//DFDF3B

var

Encrypted Track 3 Data (MSR Only)

B

O

//DFDF3C

var

Encrypted MagnePrint Data (MSR Only)

Only included for MSR swipe transactions and when Track Data and Magneprint are using the same KSN.

B

O

//DFDF43

04

MagnePrint Status Data (MSR Only)

Only included for MSR swipe transactions and when Track Data and Magneprint are using the same KSN.

· Bit 0 = MagnePrint Capable Flag

o 0 = Device is not MagnePrint capable

o 1 = Device is MagnePrint capable

· Bits 1 through 3 = Mode

o 0 = Standard MagnePrint

o 1 = Extended MagnePrint

· Bits 4 through 15 = ASIC Revision

· Bit 16 = Reserved

· Bit 17 = Reserved

· Bit 18 = Swipe too slow

· Bit 19 = Swipe too fast

· Bit 20 = Reserved

· Bit 21 = Card swipe direction

o 0 = Forward

o 1 = Reverse Bits 22..31 = Reserved

B

O

//DFDF50

var

MSR KSN Data (MSR Only)

Key Serial Number for the key the host should use to decrypt Encrypted Track 1 Data, Encrypted Track 2 Data, Encrypted Track 3 Data and Encrypted MagnePrint Data.

B

O

//DFDF51

01

MSR Encryption Type (MSR Only)

See section 4.4 Encryption Type for a list of valid values.

B

O

/FF73

var

Container for Encrypted MagnePrint Data (MSR Only) Only included when Track Data and MagnePrint encryption keys are using different KSN

T

O

//DFDF3C

var

Encrypted MagnePrint Data (MSR Only) Only included for MSR swipe transactions.

B

O

//DFDF43

04

MagnePrint Status Data (MSR Only)

Only included for MSR swipe transactions.

· Bit 0 = MagnePrint Capable Flag

o 0 = Device is not MagnePrint capable

o 1 = Device is MagnePrint capable

· Bits 1 through 3 = Mode

o 0 = Standard MagnePrint

o 1 = Extended MagnePrint

· Bits 4 through 15 = ASIC Revision

B

O

Table - EMV ARQC (DynaPro Format) DFDF59 Decrypted Contents

Tag

Len

Value / Description

Typ

Req

Default

· Bit 16 = Reserved

· Bit 17 = Reserved

· Bit 18 = Swipe too slow

· Bit 19 = Swipe too fast

· Bit 20 = Reserved

· Bit 21 = Card swipe direction

o 0 = Forward

o 1 = Reverse Bits 22..31 = Reserved

//DFDF50

var

MSR KSN Data (MSR Only)

Key Serial Number for the key the host should use to decrypt Encrypted MagnePrint Data.

B

O

//DFDF51

01

MSR Encryption Type (MSR Only)

See section 4.4 Encryption Type for a list of valid values.

B

O

/F5

var

Container for Encrypted PIN Data (Touch Only) Contains ISO PIN Block formatted data in the nested Encrypted PIN Data object, plus supporting information

to decrypt it. The host should use the current PIN DUKPT working key specified in the supporting information.

T

O

//DF71

01

PIN Block Format (Touch Only)

· 0x00 = ISO Format 0

· 0x01 = ISO Format 1

· 0x03 = ISO Format 3

· 0x04 = ISO Format 4

B

O

//99

08

Encrypted PIN Data (Touch Only)

B

O

//DFDF41

var

PIN KSN Data (Touch Only)

B

O

//DFDF42

01

PIN Encryption Type (Touch Only)

See section 4.4 Encryption Type for a list of valid values.

B

O

Padding to force DFDF59 plus padding to be a multiple of 8 bytes

Table - EMV ARQC (DynaPro Format) DFDFDF37 Decrypted Contents

Tag

Len

Value / Description

Typ

Req

Default

FC

var

Decrypted Data Container

Inside this container, if the data is not available for a given selected card data, the tag will still get transmitted with a length of ‘1’ and value = ‘*’.

T

R

/5F20

var

Only if Byte 0 – Bit 0 is set in Property 1.1.2.6.1.1 Selectable Card Data Encryption Enable.

Cardholder Name

an

O

/5A

var

Only if Byte 0 – Bit 1 is set in Property 1.1.2.6.1.1 Selectable Card Data Encryption Enable.

n15/ n16

O

Table - EMV ARQC (DynaPro Format) DFDFDF37 Decrypted Contents

Tag

Len

Value / Description

Typ

Req

Default

Primary Account Number

/5F24

02/

03

Only if Byte 0 – Bit 2 is set in Property 1.1.2.6.1.1 Selectable Card Data Encryption Enable.

Expiration Date, YYMM or YYMMDD

n4/ n6

O

/5F30

02

Only if Byte 0 – Bit 3 is set in Property 1.1.2.6.1.1 Selectable Card Data Encryption Enable.

Service Code

n3

O

/9F1F

var

Only if Byte 0 – Bit 4 is set in Property 1.1.2.6.1.1 Selectable Card Data Encryption Enable.

T1 Discretionary Data

an

O

/9F20

var

Only if Byte 0 – Bit 5 is set in Property 1.1.2.6.1.1 Selectable Card Data Encryption Enable.

T2 Discretionary Data

cn

O

Padding to force DFDFDF37 plus padding to be a multiple of 16 bytes for AES encryption.

Table – EMV ARQC Enhanced DFDF59 Decrypted Contents for EMV Data

Tag

Len

Value / Description

Typ

Req

Default

FC

var

Decrypted Data Container

This contains all EMV TLV data objects specified in

Property 1.1.1.1.1.2 EMV ARQC Message Tag List.

T

R

/FE

Var

VAS Data Container

See Table 25 – VAS Data Container Payload

T

O

Padding to ensure the length of data, starting with the message length at the very beginning, and ending with any additional padding, is a multiple of 8 bytes for TDES, or 16 bytes for AES. This is a requirement of using the CBC-MAC algorithm.

Table – EMV ARQC Enhanced DFDF59 Decrypted Contents for MSR and MagnePrint Data

Tag

Len

Value / Description

Typ

Req

Default

FC

var

Decrypted Data Container

Inside this container, the device inserts all EMV TLV data objects specified by the setting in Property 1.1.1.1.1.2 EMV ARQC Message Tag List. The remainder of this table shows the basic structure and content of MagTek custom tags. For definitions of all other standard EMV tags that can be included directly under container FC, see EMV 4.3 Book 3.

T

R

/9F41

04

Transaction Counter

B

R

Table – EMV ARQC Enhanced DFDF59 Decrypted Contents for MSR and MagnePrint Data

Tag

Len

Value / Description

Typ

Req

Default

Starts at 00000000 each time the device powers up or resets, increments for each transaction.

/DFDF36

01

MSR Track 1 Status

· 0x00 = OK

· 0x01 = Empty

· 0x02 = Error

· 0x03 = Disabled

B

O

/DF41

var

MSR Track 1 Clear Text

AN

O

/DFDF38

01

MSR Track 2 Status

· 0x00 = OK

· 0x01 = Empty

· 0x02 = Error

· 0x03 = Disabled

B

O

/DF42

var

MSR Track 2 Clear Text

AN

O

/DFDF3A

01

MSR Track 3 Status

· 0x00 = OK

· 0x01 = Empty

· 0x02 = Error

· 0x03 = Disabled

B

O

/DF43

var

MSR Track 3 Clear Text

AN

O

/DFDF43

04

MagnePrint Status

The device only includes this if MSR and MagnePrint data are both included in the transaction and the device is configured to encrypt them using the same key, to avoid consuming two DUKPT keys encrypting separate containers. If the device is configured to encrypt MSR and MagnePrint data using different keys, it provides MagnePrint data in the Container for Encrypted MagnePrint Data instead.

· Bit 0 = MagnePrint Capable Flag

o 0 = Device is not MagnePrint capable

o 1 = Device is MagnePrint capable

· Bits 1 through 3 = Mode

o 0 = Standard MagnePrint

o 1 = Extended MagnePrint

· Bits 4 through 15 = ASIC Revision

· Bit 16 = Reserved

· Bit 17 = Reserved

· Bit 18 = Swipe too slow

· Bit 19 = Swipe too fast

· Bit 20 = Reserved

· Bit 21 = Card swipe direction

  • 0 = Forward

  • 1 = Reverse

  • Bits 22..31 = Reserved

B

O

Table – EMV ARQC Enhanced DFDF59 Decrypted Contents for MSR and MagnePrint Data

Tag

Len

Value / Description

Typ

Req

Default

/DF44

var

MagnePrint Data

The device only includes this if MSR and MagnePrint data are both included in the transaction and the device is configured to encrypt them using the same key. The host can use this data in conjunction with Magensa services to determine whether the swiped card is authentic.

B

O

/FE

Var

VAS Data Container

See Table 25 – VAS Data Container Payload

T

O

Padding to ensure the length of data, starting with the message length at the very beginning, and ending with any additional padding, is a multiple of 8 bytes for TDES, or 16 bytes for AES. This is a requirement of using the CBC-MAC algorithm.

Table – EMV ARQC Enhanced DFDF59 Decrypted Contents for MagnePrint Data

Tag

Len

Value / Description

Typ

Req

Default

FC

var

Decrypted Data Container

T

R

/DFDF43

var

MagnePrint Status

The device only includes this when MSR and MagnePrint data are included in the transaction, but the device is configured to encrypt them using a different key.

· Bit 0 = MagnePrint Capable Flag

o 0 = Device is not MagnePrint capable

o 1 = Device is MagnePrint capable

· Bits 1..15 = Product revision & mode

· Bit 16 = Reserved

· Bit 17 = Reserved for noise measurement

· Bit 18 = Swipe too slow

· Bit 19 = Swipe too fast

· Bit 20 = Reserved

· Bit 21 = Card swipe direction

o 0 = Forward

o 1 = Reverse

· Bits 22..31 = Reserved

B

R

/DF44

var

MagnePrint Data

The host can use this data in conjunction with Magensa services to determine whether the swiped card is authentic.

B

R

/DF4B

var

MSR PAN

B

R

/FE

Var

VAS Data Container

See Table 25 – VAS Data Container Payload

T

O

Padding to ensure the length of data, starting with the message length at the very beginning, and ending with any additional padding, is a multiple of 8 bytes for TDES, or 16 bytes for AES. This is a requirement of using the CBC-MAC algorithm.

Table - VAS Data Container Payload

Tag

Len

Value / Description

Typ

Req

Default

/FE

var

VAS Data Container

T

O

//FF01

var

Apple VAS Container Slot 1 Container

B

O

///9F27

var

VAS Data

Up to 128 bytes.

B

O

///9F2A

var

Mobile Token Up to 36 bytes.

B

O

//FF02

var

Apple VAS Container Slot 2 Container

B

O

///9F27

var

VAS Data

Up to 128 bytes.

B

O

///9F2A

var

Mobile Token Up to 36 bytes.

B

O

//FF03

var

Apple VAS Container Slot 3 Container

B

O

///9F27

var

VAS Data

Up to 128 bytes.

B

O

///9F2A

var

Mobile Token Up to 36 bytes.

B

O

//FF04

var

Apple VAS Container Slot 4 Container

B

O

///9F27

var

VAS Data

Up to 128 bytes.

B

O

///9F2A

var

Mobile Token Up to 36 bytes.

B

O

//FF05

var

Apple VAS Container Slot 5 Container

B

O

///9F27

var

VAS Data

Up to 128 bytes.

B

O

///9F2A

var

Mobile Token Up to 36 bytes.

B

O

//FF06

var

Apple VAS Container Slot 6 Container

B

O

///9F27

var

VAS Data

Up to 128 bytes.

B

O

///9F2A

var

Mobile Token Up to 36 bytes.

B

O

//FF41

var

Google Smart Tap Container

B

O

///FF01

var

Collector ID Slot 1 Container

B

O

////DF7B

var

Service Response NDEF Record

B

O

///FF02

var

Collector ID Slot 2 Container

B

O

////DF7B

var

Service Response NDEF Record

B

O

Table – VAS Data Container Payload

Tag

Len

Value / Description

Typ

Req

Default

///FF03

var

Collector ID Slot 3 Container

B

O

////DF7B

var

Service Response NDEF Record

B

O

///FF04

var

Collector ID Slot 4 Container

B

O

////DF7B

var

Service Response NDEF Record

B

O

///FF05

var

Collector ID Slot 5 Container

B

O

////DF7B

var

Service Response NDEF Record

B

O

///FF06

var

Collector ID Slot 6 Container

B

O

////DF7B

var

Service Response NDEF Record

B

O

Table – Fleet Data Container Payload (Common Kernel Only)

Tag

Len

Value / Description

Typ

Req

Default

/FF40

var

Fleet Data Container

T

O

//DF30

var

Prompting

B

O

//DF32

var

Purchase Restrictions

B

O

//DF33

var

B

O

//DF34

var

Chip Offline purchase Restrictions for Fuel

B

O

//DF35

var

Chip Offline purchase Restrictions for Non-fuel

B

O

//DF36

var

Relationship Codes

B

O

//DF37

var

3rd Party Reference Data Generation 2

B

O

//DF38

var

Loyalty ID

B

O

//DF39

var

Purchase Device Sequence Number

B

O

//DF40

var

Generic Tag

B

O

//DF41

var

Vehicle/Trailer Number

B

O

//DF42

var

Vehicle Tag

B

O

//DF43

var

Driver ID

B

O

//DF44

var

Driver’s License Number

B

O

//DF45

var

Driver’s License State/Province Abbreviation

B

O

//DF46

var

Driver’s License Name Abbreviation

B

O

//DF47

var

Date of Birth

B

O

//DF48

var

Zip/Postal Code

B

O

//DF49 –

//DF51

var

IFSR Reserved for Future Use

B

O

//DF52

var

Trailer Number

B

O

Table – Fleet Data Container Payload (Common Kernel Only)

Tag

Len

Value / Description

Typ

Req

Default

//DF53

var

Employee Number

B

O

//DF54

var

Work Order / Purchase Order Number

B

O

//DF55

var

Additional Prompted Data 1

B

O

//DF56

var

Additional Prompted Data 2

B

O

//DF57

var

Proprietary Data

B

O

//9F5A

var

B

O

//9F0A

var

ASRPD

B

O

//9F6E

var

M/C Fleet

B

O

//9FD4

var

B

O

//9F50

var

B

O

Table – EMV ARPC Data

Tag
Len
Value / Description
Typ
Req
Default

FF74

var

Container for non-MAC ARPC

T

R

/DFDF25

var

Device Serial Number (IFD Serial Number)

B

R

/FA

var

Container for generic data

T

R

//70

var

Container for ARPC

T

R

///8A

02

Authorization Response Code

  • ‘00’ = Approved

  • ‘01’ = Issuer Referral

  • ‘05’ = Declined

  • ‘12’ = Switch Interface

  • ‘13’ = Request Online PIN

AN

R

///91

var

Issuer Authentication Data As defined in EMV Integrated Circuit Card Specifications for Payment Systems 4.3

B

O

///71

var

Issuer Script Template 1 As defined in EMV Integrated Circuit Card Specifications for Payment Systems 4.3. The host may include as many instances of this parameter as needed, up to a maximum length of 128 bytes including Tags and Lengths.

B

O

///72

var

Issuer Script Template 2 As defined in EMV Integrated Circuit Card Specifications for Payment Systems 4.3. The host may include as many instances of this parameter as needed, up to a maximum length of 128 bytes including Tags and Lengths.

B

O

EMV Batch Data Type

The device formats EMV batch data, such as merchant data and pre-defined EMV batch data tags, using the format shown in Table 27. The default is an EMV standard list of batch data message tags. The host may also customize the contents of batch data messages by setting Property 1.1.1.1.1.3 EMV Batch Data Tag List.

(EMV Contact Only) For unsuccessful transactions, this data object can contain additional pre-defined reversal data. It is normally used by the host for data capture. The default is an EMV standard list of reversal data message tags. The host may also customize the contents of reversal data messages by setting Property 1.1.1.1.1.4 EMV Reversal Data Tag List.

As part of successful completion of Command 0x1001 - Start Transaction, this data structure contains the results of the transaction. The set of tags used during a given EMV transaction is a combination of the tags defined in the EMV specification and the tags that are specific to the kernel being used for the transaction.

EMV Batch Data (DynaPro Format) Type

Table – EMV Batch Data (DynaPro Format) Type

Tag
Len
Value / Description
Typ
Req
Default

2-byte MSB message length excluding padding and CBC-MAC

F9

var

Container for MAC structure and generic data

T

R

/DFDF54

var

MAC KSN

B

R

/DFDF55

01

MAC Encryption Type See section 4.4 Encryption Type for a list of valid values.

B

R

/DFDF25

var

Device Serial Number (IFD Serial Number)

B

R

/FA

var

Container for Generic Data

T

R

//F0

var

Transaction Results

T

R

///F1

var

Container for Status Data

T

R

////DFDF1A

01

Transaction Status

  • 0x00 = Accept

  • 0x01 = Decline

  • 0x02 = Error

B

R

////DFDF1B

01

Additional Transaction Information 0x00

B

R

///F8

var

Container for Encrypted Data

T

R

////DFDF59

var

Encrypted Data Primitive Decrypt the value of this TLV data object according to the Encrypted Transaction Data KSN parameter and the Encrypted Transaction Data Encryption Type parameter to read its contents. See Table 28 for the data structure as it should appear after decryption. Use the data variant of the current MSR DUKPT working key used in the relevant transaction.

B

R

////DFDF56

var

Encrypted Transaction Data KSN

B

R

////DFDF57

01

Encrypted Transaction Data Encryption Type See section 4.4 Encryption Type for a list of valid values.

B

R

////DFDF58

01

Number of padding bytes added to DFDF59 value to force length to a multiple of 8 bytes

B

R

///F7

var

Merchant Data This contains an instance of Merchant Data Container.

T

R

/FE

Var

VAS Data Container See Table 25 – VAS Data Container Payload

T

O

Padding to ensure the length of data, starting with the message length at the very beginning, and ending with any additional padding, is a multiple of 8 bytes for TDES, or 16 bytes for AES. This is a requirement of using the CBC-MAC algorithm.

Four-byte CBC-MAC. The host should calculate the CBC-MAC and verify that it matches. For details about calculating a CBC-MAC, see About Message Authentication Codes (MAC).

Table – EMV Batch Data (DynaPro Format) DFDF59 Decrypted Contents

Tag
Len
Value / Description
Typ
Req
Default

FC

var

Decrypted Data Container

T

/F2

var

Container for Batch Data This data object contains the set of EMV TLV data objects specified in Property 1.1.1.1.1.3 EMV Batch Data Tag List.

T

//DF29

08

Only if tag DF29 is included in Property 1.1.1.1.1.3 EMV Batch Data Tag List Outcome Parameter Set Byte 1 - Outcome 0x10 = Approved 0x20 = Declined 0x30 = Online Request 0x40 = End Application 0x50 = Select Next Application 0x60 = Try Another Interface 0x70 = Try Again 0xF0 = N/A Byte 2 – Entry Point Start 0x00 = Start A 0x10 = Start B 0x20 = Start C 0x30 = Start D 0xF0 = N/A Byte 3 – Entry Point Online Response 0x00 = EMV Data 0x10 = Any 0xF0 = N/A Byte 4 – CVM 0x00 = No CVM 0x10 = Obtain Signature 0x20 = Online PIN 0x30 = Confirmation Code Verified 0xF0 = N/A Byte 5 – UI/Data/Receipt 0x80 = UI Request on Outcome Present 0x40 = UI Request on Restart Present 0x20 = Data Record Present 0x10 = Discretionary Data Present 0x08 = Provide Receipt Byte 6 – Alternate Interface Preference 0x10 = Contact 0x20 = MSR 0xF0 = N/A Byte 7 – Field Off Request FF = N/A Byte 8 – Removal Timeout

B

O

/F3

var

(EMV Contact Only) Container for Reversal Data, if any This data object contains the set of EMV TLV data objects specified in Property 1.1.1.1.1.4 EMV Reversal Data Tag List.

T

O

null

/F4

var

Container for encrypted MSR data (MSR Only)

T

O

//DFDF36

01

Encrypted Track 1 Status (MSR Only)

  • 0x00 = OK

  • 0x01 = Empty

  • 0x02 = Error

  • 0x03 = Disabled [Property 1.1.2.5.1.2 Track 1 Enable (MSR Only) set to Disabled]

B

O

//DFDF37

var

Encrypted Track 1 Data (MSR Only)

B

O

//DFDF38

01

Encrypted Track 2 Status (MSR Only)

  • 0x00 = OK

  • 0x01 = Empty

  • 0x02 = Error

  • 0x03 = Disabled [Property 1.1.2.5.1.3 Track 2 Enable (MSR Only) set to Disabled]

B

O

//DFDF39

var

Encrypted Track 2 Data (MSR Only)

B

O

//DFDF3A

01

Encrypted Track 3 Status (MSR Only)

  • 0x00 = OK

  • 0x01 = Empty

  • 0x02 = Error

  • 0x03 = Disabled [Property 1.1.2.5.1.4 Track 3 Enable (MSR Only) set to Disabled]

B

O

//DFDF3B

var

Encrypted Track 3 Data (MSR Only)

B

O

//DFDF3C

var

Encrypted MagnePrint Data (MSR Only) Only included for MSR swipe transactions and when Track Data and Magneprint are using the same KSN.

B

O

//DFDF43

04

MagnePrint Status Data (MSR Only) Only included for MSR swipe transactions and when Track Data and Magneprint are using the same KSN.

B

O

//DFDF50

var

MSR KSN Data (MSR Only)

B

O

//DFDF51

01

MSR Encryption Type (MSR Only) See section 4.4 Encryption Type for a list of valid values.

B

O

/FF73

var

Container for Encrypted MagnePrint Data (MSR Only) Only included when Track Data and MagnePrint encryption keys are using different KSN

T

O

//DFDF3C

var

Encrypted MagnePrint Data (MSR Only) Only included for MSR swipe transactions.

B

O

//DFDF43

04

MagnePrint Status Data (MSR Only) Only included for MSR swipe transactions.

B

O

//DFDF50

var

MSR KSN Data (MSR Only) Key Serial Number for the key the host should use to decrypt Encrypted MagnePrint Data.

B

O

//DFDF51

01

MSR Encryption Type (MSR Only) See section 4.4 Encryption Type for a list of valid values.

B

O

/F5

00

Container for Encrypted PIN Data (Touch Only)

T

O

//DF71

00

PIN Block Format (Touch Only)

  • 0x00 = ISO Format 0

  • 0x01 = ISO Format 1

  • 0x03 = ISO Format 3

  • 0x04 = ISO Format 4

B

O

//99

00

Encrypted PIN Data (Touch Only)

B

O

//DFDF41

00

PIN KSN Data (Touch Only)

B

O

//DFDF42

00

PIN Encryption Type (Touch Only) See section 4.4 Encryption Type for a list of valid values.

B

O

null

(var)

Padding to force DFDF59 plus padding to be a multiple of 8 bytes

B

Table - EMV Batch Data (DynaPro Format) DFDF59 Decrypted Contents

Tag
Len
Value / Description
Typ
Req
Default

FC

var

Decrypted Data Container

T

/F2

var

Container for Batch Data This data object contains the set of EMV TLV data objects specified in Property 1.1.1.1.1.3 EMV Batch Data Tag List.

T

/F3

var

Container for Reversal Data, if any This data object contains the set of EMV TLV data objects specified in Property 1.1.1.1.1.4 EMV Reversal Data Tag List.

T

O

null

null

(var)

Padding to force DFDF59 plus padding to be a multiple of 8 bytes or 16 bytes depending on the cipher block size of the algorithm being used.

B

/FE

Var

VAS Data Container See Table 25 – VAS Data Container Payload

T

O

/FE

Merchant Data Container

Merchant Data is normally used by the host for receipt printing. The contents of this container are not customizable.

Table - Merchant Data Container

EMV Terminal Configuration File Type

The host uses Command 0xD812 - Start Send File to Device (Unsecured) to load this file type to control the behavior of the device’s EMV contact kernel. The configuration loaded using this file type must be designed to work together with all instances of EMV Processing Configuration File Type and EMV Entry Point Configuration File Type the host loads into the device.

MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet for more convenient authoring, review, and change tracking. For a reference sample spreadsheet that contains EMVCo approved configurations, contact MagTek Support Services.

This document shows one example of the available Contact Level 2 certified configurations (DynaFlex C01, Merchant, Attended, ODA). To see which configurations are supported on the devices you are using, see the list of Vendor Config IDs in the device’s Letter of Approval for Contact Level 2 posted in the list of Approved / Evaluated products on the EMVCo web site. For detailed descriptions of the tags included in this file type, including possible valid values and their effects on device behavior, see EMV Integrated Circuit Card Specifications for Payment Systems v4.3.

Table - EMV Configuration Terminal File Type

Tag
Len
Value / Description
Typ
Req
Example

File Type Version

One byte indicating the version of the file type format being used.

0xAA

SHA-1 Hash

20-byte hash of all values that follow.

9F1A

02

Terminal Country Code

B

R

08 40

DF79

01

Cardholder Confirmation

B

R

01

9F35

01

Terminal Type

B

R

21

DF0A

01

EMV Contact Supported

B

R

01

9F33

03

Terminal Capabilities

B

R

E0 28 C8

9F40

05

Additional Terminal Capabilities

B

R

EF 80 F0 A0 01

DF55

01

EMV Contactless Supported

B

R

01

DF0B

01

Magnetic Stripe Supported

B

R

01

DF27

01

Time allocated to enter a PIN

B

R

0A

DF06

01

Batch / Online Data Capture managed

B

R

01

DF08

00

Advice Managed

B

R

00

DF7A

01

PSE Supported

B

R

01

DF0D

00

AutoRun Mode

B

R

00

DF10

03

Predefined amount for AutoRun mode

B

R

00 00 00

DF7B

01

PIN Bypass Supported

B

R

00

DF07

01

Referral Managed

B

R

01

DF09

01

Default TAC supported when regular TACs are not present

B

R

01

DF73

05

Default TAC default

B

R

00 00 00 00 00

DF74

05

Default TAC denial

B

R

00 00 00 00 00

DF75

05

Default TAC online

B

R

00 00 00 00 00

DF53

01

Random Transaction Selection not supported

B

R

00

DF54

01

Velocity Checking not supported

B

R

00

DF7C

01

CDA Mode

B

R

01

EMV Processing Configuration File Type

The host uses Command 0xD812 - Start Send File to Device (Unsecured) to load this file type to control the behavior of the device’s EMV kernels. The host must compile a single instance of this file type containing multiple instances of the AID Delimiter Container, one for each contact or contactless AID the device should support. For each instance of the AID Delimiter Container where tag 9F01 is set to a contactless AID, the host must load a corresponding instance of an Entry Point Table when it loads the EMV Entry Point Configuration File Type.

Table - EMV Configuration Processing File Type

File Type Version

One byte indicating the version of the file type format being used. 0xAA

SHA-1 Hash

20-byte hash of all values that follow.

FF33

var

Inside each AID Delimiter Container:

Tag
Len
Value / Description
Typ
Req
Example

/9F01

06

Payment Brand Identifier This serves as supporting information to clarify whether this instance of the AID Delimiter Container is for Contact or Contactless. Byte 1 upper nibble must be set to a value flagging that it corresponds to a Contactless AID, generally by using 0xC0 or 0xF0. For Contact AID, the value of Byte 1 is 00. Byte 1 lower nibble:

  • 0 = Contact

  • 1 = Interac (Common Kernel Only)

  • 2 = Mastercard Contactless

  • 3 = Visa payWave

  • 4 = Expresspay

  • 5 = JCB (Common Kernel Only)

  • 6 = Discover D-PAS

  • 7 = China UnionPay (Common Kernel Only)

Bytes 2..5 Reserved for future use

B

R

F2 00 00 00 00 00

/4F

0..16

Application Identifier (AID)

B

R

A0 00 00 00 04 10 10

/DF7E

01

ASI

B

R

01

/9F09

02

Application Version Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00

/DF11

01

Skip TAC/IAC default supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF12

01

Random transaction selection supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF13

01

Velocity checking supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF14

01

Floor limit checking supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF15

01

TAC supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF20

05

TAC default Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00 00 00 00

/DF21

05

TAC denial Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00 00 00 00

/DF22

05

TAC online Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00 00 00 00

/9F1B

04

Floor limit Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00 00 00

/DF70

01

Target percentage Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF6E

03

Threshold value Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00 00

/DF6F

01

Maximum target percentage Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF01

01

Default DDOL supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF71

0..FC

DDOL Only applies when Payment Brand Identifier indicates Contact.

B

R

/DF02

01

Default TDOL supported Only applies when Payment Brand Identifier indicates Contact.

B

R

00

/DF72

0..252

TDOL Only applies when Payment Brand Identifier indicates Contact.

B

R

/5F2A

02

Currency Code Only applies when Payment Brand Identifier indicates Contact.

B

R

00 00

/5F36

01

Transaction currency exponent Only applies when Payment Brand Identifier indicates Contact.

B

R

00

Additional instances of the AID Delimiter Container parameter, one per Application Identifier (AID) the device should support.

The host uses Command 0xD812 - Start Send File to Device (Unsecured) to load this file type to control the behavior of the device’s EMV kernels.

Table - EMV Entry Point Configuration File Type Header

Tag
Value (hex)
Description

File Type Version

One byte indicating the version of the file type format being used.

0xAA

SHA-1 Hash

20-byte hash of all values that follow

One or more instances of the following entry point tables for supported contactless payment brands. The host should include an Entry Point Table for each transaction type to be supported by each contactless payment brand AID listed in the loaded EMV Processing Configuration File Type.

Mastercard MCL Entry Point Table

Table - Mastercard MCL Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x02 = MasterCard Contactless (MCL)

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

02 01 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F1A

02

Terminal Country Code

B

R

08 40

//9F35

01

Terminal Type

B

R

21

//9F40

05

Additional Terminal Capabilities

B

R

00 00 00 00 00

//9F7E

01

Mobile Support Indicator

B

R

01

//DF0C

01

Kernel ID

B

R

02

//DF1B

01

Kernel Configuration

  • Bit 8 = MSD Mode Not Supported

  • Bit 7 = EMV Mode contactless transaction not supported

  • Bit 6 = On-Device-CVM Supported

  • Bit 5 = Relay Resistance Protocol Supported

  • Bit 4..1 = Reserved for future use

B

R

20

//DF2D

03

Message Hold Time (100 of ms)

B

R

00 00 0D

//9F6D

02

Magnetic Stripe Application Version Number This value only applies when the Kernel Configuration parameter is set to support MSD. The device ignores this value.

B

R

00 01

//DF1A

03

Magnetic Stripe Default UDOL This value only applies when the Kernel Configuration parameter is set to support MSD. The device ignores this value.

B

R

9F 6A 04

//DF1E

01

CVM Capability - CVM Required This value only applies when the Kernel Configuration parameter is set to support MSD. The device ignores this value.

B

R

00

//DF2C

01

CVM Capability - No CVM Required This value only applies when the Kernel Configuration parameter is set to support MSD. The device ignores this value.

B

R

00

//9F09

02

EMV Application Version Number

B

R

00 02

//DF03

01

Security Capabilities

  • Bit 8 = SDA

  • Bit 7 = DDA

  • Bit 6 = Card Capture

  • Bit 5 = Reserved for future use

  • Bit 4 = CDA

  • Bits 3..1 = Reserved for future use

B

R

08

//DF17

01

Card Data Input Capabilities

  • Bit 8 = Manual Key Entry

  • Bit 7 = MSR

  • Bit 6 = ICC

  • Bits 5..1 = Reserved for future use

B

R

60

//DF18

01

CVM Capability - CVM Required

  • Bit 8 = Offline Plaintext PIN

  • Bit 7 = Enciphered Online PIN

  • Bit 6 = Signature

  • Bit 5 = Enciphered Offline PIN

  • Bit 4 = No CVM

  • Bits 3..1 = Reserved for future use

B

R

28

//DF19

01

CVM Capability - No CVM Required

  • Bit 8 = Offline Plaintext PIN

  • Bit 7 = Enciphered Online PIN

  • Bit 6 = Signature

  • Bit 5 = Enciphered Offline PIN

  • Bit 4 = No CVM

  • Bits 3..1 = Reserved for future use

B

R

08

//DF1C

02

Max Lifetime Torn Transaction(s)

B

R

01 2C

//DF1D

01

Max Number Torn Transaction

B

R

00

//DF20

05

Terminal Action Code - Default

B

R

00 00 00 00 00

//DF21

05

Terminal Action Code - Denial

B

R

00 00 00 00 00

//DF22

05

Terminal Action Code - Online

B

R

00 00 00 00 00

//DF04

0

Balance Read Before GenAC

B

R

//DF05

0

Balance Read After GenAC

B

R

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 01 00 00

//DF24

06

Reader Contactless Transaction Limit (No On-Device CVM)

B

R

00 00 00 03 00 00

//DF25

06

Reader Contactless Transaction Limit (On-Device CVM)

B

R

00 00 00 05 00 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 00 10 00

//DF27

02

Timeout Value (ms)

B

R

13 88

//DF30

01

Hold time value before field off (100 of ms)

B

R

0D

//DF32

02

Minimum Relay Resistance Grace Period (100 of micro sec)

B

R

00 14

//DF33

02

Maximum Relay Resistance Grace Period (100 of micro seconds)

B

R

00 32

//DF34

02

Terminal Expected Transmission Time for Relay Resistance C-APDU (100 of micro seconds)

B

R

00 12

//DF35

02

Terminal Expected Transmission Time for Relay Resistance R-APDU (100 of micro seconds)

B

R

00 18

//DF36

02

Relay Resistance Accuracy Threshold (100 of micro seconds)

B

R

01 2C

//DF37

01

Relay Resistance Transmission Time Mismatch Threshold (%)

B

R

32

Visa payWave Entry Point Table

Table - Visa payWave Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x03 = Visa payWave

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

03 05 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F35

01

Terminal Type

B

R

21

//9F1A

02

Terminal Country Code

B

R

08 40

//9F33

03

Terminal Capabilities

B

R

00 00 00

//9F40

05

Additional Terminal Capabilities

B

R

00 00 00 00 00

//9F66

04

Terminal Transaction Qualifier

B

R

22 00 40 00

//DF1B

03

Kernel Configuration Byte 1 and further bytes as documented.

B

R

00 00 06

//DF2D

03

Message Hold Time (100 of ms)

B

R

00 00 0F

//9F09

02

EMV Application Version Number

B

R

00 01

//DF30

01

Bitmap Entry Point

  • Bit 8 = Status Check Support Flag

  • Bit 7 = Zero Amount Allowed Flag

  • Bit 6 = Reader Contactless Transaction Limit

  • Bit 5 = Reader Contactless Floor Limit

  • Bit 4 = Reader CVM Required Limit

B

R

F8

//DF32

01

Status Zero Amount Allowed Flag

  • 0x01 = Option 1, Online Cryptogram Request

  • 0x02 = Option 2, Not Allowed

B

R

02

//9F1B

04

Terminal Floor Limit

B

R

00 00 00 00

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 00 20 00

//DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 00 50 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 00 10 00

American Express Expresspay Entry Point Table

Table - American Express Expresspay Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x04 = Expresspay

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

04 04 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F09

02

EMV Application Version Number

B

R

00 01

//9F1A

02

Terminal Country Code

B

R

08 40

//9F33

03

Terminal Capabilities

B

R

60 28 00

//9F35

01

Terminal Type

B

R

21

//9F40

05

Additional Terminal Capabilities

B

R

00 00 00 00 00

//9F6D

01

Contactless Reader Capability Bits 8..7

  • 00 = Expresspay 1.0

  • 01 = Expresspay 2.0 and Expresspay >= 3.x (MSD)

  • 11 = Expresspay >= 3.x(MSD)

Bits 6..1 = 0 (Reserved, not to be configured)

B

R

C0

//DF1B

06

Kernel Configuration (detailed bit definitions)

B

R

31 01 00 00 00 00

//DF27

01

Timeout, Field off request (100 of ms)

B

R

20

//DF2D

03

Message Hold Time (100 of ms)

B

R

00 00 0F

//DF30

01

Bitmap Entry Point

B

R

F8

//DF32

01

Status Zero Amount Allowed

B

R

01

//DF20

05

Terminal Action Code - Default

B

R

00 00 00 00 00

//DF21

05

Terminal Action Code - Denial

B

R

00 00 00 00 00

//DF22

05

Terminal Action Code - Online

B

R

00 00 00 00 00

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 00 20 00

//DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 01 00 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 01 00 00

Discover D-PAS Entry Point Table

Table - Discover D-PAS Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x06 = Discover D-PAS

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

06 06 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F09

02

EMV Application Version Number

B

R

00 01

//9F1A

02

Terminal Country Code

B

R

08 40

//9F33

03

Terminal Capabilities

B

R

00 00 00

//9F35

01

Terminal Type

B

R

21

//9F66

04

Terminal Transaction Qualifier

B

R

B6 00 C0 00

//DF1B

01

Kernel Configuration (bit definitions)

B

R

60

//DF1B

02

Kernel Configuration (Common Kernel Only)

B

R

60 00

//DF30

02

Bitmap Entry Point

B

R

F8

//DF32

01

Status Zero Amount Allowed Flag

B

R

01

//9F1B

06

Terminal Floor Limit

B

R

00 00 00 00

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 01 50 00

//DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 03 00 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 00 20 00

China Unionpay Entry Point Table (Common Kernel Only)

Table – China Unionpay Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x07 = China Unionpay

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

07 05 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F09

02

EMV Application Version Number

B

R

00 30

//9F1A

02

Terminal Country Code

B

R

01 56

//9F33

03

Terminal Capabilities

B

R

60 08 00

//9F35

01

Terminal Type

B

R

21

//9F66

04

Terminal Transaction Qualifier

B

R

36 00 00 80

//DF1B

02

Kernel Configuration Byte1 and Byte2 (bit definitions)

B

R

00 00

//DF20

05

Terminal Action Code - Default

B

R

00 00 00 00 00

//DF21

05

Terminal Action Code - Denial

B

R

00 00 00 00 00

//DF22

05

Terminal Action Code - Online

B

R

00 00 00 00 00

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 01 50 00

//DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 03 00 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 01 20 00

//DF30

01

Bitmap Entry Point

B

R

78

9F1B

04

Terminal Floor Limit

B

R

00 00 3a 98

JCB Entry Point Table (Common Kernel Only)

Table - JCB Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x05 = JCB

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

05 06 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F01

06

Acquirer Identifier

B

R

00 00 00 00 00 01

//9F15

02

Merchant Category Code

B

R

70 32

//9F09

02

EMV Application Version Number

B

R

00 01

//9F1A

02

Terminal Country Code

B

R

03 92

//9F33

03

Terminal Capability

B

R

60 68 08

//9F35

01

Terminal Type

B

R

21

//9F4E

var

Merchant Name and Location

B

R

(example hex provided)

//DF1B

03

Kernel Configuration Byte1..Byte3 (bit definitions)

B

R

7B 00 80

//DF20

05

Terminal Action Code - Default

B

R

90 40 20 80 20

//DF21

05

Terminal Action Code - Denial

B

R

04 10 20 20 20

//DF22

05

Terminal Action Code - Online

B

R

90 60 20 90 20

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 01 50 00

//DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 03 00 00

//DF25

06

On Device CVM Contactless Transaction Limit

B

R

00 00 00 02 50 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 01 20 00

//9F1B

04

Terminal Floor Limit

B

R

00 00 3a 98

Interac Flash Entry Point Table (Common Kernel Only)

Table – Interac Flash Entry Point Table

Tag
Len
Value / Description
Typ
Req
Example

FF35

var

AID Delimiter Container There can be multiple instances of this in sequence. The contents of the first instance are loaded into Entry Point Table Slot 1, the contents of the second are loaded into Entry Point Table Slot 2, etc.

T

R

/DF0E

03

Kernel ID, Processing Slot, Transaction Type Byte 1 Kernel ID

  • 0x41 = Interac Flash

Byte 2 Processing Slot to Use See the AID Delimiter Container parameter in EMV Processing Configuration File Type for information about how to identify slots. Byte 3 Transaction Type

  • 0x00 = Purchase

  • 0x01 = Cash

  • 0x02 = Purchase with cashback

  • 0x03 = Refund

B

R

41 05 00

/DF0F

var

Payload Delimiter Container Include only one of these containers inside each AID Delimiter Container.

T

R

//9F09

02

EMV Application Version Number

B

R

00 02

//9F1A

02

Terminal Country Code

B

R

01 24

//9F33

03

Terminal Capabilities

B

R

60 68 08

//9F35

01

Terminal Type

B

R

21

//9F40

05

Additional Terminal Capabilities

B

R

E0 00 E0 F0 01

//9F58

01

Merchant Type Indicator

B

R

03

//9F5D

06

Receipt Limit

B

R

00 00 00 00 50 00

//9F5E

02

Terminal Option Status Byte1/Byte2 (bit definitions)

B

R

E0 00

//9F5F

06

Reader Contactless Floor Limit

B

R

00 00 00 01 00 00

//DF1B

02

Kernel Configuration Byte1/Byte2 (bit definitions)

B

R

02 34

//DF20

05

Terminal Action Code - Default

B

R

00 00 00 00 00

//DF21

05

Terminal Action Code - Denial

B

R

00 00 00 00 00

//DF22

05

Terminal Action Code - Online

B

R

00 00 00 00 00

//9F1B

04

Terminal Floor Limit

B

R

00 00 1F 40

EMV Configuration CA Public Keys File Type

The host can load this file type to control the behavior of the device’s EMV contact and contactless kernels when the device should support Offline Data Authentication (ODA). Populate all values from information provided by each payment brand that should be supported by the device. The host can load this file using Command 0xD812 - Start Send File to Device (Unsecured).

MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet in xlsx format for more convenient authoring, review, and change tracking. For a reference sample spreadsheet,

contact MagTek Support Services. The MagTek tools expect the spreadsheet to be formatted format as shown in Table 41. Each CA Key to be supported is defined in a tab of the Excel file.

Table - EMV Configuration CA Keys File Type

Tag
Len
Value / Description
Typ
Req
Example

DFDF79

05

Registered Application ID (RID)

B

R

A0 00 00 00 04

DFDF7A

01

CA Public Key Index

B

R

05

DFDF7B

var

CA Public key Modulus

B

R

B8 04 8A … D5 97

DFDF7C

01 or 03

CA Public Key Exponent

B

R

03

DFDF7D

14

CA Public Key Checksum

B

R

EB FA 0D 5D 06 D8 CE 70 2D A3 EA E8 90 70 1D 45 E2 74 C8 45

The MagTek tool converts the spreadsheet data into the format shown in CA Keys Raw Format.

Table - CA Keys Raw Format

CA Keys Raw Format

RID (5 Bytes) As defined by the payment brand.

Index (1 Byte) As defined by the payment brand.

Exponent Length (1 Byte)

  • 0x01

  • 0x03

Key Length (1 Byte), Max of 248 bytes per EMVCo specifications

Exponent (1 or 3 Bytes)

  • 0x03

  • 0x010001

Modulus As defined by the payment brand.

Additional CA Keys, repeating from RID through Modulus, as needed.

SHA-1 hash of all data in the file

EMV American Express DRL Configuration File Type (Not Supported on Expresspay 4.x)

The host can load this file type to control the behavior of the device’s American Express contactless kernel when the card sends tag 9F70 and one or more DRL is defined.

The host can load it using Command 0xD812 - Start Send File to Device (Unsecured). See the Expresspay 4.0.2 specification for functional details.

MagTek provides tools that allow these settings to be loaded using a Microsoft Excel spreadsheet in xlsx format for more convenient authoring, review, and change tracking. For a reference sample spreadsheet, contact MagTek Support Services. The MagTek tools expect the spreadsheet to be formatted as shown in Table 43. Each DRL to be supported is defined in a tab of the Excel file.

Table - EMV Configuration American Express DRL Set File Type

Tag
Len
Value / Description
Typ
Req
Example

DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 00 15 00

DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 00 05 00

DF26

06

Reader CVM Required Limit

B

R

00 00 00 00 10 00

The MagTek tool converts the spreadsheet data into the raw format shown in Table 44:

Table - Raw EMV Configuration American Express DRL Set File Type

Tag
Len
Value / Description
Typ
Req
Example

File Type Version One byte indicating the version of the file type format being used.

  • 0xAA

SHA-1 Hash 20 byte hash of all values that follow

FF37

var

DRL Configuration Container

T

R

/FF36

var

DRL Set Container

T

R

//DF23

06

Reader Contactless Floor Limit

B

R

00 00 00 00 15 00

//DF24

06

Reader Contactless Transaction Limit

B

R

00 00 00 00 05 00

//DF26

06

Reader CVM Required Limit

B

R

00 00 00 00 10 00

Additional instances of DRL Set Container as needed

Last updated