Card Data Description

Data Object Tag Length Value

(in Bytes)
ATC '9F36' 2 '00 00'

PIN Try Counter '9F17' 1 '03'

Limit (Initial Value)
PIN Try Limit 'C6' 1 '03'

Table 13: Internal Application Data (Values Fixed)

A PUT DATA command with the Issuer Application Data with tag '9F10' shall always
be possible (without Secure Messaging). At a later stage the acess condition for this
DO may be changed so that changing the DO is only allowed with Secure Messaging.

DKV Card Specification1 | 15.11.2021 Page 21

Version 1.21
Card Data Description Fehler! Verweisquelle konnte nicht gefunden werden.

Data Object Tag Length Value/Description

(in Bytes)
Accumulator Data 'BF30' 24 'DF 01 06 00 00 00 00 00 00
DF 11 0C 00 00 00 00 00 00 XX XX XX XX
XX XX'
('XX XX XX XX XX XX' indicates the upper
limit of Accumulator 1 and the value in Cent is
contained in position 52 of the SK-Satz in the
"personalisation bureau interface"
([DKV PBI]). The value is BCD-coded and
right-padded with '0'.
Counter Data 'BF35' 9 'DF 01 01 00 DF 11 02 00 XX''XX' indicates
the upper limit of Counter 1 and is contained
in position 53 of the SK-Satz in the
"personalisation bureau interface" ([DKV PBI])
Limit Entries 'BF3C' 9 'DF 01 06 XX XX XX XX XX XX' 'XX XX XX
XX XX XX' indicates the limit for the cyclic
Accumulator and the value in Cent is
contained in position 51 of the SK-Satz in the
"personalisation bureau interface"
([DKV PBI]). The value is BCD-coded and
right-padded with '0'.
Issuer Options Profile 'BF3B' 10 'DF 01 07 80 21 13 A5 XX 00 00' (contact
Controls only)
('XX' indicates the 20 'DF 01 07 80 21 13 A5 XX 00 00
Derivation Key Index DF 02 07 00 21 13 A5 XX 00 00'
(DKI), that is, the key (dual interface)
version of the IMKAC
fixed by the key
management)
Table 14: Internal Application Data (Card Specific Values)

Optional Data:

Data Object Tag Length Value/Description

(in Bytes)
Security limits 'C5' 6 '04 00 04 00 04 00'
Table 15: Internal Application Data (Optional data)

Page 22 DKV Card Specification1 | 15.11.2021

Version 1.21
 Card Data Description

5.1.2 Data Referenced by the AFL

The card data referenced by SFI in the AFL entries shall be coded as described in Table 16,
Table 18, Table 19, Table 20 and Table 21.

Data Object Rec# Tag Length Value/Description

(in Bytes)
Application Version 01 '9F08' 2 '00 01'
Track 2 Equivalent 01 '57' 19 'XX…XX'. The Coding is described in
Data (Chip) Table 17.
Table 16: Content of EF with SFI 1

Pos. Format Length Description Content personalisation

bureau
interface
1 n...19 up to 19 PAN ISO-Code, Position 6 +
Card number Position 18 of
Checksum the SK-Satz
2 b 1 Field Separator 'D' D
3 n4 4 Expiry Date YYMM Position 26 of
the SK-Satz:
digits 5, 6, 1, 2
4 n1 1 Chip Identifier fix 2= yes
5 n1 1 RFU 0
6 n2 2 Product Restriction nn Position 25 of
Code the SK-Satz
7 n…13 up to RFU 00
131)
Table 17: Coding of the Track 2 Equivalent Data (Chip)

Data Object Rec# Tag Length Value/Description

(in Bytes)
Certification 01 8F 1 'XX'
Authority Public Key
Index
Issuer Public Key 01 '9F32' 1 or 3 '03'
Exponent

1)
The max. length of field number 7 depends on the length of the PAN and is set to 29 – (length of
field 1). This field may be padded at the end with a single hex ‘F’ to ensure whole bytes.

DKV Card Specification1 | 15.11.2021 Page 23

Version 1.21
Card Data Description Fehler! Verweisquelle konnte nicht gefunden werden.

Data Object Rec# Tag Length Value/Description

(in Bytes)
Issuer Public Key 01 '92' Ni - Nca +36 Remainder (rightmost bytes) of
Remainder (if present) Issuer public key modulus
Issuer Public Key 02 '90' 128 to 248 Issuer Public Key, certified by the
Certificate CA;
Same size as CA public key (NCA).
ICC Public Key 03 '9F47' 3 '01 00 01'.
Exponent
ICC Public Key 03 '9F48' Nic - Ni + 42 Remainder (rightmost bytes) of ICC
Remainder (if present) public key
Table 18: Content of EF with SFI 2

Note: The value of this Data Objects is fixed by the key management.

Data Object Rec# Tag Length Value

(in Bytes)
Application 01 '5F24' 3 'YYMMDD'
Expiration Date Date after which the card application can
no longer be used.
The year and month (YYMM) of the
Application Expiration Date is received
from position 26 of the SK-Satz (digits 5,
6, 1, 2) in the "personalisation bureau
interface" ([DKV PBI]). The day (DD) of
the Application Expiration Date shall be
the last day of the month encoded as MM.
Application Primary 01 '5A' up to 10 'XX…XX'
Account Number The PAN is received from position 6 +
(PAN) Chip position 18 of the SK-Satz in the
"personalisation bureau interface"
([DKV PBI]). If the PAN consists of an odd
number of digits, it shall be padded with
one filler 'F' to ensure whole bytes.
Application Usage 01 '9F07' 2 '3D 00'
Control
CDOL1 01 '8C' 27 '9F 02 06 9F 03 06 9F 1A 02 95 05 5F 2A
02 9A 03 9C 01 9F 37 04 9F 35 01 9F 34
03'
CDOL2 01 '8D' 9 '91 08 8A 02 95 05 9F 37 04'
Issuer Country 01 '5F28' 2 'XX XX'
Code The value is received via the
"personalisation bureau
interface"([DKV PBI]).

Page 24 DKV Card Specification1 | 15.11.2021

Version 1.21
 Card Data Description

Data Object Rec# Tag Length Value

(in Bytes)
Static Data 01 '9F4A' 1 '82'
Authentication Tag
List
PAN Sequence 01 '5F34' 1 '00' (Default-Value if data element not
Number (PSN) present in the "personilation bureau
interface")
DDOL 01 '9F49' 3 '9F37 04'
Issuer Action Code 01 '9F0D' 5 'FC 40 C4 80 00'
default
Issuer Action Code 01 '9F0E' 5 '00 10 18 00 00'
denial
Issuer Action Code 01 '9F0F' 5 'FC 40 C4 98 00'
online
Table 19: Content of EF with SFI 3

Data Object Rec# Tag Length Value

(in Bytes)
ICC Public Key 01 '9F46' 128-240 ICC public key certified by the issuer.
Certificate (contact) Same size as issuer public key (Ni).
ICC Public Key 02 '9F46' 128-240 ICC public key certified by the issuer.
Certificate (contactless) Same size as issuer public key (Ni).
Table 20: Content of EF with SFI 4

Note: The value of this Data Objects is fixed by the key management.

Data Object Rec# Tag Length Value

(in Bytes)
CVM List (contact) 01 '8E' 12 '00 00 00 00 00 00 00 00 44 03 02 03'
CVM List 02 '8E' 10 '00 00 00 00 00 00 00 00 02 03'
(contactless)
Table 21: Content of EF with SFI 5

DKV Card Specification1 | 15.11.2021 Page 25

Version 1.21
Card Data Description Fehler! Verweisquelle konnte nicht gefunden werden.

Byte Bit Meaning Denial Online Default

1 b8 Offline data authentication was not performed 0 1 1
b7 SDA failed 0 1 1
b6 ICC data missing 0 1 1
b5 Card appears on terminal exception file 0 1 1
b4 DDA failed 0 1 1
b3 CDA failed 0 1 1
b2 RFU 0 0 0
b1 RFU 0 0 0
2 b8 ICC and terminal have different application versions 0 0 0
b7 Expired application 0 1 1
b6 Application not yet effective 0 0 0
b5 Requested service not allowed for card product 1 0 0
b4 New card 0 0 0
b3 RFU 0 0 0
b2 RFU 0 0 0
b1 RFU 0 0 0
3 b8 Cardholder verification was not successful 0 1 1
b7 Unrecognised CVM 0 0 0
b6 PIN Try Limit exceeded 0 1 1
b5 PIN entry required and PIN pad not present or not working 1 0 0
b4 PIN entry required, PIN pad present, but PIN was not entered 1 0 0
b3 Online PIN entered 0 1 1
b2 RFU 0 0 0
b1 RFU 0 0 0
4 b8 Transaction exceeds floor limit 0 1 1
b7 Lower consecutive offline limit exceeded 0 0 0
b6 Upper consecutive offline limit exceeded 0 0 0
b5 Transaction selected randomly for online processing 0 1 0
b4 Merchant forced transaction online 0 1 0
b3 RFU 0 0 0
b2 RFU 0 0 0
b1 RFU 0 0 0
5 b8 Default TDOL used 0 0 0
b7 Issuer authentication failed 0 0 0
b6 Script processing failed before final GENERATE AC 0 0 0
b5 Script processing failed after final GENERATE AC 0 0 0
b4 RFU 0 0 0
b3 RFU 0 0 0
b2 RFU 0 0 0
b1 RFU 0 0 0

Table 22: Issuer Action Codes Defined for the DKV Card Application

Page 26 DKV Card Specification1 | 15.11.2021

Version 1.21
 Card Data Description

5.1.3 Profile Selection Entry

The profile selection entry shall be contained in the file with SFI 22 and be coded as
described in Table 23. Table 24 shows a simplified list of the Profile Selection Entry. It
checks whether the contactless or the contact transmission mode is used. If the contact
transmission is used the profile ID '01' is selected. Otherwise the profile ID '02' is selected.

Data Object #Record Value

Profile Selection Entry 01 '08 01 01 02 FF 01 00 01 02'
Table 23: Content of EF with SFI 22 (only needed for dual interface cards)

# Extracted Data Comparative Value Check Positive Negative

Type Action Action
1 Application Selection Number 'FF' Match Select profile Select profile
(using masking) ID '01' ID '02'

Table 24: Profile Selection Entry- Overview

5.1.4 Log Entry

Transactions shall be logged in the Log Entry with SFI 21. The Log Entry shall have 10
records.

Each Log Entry has a length of 27 bytes and is built as shown in Table 25.

Position Data Length Format Tag

(in Bytes)
Bytes 1 - 6 Amount, Authorised 6 n 12 '9F02'
Bytes 7 - 8 Transaction Currency Code 2 n3 '5F2A'
Bytes 9 - 11 Transaction Date 3 n6 '9A'
Bytes 12 - 16 CVR 5 b '9F52'
Bytes 17 - 18 ATC 2 b '9F36'
Byte 19 CID 1 b '9F27'
Byte 20 Profile ID 1 b 'CA'
Bytes 21 – 22 Terminal Country Code 2 b '9F1A'
Bytes 23 - 27 TVR 5 b '95'
Table 25: Contents of a Log Entry of the DKV Card Application

Only the data elements (not length or tag) listed in Table 25 are stored in a Log Entry.

DKV Card Specification1 | 15.11.2021 Page 27

Version 1.21
Card Data Description Fehler! Verweisquelle konnte nicht gefunden werden.

5.2 Additional Tables

5.2.1 CIACs

The individual setting of the bits in the CIACs Entry defined for the contact DKV Card
Application is shown in Table 26.

Byte Bit Meaning Decline Default Online

1 b8 Last Online Transaction Not Completed 0 0 0
b7 Go Online On Next Transaction Was Set 0 1 1
b6 Issuer Script Processing Failed 0 1 1
b5 Issuer Authentication Failed 0 0 1
b4 Issuer Authentication Data Not Received in Online 0 0 1
Response
b3 PIN Try Limit Exceeded 0 1 1
b2 Offline PIN Verification Not Performed 0 1 1
b1 Offline PIN Verification Failed 0 1 1
2 b8 Unable To Go Online 0 0 1
b7 Terminal Erroneously Considers Offline PIN OK 0 1 1
b6 Script Received 0 0 0
b5 Offline Data Authentication Failed on Previous 0 0 1
Transaction
b4 Match Found In Additional Check Table 1 0 0 0
b3 No Match Found In Additional Check Table 1 0 0 0
b2 Match Found In Additional Check Table 2 0 0 0
b1 No Match Found In Additional Check Table 2 0 0 0
3 b8 Accumulator 1 Lower Limit Exceeded 0 0 1
b7 Accumulator 2 Lower Limit Exceeded 0 0 0
b6 Counter 1 Lower Limit Exceeded 0 0 1
b5 Counter 2 Lower Limit Exceeded 0 0 0
b4 Counter 3 Lower Limit Exceeded 0 0 0
b3 Accumulator 3 Lower Limit Exceeded 0 0 0
b2 Counter 4 Lower Limit Exceeded 0 0 0
b1 Number of Days Offline Limit Exceeded 0 0 0
4 b8 Accumulator 1 Upper Limit Exceeded 0 1 1
b7 Accumulator 2 Upper Limit Exceeded 0 0 0
b6 Counter 1 Upper Limit Exceeded 0 1 1
b5 Counter 2 Upper Limit Exceeded 0 0 0
b4 Counter 3 Upper Limit Exceeded 0 0 0
b3 Accumulator 3 Upper Limit Exceeded 0 0 0
b2 Counter 4 Upper Limit Exceeded 0 0 0
b1 MTA exceeded 0 0 0

Page 28 DKV Card Specification1 | 15.11.2021

Version 1.21
 Magnetric track structure

Byte Bit Meaning Decline Default Online

5 b8 Cyclic Accumulator 1 Limit Exceeded 0 1 1
b7 Cyclic Accumulator 2 Limit Exceeded 0 0 0
b6 Cyclic Accumulator 3 Limit Exceeded 0 0 0
b5 Check Failed 0 1 1
b4 RFU 0 0 0
b3 RFU 0 0 0
b2 RFU 0 0 0
b1 RFU 0 0 0
6 b8 RFU 0 0 0
b7 RFU 0 0 0
b6 RFU 0 0 0
b5 RFU 0 0 0
b4 RFU 0 0 0
b3 RFU 0 0 0
b2 RFU 0 0 0
b1 RFU 0 0 0
Table 26: Card Issuer Action Codes

6 Magnetric track structure

The encoded information of the DKV CARD is stored on tracks 1, 2 and 3. For the specific
information, please refer to the following description.

The DKV CARD’s magnetic track 1 contains additional information and is alphanumeric in
accordance with ISO 7811/2. Magnetic track 2 is the DKV CARD’s main track and contains
all relevant information in numeric form. Track 3 contains the information of the other tracks
in redundant form for the event that the other tracks cannot be read. In contrast to track 1,
the license plate number on track 3 is stored in encoded form to permit storing of
alphanumeric characters.

Track 2 contains the information if a chip is present on the card (chip identifier). If a chip is
present the payment has to be handled priorized using the chip application.

Fallback to magnetic stripe processing is not permitted. If authorisation via chip is not
possible, the DKV hotline must be called for authorisation (voice authorisation), if
contractually agreed.

In the case of outdoor terminals, voice authorization is not possible.

DKV Card Specification1 | 15.11.2021 Page 29

Version 1.21
Magnetric track structure Fehler! Verweisquelle konnte nicht gefunden werden.

6.1 Coding of Track 1

Nr Position Length Description Content

(Format)
1 1 .. 1 1 Start Sentinel “%”
2 2 .. 2 1 Format Code “A”
3 3 .. 30 28 RFU2
4 31 .. 31 1 Separator “^”
5 32 .. 43 12 Vehicle Tag (License Plate)
6 44 .. 44 1 Separator “^”
7 45 .. 77 33 RFU
8 78 .. 78 1 End Sentinel “?”
9 79 .. 79 1 Control Character (LRC Sum [ISO 7811-2] and
[ISO 7811-6] chapter 11.2)

The length of track 1 is exactly 79 bytes.

2
RFU = Reserved for future use

Page 30 DKV Card Specification1 | 15.11.2021

Version 1.21