4.

3 Data Element Format Conventions The EMV specifications use the following data
element formats: a Alphabetic data elements contain a single character per byte. The
permitted characters are alphabetic only (a to z and A to Z, upper and lower case). an
Alphanumeric data elements contain a singleTo support SDA, each terminal shall be able to
store six certification authority public keys per Registered Application Provider Identifier
(RID) and shall associate with each such key the key-related information to be used with the
key (so that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in sectionAlphabetic data elements contain a
single character per byte. The permitted characters are alphabetic only (a to z and A to Z,
upper and lower case). an Alphanumeric data elements contain a singleTo support SDA,
each terminal shall be able to store six certification authority public keys per Registered
Application Provider Identifier (RID) and shall associate with each such key the key-related
information to be used with the key (so that terminals can in the future support multiple
algorithms and allow an evolutionary transition from one to another, as discussed in section
11.2.2). The terminal shall be able to locate any such key (and the key-related information)
given the RID and Certification Authority Public Key Index as provided by the ICC. SDA shall
use a reversible algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an
overview of the keys and certificates involved in the SDA process, and sections 5.2 to 5.4
specify the three main steps in the process, namely: • Retrieval of the Certification Authority
Public Key by the terminal • Retrieval of the Issuer Public K character per byte. The
permitted characters are alphabetic (a to z and A to Z, upper and lower case) and numeric (0
to 9). ans Alphanumeric Special data elements contain a single character per byte. The
permitted characters and their coding are shown in the Common Character Set table in
Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit
combination example: Processing Options Data Object List (PDOL) is defined as “b” with the
format shown in Book 3, section 5.4. cn Compressed numeric data elee three main steps in
the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as
“cn” with a length of up to ten bytes. A value of 1234567890123 may be stored in the
Application PAN as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data
elements consist of two numeric digits (having values in the range Hex '0' – '9') per byte.
These digits are right justified and padded with leading hexadecimal zeroes. Othments
consist of two numeric digits (having values in the range Hex '0'–'9') per byte. These data
elements are left justified and padded with trailing hexadecimal 'F's. Example: The
Application Primary Avided by the ICC. SDA shall use a reversible algorithm as specified in
Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and certificates
involved in the SDA pro) is defined as “b” with the format shown in Book 3, section 5.4. cn
Compressed numeric data elee three main steps in the process, namely: • Retrieval of the
Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00
13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of
1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justificess, and sections 5.2 to 5.4
specify the three main steps in the process, namely: • Retrieval of the Certification Authority
Public Key by the terminal • Retrieval of the Issuer ssociated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'. Bit combination example: Processing Options Data Object List (PDOL) is
defined as “b” with the format shown in Book 3, section 5.4. cn Compressed numeric data
elee three main steps in the process, namely: • Retrieval of the Certification Auth K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is on4.3 Data Element Format Conventions The EMV
specifications use the following data element formats: a Alphabetic data elements contain a
single character per byte. The permitted characters are alphabetic only (a to z and A to Z,
upper and lower case). an Alphanumeric data elements contain a singleTo support SDA,
each terminal shall be able to store six certification authority public keys per Registered
Application Provider Identifier (RID) and shall associate with each such key the key-related
information to be used with the key (so that terminals can in the future support multiple
algorithms and allow an evolutionary transition from one to another, as discussed in
sectionAlphabetic data elements contain a single character per byte. The permitted
characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric
data elements contain a singleTo support SDA, each terminal shall be able to store six
certification authority public keys per Registered Application Provider Identifier (RID) and
shall associate with each such key the key-related information to be used with the key (so
that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the I4.3 Data Element Format Conventions The EMV specifications
use the following data element formats: a Alphabetic data elements contain a single
character per byte. The permitted characters are alphabetic only (a to z and A to Z, upper
and lower case). an Alphanumeric data elements contain a singleTo support SDA, each
terminal shall be able to store six certification authority public keys per Registered
Application Provider Identifier (RID) and shall associate with each such key the key-related
information to be used with the key (so that terminals can in the future support multiple
algorithms and allow an evolutionary transition from one to another, as discussed in
sectionAlphabetic data elements contain a single character per byte. The permitted
characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric
data elements contain a singleTo support SDA, each terminal shall be able to store six
certification authority public keys per Registered Application Provider Identifier (RID) and
shall associate with each such key the key-related information to be used with the key (so
that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K
character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and
lower case) and numeric (0 to 9). ans Alphanumeric Special data elements contain a single
character per byte. The permitted characters and their coding are shown in the Common
Character Set table in Annex B of Book 4. There is one exception: The permitted characters
for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859
part designated in the Issuer Code Table Index associated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value
of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justificess, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
ssociated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Auth K character per byte. The permitted characters are alphabetic (a to z
and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data
elements contain a single character per byte. The permitted characters and their coding are
shown in the Common Character Set table in Annex B of Book 4. There is one exception:
The permitted characters for Application Preferred Name are the non-control characters
defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with
the Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justified and padded with leading hexadecimal zeroes. OthSO/IEC 8859 part designated in
the Issuer Code Table Index associated with the Application Preferred Name. b These data
elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit
combination example: Processing Options Data Object List (PDOL) is defined as “b” with the
format shown in Book 3, section 5.4. cn Compressed numeric data elee three main steps in
the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common4.3 Data Element Format Conventions The EMV specifications
use the following data element formats: a Alphabetic data elements contain a single
character per byte. The permitted characters are alphabetic only (a to z and A to Z, upper
and lower case). an Alphanumeric data elements contain a singleTo support SDA, each
terminal shall be able to store six certification authority public keys per Registered
Application Provider Identifier (RID) and shall associate with each such key the key-related
information to be used with the key (so that terminals can in the future support multiple
algorithms and allow an evolutionary transition from one to another, as discussed in
sectionAlphabetic data elements contain a single character per byte. The permitted
characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric
data elements contain a singleTo support SDA, each terminal shall be able to store six
certification authority public keys per Registered Application Provider Identifier (RID) and
shall associate with each such key the key-related information to be used with the key (so
that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K
character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and
lower case) and numeric (0 to 9). ans Alphanumeric Special data elements contain a single
character per byte. The permitted characters and their coding are shown in the Common
Character Set table in Annex B of Book 4. There is one exception: The permitted characters
for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859
part designated in the Issuer Code Table Index associated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value
of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justificess, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
ssociated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as H4.3 Data Element Format Conventions The
EMV specifications use the following data element formats: a Alphabetic data elements
contain a single character per byte. The permitted characters are alphabetic only (a to z and
A to Z, upper and lower case). an Alphanumeric data elements contain a singleTo support
SDA, each terminal shall be able to store six certification authority public keys per
Registered Application Provider Identifier (RID) and shall associate with each such key the
key-related information to be used with the key (so that terminals can in the future support
multiple algorithms and allow an evolutionary transition from one to another, as discussed in
sectionAlphabetic data elements contain a single character per byte. The permitted
characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric
data elements contain a singleTo support SDA, each terminal shall be able to store six
certification authority public keys per Registered Application Provider Identifier (RID) and
shall associate with each such key the key-related information to be used with the key (so
that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K
character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and
lower case) and numeric (0 to 9). ans Alphanumeric Special data elements contain a single
character per byte. The permitted characters and their coding are shown in the Common
Character Set table in Annex B of Book 4. There is one exception: The permitted characters
for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859
part designated in the Issuer Code Table Index associated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specificatio4.3 Data Element Format Conventions The
EMV specifications use the following data element formats: a Alphabetic data elements
contain a single character per byte. The permitted characters are alphabetic only (a to z and
A to Z, upper and lower case). an Alphanumeric data elements contain a singleTo support
SDA, each terminal shall be able to store six certification authority public keys per
Registered Application Provider Identifier (RID) and shall associate with each such key the
key-related information to be used with the key (so that terminals can in the future support
multiple algorithms and allow an evolutionary transition from one to another, as discussed in
sectionAlphabetic data elements contain a single character per byte. The permitted
characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric
data elements contain a singleTo support SDA, each terminal shall be able to store six
certification authority public keys per Registered Application Provider Identifier (RID) and
shall associate with each such key the key-related information to be used with the key (so
that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K
character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and
lower case) and numeric (0 to 9). ans Alphanumeric Special data elements contain a single
character per byte. The permitted characters and their coding are shown in the Common
Character Set table in Annex B of Book 4. There is one exception: The permitted characters
for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859
part designated in the Issuer Code Table Index associated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value
of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justificess, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
ssociated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Auth K character per byte. The permitted characters are alphabetic (a to z
and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data
elements contain a single character per byte. The permitted characters and their coding are
shown in the Common Character Set table in Annex B of Book 4. There is one exception:
The permitted characters for Application Preferred Name are the non-control characters
defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with
the Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justified and padded with leading hexadecimal zeroes. Othn. Binary example: The
Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An ATC
value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of
up to ten bytes. A value of 1234567890123 may be stored in the Application PAN as Hex '12
34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two numeric
digits (having values in the range Hex '0' – '9') per byte. These digits are right justified and
padded with leading hexadecimal zeroes. Othments consist of two numeric digits (having
values in the range Hex '0'–'9') per byte. These data elements are left justified and padded
with trailing hexadecimal 'F's. Example: The Application Primary Avided by the ICC. SDA
shall use a reversible algorithm as specified in Annex A2.1 and Annex B2. Section 5.1
contains an overview of the keys and certificates involved in the SDA pro) is defined as “b”
with the format shown in Book 3, section 5.4. cn Compressed numeric data elee three main
steps in the process, namely: • Retrieval of the Certification Authority Public Key by the
terminal • Retrieval of the Issuer Public K character per byte. The permitted characters are
alphabetic (a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric
Special data elements contain a single character per byte. The permitted characters and
their coding are shown in the Common Character Set table in Annex B of Book 4. There is
one exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as
“cn” with a length of up to ten bytes. A value of 1234567890123 may be stored in the
Application PAN as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data
elements consist of two numeric digits (having values in the range Hex '0' – '9') per byte.
These digits are right justificess, and sections 5.2 to 5.4 specify the three main steps in the
process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer ssociated with the Application Preferred Name. b These data
elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit
combination example: Processing Options Data Object List (PDOL) is defined as “b” with the
format shown in Book 3, section 5.4. cn Compressed numeric data elee three main steps in
the process, namely: • Retrieval of the Certifi4.3 Data Element Format Conventions The
EMV specifications use the following data element formats: a Alphabetic data elements
contain a single character per byte. The permitted characters are alphabetic only (a to z and
A to Z, upper and lower case). an Alphanumeric data elements contain a singleTo support
SDA, each terminal shall be able to store six certification authority public keys per
Registered Application Provider Identifier (RID) and shall associate with each such key the
key-related information to be used with the key (so that terminals can in the future support
multiple algorithms and allow an evolutionary transition from one to another, as discussed in
sectionAlphabetic data elements contain a single character per byte. The permitted
characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric
data elements contain a singleTo support SDA, each terminal shall be able to store six
certification authority public keys per Registered Application Provider Identifier (RID) and
shall associate with each such key the key-related information to be used with the key (so
that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K
character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and
lower case) and numeric (0 to 9). ans Alphanumeric Special data elements contain a single
character per byte. The permitted characters and their coding are shown in the Common
Character Set table in Annex B of Book 4. There is one exception: The permitted characters
for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859
part designated in the Issuer Code Table Index associated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value
of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These dataare alphabetic only (a to z and A to Z, upper and
lower case). an Alphanumeric data elements contain a singleTo support SDA, each terminal
shall be able to store six certification authority public keys per Registered Application
Provider Identifier (RID) and shall associate with each such key the key-related information
to be used with the key (so that terminals can in the future support multiple algorithms and
allow an evolutionary transition from one to another, as discussed in sectionAlphabetic data
elements contain a single character per byte. The permitted characters are alphabetic only
(a to z and A to Z, upper and lower case). an Alphanumeric data elements contain a singleTo
support SDA, each terminal shall be able to store six certification authority public keys per
Registered Application Provider Identifier (RID) and shall associate with each such key the
key-related information to be used with the key (so that terminals can in the future support
multiple algorithms and allow an evolutionary transition from one to another, as discussed in
section 11.2.2). The terminal shall be able to locate any such key (and the key-related
information) given the RID and Certification Authority Public Key Index as provided by the
ICC. SDA shall use a reversible algorithm as specified in Annex A2.1 and Annex B2. Section
5.1 contains an overview of the keys and certificates involved in the SDA process, and
sections 5.2 to 5.4 specify the three main steps in the process, namely: • Retrieval of the
Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit
combination example: Processing Options Data Object List (PDOL) is defined as “b” with the
format shown in Book 3, section 5.4. cn Compressed numeric data elee three main steps in
the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as
“cn” with a length of up to ten bytes. A value of 1234567890123 may be stored in the
Application PAN as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data
elements consist of two numeric digits (having values in the range Hex '0' – '9') per byte.
These digits are right justified and padded with leading hexadecimal zeroes. Othments
consist of two numeric digits (having values in the range Hex '0'–'9') per byte. These data
elements are left justified and padded with trailing hexadecimal 'F's. Example: The
Application Primary Avided by the ICC. SDA shall use a reversible algorithm as specified in
Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and certificates
involved in the SDA pro) is defined as “b” with the format shown in Book 3, section 5.4. cn
Compressed numeric data elee three main steps in the process, namely: • Retrieval of the
Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00
13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of
1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justificess, and sections 5.2 to 5.4
specify the three main steps in the process, namely: • Retrieval of the Certification Authority
Public Key by the terminal • Retrieval of the Issuer ssociated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'. Bit combination example: Processing Options Data Object List (PDOL) is
defined as “b” with the format shown in Book 3, section 5.4. cn Compressed numeric data
elee three main steps in the process, namely: • Retrieval of the Certification Auth K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00
13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of
1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othin the Issuer Code Table Index associated with the Application
Preferred Name. b These data elements consist of either unsigned binary numbers or bit
combinations that are defined elsewhere in the specification. Binary example: The
Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An ATC
value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of
up to ten bytes. A value of 1234567890123 may be stored in the Application PAN as Hex '12
34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two numeric
digits (having values in the range Hex '0' – '9') per byte. These digits are right justified and
padded with leading hexadecimal zeroes. Othcation Auth K character per byte. The
permitted characters are alphabetic (a to z and A to Z, upper and lower case) and numeric (0
to 9). ans Alphanumeric Special data elements contain a single character per byte. The
permitted characters and their coding are shown in the Common Character Set table in
Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
4.3 Data Element Format Conventions The EMV specifications use the following data
element formats: a Alphabetic data elements contain a single character per byte. The
permitted characters are alphabetic only (a to z and A to Z, upper and lower case). an
Alphanumeric data elements contain a singleTo support SDA, each terminal shall be able to
store six certification authority public keys per Registered Application Provider Identifier
(RID) and shall associate with each such key the key-related information to be used with the
key (so that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in sectionAlphabetic data elements contain a
single character per byte. The permitted characters are alphabetic only (a to z and A to Z,
upper and lower case). an Alphanumeric data elements contain a singleTo support SDA,
each terminal shall be able to store six certification authority public keys per Registered
Application Provider Identifier (RID) and shall associate with each such key the key-related
information to be used with the key (so that terminals can in the future support multiple
algorithms and allow an evolutionary transition from one to another, as discussed in section
11.2.2). The terminal shall be able to locate any such key (and the key-related information)
given the RID and Certification Authority Public Key Index as provided by the ICC. SDA shall
use a reversible algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an
overview of the keys and certificates involved in the SDA process, and sections 5.2 to 5.4
specify the three main steps in the process, namely: • Retrieval of the Certification Authority
Public Key by the terminal • Retrieval of the Issuer Public K character per byte. The
permitted characters are alphabetgiven the RID and Certification Authority Public Key Index
as provided by the ICC. SDA shall use a reversible algorithm as specified in Annex A2.1 and
Annex B2. Section 5.1 contains an overview of the keys and certificates involved in the SDA
process, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
Public K character per byte. The permitted characters are alphabetic (a to z and A to Z,
upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing Options Data
Object List (PDOL) is defined as “b” with the format shown in Book 3, section 5.4. cn
Compressed numeric data elee three main steps in the process, namely: • Retrieval of the
Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00
13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of
1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justificess, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
ssociated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Auth K character per byte. The permitted characters are alphabetic (a to z
and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data
elements contain a single character per byte. The permitted characters and their coding are
shown in the Common Character Set table in Annex B of Book 4. There is one exception:
The permitted characters for Application Preferred Name are the non-control characters
defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with
the Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justified and padded with leading hexadecimal zeroes. Oth that are defined elsewhere in the
specification. Binary example: The Application Transaction Counter (ATC) is defined as “b”
with a length of two bytes. An ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN)
is defined as “cn” with a length of up to ten bytes. A value of 1234567890123 may be stored
in the Application PAN as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data
elements consist of two numeric digits (having values in the range Hex '0' – '9') per byte.
These digits are right justified and padded with leading hexadecimal zeroes. Othments
consist of two numeric digits (having values in the range Hex '0'–'9') per byte. These data
elements are left justified and padded with trailing hexadecimal 'F's. Example: The
Application Primary Avided by the ICC. SDA shall use a reversible algorithm as specified in
Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and certificates
involved in the SDA pro) is defined as “b” with the format shown in Book 3, section 5.4. cn
Compressed numeric data elee three main steps in the process, namely: • Retrieval of the
Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00
13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of
1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justificess, and sections 5.2 to 5.4
specify the three main steps in the process, namely: • Retrieval of the Certification Authority
Public Key by the terminal • Retrieval of the Issuer ssociated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'. Bit combination example: Processing Options Data Object List (PDOL) is
defined as “b” with the format shown in Book 3, section 5.4. cn Compressed numeric data
elee three main steps in the process, namely: • Retrieval of the Certification Auth K character
per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case)
and numeric (0 to 9). ans Alphanumeric Special data elements contain a single character per
byte. The permitted characters and their coding are shown in the Common Character Set
table in Annex B of Book 4. There is one exception: The permitted characters for Application
Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated
in the Issuer Code Table Index associated with the Application Preferred Name. b These
data elements consist of either unsigned binary numbers or bit combinations that are defined
elsewhere in the specification. Binary example: The Application Transaction Counter (ATC)
is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00
13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of
1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othin the Issuer Code Table Index associated with the Application
Preferred Name. b These data elements consist of either unsigned binary numbers or bit
combinations that are defined elsewhere in the specification. Binary example: The
Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An ATC
value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of
up to ten bytes. A value of 1234567890123 may be stored in the Application PAN as Hex '12
34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two numeric
digits (having values in the range Hex '0' – '9') per byte. These digits are right justified and
padded with leading hexadecimal zeroes. Othex '00 13'. Bit combination example:
Processing Options Data Object List (PDOL) is defined as “b” with the format shown in Book
3, section 5.4. cn Compressed numeric data elee three main steps in the process, namely: •
Retrieval of the Certification Auth K character per byte. The permitted characters are
alphabetic (a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric
Special data elements contain a single character per byte. The permitted characters and
their coding are shown in the Common Character Set table in Annex B of Book 4. There is
one exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated 4.3 Data Element Format
Conventions The EMV specifications use the following data element formats: a Alphabetic
data elements contain a single character per byte. The permitted characters are alphabetic
only (a to z and A to Z, upper and lower case). an Alphanumeric data elements contain a
singleTo support SDA, each terminal shall be able to store six certification authority public
keys per Registered Application Provider Identifier (RID) and shall associate with each such
key the key-related information to be used with the key (so that terminals can in the future
support multiple algorithms and allow an evolutionary transition from one to another, as
discussed in sectionAlphabetic data elements contain a single character per byte. The
permitted characters are alphabetic only (a to z and A to Z, upper and lower case). an
Alphanumeric data elements contain a singleTo support SDA, each terminal shall be able to
store six certification authority public keys per Registered Application Provider Identifier
(RID) and shall associate with each such key the key-related information to be used with the
key (so that terminals can in the future support multiple algorithms and allow an evolutionary
transition from one to another, as discussed in section 11.2.2). The terminal shall be able to
locate any such key (and the key-related information) given the RID and Certification
Authority Public Key Index as provided by the ICC. SDA shall use a reversible algorithm as
specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the keys and
certificates involved in the SDA process, and sections 5.2 to 5.4 specify the three main steps
in the process, namely: • Retrieval of the Certification Authority Public Key by the terminal •
Retrieval of the Issuer Public K character per byte. The permitted characters are alphabetic
(a to z and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special
data elements contain a single character per byte. The permitted characters and their coding
are shown in the Common Character Set table in Annex B of Book 4. There is one
exception: The permitted characters for Application Preferred Name are the non-control
characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Authority Public Key by the terminal • Retrieval of the Issuer Public K
character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and
lower case) and numeric (0 to 9). ans Alphanumeric Special data elements contain a single
character per byte. The permitted characters and their coding are shown in the Common
Character Set table in Annex B of Book 4. There is one exception: The permitted characters
for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859
part designated in the Issuer Code Table Index associated with the Application Preferred
Name. b These data elements consist of either unsigned binary numbers or bit combinations
that are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value
of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justificess, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
ssociated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Auth K character per byte. The permitted characters are alphabetic (a to z
and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data
elements contain a single character per byte. The permitted characters and their coding are
shown in the Common Character Set table in Annex B of Book 4. There is one exception:
The permitted characters for Application Preferred Name are the non-control characters
defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with
the Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justified and padded with leading hexadecimal zeroes. Othin the Issuer Code Table Index
associated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as
“cn” with a length of up to ten bytes. A value of 1234567890123 may be stored in the
Application PAN as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data
elements consist of two numeric digits (having values in the range Hex '0' – '9') per byte.
These digits are right justified and padded with leading hexadecimal zeroes. Oth Character
Set table in Annex B of Book 4. There is one exception: The permitted characters for
Application Preferred Name are the non-control characters defined in the ISO/IEC 8859 part
designated in the Issuer Code Table Index associated with the Application Preferred Name.
b These data elements consist of either unsigned binary numbers or bit combinations that
are defined elsewhere in the specification. Binary example: The Application Transaction
Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as
Hex '00 13'.ccount Number (PAN) is defined as “cn” with a length of up to ten bytes. A value
of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF'
with a length of 8. n Numeric data elements consist of two numeric digits (having values in
the range Hex '0' – '9') per byte. These digits are right justified and padded with leading
hexadecimal zeroes. Othments consist of two numeric digits (having values in the range Hex
'0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal
'F's. Example: The Application Primary Avided by the ICC. SDA shall use a reversible
algorithm as specified in Annex A2.1 and Annex B2. Section 5.1 contains an overview of the
keys and certificates involved in the SDA pro) is defined as “b” with the format shown in
Book 3, section 5.4. cn Compressed numeric data elee three main steps in the process,
namely: • Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the
Issuer Public K character per byte. The permitted characters are alphabetic (a to z and A to
Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data elements
contain a single character per byte. The permitted characters and their coding are shown in
the Common Character Set table in Annex B of Book 4. There is one exception: The
permitted characters for Application Preferred Name are the non-control characters defined
in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justificess, and sections 5.2 to 5.4 specify the three main steps in the process, namely: •
Retrieval of the Certification Authority Public Key by the terminal • Retrieval of the Issuer
ssociated with the Application Preferred Name. b These data elements consist of either
unsigned binary numbers or bit combinations that are defined elsewhere in the specification.
Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of
two bytes. An ATC value of 19 is stored as Hex '00 13'. Bit combination example: Processing
Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section
5.4. cn Compressed numeric data elee three main steps in the process, namely: • Retrieval
of the Certification Auth K character per byte. The permitted characters are alphabetic (a to z
and A to Z, upper and lower case) and numeric (0 to 9). ans Alphanumeric Special data
elements contain a single character per byte. The permitted characters and their coding are
shown in the Common Character Set table in Annex B of Book 4. There is one exception:
The permitted characters for Application Preferred Name are the non-control characters
defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with
the Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justified and padded with leading hexadecimal zeroes. Othe exception: The permitted
characters for Application Preferred Name are the non-control characters defined in the
ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the
Application Preferred Name. b These data elements consist of either unsigned binary
numbers or bit combinations that are defined elsewhere in the specification. Binary example:
The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An
ATC value of 19 is stored as Hex '00 13'.ccount Number (PAN) is defined as “cn” with a
length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN
as Hex '12 34 56 78 90 12 3F FF' with a length of 8. n Numeric data elements consist of two
numeric digits (having values in the range Hex '0' – '9') per byte. These digits are right
justified and padded with leading hexadecimal zeroes. Oth