ISO/IEC 7816-6:2023

INTERNATIONAL ISO/IEC
STANDARD 7816-6
Fourth edition
2023-04
Identification cards — Integrated
circuit cards —
Part 6:
Interindustry data elements for
interchange
Cartes d'identification — Cartes à circuit intégré —
Partie 6: Éléments de données intersectoriels pour les échanges
Reference number
© ISO/IEC 2023
© ISO/IEC 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2023 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope .1
2 Normative references .1
3 Terms and definitions .1
4 Abbreviated terms and notation . 2
5 Maintenance of interindustry data objects . 3
6 Specific interindustry data elements . 3
6.1 Name of an individual . 3
6.2 Proprietary login data . 3
6.3 Magnetic stripe data . 4
6.4 PIN usage policy . 4
6.5 Login template . 4
6.6 Qualified name template . 5
6.7 Cardholder image template . 6
6.8 Application image template . 6
6.9 Display control template . . 6
7 Identification of integrated circuit manufacturers .6
7.1 General . 6
7.2 Identifier . 6
7.3 Rules for assignment . 7
8 Interchange profile .7
9 Interindustry data elements in alphabetic order .8
10 Interindustry tags in numeric order .15
11 Interindustry templates .23
11.1 Interindustry data objects within interindustry templates . 23
11.2 Interindustry templates defining a context . 25
Annex A (informative) Application for integrated circuit manufacturers number .26
Bibliography .27
iii
© ISO/IEC 2023 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see http://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence
to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT),
see www.iso.org/iso/foreword.html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
This fourth edition cancels and replaces the third edition (ISO/IEC 7816-6:2016), which has been
technically revised.
The main changes compared to the previous edition are as follows:
— The data format of IC manufacturer ID has been extended from a single byte to multiple bytes.
A list of all parts in the ISO/IEC 7816 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
© ISO/IEC 2023 – All rights reserved

Introduction
ISO/IEC 7816 is a series of International Standards specifying integrated circuit cards and the use of
such cards for interchange. These cards are identification cards intended for information exchange
negotiated between the outside world and the integrated circuit in the card. As a result of an information
exchange, the card delivers information (computation result, stored data), and/or modifies its content
(data storage, event memorization).
— Five parts are specific to cards with galvanic contacts and three of them specify electrical interfaces.
— ISO/IEC 7816-1 specifies physical characteristics for cards with contacts.
— ISO/IEC 7816-2 specifies dimensions and location of the contacts.
— ISO/IEC 7816-3 specifies electrical interface and transmission protocols for asynchronous
cards.
— ISO/IEC 7816-10 specifies electrical interface and answer to reset for synchronous cards.
— ISO/IEC 7816-12 specifies electrical interface and operating procedures for USB cards.
— All the other parts are independent from the physical interface technology. They apply to cards
accessed by contacts and/or by radio frequency.
— ISO/IEC 7816-4 specifies organization, security and commands for interchange.
— ISO/IEC 7816-5 specifies registration of application providers.
— ISO/IEC 7816-6 specifies interindustry data elements for interchange.
— ISO/IEC 7816-7 specifies commands for structured card query language.
— ISO/IEC 7816-8 specifies commands for security operations.
— ISO/IEC 7816-9 specifies commands for card management.
— ISO/IEC 7816-11 specifies personal verification through biometric methods.
— ISO/IEC 7816-13 specifies commands for handling the life cycle of applications.
— ISO/IEC 7816-15 specifies cryptographic information application.
The ISO/IEC 10536 series specifies access by close coupling. The ISO/IEC 14443 series and the
ISO/IEC 15693 series specify access by radio frequency. Such cards are also known as contactless cards.
v
© ISO/IEC 2023 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 7816-6:2023(E)
Identification cards — Integrated circuit cards —
Part 6:
Interindustry data elements for interchange
1 Scope
This document specifies directly or by reference, data elements, including composite data elements that
are applicable to interindustry interchange.
It identifies the following characteristics of each data element:
— identifier;
— name;
— description and reference;
— format and coding (if not available in other ISO standards or parts of the ISO/IEC 7816 series).
The layout of each data element is described as seen at the interface between the interface device and
the card.
This document provides the definition of data elements without consideration of any restrictions on the
usage of the data elements.
It does not cover the internal implementation within the card and/or the outside world. With the
exception of login data objects (6.5), only application class tags are eligible in this document.
When using an interindustry template, an application is allowed to nest context-specific class tags (see
ISO/IEC 7816-4) under such a template unless it is previously marked as reserved for future use by ISO/
IEC JTC 1/SC 17.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 4909, Identification cards — Financial transaction cards — Magnetic stripe data content for track
ISO/IEC 7813, Information technology — Identification cards — Financial transaction cards
ISO/IEC 10918-1, Information technology — Digital compression and coding of continuous-tone still
images: Requirements and guidelines
ISO/IEC 11544, Information technology — Coded representation of picture and audio information —
Progressive bi-level image compression
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
© ISO/IEC 2023 – All rights reserved

ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
cardholder
end user of the security device
3.2
data element
item of information seen at the interface for which are defined a name, a description of logical content,
a format and a coding
[SOURCE: ISO/IEC 7816-4:2020, 3.15]
3.3
data object
information seen at the interface consisting of the concatenation of a mandatory tag field, a mandatory
length field and a conditional value field
[SOURCE: ISO/IEC 7816-4:2020, 3.16]
3.4
template
concatenation of BER-TLV data objects (3.3) forming the value field of a constructed BER-TLV data object
Note 1 to entry: The meaning of which is the same when found in ‘XY’ template, template for ‘XY’ DOs or ‘XY’ DOs
template
[SOURCE: ISO/IEC 7816-4:2020, 3.59, modified — Note 1 to entry has been added.]
4 Abbreviated terms and notation
a alphabetic character
n numeric (binary-coded decimal format)
s special character
an alphanumeric character
ans alphanumeric and special characters
.. denotes a range of values between two numbers
BCD binary-coded decimal
BER-TLV basic encoding rules – tag length value
NOTE 1 For BCD several encodings exist, e.g. packed and unpacked. The letter 'n' covers all of them unless
specified otherwise.
Any number following the notation denotes the number of digits or characters.
EXAMPLE
— a3 means three alphabetic characters;
— n.100 means up to 100 digits, lower boundary out of scope for this document (possibly zero, one or any
number lower or equal to 100);
© ISO/IEC 2023 – All rights reserved

— n2.4 means two, three or four numeric digits.
If the number of bits representing a data element is not a multiple of eight, then the mapping into a
byte string should be defined in the context of the respective data element. If not specified otherwise,
the bit-string representing the data element is right-padded with bits set to '1' until the length of the
padded bit-string is a multiple of eight.
YDDD last digit of year concatenated with day of year on three digits
YDDDHHMMSS YDDD concatenated with hour of day, minute and second each on two digits
YYMM last two digits of year concatenated month on two digits
YYMMDD YYMM concatenated with day of month on two digits
YYYYMMDD four digits of year concatenated with month and day of month each on two digits
NOTE 2 The former 3-period notation being equivalent to 2-period notation is deprecated.
5 Maintenance of interindustry data objects
It is the intention that every interindustry data object, specified at the time of publication, should
be listed in this document. To allow the introduction, deletion, or amendment of any data object, the
following procedures shall be adopted:
— Interindustry data objects from the ISO/IEC 7816 series — Following the publication of any part
of the ISO/IEC 7816 series that introduces new data objects, these data objects will be incorporated
into this document at the next revision.
— Interindustry data objects from other standards — For such data objects, an amendment to this
document will be required and this will be subject to the normal ISO/IEC JTC 1 voting procedures.
Following a successful ballot, the data objects will be incorporated into this document.
— Allocation authority — Once an application class tag is allocated to a norm as described above,
this norm becomes the allocation authority for all context-specific data objects it endorses and
encapsulates under the aforementioned tag.
6 Specific interindustry data elements
6.1 Name of an individual
Referenced by tag ‘5B’, this interindustry data element consists of up to 39 bytes; each byte is a character
as defined in ISO/IEC 7501-1. The data element consists of surname, i.e. family name, given name(s), i.e.
forename(s), name suffix, e.g. Jr., number, and filler(s), all coded according to ISO/IEC 8859-1.
National languages with non-Latin characters shall be transliterated or transcribed into the Latin
alphabet using the appropriate International Standard. In cases where names cannot be shown in full
or a special alphabet is needed or the transliteration or transcription is not sufficient, the qualified
name template should be used.
6.2 Proprietary login data
Referenced by tag ‘5E’, this interindustry data element consists of login data with proprietary structures
not specified in the ISO/IEC 7816 series.
© ISO/IEC 2023 – All rights reserved

6.3 Magnetic stripe data
The coding of the magnetic stripe data is as follows:
— referenced respectively by tags ‘5F21’, ‘5F22’ and ‘5F23’, these interindustry data elements shall code
card tracks 1, 2 and 3. Such a tag shall be used when the data element is identical to the data coded
on the corresponding track on the magnetic stripe of the card in accordance with ISO/IEC 7813 and
ISO/IEC 4909;
— referenced respectively by tags ‘56’, ‘57’ and ‘58’, these interindustry data elements shall code
application tracks 1, 2 and 3. Such a tag shall be used when, while formatted according to ISO/IEC 7813
and ISO/IEC 4909, the data element may differ from the data coded on the corresponding track of
the magnetic stripe of the card.
6.4 PIN usage policy
Referenced by tag ‘5F2F’, this interindustry data element shall consist of two bytes. It lists the tests
the terminal shall perform in order to determine whether a PIN (personal identification number) is
applicable to the current transaction, and, therefore, whether the terminal should prompt for the PIN. If
set to one, bit 8 of the first byte specifies that a PIN applies to this application and the terminal should
prompt for the PIN. The meaning of the other fifteen bits is application-dependent. If all bits are set to
zero, then the terminal should not prompt for the PIN. If bit 8 of the first byte is set to one or if any test
implies a PIN, but the PIN cannot be presented, then the action to take is application-dependent.
6.5 Login template
Referenced by tag ‘6A’, this interindustry template shall consist of one or more primitive data objects.
Within the login template, the context-specific class (first byte in the range ‘80’ to ‘BF’) is reserved
for login data objects, such as qualifiers, numbers, texts and delay indicators, as listed in Table 1 and
specified hereafter.
Table 1 — Login data objects
Tag (hex) Meaning
6A Interindustry template for nesting login data objects with the following tags
80 Qualifier
81 Number
82 Text
83, 84 Delay indicators
In this context, ISO/IEC JTC 1/SC 17 reserves any other data object of the context-specific class (first byte
from ‘80’ to ‘BF’)
— Qualifier — Referenced by tag ‘80’ in a login template, this data element shall consist of one to
nine bytes: A mandatory first byte coding a rank, followed by up to eight optional bytes coding a
mnemonic. It shall qualify the subsequent objects in the template, until the next qualifier, if any.
— The rank is a number from zero to 255. If two or more qualifiers have the same rank within the
same context, then only the set of objects qualified by the most recent one is valid.
— The mnemonic is a string of up to eight bytes consisting of 7-bit characters (bit 8 set to 0, see
ISO/IEC 646) to display at the man-machine interface.
— Number — Referenced by tag ‘81’ in a login template, this data element shall consist of an even
number of quartets where each quartet codes one character for representing a telephone number
according to Table 2.
— Text — Referenced by tag ‘82’ in a login template, this data element shall consist of one or more
bytes where each byte codes one character. Bit 8 sets the difference between data characters (bit 8
© ISO/IEC 2023 – All rights reserved

set to zero) and control characters (bit 8 set to one). The byte string consists of one or more strings
of data characters (7-bit character, see ISO/IEC 646) separated by strings of control characters. The
following control characters are defined.
— ‘80’ — A message has to be received before sending the next character.
— ‘C0’ — A modulation has to be present before sending the next character.
— ‘8X’ — X characters have to be received in echo before waiting for a message.
— Delay indicators — Referenced by tag ‘83’ or ‘84’ in a login template, this data element shall consist
of one byte as specified in Table 3.
— When present, a delay indicator data object with tag ‘83’ fixes the time for detecting an end of
message. The default value shall be two seconds.
— When present, a delay indicator data object with tag ‘84’ fixes the time for detecting an absence
of response. The default value shall be sixty seconds.
Table 2 — Telephone number
Quartet Character Meaning
‘0’ to ‘9’ 0 to 9 Decimal digits
‘A’ ( Opening bracket
‘B’ ) Closing bracket
‘C’ C Requirement for connecting to the line before continuing
‘D’ + Introduction to an international telephone number
If first, introduction of a number to use without prefix
‘E’ —
If not first, requirement for a delay (two seconds) before continuing
‘F’ Reserved for padding
Table 3 — Delay indicator byte
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
0 0   Any other value is reserved for future use by ISO/IEC JTC 1/SC 17.
— — x x — — — — The time unit is
— — 0 0 — — — — — 100 milliseconds
— — 0 1 — — — — — 1 second
— — 1 0 — — — — — 10 seconds
— — 1 1 — — — — — 100 seconds
x x x x Number of time units from zero to fifteen
6.6 Qualified name template
Referenced by tag ‘6B’, this interindustry template shall consist of the following:
— one or more object identifiers (tag ‘06’) referring to the standards defining the qualified name
presentation;
— a name (tag ‘80’ or ‘A0’), the value and coding of which are defined by the aforementioned standards;
— other related optional information (e.g. sex, nationality, place of birth).
© ISO/IEC 2023 – All rights reserved

6.7 Cardholder image template
Referenced by tag ‘6C’, this interindustry template shall contain at least one data object as defined
hereafter, possibly preceded by a tag allocation authority indicator (see ISO/IEC 7816-4) for identifying
the authority responsible for the data object format.
— Cardholder biometric data — referenced by tag ‘5F2E’, this interindustry data element contains
biometric data for verifying the claimed identity of the person presenting the card. Examples of
biometric data are fingerprints, palm prints, voiceprints, dynamic signatures, etc.
— Cardholder portrait image — referenced by tag ‘5F40’, this interindustry data element shall
be formatted as defined in ISO/IEC 10918-1, unless otherwise specified and/or requested by an
authority.
— Cardholder handwritten signature image — referenced by tag ‘5F43’, this interindustry data
element shall be formatted as defined in ISO/IEC 11544 unless otherwise specified and/or requested
by an authority.
The use of this interindustry data object should be associated with appropriate security measures.
Further information on personal verification through biometric methods may be found in
ISO/IEC 7816-11.
6.8 Application image template
Referenced by tag ‘6D’, this interindustry template shall contain at least an application image (tag
‘5F44’), i.e. an icon or a logo related to the application. It may also contain an authority indicator (see
ISO/IEC 7816-4) identifying the authority responsible for the data format of the application image. In
the absence of authority indicator, the format shall be as defined in ISO/IEC 10918-1.
6.9 Display control template
Referenced by tag ‘7F20’, this interindustry template may contain one or more data objects, the value of
which, either directly or indirectly through templates, is not intended to be displayed and should only
be used, when relevant, for processing of transmission.
7 Identification of integrated circuit manufacturers
7.1 General
This clause specifies
— a numbering system for integrated circuit manufacturer identifiers, and
— rules for registration of integrated circuit manufacturers and rules for assignment of identifiers
to identify manufacturers of integrated circuits to be embedded in contact and/or contactless
integrated circuits cards. The assigned values of the integrated circuit manufacturer identifiers will
form the register.
7.2 Identifier
The identifier is referenced by tag ‘5F4D’. It may be present in pre-issuing data (compact header ‘6Y’ in
the historical bytes and interindustry tag ‘46’ in EF .ATR/ INFO) on a proprietary basis.
NOTE Tag '5F4B' for referencing identifiers is deprecated in the ISO/IEC 7816 series, because two different
definitions existed within that series.
© ISO/IEC 2023 – All rights reserved

The identifier consists of one or more byte. The identifier shall be coded according to Table 4 and
Table 5.
Table 4 — First identifier byte
Value Meaning
‘00’ No information given
‘01’ . ‘7E’ Reserved for the register of one byte identifier
‘7F’, ‘80’ Reserved for future use by ISO/IEC JTC 1/SC 17
‘81’ . ‘FE’ Proprietary
‘FF’ Reserved for register of identifiers with more than one byte, at least one
subsequent identifier byte follows, see Table 5
Table 5 — Subsequent identifier bytes
Value Meaning
If bit b8 equals 1: Another identifier byte follows.
If bit b8 equals 0: Last byte of identifier.
‘xx’
Bits b7 to b1 contain arbitrary values.
The integrated circuit manufacturer identifier is represented by the sequence of bytes
starting with ‘FF’ up to and including the last byte of the sequence.
7.3 Rules for assignment
The name and contact information of the maintenance agency for this integrated circuit manufacturer
identifiers can be found at www .iso .org/ maintenance _agencies. Such identifiers will be assigned
according to the following rules:
a) the assignment is made upon request from any integrated circuit manufacturer or any interested
party;
b) the form contained in Annex A should be used to request an assignment;
c) a single number shall be assigned to each manufacturer;
d) the last assigned number shall be incremented by one to build the newly assigned number (i.e. only
if all available n-byte values have been assigned, the assignment of (n+1)-byte identifier shall start);
NOTE 1 ‘FF00’ is the first two byte identifier. ‘FF7F’ is the last two byte identifier. ‘FF8000’ is the first three
byte identifier. ‘FFFF7F’ is the last three byte identifier. Incrementing the identifier value ‘FF807F’ by one leads
to the value ‘FF8100’.
NOTE 2 Between 2007 and 2018 an average of approximately six identifiers have been assigned per year.
Keeping up that rate it follows that the first two byte identifier is expected soon, in 2040 the first three byte IC
manufacturer is expected and 2700 years later the first four byte identifier is expected. If the rate of assigning
increases from six per year to one per day then the first four byte identifier is expected in approximately the year
2060.
WARNING — As pointed out by NOTE 2 it is expected that the length of assigned integrated
circuit manufacturer identifier possibly increases from one byte to two bytes soon.
8 Interchange profile
The specification of data objects associated with the interchange profile of the card (e.g. available
authentication methods and security functions) may be further detailed in future parts of the
ISO/IEC 7816 series. Table 6 shows interindustry data objects reserved for interchange profile.
© ISO/IEC 2023 – All rights reserved

Table 6 — Interindustry data objects reserved for interchange profile
Tag Value
5F29 Interchange profile
5F37 Static internal authentication (one-step)
5F38 Static internal authentication, first associated data
5F39 Static internal authentication, second associated data
5F3A Dynamic internal authentication
5F3B Dynamic external authentication
5F3C Dynamic mutual authentication
9 Interindustry data elements in alphabetic order
Table 7 lists interindustry data elements in alphabetic order, with description, reference, tag, length
and format where appropriate.
NOTE 1 Whenever widely used, for example, in published specifications, Data element acronyms are indicated
and their first character is in capital letter.
NOTE 2 The encoding format is out of scope unless a standard is referenced or a definition is given. This
applies especially for combinations of abbreviations as in 'an' or 'ans'.
Table 7 — Interindustry data elements in alphabetic order
May be found
Tag
Data element Description and reference Length/format within
(hex)
template
Indicates the type of account selected by the
Account type cardholder for the transaction 5F57 n2 6E
(see EMV for coding)
Address Address of an individual 5F42 variable 65
Answer-to-reset Indicates operating characteristics of the card
5F51 1.32 bytes —
(ATR) (defined in ISO/IEC 7816-3)
Application
Template for description of each card-application
capability
including alpha card-application 7F63 variable —
description
(see ISO/IEC 24727-2)
template (ACD)
Date from which the application can be used,
Application
under the responsibility of the application 5F25 n6/YYMMDD 6E
effective date
provider
Application Date after which an application expires, under the
5F24 n6/YYMMDD 6E
expiration date responsibility of the application provider
Designation of several application areas to enable
Application family
global interoperability 49 1 byte ‘00’.‘FF’ —
identifier (AFI)
(see ISO/IEC 14443-3)
Application Data element identifying an application in the card
4F variable 61, 6E
identifier (AID) (coding defined in ISO/IEC 7816-4)
Icon or logo associated with an application
Application image 5F44 variable 6D
(see ISO/IEC 10918-1)
Application image
Template nesting at least an application image 6D variable 6E
template
Data element for use at the man machine
Application label 50 variable 61, 6E
interface
Application related
Template nesting parameters of an application 6E variable —
data template
a
This data element should be encoded as unpacked BCD.
© ISO/IEC 2023 – All rights reserved

TTaabblle 7 e 7 ((ccoonnttiinnueuedd))
May be found
Tag
Data element Description and reference Length/format within
(hex)
template
Application Template identifying an application in the card
61 variable —
template (defined in ISO/IEC 7816-4)
Authentication data Template nesting authentication data and
67 variable 66
template parameters
A universal business identifier code (former bank
Business identifier identifier code) for use in automated processing in
5F54 an8 or an11 6E
code (BIS) banking and related financial environments
(see ISO 9362)
Biometric
Template nesting biometric information data
information 7F60 variable —
objects (defined in ISO/IEC 7816-11)
template (BIT)
Biometric informa- Template used for nesting biometric information
7F61 variable —
tion group template templates (see ISO/IEC 7816-11)
Biometric data Template nesting biometric reference data objects
7F2E variable 7F60
template (defined in ISO/IEC 7816-11)
Data element fixing card behaviours
Card capabilities 47 variable 66
(defined in ISO/IEC 7816-4)
Card capability Template describing card capability, may be
description present in EF.ATR or in alpha card-application 7F62 variable —
template (CCD) (see ISO/IEC 24727-2)
Card data template Template nesting data related to the card 66 variable —
Date from which the card can be used, under the
Card effective date 5F26 n6/YYMMDD 66
responsibility of the card issuer
Card expiration
Date after which the card expires 59 n4/YYMM 66
date
Card issuer's data Proprietary (see ISO/IEC 7816-4) 45 variable 66
Template for card management data objects
Card management
description, may be found in EF.ATR 7F64 variable —
service template
(see ISO/IEC 7816-13)
Card sequence Number distinguishing between separate cards
5F34 n2 66
number with the same primary account number
Indication of methods available in the card for
Card service data 43 1 byte —
supporting services (defined in ISO/IEC 7816-4)
Cardholder
Biometric data related to the cardholder 5F2E variable 65
biometric data
Cardholder Template nesting the cardholder public key,
certificate further information, signature of certification 7F21 variable 65
template authority
Cardholder
Image of the cardholder's handwritten signature
handwritten 5F43 variable 6C
(see ISO/IEC 11544)
signature image
Cardholder image Cardholder related images stored within the card
6C variable 65
template (defined in ISO/IEC 7816-4)
Name of the cardholder
Cardholder name 5F20 ans2.26 65
(defined in ISO/IEC 7813)
Cardholder Nationality of the cardholder
5F2C n3 65
nationality (coding defined in ISO 3166-1)
Encoded image data, used for the
Cardholder
cardholder portrait image 5F40 variable 6C
portrait image
(format defined in ISO/IEC 10918-1)
a
This data element should be encoded as unpacked BCD.
© ISO/IEC 2023 – All rights reserved

TTaabblle 7 e 7 ((ccoonnttiinnueuedd))
May be found
Tag
Data element Description and reference Length/format within
(hex)
template
Data element containing the cardholder's private
Cardholder
key for digital signature functionality using 5F48 variable 65
private key
asymmetric mechanisms
Cardholder
private key Template nesting private key related data objects 7F48 variable 65
template
Data element containing the cardholder's public
Cardholder
key data elements for digital signature 5F49 variable 65
public key
functionality using asymmetric mechanisms
Template containing the cardholder's public key
Cardholder
data objects for digital signature functionality
public key 7F49 variable 65
using asymmetric mechanisms
template
(defined in ISO/IEC 7816-8)
Cardholder related
Template nesting data related to the cardholder 65 variable —
data template
Data element containing cardholder's require-
Cardholder
ments for excluded features e.g. cardholder is not
requirements
able to use fingerprint verification (see EN 1332-4 7F23 variable 65
template,
for further information on coding of user require-
excluded features
ments)
Data element containing a cardholder's require-
Cardholder
ments for included features e.g. cardholder
requirements
requires audio assistance from an ATM (see 7F22 variable 65
template,
EN 1332-4 for further information on coding of
included features
user requirements)
Data element containing the content of a
Certificate content 5F4E variable 7F21
certificate
Certificate content Template for nesting certificate content data
7F4E variable —
template objects
Certificate effective
a
Date from which the certificate can be used 5F25 n6/YYMMDD 7F4E
date (CED)
Certificate
a
expiration Date after which a certificate expires 5F24 n6/YYMMDD 7F4E
date (CXD)
Certificate holder
Deprecated (see 7.2 and NOTE under Table 8) 5F4B variable —
authorization
A certificate holder authorization (e.g. a role
Certificate holder
identifier) may be contained in a data element 5F4C variable —
authorization (CHA)
or data object with tag ‘5F4C’
Template containing an object identifier
Certificate holder
specifying the format of the template and data
authorization 7F4C variable 7F4E
object(s) encoding the certificate holder
template (CHAT)
authorization (e.g. role and access rights)
Coexistent tag
Template used to identify a coexistent tag
allocation
allocation scheme and the authority responsible 79 variable —
authority
for the scheme
template
Command-to-
Command APDU (see ISO/IEC 7816-3) 52 variable 61
perform
Compatible tag Template used to identify a compatible tag
allocation allocation scheme and the authority responsible 78 variable —
authority for the scheme
a
This data element should be encoded as unpacked BCD.
© ISO/IEC 2023 – All rights reserved

TTaabblle 7 e 7 ((ccoonnttiinnueuedd))
May be found
Tag
Data element Description and reference Length/format within
(hex)
template
Control parameters Template for nesting file or data object control
62 variable —
(CP) template parameters
Indication of a country (coding and registration
Country code 5F28 n3 66
defined in ISO 3166-1)
Country code (alpha
Indication of a country (see ISO 3166-1) 5F55 a2 66
2 format)
Country code (alpha
Indication of a country (see ISO 3166-1) 5F56 a3 66
3 format)
Country code and Indication of a country followed by national data
optional national (coding and registration defined in ISO 3166-1) 41 n3 and national data 66
data and optional national data
Code for the representation of currencies and
Currency code 5F2A a3 or n3 6E
funds (see ISO 4217)
Number by which an amount of the currency
Currency exponent indicated in the card shall be multiplied 5F36 n1 6E
(see ISO 4217)
Date of birth Date of birth of related individual 5F2B n8/YYYYMMDD 65
Data element containing a digital signature
Digital signature 5F3D variable 7F3D
(asymmetric or symmetric algorithm)
Digital signature Template nesting digital signature related data
7F3D variable —
block template objects
Data element not defined in ISO/IEC 7816 (all Interindustry
Discretionary data 53 variable
parts) template
Discretionary data Concatenation of data objects not defined in Interindustry
73 variable
objects template ISO/IEC 7816 (all parts) template
Display control Template used to control data displayed at the
7F20 variable 66
template terminal
Display message Data element containing a message to display 5F45 variable 66
Dynamic Template used in the command and response data
authentication fields of the general authenticate command 7C variable —
template (defined in ISO/IEC 7816-4)
Composite data element used for identifying the
Dynamic external
algorithm and the key to use in the external 5F3B variable 67
authentication
authenticate command
Composite data element used for identifying the
Dynamic internal
algorithm and the key to use in the 5F3A variable 67
authentication
internal authenticate command
Composite data element used for identifying the
Dynamic mutual algorithm and the key to use in the mutual
5F3C variable 67
authentication authentication process
(see ISO/IEC 9798-2 and ISO/IEC 9798-3)
Sequence of elements and related information,
Element list without identifiers (to be used only within a 5F41 variable —
wrapper)
Extended header Data element for indirectly referencing data
4D variable —
list elements (coding defined in ISO/IEC 7816-4)
Extended header Extended header list for referencing a byte string
list referencing a with no stated structure and entitle skipping 5F60 variable —
byte string indication of primitive DOs
Extended header
Extended header list (referencing one or several
list referencing one 5F61 variable —
DOs); entitle skipping indication of primitive DOs
or several DOs
a
This data element should be encoded as unpacked BCD.
© ISO/IEC 2023 – All rights reserved

TTaabblle 7 e 7 ((ccoonnttiinnueuedd))
May be found
Tag
Data element Description and reference Length/format within
(hex)
template
Extended length information template (coding
Extended
defined in ISO/IEC 7816-4:2020, 12.8.1) may be
length
present in EF .ATR/ INFO and/or in the FMD of any 7F66 variable —
information tem-
Application DF and it is denoted by the third
plate
software function table of the card capabilities
File Control Information Template for nesting file
FCI template 6F variable —
control parameters and file management data
Possibly extendable features on the card exposed
Features
to outside world in a generic way. May be located
management 7F74 variable —
in EF .ATR/ INFO and/or in the FCI of any
template
application DF (see ISO/IEC 7816-4)
Reference to a file, e.g. a path
File reference 51 variable 61
(coding defined in ISO/IEC 7816-4)
Template referencing a constructed data objects
Filter template 7F71 variable 60
by its content
File Management
File Management Data Template for nesting file
Data (FMD) 64 variable —
management data
template
Template conveyed in a command data field or
General reference nested in object locator template ‘7F72’ and
60 variable —
template indicating a DF, EF, DO, or DataString with
possibly the application of a filter or a mask
Concatenation of pairs of tag fields and length
Header list fields without delimitation 5D variable —
(as defined in ISO/IEC 7816-4)
Indicate operating characteristics of the card
Historical bytes 5F52 0.15 bytes —
(see ISO/IEC 7816-4)
Integrated circuit
manufacturer Indication of a manufacturer of integrated circuits 5F4D 1 byte —
identifier
Indication of a command-to-perform for retrieving
Initial access data the initial data string 44 variable 66
(coding defined in ISO/IEC 7816-4)
Indication to use in association with a country
Interchange control code to indicate whether international interchange 5F27 n1 66
is permitted on a card (see ISO/IEC 4909)
Data element describing capabilities available in
Interchange profile 5F29 variable 67
the card to perform an interchange transaction
International Bank A number used internationally to uniquely identify
Account Number the account of a customer at a financial institution 5F53 an.34 6E
(IBAN) (see ISO 13616-1)
Issuer
Data element for identifying the card issuer
Identification
(coding and registration defined in ISO/IEC 7812- 42 variable —
Number (IIN) and
1), possibly followed by more data
optional issuer data
Language Indication, in order of preference, of up to four
5F2D a2.8 65
preferences languages for the cardholder (see ISO 639-1)
List of supported INS codes that may be located in
List of supported
EF .ATR/ INFO and/or in the FMD of any application 5F63 variable 64
INS codes
DF
Proprietary information intended for connecting
Login data
the interface device to a remote host, a remote 5E variable 6E
(Proprietary)
server or an application within these devices
a
This data element should be encoded as unpacked BCD.
© ISO/IEC 2023 – All rights reserved

TTaabblle 7 e 7 ((ccoonnttiinnueuedd))
May be found
Tag
Data element Description an
...