MACA Manual

M/Chip Advance Card
Application
Specification
Payment
Version 1.2, June 2015
Proprietary Rights
The information contained in this document is proprietary and confidential to

MasterCard International Incorporated, one or more of its affiliated entities
(collectively “MasterCard”), or both.
This material may not be duplicated, published, or disclosed, in whole or in part,

without the prior written permission of MasterCard.
Please ensure that you have signed an M/Chip™ Development Agreement and
have any other relevant license before developing a product.
Trademarks
Trademark notices and symbols used in this manual reflect the registration status of
MasterCard trademarks in the United States. Please consult with the Customer
Operations Services team or the MasterCard Law Department for the registration
status of particular product, program, or service names outside the United States.
All third-party product and service names are trademarks or registered trademarks
of their respective owners.
Disclaimer
Implementation of this M/Chip Advance Card Application Specification requires a

separate license from MasterCard and may require a license from third party
intellectual property owners.
MasterCard makes no representations or warranties of any kind, express or implied,

with respect to the contents of this Specification. Without limitation, MasterCard
specifically disclaims all representations and warranties with respect to the
Specification and any intellectual property rights subsisting therein or any part
thereof, including but not limited to any and all implied warranties of title, non-
infringement, or suitability for any purpose (whether or not MasterCard has been
advised, has reason to know, or is otherwise in fact aware of any information).
Without limitation, MasterCard specifically disclaims all representations and
warranties that any practice or implementation of the Specification will not infringe
any third party patents, copyrights, trade secrets or other rights. Without limitation,
MasterCard specifically disclaims all representations and warranties in relation to
the Specifications, including but not limited to any and all implied warranties of
suitability for any purpose (whether or not MasterCard has been advised, has
reason to know, or is otherwise in fact aware of any information) or achievement of
any particular result.
MasterCard Worldwide
Chaussée de Tervuren, 198A
B-1410 Waterloo
Belgium
E-mail: chip_help@mastercard.com
www.mastercard.com
©2015 MasterCard – Proprietary and Confidential

M/Chip Advance Card Application Specification—Payment  June 2015 Page 2
Table of Contents
Table of Contents
1. Using This Manual................................................................. 9
1.1. Purpose......................................................................................................... 10
1.2. Audience ...................................................................................................... 10
1.3. Related Information ..................................................................................... 10
1.4. Abbreviations ............................................................................................... 11
1.5. Specification Language ................................................................................ 13
1.6. Notational Conventions ............................................................................... 15
1.6.1. Hexadecimal Notational Convention ................................................... 15
1.6.2. Binary Notational Convention ............................................................. 15
1.6.3. Decimal Notational Convention .......................................................... 15
1.6.4. Data Object Notational Convention ..................................................... 15
1.6.5. Logic .................................................................................................... 16
1.6.6. Memory ................................................................................................ 17
1.6.7. State Notational Convention ................................................................ 18
1.6.8. C-APDU Notational Convention ......................................................... 18
1.7. Data Object Format ...................................................................................... 19
1.8. Specification Principles ............................................................................... 19
1.9. Revision History .......................................................................................... 20
2. General Card Requirements ............................................... 21
2.1. Overview ...................................................................................................... 22
2.2. State Machine Interface ............................................................................... 22
2.3. The ICC interface ......................................................................................... 23
2.3.1. Contact ................................................................................................. 23
2.3.2. Contactless ........................................................................................... 23
2.4. Multiple Logical Channels ........................................................................... 23
2.5. Selection and Multi-application Cards......................................................... 23
2.5.1. M/Chip Advance Application Activation ............................................ 24
2.5.2. M/Chip Advance Application De-activation ....................................... 26
2.6. Signals from the Multi-application Manager to M/Chip Advance .............. 26
2.7. Linked Applications ..................................................................................... 29
2.8. Support for the PSE ..................................................................................... 30
2.9. Support for the PPSE ................................................................................... 30
3. State Machine ...................................................................... 31
3.1. Application States ........................................................................................ 32
3.1.1. Idle ....................................................................................................... 32
3.1.2. Selectednotenabled .............................................................................. 33
3.1.3. Selected ................................................................................................ 33
3.1.4. Initiated ................................................................................................ 33
3.1.5. Online................................................................................................... 34
3.1.6. Script .................................................................................................... 34
3.2. Knowledge of the Active Interface .............................................................. 35
3.3. Signal Processing and Notation ................................................................... 35

Table of Contents
3.4. Select Processing ......................................................................................... 36

3.4.1. Select Processing in State Idle ............................................................. 37
3.4.2. Select Processing in Any Other State .................................................. 40
3.5. Card Command(C-APDU)........................................................................... 42
3.5.1. C-APDU Recognition .......................................................................... 42
3.5.2. BAD CLA, BAD INS or BAD LENGTH ........................................... 43
3.5.3. C-APDU Acceptance ........................................................................... 43
3.6. Unselect processing ..................................................................................... 46
3.7. Get Challenge Flag ...................................................................................... 47
4. Data Organization ............................................................... 48
4.2. Single Code .................................................................................................. 49
4.3. Interface Specific Data ................................................................................. 50
4.3.1. Characteristics ...................................................................................... 50
4.3.2. The Interface Specific Data ................................................................. 50
4.3.3. Notation for the Usage of Interface Specific Data ............................... 51
4.4. Common Data .............................................................................................. 51
4.5. Persistent Data ............................................................................................. 52
4.6. Transient Data Objects ................................................................................. 55
4.7. Transient Data .............................................................................................. 56
4.7.1. Global Transient Data .......................................................................... 56
4.7.2. Local Transient Data ............................................................................ 57
4.8. Personalization ............................................................................................. 59
4.9. Initialized Data ............................................................................................. 62
4.10. Files .............................................................................................................. 63
4.10.1. SFI in the Range 1 to 10 ...................................................................... 63
4.10.2. Transaction Log File ............................................................................ 64
4.10.3. Other Files ............................................................................................ 67
5. Application Block ................................................................ 68
5.1. Application Block Command Message ....................................................... 69
5.2. Local Transient Data .................................................................................... 69
5.3. Application Block Processing ...................................................................... 70
6. Application Unblock............................................................ 79
6.1. Application Unblock Command Message ................................................... 80
6.3. Application Unblock Processing.................................................................. 81
7. Compute Cryptographic Checksum .................................. 90
7.1. Compute Cryptographic Checksum Command Message ............................ 91
7.3. Compute Cryptographic Checksum Processing........................................... 92
8. Exchange Relay Resistance Data ...................................... 96
8.1. Exchange Relay Resistance Data Command Message ................................ 97

Table of Contents
8.3. Exchange Relay Resistance Data Processing .............................................. 98

9. First Generate AC .............................................................. 102
9.1. First Generate AC Command Message...................................................... 103
9.2. Local Transient Data .................................................................................. 103
9.3. First Generate AC Processing .................................................................... 105
9.3.1. Start .................................................................................................... 105
9.3.2. ARQC Requested ............................................................................... 127
9.3.3. TC Requested ..................................................................................... 132
9.3.4. AAC Decided ..................................................................................... 138
9.3.5. TC Decided ........................................................................................ 143
9.3.6. ARQC Decided .................................................................................. 148
9.3.7. No CDA – No Host Backwards Compatibility .................................. 153
9.3.8. No CDA – V1.1/V1.3 Host Backwards Compatibility ...................... 161
9.3.9. No CDA - V2.1/V2.2 Host Backwards Compatibility ...................... 168
9.3.10. No CDA – V2.05 Host Backwards Compatibility ............................. 171
9.3.11. MAS4C .............................................................................................. 174
9.3.12. CDA – No Host Backwards Compatibility........................................ 183
9.3.13. CDA – V1.1/V1.3 Host Backwards Compatibility ............................ 194
9.3.15. CDA – V2.05 Host Backwards Compatibility................................... 211
10. Second Generate AC......................................................... 218
10.1. Second Generate AC Command Message ................................................. 219
10.3. Second Generate AC Processing ............................................................... 221
10.3.1. Start .................................................................................................... 221
10.3.2. Unable To Go Online ......................................................................... 229
10.3.3. Issuer Authentication Data Present .................................................... 233
10.3.4. Issuer Authentication Data Not Present ............................................. 253
10.3.5. Decision AAC .................................................................................... 265
10.3.6. Decision TC ....................................................................................... 270
11. Get Challenge .................................................................... 338
11.1. Get Challenge Command Message ............................................................ 339
11.2. Get Challenge Processing .......................................................................... 340
12. Get Data ............................................................................. 342
12.1. Get Data Command Message..................................................................... 343
12.3. Get Data Processing ................................................................................... 346

Table of Contents
13. Get Processing Options ................................................... 353

13.1. Get Processing Options Command Message ............................................. 354
13.3. Get Processing Options Processing ........................................................... 355
14. Internal Authenticate......................................................... 361
14.1. Internal Authenticate Command message ................................................. 362
14.3. Internal Authenticate Processing ............................................................... 363
15. Issuer Updates .................................................................. 367
15.1. Issuer Updates Command Message ........................................................... 368
15.3. Issuer Updates Processing.......................................................................... 369
16. Offline Change PIN ............................................................ 378
16.1. Offline Change PIN Command Message ................................................... 379
16.3. Offline Change PIN Processing ................................................................. 380
16.3.1. Start .................................................................................................... 380
16.3.2. Encrypted PIN .................................................................................... 382
16.3.3. Plaintext PIN ...................................................................................... 388
17. PIN Change/Unblock ......................................................... 392
17.1. PIN Change/Unblock Command Message ................................................ 393
17.3. PIN Change/Unblock Processing ............................................................... 394
17.3.1. Start .................................................................................................... 394
17.3.2. PIN Unblock ...................................................................................... 396
17.3.3. PIN Change ........................................................................................ 405
18. Put Data ............................................................................. 416
18.1. Put Data Command Message ..................................................................... 417
18.3. Put Data Processing ................................................................................... 420
19. Read Record ...................................................................... 437
19.1. Read Record Command Message .............................................................. 438
19.3. Read Record Processing ............................................................................ 439
20. Recover AC ........................................................................ 446
20.1. Recover AC Command Message ............................................................... 447
20.3. Recover AC Processing ............................................................................. 448
21. Update Record................................................................... 455
21.1. Update Record Command Message ........................................................... 456

Table of Contents
21.3. Update Record Processing ......................................................................... 457

22. Verify .................................................................................. 467
22.1. Verify Command Message ........................................................................ 468
22.3. Verify Processing ....................................................................................... 469
22.3.1. Start .................................................................................................... 469
22.3.2. Encrypted PIN .................................................................................... 471
22.3.3. Plaintext PIN ...................................................................................... 480
23. Subroutines ....................................................................... 484
23.1. Overview .................................................................................................... 485
23.2. Add Additional Log Info ........................................................................... 486
23.2.1. Description ......................................................................................... 486
23.2.2. Computation....................................................................................... 486
23.3. Add transaction Amount to Temporary Accumulator ............................... 487
23.3.1. Description ......................................................................................... 487
23.3.2. Input arguments ................................................................................. 487
23.3.3. Computation....................................................................................... 487
23.4. Build Counters Field .................................................................................. 489
23.4.1. Description ......................................................................................... 489
23.4.2. Computation....................................................................................... 490
23.5. Check Accumulators and Counters Limits and Set CVR .......................... 494
23.5.1. Description ......................................................................................... 494
23.5.2. Computation....................................................................................... 494
23.6. Check Accumulators and Counters Limits and Set/Reset CVR ................ 496
23.6.1. Description ......................................................................................... 496
23.6.2. Computation....................................................................................... 496
23.7. Check for CVM Transaction ...................................................................... 497
23.7.1. Description ......................................................................................... 497
23.7.2. Output ................................................................................................ 497
23.7.3. Computation....................................................................................... 497
23.8. Check Format of Issuer Updates Data ....................................................... 498
23.8.1. Description ......................................................................................... 498
23.8.2. Output ................................................................................................ 498
23.8.3. Computation....................................................................................... 498
23.9. Check Format of Transaction Date ............................................................ 499
23.9.1. Description ......................................................................................... 499
23.9.2. Output ................................................................................................ 499
23.9.3. Computation....................................................................................... 499
23.10. Check If Record Is in Read Record Filter .................................................. 500
23.10.1. Description ......................................................................................... 500
23.10.2. Output ................................................................................................ 500
23.10.3. Computation....................................................................................... 500
23.11. Check Temp Accumulators and Temp Counters Limits and Set/Reset CVR
501
23.11.1. Description ......................................................................................... 501
23.11.2. Computation....................................................................................... 501

Table of Contents
23.12. Compute M/Chip 2.05 CVR ...................................................................... 503

23.12.1. Description ......................................................................................... 503
23.12.2. Computation....................................................................................... 503
23.13. Compute M/Chip 2.2 CVR ........................................................................ 504
23.13.1. Description ......................................................................................... 504
23.13.2. Computation....................................................................................... 504
23.14. Compute M/Chip 4 1.1 CVR ..................................................................... 505
23.14.1. Description ......................................................................................... 505
23.14.2. Computation....................................................................................... 505
23.15. Determine Accumulator Active Flag ......................................................... 507
23.15.1. Description ......................................................................................... 507
23.15.2. Input arguments ................................................................................. 507
23.15.3. Computation....................................................................................... 507
23.16. Determine Counter Active Flag ................................................................. 509
23.16.1. Description ......................................................................................... 509
23.16.2. Input Arguments ................................................................................ 509
23.16.3. Computation....................................................................................... 509
23.17. Process Additional Check Table ................................................................ 511
23.17.1. Description ......................................................................................... 511
23.17.2. Computation....................................................................................... 511
23.18. Process Issuer Updates ............................................................................... 512
23.18.1. Description ......................................................................................... 512
23.18.2. Computation....................................................................................... 512
23.19. Recognize Currency ................................................................................... 515
23.19.1. Description ......................................................................................... 515
23.19.2. Input Arguments ................................................................................ 515
23.19.3. Output ................................................................................................ 515
23.19.4. Computation....................................................................................... 515
23.20. Save Active Accumulators and Counters .................................................. 516
23.20.1. Description ......................................................................................... 516
23.20.2. Computation....................................................................................... 516
23.21. Update Temporary Accumulators and Counters........................................ 517
23.21.1. Description ......................................................................................... 517
23.21.2. Computation....................................................................................... 517
24. Data Dictionary .................................................................. 518

Using This Manual
1. Using This Manual

1.1. Purpose......................................................................................................... 10
1.2. Audience ...................................................................................................... 10
1.3. Related Information ..................................................................................... 10
1.4. Abbreviations ............................................................................................... 11
1.5. Specification Language ................................................................................ 13
1.6. Notational Conventions ............................................................................... 15
1.6.1. Hexadecimal Notational Convention ................................................... 15
1.6.2. Binary Notational Convention ............................................................. 15
1.6.3. Decimal Notational Convention .......................................................... 15
1.6.4. Data Object Notational Convention ..................................................... 15
1.6.5. Logic .................................................................................................... 16
1.6.6. Memory ................................................................................................ 17
1.6.7. State Notational Convention ................................................................ 18
1.6.8. C-APDU Notational Convention ......................................................... 18
1.7. Data Object Format ...................................................................................... 19
1.8. Specification Principles ............................................................................... 19
1.9. Revision History .......................................................................................... 20

Using This Manual
Purpose
1.1. Purpose
The M/Chip Advance Card Application Specification—Payment defines the behavior
of M/Chip™ Advance, once deployed.
1.2. Audience
MasterCard provides this manual for customers and their authorized agents.
Specifically, the following personnel should find this manual useful:
 Card application developers
 Card application testers
 Customers
1.3. Related Information

The following references are used in this document. The latest version applies unless
a publication date is explicitly stated.
[EMV BOOK 1] Integrated Circuit Card Specification for Payment Systems:

Application Independent ICC to Terminal Interface
Requirements, Version 4.3, November 2011
Security and Key Management, Version 4.3, November 2011
Application Specification, Version 4.3, November 2011
[EMV] [EMV BOOK 1], [EMV BOOK 2] and [EMV BOOK 3]
[EMV BOOK B] EMV Contactless Specifications for Payment Systems,
Book B, Entry Point Specification
[EMV BOOK C2] EMV Contactless Specifications for Payment Systems, Book
C-2, Kernel 2 Specification
[EMV BOOK D] EMV Contactless Specifications for Payment Systems,
Book D, EMV Contactless Communication Protocol
Specification
[SECURITY] M/Chip Card Application Cryptographic Algorithms

Using This Manual
Abbreviations
1.4. Abbreviations
Table 1.1 contains the abbreviations used in this document.
Table 1.1—Abbreviations
AAC Application Authentication Cryptogram
AC Application Cryptogram
ADF Application Definition File
AFL Application File Locator
AID Application Identifier
AIP Application Interchange Profile
an Alphanumeric characters
ans Alphanumeric and Special characters
APDU Application Protocol Data Unit
ARPC Authorization Response Cryptogram
ARQC Authorization Request Cryptogram
ATC Application Transaction Counter
b Binary
BER Basic Encoding Rules
C-APDU Command APDU
CAT Cardholder Activated Terminal
CDA Combined DDA/AC Generation
CDOL Card Risk Management Data Object List
CIAC Card Issuer Action Code
CID Cryptogram Information Data
CLA Class byte of command message
cn Compressed Numeric
CRM Card Risk Management
CRT Chinese Remainder Theorem
CSK Common Session Key
CTR Session Key Counter
CVC Card Verification Code
CVR Card Verification Results
DAC Data Authentication Code
DDA Dynamic Data Authentication
DDOL Dynamic Data Authentication Data Object List
DES Data Encryption Standard
DF Dedicated File
DRDOL Data Recovery Data Object List
EMV Europay MasterCard Visa
FCI File Control Information
IAD Issuer Application Data
ICC Integrated Circuit Card
IDN ICC Dynamic Number
INS Instruction byte of command message
IVCVC3 Initialization Vector for CVC3 generation
KDCVC3 ICC Derived Key for CVC3 generation
LCOL Lower Consecutive Offline Limit

Using This Manual
Abbreviations
LCOTA Lower Cumulative Offline Transaction Amount

LIM Security Counter Limit
MAC Message Authentication Code
MKAC AC Master Key
MKIDN ICC Dynamic Number Master Key
MKSMC SM for Confidentiality Master Key
MKSMI SM for Integrity Master Key
MTA Maximum Transaction Amount
n Numeric
NIC Length of the ICC Public Key Modulus
O Optional
P Processed
PAN Primary Account Number
PDOL Processing Options Data Object List
PIN Personal Identification Number
PPSE Proximity Payment System Environment
PSE Payment System Environment
PTH Previous Transaction History
R/CNS Rejected, Conditions Not Satisfied
RFU Reserved for Future Use
R-APDU Response APDU
RID Registered Application Provider Identifier
RRP Relay Resistance Protocol
SFI Short File Identifier
SHA Secure Hash Algorithm
SK Session Key (or private key in RSA context)
SKD Session Key Derivation
SMC Secure Messaging for Confidentiality
SMI Secure Messaging for Integrity
SW12 Status bytes 1-2
TC Transaction Certificate
TLV Tag Length Value
TVR Terminal Verification Results
UCOL Upper Consecutive Offline Limit
UCOTA Upper Cumulative Offline Transaction Amount
var. Variable

Using This Manual
Specification Language
1.5. Specification Language

This document specifies the M/Chip Advance application as a state machine. The
transitions between states are represented graphically in transition flow diagrams. A
textual description accompanies the transition flow diagrams. Figure 1.1 shows the
symbols used in the flow diagrams.
Figure 1.1—Symbols Used in Transition Flow Diagrams
Procedure
YES NO
Procedure start Procedure return decision
task complex task Subroutine call
NO
state
YES
connector complex decision state transition
Each diagram in this specification has a unique label and each symbol in a diagram
has a unique identifier. The identifier is the concatenation of the diagram label with
the symbol number. When a paragraph in the textual description starts with a symbol
identifier, then it corresponds to the symbol bearing the same identifier in the
transition flow diagram.

Using This Manual
Specification Language
Example
Symbols in the diagram in Figure 1.2 are labeled as VY.1.x. The symbol with
number 1 is identified in the textual description by VY.1.1.
Figure 1.2— Example of Symbol Identifier
VY.1
Verify
1
Update Get Challenge
Flag
An explanation of the task performed by symbol VY.1.1 is provided as follows:
VY.1.1
'Challenge Availability' in Get Challenge Flag := 'Successful Get Challenge' in Get
Challenge Flag
Clear 'Successful Get Challenge' in Get Challenge Flag
The order of execution of the processing steps is defined by the relevant flow
diagram. The textual description specifies the behavior of the individual steps not the
order of execution.
A GOTO statement is used to indicate the next step in the following two instances:
 A decision diamond, containing a test whose outcome determines subsequent
processing
 An off-page reference to another flow diagram

Using This Manual
Notational Conventions
1.6. Notational Conventions
1.6.1. Hexadecimal Notational Convention

Values expressed in hexadecimal form are enclosed in single quotes.
For example, 27509 decimal is expressed in hexadecimal as '6B75'.
1.6.2. Binary Notational Convention

Values expressed in binary form are followed by a b.
For example, '08' hexadecimal is expressed in binary as 00001000b.
1.6.3. Decimal Notational Convention

Values expressed in decimal form are not enclosed in single quotes.
For example, '08' hexadecimal is expressed in decimal as 8.
1.6.4. Data Object Notational Convention

Data objects used for this specification are written in a specific font to distinguish
them from the text. The font depends on the type of data object (refer to chapter 4 for
the definition of the different types of data objects):
Transient data objects:

Data Object Name
Persistent data objects:
Data Object Name
Example:
Accumulator 1 Amount Temp
AC Master Key
To refer to a sub-element of a data object (i.e. a specific bit, set of bits or byte of a
multi-byte data object), the following notational convention is used:
'Name of Sub-element' in Data Object Name
Example:
'Allow Retrieval Of Balance' in Application Control
refers to bit 2 of byte 2 in the Application Control
The sub-elements are defined in the data dictionary.
Each of the possible values of a sub-element has a name. To refer to a value, the
following notational convention is used:
Value Of Sub-element
Example:
'Key For Offline Encrypted PIN Verification' in Application Control := DDA
Key
means the same as bit 5 of byte 1 of Application Control is set to 0b.

Using This Manual
In a few exceptional cases, an index is used to identify a sub-element of a data object.

In this case the following notational conventions apply:
 To refer to a specific byte of a multi-byte data object, a byte index is used within
brackets (i.e. [_]).
For example, Transaction Related Data[11] represents byte 11 of the Transaction
Related Data. The first byte (leftmost or most significant) of a data object has
index 1.
 To refer to a specific bit of a single byte multi-bit data object, a bit index is used
within brackets [_].
For example, Cryptogram Version Number[7] represents the 7th bit of the
Cryptogram Version Number. The first bit (rightmost or least significant) of a
data object has index 1.
 To refer to a specific bit of a multi-byte data object, a byte index and a bit index
are used within brackets (i.e. [_][_]).
For example, Card Verification Results[2][4] represents bit 4 of byte 2 of the
Card Verification Results.
 Ranges of bytes are expressed with the x : y notational convention:

For example, Card Verification Results[1 : 5] represents bytes 1, 2, 3, 4, and 5 of
the Card Verification Results.
 Ranges of bits are expressed with the y : x notational convention:

For example, Cryptogram Version Number[5 : 1] represents bits 5, 4, 3, 2, and 1
of the Cryptogram Version Number.
1.6.5. Logic
 Decision symbols in the transition flow diagrams are translated in the textual
description as follows:
IF T
THEN
GOTO X
ELSE
GOTO Y
ENDIF
Where T is a statement resulting in true or false and X and Y are symbol
identifiers.
Example:
IF Amount, Authorized (Numeric) > MTA CVM
THEN
GOTO 2G.1.22
ELSE
GOTO 2G.1.23
ENDIF

Using This Manual
 Functionality of a certain complexity and appearing more than once is

implemented by means of a subroutine. The subroutines are specified in
chapter 23. In the textual description a subroutine is referenced by means of the
key word:
CALL
Example:
CALL UpdateTempAccsCntrs( )
 The notational convention NOT is used for bit inversion.
Example:
'Offline PIN Verification Not Performed' in Card Verification Results :=
NOT 'Offline PIN Verification Performed' in PIN Verification Status
 The notational conventions OR and AND are used for both the logical and bitwise
operations. Their meaning is context specific.
Example:
Logical OR:
IF (Authorisation Response Code = Y3) OR (Authorisation Response Code
= Z3)
Bitwise AND:
IF 'CVR Decisional Part' in Card Verification Results AND (Card Issuer
Action Code – Default = '000000')
 The notational convention | is used for the concatenation of two binary data
objects.
Example:
A := 'AB34'
B := A | 'FFFF'
means that B is assigned the value 'AB34FFFF'
1.6.6. Memory
 When a specific bit in a data object is set to 1b the word Set is used.
Example:
Set 'MTA Limit Exceeded' in Card Verification Results
 When a specific bit in a data object is set to 0b the word Clear is used.
Example:
Clear 'Issuer Authentication Failed' in Card Verification Results

Using This Manual
 When a specific value is assigned to a data object the symbol ':=' is used.
Example:
Script Counter := '00'
 When a write to a persistent data object must not be committed at the moment of
the assignment in the flow diagram, the notational convention (do not commit) is
used. In this case, the commit of the persistent data object happens at the end of
the command processing as explicitly indicated in the flow diagram.
If the symbol ':= ' is used for an assignment of a persistent data object without the
(do not commit) indication, it means an actual write in persistent memory of the
new value of the persistent data object.
Example:
Accumulator 1 Amount := Accumulator 1 Amount Temp (do not
commit)
The notational conventions are strictly followed in the body of this specification
but not in the diagrams.
1.6.7. State Notational Convention

The application states of the M/Chip Advance application are written in a specific
format to distinguish them from the text:
state
Example:
Successful processing of the select(active interface, C-APDU) signal changes
the application state from idle to:
 selected
 or to selectednotenabled.
1.6.8. C-APDU Notational Convention

The C-APDUs supported by the M/Chip Advance application are written in a specific
format to distinguish them from the text:
COMMAND
Example:
GET PROCESSING OPTIONS

Using This Manual
Data Object Format
1.7. Data Object Format

Data objects that have the numeric (n) format are BCD encoded, right justified with
leading hexadecimal zeros. Data objects that have the compressed numeric (cn)
format are BCD encoded, left justified and padded with trailing 'F's.
Note
The length indicator in the numeric and compressed numeric format notational
conventions (e.g. n 4) specifies the number of digits and not the number of bytes.
Data objects that have the alphanumeric (an) or alphanumeric special (ans) format are
ASCII encoded, left justified and padded with trailing hexadecimal zeros.
1.8. Specification Principles

In this document, the M/Chip Advance application is specified using the following
principles:
 The application is a state machine
 The processing of an external signal (e.g. C-APDU) is a transition between states
 The processing of external signals is structured into logical units.
These principles are used in order to present the application concepts. The same
principles do not have to be followed in the actual implementation. However, the
implementation must behave in a way that is indistinguishable from the behavior
specified in this document.
The Type Approval services consider the card application as a black box. They
validate output signals that the application generates as a result of processing of input
signals, against the output signals predicted by these specifications.

Using This Manual
Revision History
1.9. Revision History
Version 1.2  Implemented Relay Resistant Protocol (RRP)

 Added new configuration parameter 'Use M/Chip 4 CDOL1'
in Application Control allowing personalization of the
M/Chip Advance application with the M/Chip 4 CDOL1.
 Added new configuration parameter 'Enable Alternate
Interface After Successful Verify' in Application Control
allowing enablement of the alternate interface only after a
successful VERIFY command.
 Added new configuration parameter 'Enable Alternate
Interface After TC Generated' in Application Control
allowing enablement of the alternate interface only if a TC is
generated.
 Added new configuration parameter 'Save Accumulators
And Counters on ARQC Response' in Application Control
allowing the update of accumulators and counters also in
case an ARQC is generated.
 Added new configuration parameter 'Allow Retrieval Of
Transaction Log Records' in Application Control to disable
the READ RECORD command for Transaction Log records.
 Added new configuration parameter 'Key for MAS4C
Processing Flow' in Application Control allowing the use of a
dedicated AC Master Key for the MAS4C processing flow.
 Added new configuration parameter 'AC for MAS4C
Processing Flow' in Application Control allowing the
configuration of the cryptogram type (AAC or ARQC) that
is generated in the MAS4C processing flow.
 Added mechanism that allows parameters to be updated in a
linked application while another application is active.
Version 1.1  Included improvements and changes published in the
M/Chip Advance - Errata 7 for Card Specification
document.
 Included a method of configuring the M/Chip Advance
payment+data storage application to emulate the behavior of
the M/Chip Advance payment only variant.
Version 1.0 Initial version

General Card Requirements
2. General Card Requirements

2.1. Overview ...................................................................................................... 22
2.2. State Machine Interface ............................................................................... 22
2.3. The ICC interface ......................................................................................... 23
2.3.1. Contact ................................................................................................. 23
2.3.2. Contactless ........................................................................................... 23
2.4. Multiple Logical Channels ........................................................................... 23
2.5. Selection and Multi-application Cards......................................................... 23
2.5.1. M/Chip Advance Application Activation ............................................ 24
2.5.2. M/Chip Advance Application De-activation ....................................... 26
2.6. Signals from the Multi-application Manager to M/Chip Advance .............. 26
2.7. Linked Applications ..................................................................................... 29
2.8. Support for the PSE ..................................................................................... 30
2.9. Support for the PPSE ................................................................................... 30

Overview
2.1. Overview
The main part of this specification is at the application layer. M/Chip Advance is
specified as an abstract state machine using states, transitions and signals to model its
behavior. However, the behavior of the card –even for a mono application card– is
not fully covered by the state machine; the card must follow a number of requirements
and principles that are not present in the state machine.
Furthermore, the interface defined by the state machine is not the card interface at the
application layer. The interface defined by the state machine is in fact internal to the
card. To fully specify the card interface at the application layer, the link between the
state machine and the card interface is needed.
This section captures the requirements and principles that are not covered by the state
machine.
2.2. State Machine Interface

The external interface of the state machine is composed of signals. This interface is
internal to the card, as illustrated in Figure 2.1, and is defined in section 2.6.
Figure 2.1—State machine Interface
card interface
State machine to card link
state machine interface
state machine
Since it is internal to the card, the actual implementation of this interface is left to the
vendor.

The ICC interface
2.3. The ICC interface
2.3.1. Contact
The physical, data link and transport layers on the contact interface must be compliant
with [EMV BOOK 1]. The transmission protocol may be T = 0 or T = 1.
The application layer on the contact interface must be compliant with [EMV]. The C-
APDUs and R-APDUs visible on the contact interface are a direct transposition of all
C-APDUs and R-APDUs defined in this specification.
2.3.2. Contactless
The physical, data link and transport layers on the contactless interface must be
compliant with [EMV BOOK D]. The signaling scheme may be Type A or Type B.
The application layer on the contactless interface must be compliant with

[EMV BOOK C2]. The C-APDUs and R-APDUs visible on the contactless interface
are a direct transposition of all C-APDUs and R-APDUs defined in this specification.
2.4. Multiple Logical Channels

Support of multiple logical channels for M/Chip Advance is not needed and it is
assumed for the description below that the card does not support multiple logical
channels. The same state machine is used through both interfaces.
2.5. Selection and Multi-application Cards

M/Chip Advance may reside on a multi-application ICC. To allow this, it is necessary
to specify how the multi-application environment influences M/Chip Advance. These
specifications assume that an entity, referred to as the multi-application manager,
manages the multi-application aspects.
Note
The requirements below are also valid when M/Chip Advance is the only application
present on the card.
Figure 2.2 illustrates a card with three different applications.

Selection and Multi-application Cards
Figure 2.2—Multi-application Card
card interface
Multi-application manager
App.1 App.2 App.3
The functionality of the multi-application manager is an example of the link needed

between the application state machine and the card as a whole. The management of
M/Chip Advance by the multi-application manager must comply with a number of
principles, described below.
2.5.1. M/Chip Advance Application Activation

For the multi-application manager, an application may be either active or inactive.
Active applications in the ICC are the applications currently selected. Inactive
applications are all the applications that are not currently selected.
The M/Chip Advance application is inactive for the multi-application manager if and
only if it is in the idle state. To activate the M/Chip Advance application on the
ICC, the multi-application manager sends a select signal to it. M/Chip Advance may
be activated by the multi-application manager through either interface (contact and
contactless). For M/Chip Advance, the select signal identifies the active interface and
this is reflected by using the select(active interface, C-APDU) terminology. The
'active interface' parameter identifies the interface currently active while the 'C-
APDU' parameter represents the C-APDU received by the multi-application and
passed on to M/Chip Advance. In a real card, this can be implemented in various
ways, but what is essential is that M/Chip Advance knows, when it is activated, which
interface is active.
Note
Only one interface may be active at a time and switching the active interface implies
the power off of the currently active interface.
In Figure 2.3, the multi-application manager activates application 1 (the active

application, App.1, on the ICC is indicated in bold) in contactless mode.

Selection and Multi-application Cards
Figure 2.3—Application Activation

Select App.1
Contact interface Contactless interface

select(contactless,
C-APDU)
App.1 App.2 App.3
The multi-application manager sends a select(active interface, C-APDU) signal to

M/Chip Advance if:
 The card has received a select C-APDU compliant with [EMV] on the active
interface, and
 The AID in the select C-APDU matches the first bytes of the AID supported by
M/Chip Advance.
The multi-application manager may also send a select(active interface, C-APDU)

signal to M/Chip Advance if:
 The card has previously received a select C-APDU compliant with [EMV] on
the active interface that activated another application, and
 The AID in this previous select C-APDU matches the first bytes of the AID
supported by M/Chip Advance, and
 The card has received a select next C-APDU compliant with [EMV], and
 M/Chip Advance has not yet been selected in the sequence of the initial select
C-APDU and consecutive select next C-APDUs.
In this case, the position of M/Chip Advance in the sequence of applications
successively selected by the initial select C-APDU and consecutive select next C-
APDUs is free. What is essential is that M/Chip Advance would eventually be
selected by such a sequence.
In other words, it is mandatory to support partial selection and the select next C-
APDU, as defined in [EMV BOOK 1]. This is true on both the contact and
contactless interface.
Optionally the multi-application manager can send a select(active interface, C-APDU)

signal to M/Chip Advance if the ICC is reset and M/Chip Advance is selected by
default. It is not forbidden, when an interface is reset, to select M/Chip Advance, but
this is not required.

Signals from the Multi-application Manager to M/Chip Advance
When M/Chip Advance is inactive, the only signal that it can receive from the multi-
application manager is the select(active interface, C-APDU) signal.
2.5.2. M/Chip Advance Application De-activation

To de-activate an application on the ICC, the multi-application manager sends an
unselect signal to an active application. These specifications represent the reset, or
power off of the active interface, or the activation of another application when M/Chip
Advance is currently active, as the reception by M/Chip Advance of the unselect signal
from the multi-application manager.
In Figure 2.4, the multi-application manager de-activates application App. 1.
Figure 2.4—Application De-activation
reset

unselect
App.1 App.2 App.3
2.6. Signals from the Multi-application Manager

to M/Chip Advance
When M/Chip Advance is active, the signals that it can receive from the multi
application manager are:
 The select(active interface, C-APDU) signal
 A card command(active interface, C-APDU)
 The unselect signal
Any C-APDU received by the card when M/Chip Advance is active will lead to one of
the following behaviors:
 The C-APDU is recognized by the multi-application manager as a select
carrying an AID supported by M/Chip Advance or a select next as mentioned
above. The multi application manager sends the select(active interface, C-
APDU) signal to M/Chip Advance. The active interface parameter is used to
represent the fact that M/Chip Advance has knowledge of the active interface
when processing the select(active interface, C-APDU) signal. The C-APDU
parameter represents the complete C-APDU (header and conditional body of
variable length).

 The C-APDU leads to the selection of another application on the card. The
unselect signal is sent to M/Chip Advance .
 The C-APDU does not lead to the selection of an application on the card. The
C-APDU is sent to M/Chip Advance as a card command(active interface, C-
APDU). The active interface parameter is used to represent the fact that
M/Chip Advance has knowledge of the active interface when processing the C-
APDU. The C-APDU parameter represents the complete C-APDU (header
and conditional body of variable length). In Figure 2.5, the multi-application
manager sends a card command to application App. 1.
Figure 2.5—Sending a Card Command to an Application
C-APDU

card command(contact,
C-APDU)
App.1 App.2 App.3
There are three exceptions.
The first exception is when the format of the C-APDU received by the card is not
correct. Format errors include:
 The number of bytes received is insufficient to carry a C-APDU header
 Lc in the command header is inconsistent with the number of command data
bytes
How to handle format errors is left to the implementation. These specifications

assume that the multi-application manager will not present a C-APDU to M/Chip
Advance with format errors that could have been detected at lower layers. As a result,
a card command(active interface, C-APDU) has the following characteristics:
 Length C-APDU is greater than or equal to 4
 Lc in C-APDU is equal to number of command data bytes
The second exception is the select C-APDU with an AID that is not supported on the
active interface. In this case, the response from the card must be SW12 equal to
'6A82', as specified in [EMV]. It is assumed that this response is handled by the multi-
application manager. In some implementations, the response would be handled by the
M/Chip Advance software. This is allowed and how to implement this behavior is left
to the implementation. The impact of such a C-APDU on the M/Chip Advance state
machine (if M/Chip Advance is active) is also left to the implementation. M/Chip

Advance may go to the idle state, or to the selected state or may remain in its
current state.
The third exception is the select next C-APDU when all matching DF files have
already been selected. In that case, the response from the card must also be SW12
equal to '6A82', as specified in [EMV]. Again, it is assumed that this response is
handled by the multi-application manager. In some implementations, the response
would be handled by the M/Chip Advance software. This is allowed and how to
implement this behavior is also left to the implementation. Again, the impact of such a
C-APDU on the M/Chip Advance state machine (if M/Chip Advance is active) is left
to the implementation: M/Chip Advance may go to the idle state, or to the
selected state or may remain in the current state.
Assuming the exceptions above are handled by the multi-application manager, the
signals received by M/Chip Advance from the multi-application manager are given in
Table 2.1.
Table 2.1—Signals from the Multi-application Manager
M/Chip Advance Inactive Active
State for the Multi-
application
Manager
Possible signals  select(active  select(active interface, C-APDU)
interface, C-  card command(active interface,
APDU) C-APDU)
 unselect
The use of the select(active interface, C-APDU), card command(active interface, C-

APDU), and unselect signals is an abstraction, which, in a real card, can be
implemented in various ways. In a real card, no signal is exchanged internally.

Linked Applications
2.7. Linked Applications

M/Chip Advance supports a mechanism that allows one application to be updated
while another application is active (selected). This mechanism involves the following
applications present on the card which must be controlled by the same issuer:
 M/Chip Advance application(s)
 PSE (optional)
 PPSE.
The update mechanism is available whenever any of the M/Chip Advance applications
present on the card is in the script state and works as described here.
A PUT DATA is sent as a script command to the currently selected M/Chip Advance
application.
This application verifies the MAC on the PUT DATA using its SMI Session Key and
if the verification is successful the update is applied to one of the following:
 the currently selected application
 any other M/Chip Advance application present on the card
 the PSE present on the card
 the PPSE present on the card.
This implies that the strict firewalling between these applications must be loosened.
How the mechanism is implemented internally between the linked applications is left
to the implementer.
The PUT DATA is done on Linked Application Data. The target application (that is
the application that will be updated) can be addressed in two ways via Linked
Application Data:
 through its AID
 through its Linked Application Index (for M/Chip Advance target applications
only).
When the target application is addressed via Linked Application Index, M/Chip
Advance application updates the first target application it finds with a matching
Linked Application Index. Thefore, all linked M/Chip Advance target applications
must be assigned different indexes by the issuer. The index of an M/Chip Advance
application is defined at personalization by assigning a value to the data object Linked
Application Index.
Addressing the target application by index is not supported for PSE and PPSE.
The following updates are available on the target application:

 for M/Chip Advance applications: the Previous Transaction History[5]
(allowing to block or unblock the application) and the FCI Proprietary
Template (tag 'A5')
 for the PSE and the PPSE: the FCI Proprietary Template (Tag 'A5')

Support for the PSE
2.8. Support for the PSE

This specification views support for the PSE as another application on the contact
interface. Since multi-application cards are allowed, support for the PSE is allowed.
If the PSE is supported, it must comply with [EMV]. The PSE may be visible on the
contactless interface.
If the PSE is not supported, the response from the ICC when the terminal attempts to
select it must comply with [EMV], i.e. the response must consist of SW12 equal to
'6A82'.
If the PSE is supported, then the PSE must be supported as target application in
Linked Application Data passed in the PUT DATA command to update the FCI
Proprietary Template (tag 'A5') of the PSE.
2.9. Support for the PPSE

This specification views support for the PPSE as another application accessible via
the contactless interface. Support for the PPSE is mandatory. The PPSE may be
visible on the contact interface.
The PPSE must comply with [EMV BOOK B].
The PPSE must be supported as target application in Linked Application Data passed
in the PUT DATA command to update the FCI Proprietary Template (tag 'A5') of the
PPSE.

State Machine
3. State Machine
3.1. Application States ........................................................................................ 32
3.1.1. Idle ....................................................................................................... 32
3.1.2. Selectednotenabled .............................................................................. 33
3.1.3. Selected ................................................................................................ 33
3.1.4. Initiated ................................................................................................ 33
3.1.5. Online................................................................................................... 34
3.1.6. Script .................................................................................................... 34
3.3. Signal Processing and Notation ................................................................... 35
3.4. Select Processing ......................................................................................... 36
3.4.1. Select Processing in State Idle ............................................................. 37
3.4.2. Select Processing in Any Other State .................................................. 40
3.5. Card Command(C-APDU)........................................................................... 42
3.5.1. C-APDU Recognition .......................................................................... 42
3.5.2. BAD CLA, BAD INS or BAD LENGTH ........................................... 43
3.5.3. C-APDU Acceptance ........................................................................... 43
3.6. Unselect processing ..................................................................................... 46
3.7. Get Challenge Flag ...................................................................................... 47

State Machine
Application States
3.1. Application States

When the application is in operational phase (i.e. personalized), its behavior can be
specified as an Extended Finite State Machine. The application states of M/Chip
Advance are listed in Table 3.1.
Table 3.1—Application States
State Description
idle Application is not currently selected
selected Application is selected and enabled
selectednotenabled Application is selected but is not enabled
initiated Transaction is initiated
online Application expects a connection with the
issuer
script Application is ready to accept a script
command from the issuer
3.1.1. Idle
M/Chip Advance is in state idle if it is not currently activated. In a multi-application
card for instance, the application may be in state idle if another application is
activated. The application also goes to the state idle when the card is reset or
powered off (unselect signal).
In the state idle the application does not process C-APDUs (i.e. card
command(active interface, C-APDU)), but is only waiting for an external select(active
interface, C-APDU) signal.
Successful processing of the select(active interface, C-APDU) signal changes the
application state from idle to:
 selected
 or to selectednotenabled.
The destination state from the idle state depends on the following:
 Which interface is currently active
 Whether that interface is currently enabled or not
The following tables show the destination state.

Table 3.2—Destination States-1
contact interface enabled contact interface not enabled
select(contact, selected selectednotenabled
C-APDU)

State Machine
Application States
Table 3.3—Destination States-2

contactless interface enabled contactless interface not enabled
select(contactless, selected selectednotenabled
C-APDU)
3.1.2. Selectednotenabled
In the state selectednotenabled all C-APDUs are rejected and M/Chip
Advance remains in this state. The select signal is processed but does not change the
state. Only the unselect signal allows to leave this state (and go back to the idle
state).
3.1.3. Selected
Every transaction starts in the state selected. There are six C-APDUs processed in
this state:
 GET CHALLENGE
 GET DATA
 GET PROCESSING OPTIONS
 OFFLINE CHANGE PIN
 READ RECORD
 VERIFY
M/Chip Advance goes to state initiated after the successful processing of the
GET PROCESSING OPTIONS command. The other commands do not modify the
application state.
3.1.4. Initiated
In this state, a new transaction is initiated. There are eleven C-APDUs processed in
this state:
 COMPUTE CRYPTOGRAPHIC CHECKSUM
 EXCHANGE RELAY RESISTANCE DATA
 GENERATE AC
 GET CHALLENGE
 GET DATA
 GET PROCESSING OPTIONS,
 INTERNAL AUTHENTICATE
 READ RECORD
 RECOVER AC
 VERIFY

State Machine
Application States
M/Chip Advance goes back from the state initiated to the state selected after
successful processing of the COMPUTE CRYPTOGRAPHIC CHECKSUM
command.
M/Chip Advance proceeds from the state initiated to the state script after
successful processing of the first GENERATE AC command, completed with a TC or
AAC.
M/Chip Advance proceeds from the state initiated to the state online after
successful processing of the first GENERATE AC command, completed with an
ARQC.
The other commands do not modify the application state.
3.1.5. Online
In this state, the application is expecting a response from the issuer. There are ten
C-APDUs processed in this state:
 APPLICATION BLOCK
 APPLICATION UNBLOCK
 GENERATE AC
 GET CHALLENGE
 GET DATA
 ISSUER UPDATES
 PIN CHANGE/UNBLOCK
 READ RECORD
 VERIFY
M/Chip Advance proceeds from the state online to the state script after
successful processing of the second GENERATE AC command, which may or may
not carry the response from the issuer. The other commands do not modify the
application state.
3.1.6. Script
In this state, the application can process script commands from the issuer. The script
commands processed in this state are:
 APPLICATION BLOCK
 APPLICATION UNBLOCK
 PIN CHANGE/UNBLOCK
 PUT DATA
 UPDATE RECORD
M/Chip Advance stays in the state script after successful processing of a script
command.

State Machine
Knowledge of the Active Interface
In this state, the application also processes the following commands:

 GET CHALLENGE
 GET DATA
 READ RECORD
 VERIFY
These commands do not modify the application state.
3.2. Knowledge of the Active Interface

The behavior of M/Chip Advance –for the same signal– may depend on the interface
currently active. This is why the select(active interface, C-APDU) signal and the card
command(active interface, C-APDU) signal both carry the active interface parameter.
Processing of the select(active interface, C-APDU) signal depends on the active
interface in order to check if this interface is enabled.
Processing of a card command(active interface, C-APDU) depends on the active
interface as follows:
Some of the persistent data objects are interface specific. A number of
persistent data objects are duplicated so that one instance is used only if the
contact interface is active, while the other instance is used only if the
contactless interface is active.
The data objects that are duplicated are listed in chapter 4. The selection of the
contact specific data or of the contactless specific data is the only difference in the
processing of card commands.
The state machine is independent of the active interface: whatever the active interface
used for a transaction, all the functionality of M/Chip Advance is available.
3.3. Signal Processing and Notation

The card manager sends signals to M/Chip Advance via the internal interface. The
application state determines which signals are accepted by M/Chip Advance.
When M/Chip Advance is in the state idle, the only signal accepted from the card
manager is the select(active interface, C-APDU) signal.
When M/Chip Advance is active (i.e. the application is in a state other than idle), the
signals that it accepts from the card manager are:
 The select(active interface, C-APDU) signal
 The card command(active interface, C-APDU) signal
 The unselect(active interface, C-APDU) signal
As the difference in behavior is only in the data used, the processing of the card
command(active interface, C-APDU) signals can be specified generically, i.e. not
differentiating between contact and contactless. The context (i.e. the interface
currently active) determines which data is used, following the rule in section 3.2. As
a consequence, the parameter carrying the identifier of the active interface in the card
command signals will be omitted in the remainder of this document. The card
command(C-APDU) signals will be used instead of the card command(active
interface, C-APDU) signals, leaving the interface dependencies as contextual.

State Machine
Select Processing
Table 3.4—Signals Sent by the Card Manager

Application State idle all other states
Valid signals select(active interface, select(active interface, C-APDU),
C-APDU) card command(C-APDU),
unselect
3.4. Select Processing

When receiving a select(active interface, C-APDU) signal, the application performs a
validity check on Le. The select(active interface, C-APDU) signals that fail this
validity check lead to the following processing:
 The application does not perform any action and responds with only SW12
equal to '6700'
 The application remains in its current state
Note
The validity check on Le might be performed by the application manager instead of
the application.
Processing of an incoming select(active interface, C-APDU) signal depends on the

application state. If M/Chip Advance is in state idle, then the application behavior is
specified in section 3.4.1. If M/Chip Advance is in any other state, then its behavior is
specified in section 3.4.2.

State Machine
Select Processing
3.4.1. Select Processing in State Idle

Figure 3.1 shows the starting diagram for the processing of the select signal in state
idle. The symbols in the diagram are labeled SI.x.
Figure 3.1—Select Processing in State Idle
SI
Select
1
Create global transient
data
2
No
Application Yes
blocked?
4 3
Build response Build response
SW12 = '9000' SW12 = '6283'
5
contact Active interface? contactless
6 7
Interface Yes Yes
Interface
disabled? disabled?
9
Build response for
disabled interface
No No
8 10 8
To selected To selectednotenabled To selected

state state state

State Machine
Select Processing
SI.1
The global transient data objects are created. The initial value is binary zero(es). The
global transient data objects are listed in chapter 4.
Note
It is possible to create these data objects during the processing of other C-APDUs,
without changing the external behavior of M/Chip Advance. This is allowed as long as
it is indistinguishable from the behavior described in this specification.
SI.2
IF 'Application Blocked' in Previous Transaction History is set
THEN
GOTO SI.3
ELSE
GOTO SI.4
ENDIF
SI.3
Build the response. The application will return the File Control Information and
SW12 equal to '6283'.
SI.4
SI.5
IF the contact interface is active
THEN
GOTO SI.6
ELSE
GOTO SI.7
ENDIF
SI.6
IF 'Interfaces Status' in Interface Enabling Switch = Contact Interface Disabled
THEN
GOTO SI.9
ELSE
GOTO SI.8
ENDIF
SI.7
IF 'Interfaces Status' in Interface Enabling Switch = Contactless Interface Disabled
THEN
GOTO SI.9
ELSE
GOTO SI.8
ENDIF
SI.8
Send the response and go to state selected.

State Machine
Select Processing
SI.9
Build the response for a disabled interface. The implementer has the choice of either
of the following methods:
 Use the File Control Information and SW12 as prepared in SI.3 and SI.4, or
 Set SW12= '6985' or another appropriate error status word, and do not return
the File Control Information
SI.10
Send the response and go to state selectednotenabled.

State Machine
Select Processing
3.4.2. Select Processing in Any Other State

Figure 3.2 shows the starting diagram for the processing of the select signal in state
selected, selectednotenabled, initiated, online, script.
The symbols in the diagram are labeled SO.x.
Figure 3.2—Select Processing in Any Other State
SO
Select
1
Clear global transient
data
2
No
Application Yes
blocked?
4 3
SW12 = '9000' SW12 = '6283'
5
contact Active interface? contactless
6 7
Interface Yes Yes
Interface
disabled? disabled?
9
Build response for
disabled interface
No No
8 10 8
To selected To selectednotenabled To selected

state state state

State Machine
Select Processing
SO.1
The global transient data objects are cleared. The resulting value is binary zero(es).
The global transient data objects are listed in chapter 4.
Note
It is possible to clear these data objects during the processing of other C-APDUs,
without changing the external behavior of the M/Chip Advance application. This is
allowed as long as it is indistinguishable from the behavior described in this
specification.
SO.2
THEN
GOTO SO.3
ELSE
GOTO SO.4
ENDIF
SO.3
SO.4
SO.5
IF the contact interface is active
THEN
GOTO SO.6
ELSE
GOTO SO.7
ENDIF
SO.6
IF 'Interfaces Status' in Interface Enabling Switch = Contact Interface Disabled
THEN
GOTO SO.9
ELSE
GOTO SO.8
ENDIF
SO.7
IF 'Interfaces Status' in Interface Enabling Switch = Contactless Interface Disabled
THEN
GOTO SO.9
ELSE
GOTO SO.8
ENDIF

State Machine
Card Command(C-APDU)
SO.8
Send the response and go to state selected.
SO.9
Build the response for a disabled interface. The implementer has the choice of either
of the following methods:
 Use the File Control Information and SW12 as prepared in SO.3 and SO.4, or
 Set SW12= '6985' or another appropriate error status word, and do not return
the File Control Information.
SO.10
Send the response and go to state selectednotenabled.
3.5. Card Command(C-APDU)

Processing of a card command is done in three consecutive steps:
1. Analyze the C-APDU header to recognize the C-APDU (C-APDU
recognition),
2. If the C-APDU is supported, check the state to decide if the C-APDU has to be
processed or not (C-APDU acceptance)
3. Process the C-APDU (C-APDU processing)
3.5.1. C-APDU Recognition

M/Chip Advance identifies the C-APDU transmitted by the terminal based on the
CLA and INS byte.
M/Chip Advance supports the CLA and INS bytes specified in Table 3.5.
Table 3.5—Supported C-APDUs
CLA INS C-APDU
'84' '1E' APPLICATION BLOCK
'84' '18' APPLICATION UNBLOCK
'80' '2A' COMPUTE CRYPTOGRAPHIC CHECKSUM
'80' 'EA' EXCHANGE RELAY RESISTANCE DATA
'80' 'AE' GENERATE AC
'00' '84' GET CHALLENGE
'80' 'CA' GET DATA
'80' 'A8' GET PROCESSING OPTIONS
'00' '88' INTERNAL AUTHENTICATE
'84' 'D4' ISSUER UPDATES
'80' 'D2' OFFLINE CHANGE PIN
'84' '24' PIN CHANGE/UNBLOCK
'84' 'DA' PUT DATA
'00' 'B2' READ RECORD
'80' 'D0' RECOVER AC
'84' 'DC' UPDATE RECORD
'00' '20' VERIFY

State Machine
C-APDUs with unrecognized CLA byte lead to BAD CLA.

C-APDUs with unrecognized INS byte lead to BAD INS.
The application must perform a validity check on Le. C-APDUs that fail this validity
check lead to BAD LENGTH.
The order in which the CLA check, the INS check and the Le validity check are done
is left to the implementation. However, it is required that:
 The checks are done and that only C-APDUs passing all checks are supported
 The C-APDUs that do not pass all checks are processed as specified in
section 3.5.2
If the outcome of the C-APDU recognition is BAD CLA, BAD INS or BAD
LENGTH, the C-APDU is not supported by M/Chip Advance and the application
processes as specified in section 3.5.2. Otherwise the C-APDU is supported and the
application processes as specified in section 3.5.3.
3.5.2. BAD CLA, BAD INS or BAD LENGTH

The processing of unsupported C-APDUs is as follows:
The SW12 supported are as follows:
Table 3.6—BAD CLA/INS/LENGTH SW12s
Reason SW12
BAD CLA '6E00'
BAD INS '6D00'
BAD LENGTH '6700'
3.5.3. C-APDU Acceptance

When a C-APDU is recognized, M/Chip Advance checks whether it is in a state
allowing the actual processing of the C-APDU.
Acceptance or rejection of a C-APDU is specified in Table 3.7.
If the C-APDU is accepted in the current application state (P: Processed), then the C-
APDU is processed as specified in the chapter dedicated to the C-APDU. The
destination states are defined in section 3.5.3.2.
If the C-APDU is rejected in the current state (R/CNS: Rejected, Conditions Not
Satisfied), then further processing is specified in section 3.5.3.1.

State Machine
Table 3.7—Acceptance Matrix

state selected selected initiated online script
notenabled
C-APDU
APPLICATION R/CNS (1) R/CNS (1) R/CNS (1) P P
BLOCK
APPLICATION R/CNS (1) R/CNS (1) R/CNS (1) P P
UNBLOCK
COMPUTE R/CNS (1) R/CNS (2) P R/CNS (2) R/CNS (2)
CRYPTOGRAPHIC
CHECKSUM
EXCHANGE R/CNS (1) R/CNS (1) P R/CNS (1) R/CNS (1)
RELAY
RESISTANCE
DATA
GENERATE AC R/CNS (1) R/CNS (2) P P R/CNS (2)
GET CHALLENGE R/CNS (1) P P P P
GET DATA R/CNS (1) P P P P
GET PROCESSING R/CNS (1) P P R/CNS (2) R/CNS (2)
OPTIONS
INTERNAL R/CNS (1) R/CNS (1) P R/CNS (1) R/CNS (1)
AUTHENTICATE
ISSUER UPDATES R/CNS (1) R/CNS (1) R/CNS (1) P R/CNS (1)
OFFLINE CHANGE R/CNS (1) P P P P
PIN
PIN CHANGE/ R/CNS (1) R/CNS (1) R/CNS (1) P P
UNBLOCK
PUT DATA R/CNS (1) R/CNS (1) R/CNS (1) R/CNS (1) P
READ RECORD R/CNS (1) P P P P
RECOVER AC R/CNS (1) R/CNS (1) P R/CNS (1) R/CNS (1)
UPDATE RECORD R/CNS (1) R/CNS (1) R/CNS (1) R/CNS (1) P
VERIFY R/CNS (1) P P P P
3.5.3.1. Rejected C-APDU Processing

Rejected C-APDUs identified as R/CNS (1) in Table 3.7 are processed as follows:
equal to '6985'
Rejected C-APDUs identified as R/CNS (2) in Table 3.7 are processed as follows:
 The global transient data objects are cleared
 The application does not perform any other action than transitioning states and
responds with only SW12 equal to '6985'
 The destination state is the state selected

State Machine
3.5.3.2. Processed C-APDU Processing

The transition matrix of accepted C-APDUs is as follows:
Table 3.8—Transition Matrix
state selected initiated online script
C-APDU
APPLICATION
BLOCK
'9000' - - online script
Other (error) - - online script
APPLICATION
UNBLOCK
COMPUTE
CRYPTOGRAPHIC
CHECKSUM
'9000' - selected - -
Other (error) - selected - -
EXCHANGE RELAY
RESISTANCE DATA
'9000' initiated
Other (error) initiated
GENERATE AC
AAC '9000' - script script -
TC '9000' - script script -
ARQC '9000' - online - -
Other (error) - selected selected -
GET CHALLENGE
'9000' selected initiated online script
Other (error) selected initiated online script
GET DATA
GET PROCESSING
OPTIONS
'9000' initiated initiated - -
Other (error) selected selected - -
INTERNAL
AUTHENTICATE
'9000' - initiated - -
Other (error) - initiated - -
ISSUER UPDATES
'9000' - - online -
Other (error) - - online -

State Machine
Unselect processing
state selected initiated online script
C-APDU
OFFLINE CHANGE
PIN
PIN
CHANGE/UNBLOCK
PUT DATA
'9000' - - - script
Other (error) - - - script
READ RECORD
RECOVER AC
'9000' - initiated - -
Other (error) - initiated - -
UPDATE RECORD
'9000' - - - script
Other (error) - - - script
VERIFY
'9000', '63Cx', selected initiated online script
'6983'
3.6. Unselect processing

The unselect signal is processed in all states where it is received:
Table 3.9—Unselect Signal Acceptance Matrix
state selectednotenabled selected initiated online script
signal
unselect P P P P P
The transition matrix of the unselect signal is as follows:

Table 3.10—Unselect Signal Transition Matrix
state selectednotenabled selected initiated online script
signal
unselect idle idle idle idle idle
The processing of the unselect signal is the following:

 The values of the global transient data are cleared
 The global transient data are de-allocated

State Machine
Get Challenge Flag
3.7. Get Challenge Flag

The purpose of the Get Challenge Flag is to ensure that the VERIFY command and
the OFFLINE CHANGE PIN command immediately follow the GET CHALLENGE
command, when the PIN is provided in encrypted form.
In this specification the Get Challenge Flag is updated at the command level. As a
consequence, C-APDUs rejected in earlier steps than command processing would not
update the Get Challenge Flag.
The update of the Get Challenge Flag corresponding to a reset is specified as follows
in the command processing chapters:
'Challenge Availability' in Get Challenge Flag := 'Successful Get Challenge'
in Get Challenge Flag
This update, at the command level, is the minimum required from implementations.
Implementations may also perfom this update of the Get Challenge Flag in the earlier
steps. In particular, implementations may update the Get Challenge Flag during the
C-APDU recognition step or C-APDU acceptance step.

Data Organization
4. Data Organization
4.2. Single Code .................................................................................................. 49
4.3. Interface Specific Data ................................................................................. 50
4.3.1. Characteristics ...................................................................................... 50
4.3.2. The Interface Specific Data ................................................................. 50
4.3.3. Notation for the Usage of Interface Specific Data ............................... 51
4.4. Common Data .............................................................................................. 51
4.5. Persistent Data ............................................................................................. 52
4.6. Transient Data Objects ................................................................................. 55
4.7. Transient Data .............................................................................................. 56
4.7.1. Global Transient Data .......................................................................... 56
4.7.2. Local Transient Data ............................................................................ 57
4.8. Personalization ............................................................................................. 59
4.9. Initialized Data ............................................................................................. 62
4.10. Files .............................................................................................................. 63
4.10.1. SFI in the Range 1 to 10 ...................................................................... 63
4.10.2. Transaction Log File ............................................................................ 64
4.10.3. Other Files ............................................................................................ 67

Data Organization
Knowledge of the Active Interface
4.1. Knowledge of the Active Interface

Processing of the select(active interface, C-APDU) signal and of a card
command(active interface, C-APDU) depends on the active interface as follows:
Some of the persistent data objects are interface specific. A number of

persistent data objects are duplicated so that one instance is used only when
the contact interface is active, while the other instance is used only when the
contactless interface is active. For instance, the Application Interchange
Profile returned by the card depends on the interface currently active.
Note
Most of the persistent data objects are not duplicated: for those data objects, the same
value is used whatever the active interface. For example, the Application Life Cycle
Data is a common data object, used whatever the active interface.
4.2. Single Code

M/Chip Advance is designed so that the same code will run all M/Chip Advance
transactions. Whichever interface is used for a transaction, all the functionality of
M/Chip Advance is available. Different behaviors between transactions conducted
with different interfaces depend only on the different persistent data objects used for
these interfaces, but not on the code running these transactions.
When a transaction is processed with M/Chip Advance the complete list of persistent
data objects that will be used by the M/Chip Advance code for this transaction consists
of:
 The common data objects
 The interface specific data objects assigned to this interface
It is to be noted that the state machine, which is part of the code, is also common. It is
the same state machine that is used when the contact interface is active and when the

Data Organization
Interface Specific Data
4.3. Interface Specific Data
4.3.1. Characteristics
Usage of interface specific data modifies the behavior of M/Chip Advance depending
on the interface currently active. The interface specific data always exist for the:
1. Contact instance
2. Contactless instance
The contact specific instances of these data are exclusively used when the contact
interface is active. Conversely, the contactless specific instances of these data are
exclusively used when the contactless interface is active.
All the interface specific data share the following characteristics:
1. The coding (format and semantics) of the data is identical for both interfaces
2. The data are persistent
3. The data can be personalized
4. When accessed through the GET DATA and PUT DATA commands, the tags
are different for the contact instance and the contactless instance
4.3.2. The Interface Specific Data

The following data are interface specific:
Table 4.1—Interface Specific Data
AC Master Key
AC Session Key Counter
AC Session Key Counter Limit
Accumulator 1 Control
Accumulator 1 CVR Dependency Data
Accumulator 2 Control
Accumulator 2 CVR Dependency Data
Application Control
Application File Locator
Application Interchange Profile
Card Issuer Action Code – Decline
Card Issuer Action Code – Default
Card Issuer Action Code – Online
Counter 1 Control
Counter 1 CVR Dependency Data
Counter 2 Control
Counter 2 CVR Dependency Data
CVR Issuer Discretionary Data
ICC Dynamic Number Master Key
Interface Identifier
IVCVC3(Track1)
IVCVC3(Track2)

Data Organization
Common Data

KDCVC3
Key Derivation Index
Max Time For Processing Relay Resistance APDU
Min Time For Processing Relay Resistance APDU
MTA CVM
MTA NoCVM
Read Record Filter
Security Limits Status
SMC Master Key
SMI Master Key
SMI Session Key Counter
SMI Session Key Counter Limit
Transmission Time For Relay Resistance R-APDU
For example there are two instances of the Accumulator 1 Control as follows:
 Accumulator 1 Control (Contact)
 Accumulator 1 Control (Contactless)
4.3.3. Notation for the Usage of Interface Specific

Data
Contact and contactless specific data are identified with "(Contact)" and
"(Contactless)" in their full name. However, in most of this specification, only the
generic name (i.e. the name without "(Contact)" or "(Contactless)") will be used and
the following rule applies:
Any time the name of interface specific data is used in these specifications without the
qualifier "(Contact)" or "(Contactless)", the context determines if it represents the
contact specific instance or the contactless specific instance. The context is the
interface currently active (contact or contactless).
4.4. Common Data

All persistent data objects used in these specifications and not listed in Table 4.1 are
shared between the contact and the contactless interface. There is only one instance
of those data objects, and it is used irrespective of the interface that is currently active.

Data Organization
Persistent Data
4.5. Persistent Data

M/Chip Advance uses the following persistent data objects:
Table 4.2—Persistent Data Objects
Persistent Data Objects
AC Master Key (Contact)
AC Master Key (Contactless)
AC Master Key (MAS4C)
AC Session Key Counter (Contact)
AC Session Key Counter (Contactless)
AC Session Key Counter (MAS4C)
AC Session Key Counter Limit (Contact)
AC Session Key Counter Limit (Contactless)
AC Session Key Counter Limit (MAS4C)
Accumulator 1 Amount
Accumulator 1 Control (Contact)
Accumulator 1 Control (Contactless)
Accumulator 1 Currency Code
Accumulator 1 Currency Conversion Table
Accumulator 1 CVR Dependency Data (Contact)
Accumulator 1 CVR Dependency Data (Contactless)
Accumulator 1 Lower Limit
Accumulator 1 Upper Limit
Additional Check Table
AID
Application Control (Contact)
Application Control (Contactless)
Application Cryptogram (Recovery)
Application File Locator (Contact)
Application File Locator (Contactless)
Application Interchange Profile (Contact)
Application Interchange Profile (Contactless)
Application Life Cycle Data
Application Transaction Counter
Application Transaction Counter (Recovery)
Application Transaction Counter Limit
Card Issuer Action Code (Contact) – Decline
Card Issuer Action Code (Contact) – Default

Data Organization
Persistent Data

Card Issuer Action Code (Contact) – Online
Card Issuer Action Code (Contactless) – Decline
Card Issuer Action Code (Contactless) – Default
Card Issuer Action Code (Contactless) – Online
CDA Transaction Flag (Recovery)
CDOL1 Related Data Length
Counter 1 Control (Contact)
Counter 1 Control (Contactless)
Counter 1 CVR Dependency Data (Contact)
Counter 1 CVR Dependency Data (Contactless)
Counter 1 Lower Limit
Counter 1 Number
Counter 1 Upper Limit
Counter 2 Number
CRM Country Code
Cryptogram Information Data (Recovery)
Cryptogram Version Number V2.x
CVR Issuer Discretionary Data (Contact)
CVR Issuer Discretionary Data (Contactless)
Default ARPC Response Code
Device Relay Resistance Entropy (Recovery)
File Control Information
Hash Result (Recovery)
ICC Dynamic Number Master Key (Contact)
ICC Dynamic Number Master Key (Contactless)
ICC PIN Encipherment Private Key
ICC Private Key
Interface Enabling Switch
Interface Identifier (Contact)
Interface Identifier (Contactless)
Issuer Application Data (Recovery)
IVCVC3(Track1) (Contact)
IVCVC3(Track1) (Contactless)
KDCVC3 (Contact)
KDCVC3 (Contactless)
Key Derivation Index (Contact)
Key Derivation Index (Contactless)
Key Derivation Index (MAS4C)
Last Online ATC

Data Organization
Persistent Data

Last Online Transaction Date
Length Of ICC PIN Encipherment Public Key Modulus
Length Of ICC Public Key Modulus
Linked Application Index
Log Data Table
Log Format
Max Time For Processing Relay Resistance APDU (Contact)
Max Time For Processing Relay Resistance APDU (Contactless)
Min Time For Processing Relay Resistance APDU (Contact)
Min Time For Processing Relay Resistance APDU (Contactless)
MTA Currency Code
MTA CVM (Contact)
MTA CVM (Contactless)
MTA NoCVM (Contact)
MTA NoCVM (Contactless)
Number Of Days Off Line Limit
PIN Decipherments Error Counter
PIN Decipherments Error Counter Limit
PIN Try Counter
PIN Try Limit
Previous Transaction History
Read Record Filter (Contact)
Read Record Filter (Contactless)
Reference PIN
RRP Performed Flag (Recovery)
Script Counter
Security Limits Status (Contact)
Security Limits Status (Contactless)
Security Limits Status Common
SMC Master Key (Contact)
SMC Master Key (Contactless)
SMI Master Key (Contact)
SMI Master Key (Contactless)
SMI Session Key Counter (Contact)
SMI Session Key Counter (Contactless)
SMI Session Key Counter Limit (Contact)
SMI Session Key Counter Limit (Contactless)
Terminal Relay Resistance Entropy (Recovery)
Transmission Time For Relay Resistance R-APDU (Contact)
Transmission Time For Relay Resistance R-APDU (Contactless)
Unpredictable Number (Recovery)
These persistent data objects are stored in non-volatile memory and retain value
through consecutive transactions (transactions start when the application goes to the
state selected).

Data Organization
Transient Data Objects
4.6. Transient Data Objects

As well as the persistent data, M/Chip Advance also uses transient data objects.
Transient data objects do not retain value through consecutive transactions and can be
stored in volatile memory. They are of two different kinds:
 Global transient data
 Local transient data
Global transient data objects have the following characteristics:
 Initialized to zero when the application goes from the state idle to the state
selected
 Erased when the application is unselected (state idle)
 Re-initialized to zero when the application goes to states selected and
initiated
 Values are retained from one C-APDU to the next (except for re-initialization
as mentioned above)
Local transient data objects have the following characteristics:
 Created on entry of a specific C-APDU
 Initialized to zero
 Destroyed when the C-APDU processing is complete
Global transient data objects can be seen as variables with global scope (a transaction)
while local transient data objects are variables with local scope (a C-APDU).
To be complete, it is to be noted that this specification also makes use of variables

that are local to a procedure or subroutine. Some processing is specified using
pseudo-code. Indexes in a loop for example are variables and, when used in a
subroutine, only have local scope. Those variables are only used in chapter 23 and
are self explanatory. The syntax for those variables does not follow the general rule
used for transient data as they are only local to chapter 23.

Data Organization
Transient Data
4.7. Transient Data
4.7.1. Global Transient Data

M/Chip Advance uses the following global transient data objects:
Table 4.3—Global Transient Data Objects
Global Transient Data Objects
AC Session Key
Accumulator 1 Active Flag
Amount, Authorized 1
Amount, Other 1
ATeC
Card Verification Results
CDOL1 Related Data
Counter 1 Active Flag
Current Date In Days
CVM Results
Data Authentication Code
Device Relay Resistance Entropy
First AC
Get Challenge Flag
ICC Dynamic Number
ICC Unpredictable Number
Internal Authentication Performed Flag
Issuer Updates Data
Issuer Updates Received Flag
Merchant Custom Data
Offline Change PIN Status
PDOL Values
PIN Verification Status
Rand
Recover AC Performed Flag
RRP Counter
Script Failed Flag
SMC CSK Key Present Flag
SMC Session Key
SMI CSK Key Present Flag
SMI Session Key
Terminal Country Code
Terminal Relay Resistance Entropy
Transaction Currency Code
Transaction Date
Transaction Time
Transaction Type

Data Organization
Transient Data
4.7.2. Local Transient Data

M/Chip Advance uses the following local transient data objects:
Table 4.4—Local Transient Data Objects
Local Transient Data Objects
Accumulator 1 Lower Limit Temp
Accumulator 1 Upper Limit Temp
Amount, Authorized (Numeric)
Amount, Other (Numeric)
Application Cryptogram
ARPC Response Code
Authorisation Response Code
CDOL2 Related Data
Counter 1 Lower Limit Temp
Counter 1 Number Temp
Counter 1 Upper Limit Temp
Cryptogram Information Data
Cryptogram Version Number
CVC3(Track1)
CVC3(Track2)
CVR V2.05
CVR V2.1/V2.2
CVR V1.1/V1.3
DAC/ICC Dyn Nr
DDOL Related Data
Dynamic Application Data To Be Signed
Enciphered New PIN Block
Hash Result
ICC Dynamic Data
ICC Dynamic Number (Terminal)
Issuer Application Data
Issuer Application Data V2.05
Issuer Application Data V2.1/V2.2
Issuer Authentication Data
Linked Application Data
MAC
New Data Value
New PIN Block
New Record Value
New SMI Key Flag

Data Organization
Transient Data
Local Transient Data Objects

Offline Accumulator Balance 1
Offline Counter Balance 1
PDOL Related Data
PIN Related Data
Plaintext/Encrypted Counters
Record Number
Recovered Data
Reference Control Parameter
Relay Resistance Related Data
Return Value
Signed Dynamic Application Data
Temp Transaction Log Record
Terminal Type
Terminal Verification Results
Transaction Related Data
Unpredictable Number
Unpredictable Number (Numeric)
The usage of the local transient data by command is given in the chapters specifying
the commands.

Data Organization
Personalization
4.8. Personalization
The data objects listed in Table 4.5 can be personalized. When a range is given in the
"Length" column, the M/Chip Advance application must accept personalization values
with any size in this range, unless otherwise stated in this section.
Table 4.5—Personalization Data Objects
Data Object Length (in
bytes)
AC Master Key (Contact) 16
AC Master Key (Contactless) 16
AC Master Key (MAS4C) 16
AC Session Key Counter Limit (Contact) 2
AC Session Key Counter Limit (Contactless) 2
AC Session Key Counter Limit (MAS4C) 2
Accumulator 1 Control (Contact) 1
Accumulator 1 Control (Contactless) 1
Accumulator 1 Currency Code 2
Accumulator 1 Currency Conversion Table 25
Accumulator 1 CVR Dependency Data (Contact) 3
Accumulator 1 CVR Dependency Data (Contactless) 3
Accumulator 1 Lower Limit 6
Accumulator 1 Upper Limit 6
Accumulator 2 Control (Contact) 1
Accumulator 2 Control (Contactless) 1
Accumulator 2 Currency Code 2
Accumulator 2 Currency Conversion Table 25
Accumulator 2 CVR Dependency Data (Contact) 3
Accumulator 2 CVR Dependency Data (Contactless) 3
Accumulator 2 Lower Limit 6
Accumulator 2 Upper Limit 6
Additional Check Table 18
AID Variable, 5–16
Application Control (Contact) 6
Application Control (Contactless) 6
Application File Locator (Contact) Variable
Application File Locator (Contactless) Variable
Application Interchange Profile (Contact) 2
Application Interchange Profile (Contactless) 2
Application Life Cycle Data 48, see below
Application Transaction Counter Limit 2
Card Issuer Action Code (Contact) – Decline 3
Card Issuer Action Code (Contact) – Default 3
Card Issuer Action Code (Contact) – Online 3
Card Issuer Action Code (Contactless) – Decline 3
Card Issuer Action Code (Contactless) – Default 3
Card Issuer Action Code (Contactless) – Online 3

Data Organization
Personalization

bytes)
CDOL1 Related Data Length 1
Counter 1 Control (Contact) 1
Counter 1 Control (Contactless) 1
Counter 1 CVR Dependency Data (Contact) 3
Counter 1 CVR Dependency Data (Contactless) 3
Counter 1 Lower Limit 1
Counter 1 Upper Limit 1
Counter 2 Control (Contact) 1
Counter 2 Control (Contactless) 1
Counter 2 CVR Dependency Data (Contact) 3
Counter 2 CVR Dependency Data (Contactless) 3
Counter 2 Lower Limit 1
Counter 2 Upper Limit 1
CRM Country Code 2
Cryptogram Version Number V2.x 1
CVR Issuer Discretionary Data (Contact) 1
CVR Issuer Discretionary Data (Contactless) 1
Default ARPC Response Code 2
File Control Information Variable, 10–
252
ICC Dynamic Number Master Key (Contact) 16
ICC Dynamic Number Master Key (Contactless) 16
ICC PIN Encipherment Private Key Implementation
specific
ICC Private Key Implementation
specific
Interface Enabling Switch 1
Interface Identifier (Contact) 1
Interface Identifier (Contactless) 1
IVCVC3(Track1) (Contact) 2
IVCVC3(Track1) (Contactless) 2
IVCVC3(Track2) (Contact) 2
IVCVC3(Track2) (Contactless) 2
KDCVC3 (Contact) 16
KDCVC3 (Contactless) 16
Key Derivation Index (Contact) 1
Key Derivation Index (Contactless) 1
Key Derivation Index (MAS4C) 1
Last Online Transaction Date 2
Length Of ICC PIN Encipherment Public Key Modulus 1
Length Of ICC Public Key Modulus 1
Linked Application Index 1
Log Data Table 9
Log Format Variable
Max Time For Processing Relay Resistance APDU (Contact) 2
Max Time For Processing Relay Resistance APDU (Contactless) 2

Data Organization
Personalization

bytes)
Min Time For Processing Relay Resistance APDU (Contact) 2
Min Time For Processing Relay Resistance APDU (Contactless) 2
MTA Currency Code 2
MTA CVM (Contact) 6
MTA CVM (Contactless) 6
MTA NoCVM (Contact) 6
MTA NoCVM (Contactless) 6
Number Of Days Off Line Limit 2
PIN Decipherments Error Counter Limit 2
PIN Try Counter 1
PIN Try Limit 1
Previous Transaction History 1
Read Record Filter (Contact) Variable
Read Record Filter (Contactless) Variable
Reference PIN 8
SMC Master Key (Contact) 16
SMC Master Key (Contactless) 16
SMI Master Key (Contact) 16
SMI Master Key (Contactless) 16
SMI Session Key Counter Limit (Contact) 2
SMI Session Key Counter Limit (Contactless) 2
Transmission Time For Relay Resistance R-APDU (Contact) 2
Transmission Time For Relay Resistance R-APDU (Contactless) 2
Only parts of the Application Life Cycle Data are personalized. The personalization
requirements are as follows:
Table 4.6—Application Life Cycle Data Personalization Requirements
Field Personalizable
'Version Number' Optional
'Type Approval ID' Optional
'Application Issuer ID' Mandatory
'Application Code ID' Not allowed
It is up to the implementation to allow personalization of the optional fields.

Data Organization
Initialized Data
4.9. Initialized Data

The following data objects are not personalized but have a fixed initial value:
Table 4.7—Initialized Data Objects
Data Object Length Value
AC Session Key Counter (Contact) 2 '0000'
AC Session Key Counter (Contactless) 2 '0000'
AC Session Key Counter (MAS4C) 2 '0000'
Accumulator 1 Amount 6 '000000000000'
Accumulator 2 Amount 6 '000000000000'
Application Transaction Counter 2 '0000'
Application Transaction Counter (Recovery) 2 '0000'
CDA Transaction Flag (Recovery) 1 bit 0b
Counter 1 Number 1 '00'
Counter 2 Number 1 '00'
Cryptogram Information Data (Recovery) 1 '00'
Hash Result (Recovery) 20 '00…00'
Issuer Application Data (Recovery) 28 '00…00'
Last Online ATC 2 '0000'
PIN Decipherments Error Counter 2 '0000'
RRP Performed Flag (Recovery) 1 '00'
Script Counter 1 '00'
SMI Session Key Counter (Contact) 2 '0000'
SMI Session Key Counter (Contactless) 2 '0000'
Security Limits Status (Contact) 1 '00'
Security Limits Status (Contactless) 1 '00'
Security Limits Status Common 1 '00'
Unpredictable Number (Recovery) 4 '00000000'

Data Organization
Files
4.10. Files
4.10.1. SFI in the Range 1 to 10

The persistent data objects stored in files with an SFI in the range 1 to 10 are stored in
records and are retrievable with the READ RECORD command, as specified in
chapter 19. These records are also updateable with the UPDATE RECORD
command, as specified in chapter 21.
M/Chip Advance does not interpret the data objects stored in these records. Instead, it
interprets the record itself (e.g. to build the response message to the READ
RECORD). These data objects are neither retrievable with the GET DATA command
nor updateable with the PUT DATA command. Therefore, for the implementation,
only references to records are needed.
When the card is issued, an area of memory is reserved for each record. The reserved
length for a record represents the size allocated to a record and is greater than or equal
to the size needed for personalization of the record. The reserved length for a record
may vary between records. The reserved length for each record is a record attribute
that is not modified by the UPDATE RECORD command. The memory allocated to a
record remains available to store a new value using the UPDATE RECORD
command. The method for reserving the length for a record is beyond the scope of
this specification and is left to the implementation.
If the length of the new value for a record is less than or equal to the reserved length
for a record, the UPDATE RECORD replaces the current record with a new record,
even if the actual size of those records differ. Partial update of a record is not
supported. The length of the record data is updated with the length of the new data,
but the reserved length for the record has not changed. The new record value is the
value that would be returned in response to the READ RECORD command.
Since the application does not interpret the value of records, it is the responsibility of
the issuer to correctly format the record values:
 At personalization
 When generating the data for the UPDATE RECORD command
Constraints on the records are as follows:

 The maximum record length is platform-dependent but must be greater than,
or equal to, 247 bytes.
 The memory reserved for a record at personalization or pre-personalization
must be available for update. For example, if 100 bytes were reserved for a
record at personalization, the UPDATE RECORD must allow the storage of
100 bytes or less in this record. The dynamic allocation of memory for records
(i.e. the UPDATE RECORD allows the storage of more bytes than those
reserved at personalization), is allowed but is not mandatory.
 At a minimum, M/Chip Advance must support up to 3K (3072) bytes of
memory to store EMV records.

Data Organization
Files
 It is an issuer option to store the EMV records in any file with an SFI between
1 and 10 (for example, records may be stored in SFI 1 and 2; or in SFI 1, 3,
and 4; or in SFI 5, 6, 8, 9).
 At a minimum, M/Chip Advance must support up to a total of 16 records for
EMV data.
 It is an issuer option to place up to 16 records in any file with SFI between 1
and 10.
4.10.2. Transaction Log File

M/Chip Advance uses a payment system specific file - Transaction Log File – to store
information about recent transactions. The SFI for the Transaction Log File is 11.
At a minimum, the Transaction Log File contains records for at least ten Transaction
Log Records. It is left to the implementation to extend the number of records in the
Transaction Log File.
The records in the Transaction Log File can be retrieved by a terminal using the
READ RECORD command.
The fixed part of the Transaction Log Record is the concatenation of the data objects
listed in Table 4.8.
Table 4.8—Fixed Part of Transaction Log Record
Data Object Length
Cryptogram Information Data 1
Amount, Authorized (Numeric) 6
Transaction Currency Code 2
Transaction Date 3
Application Transaction Counter 2
Card Verification Results 6
Interface Identifier 1
Transaction Time 3
Merchant Custom Data 20
M/Chip Advance allows the Transaction Log Record to be extended by means of the
Log Data Table. The Log Data Table provides information to extend the Transaction
Log Record with terminal sourced data provided to the card in the first GENERATE
AC command data.
The Log Data Table is the concatenation (without TLV coding) of the data objects
identified in Table 4.9.

Data Organization
Files
Table 4.9—Format of Log Data Table

Data Object Length Description
Count Of Data Entries 1 The number of the following data
entries that are logged at the end of the
Transaction Log Record.
Data Entry 1 2 The position and length of the 1st block
of additional terminal sourced log data
in the 1st GENERATE AC command
data field.
…
Data Entry n 2 The position and length of the nth block
of additional terminal sourced log data
in the 1st GENERATE AC command
data.
Padding 8 – 2*n 'FF … FF'
Where Data Entry x is formatted as the concatenation of:

 Data Position x (Byte 1): the position of the xth block of additional terminal
sourced log data in the 1st GENERATE AC command data field. The position
of the first byte is 1.
 Data Length x (Byte 2): the length (in bytes) of the xth block of additional
terminal sourced log data in the 1st GENERATE AC command data field.
The maximum number of data entries (n) is 4. The total length of the additional
transaction log data must be less than or equal to 32 bytes.
The additional data is stored at the end of the fixed part of the Transaction Log
Record as shown in Table 4.10.
Table 4.10—Transaction Log Record with Additional Info
Data Object Length
Transaction Date 3
Transaction Time 3
Additional info Var.
No padding is allowed in a Transaction Log Record and the size of the additional info
retrieved when reading the record corresponds to the data written by the
AddAdditionalLogInfo( ) subroutine.

Data Organization
Files
The Log Data Table, the Log Format and the Transaction Log File are common for
the contact and contactless interface. Therefore, the records in the Transaction Log
File generated by contact transactions have the same length and content as records
generated during contactless transactions.
Table 4.11 provides the relationship between the Record Number in P1 of the READ
RECORD command and the Transaction Log Record in the response to the READ
RECORD command.
Table 4.11—Correspondence between Record Number and Transaction Log
Record
Record Number Transaction Log
1 Last Transaction Log Record
2 Last but one Transaction Log Record
3 Last but two Transaction Log Record
… …
If in its lifetime M/Chip Advance has not logged at least one transaction for each record in the
Transaction Log File, some of the entries in the Transaction Log File do not represent
transactions, but are empty. These empty entries are not retrievable with the READ
RECORD command. The actual implementation approach is the decision of the card
application developer. This requirement is also applicable to logs with more than ten
entries.
A Transaction Log Record may be written in the Transaction Log File during the 1st
and 2nd GENERATE AC commands. The conditions whether to log a transaction, are
defined by the personalization of the Application Control (Contact) and Application
Control (Contactless).
During the 1st GENERATE AC command a new Transaction Log Record is added to
the Transaction Log File when the 1st GENERATE AC command completes with a
TC and 'TC Logging' in Application Control is set or the 1st GENERATE AC
command completes with an AAC and 'AAC Logging' in Application Control is set.
If the 'ARQC Pre-logging' in Application Control is set, then a Transaction Log
Record is added also to the Transaction Log File in case of an ARQC.
If all entries in the Transaction Log File are occupied, M/Chip Advance overwrites the
oldest entry. The method for achieving this is left to the implementation.
During the 2nd GENERATE AC command a transaction is logged when the 2nd
GENERATE AC command completes with a TC and 'TC Logging' in Application
Control is set or the 2nd GENERATE AC command completes with an AAC and
'AAC Logging' in Application Control is set.
When a transaction is logged during the 2nd GENERATE AC command, a new
Transaction Log Record is added to the Transaction Log File when the 'ARQC Pre-
logging' in Application Control is not set. If the 'ARQC Pre-logging' in Application
Control is set, then the most recent Transaction Log Record is overwritten (this is the
record written during the 1st GENERATE AC command).
The method for achieving this is left to the implementation.

Data Organization
Files
4.10.3. Other Files

Files with SFI in the range from 11 to 30 other than the Transaction Log File are out
of scope for this specification.

Application Block
5. Application Block
5.1. Application Block Command Message ....................................................... 69
5.3. Application Block Processing ...................................................................... 70

Application Block
Application Block Command Message
5.1. Application Block Command Message

The APPLICATION BLOCK command message is specified in Table 5.1.
Table 5.1—Application Block Command Message
Code Value
CLA '84'
INS '1E'
P1 '00'
P2 '00'
Lc '08'
Data MAC
Le Not present
5.2. Local Transient Data

This command uses the following local transient data:
Table 5.2—Local Transient Data for Application Block
MAC
New SMI Key Flag

Application Block
Application Block Processing
5.3. Application Block Processing

The symbols in the diagram are labeled AB.x.
AB
APPLICATION BLOCK

Flag
2 3
Build response
P1-P2 NOK
SW12 = '6A86'
OK
4 5
Build response
Lc NOK
SW12 = '6700'
OK
6
7
Script Failed Flag Yes
Build response
set? SW12 = '6982'
No
8
Set Script Received in
PTH

Application Block
AB
9 11
Set SMI Session Key Counter
CTRSMI < LIMSMI No Limit Exceeded in Security
Limits Status
12
Yes
10 Set Script Failed in PTH
Retrieve MAC
13
Set Script Failed Flag
14
2 Build response
SW12 = '6985'
15
Commit persistent data

Application Block
AB
16
Session Key
EMV CSK MasterCard Proprietary
Derivation
method
17
SMI CSK
No
key present?
19 22
Increment CTRSMI Increment CTRSMI

Yes
18 20 23
Derive SMI Session
New SMI Key Flag = 0 Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
21 24
SMI CSK Key Present SMI CSK Key Present
Flag = 1 Flag = 0
New SMI Key Flag = 1 New SMI Key Flag = 1

Application Block
AB
27
25
Verify NOK
Set Script Failed in
MAC PTH
OK 28
26 Set Script Failed Flag
New SMI Key

Flag = 1? 29
Build response
SW12 = '6982'
No
Yes
31 30
Commit persistent
Decrement CTRSMI data
32
Set Application
Blocked in PTH
33
Increment Script
Counter

Application Block
AB
34
Increment Rand
35
Build response
SW12 = '9000'
36
Commit persistent
data

Application Block
AB.1
Challenge Flag
AB.2
IF P1|P2 = '0000'
THEN
GOTO AB.4
ELSE
GOTO AB.3
ENDIF
AB.3
Build R-APDU consisting of SW12 equal to '6A86'.
AB.4
IF Lc = '08'
THEN
GOTO AB.6
ELSE
GOTO AB.5
ENDIF
AB.5
Build R-APDU consisting of SW12 equal to '6700'.
AB.6
IF Script Failed Flag is set
THEN
GOTO AB.7
ELSE
GOTO AB.8
ENDIF
AB.7
AB.8
Set 'Script Received' in Previous Transaction History (do not commit)
AB.9
IF SMI Session Key Counter < SMI Session Key Counter Limit
THEN
GOTO AB.10
ELSE
GOTO AB.11
ENDIF
AB.10
Retrieve MAC from the APPLICATION BLOCK command message.

Application Block
AB.11
Set 'SMI Session Key Counter Limit Exceeded' in Security Limits Status
AB.12
Set 'Script Failed' in Previous Transaction History (do not commit)
AB.13
AB.14
AB.15
Commit the persistent data objects, that have a new value assigned but that have not
yet been committed, in one atomic operation.
Implementations have the freedom to choose the optimal method through which this
goal is achieved, depending on their card operating system and application
characteristics.
AB.16
IF 'Session Key Derivation' in Application Control = EMV CSK
THEN
GOTO AB.17
ELSE
GOTO AB.22
ENDIF
AB.17
IF SMI CSK Key Present Flag is set
THEN
GOTO AB.18
ELSE
GOTO AB.19
ENDIF
AB.18
Clear New SMI Key Flag
AB.19
SMI Session Key Counter := SMI Session Key Counter + 1
AB.20
Derive new SMI Session Key according to the EMV CSK method.
Refer to [SECURITY] for details.
AB.21
Set SMI CSK Key Present Flag
Set New SMI Key Flag
AB.22

Application Block
AB.23
Derive new SMI Session Key according to the MasterCard Proprietary SKD method.
AB.24
Clear SMI CSK Key Present Flag
AB.25
Verify MAC on the APPLICATION BLOCK command.
IF MAC is correct
THEN
GOTO AB.26
ELSE
GOTO AB.27
ENDIF
AB.26
IF New SMI Key Flag is set
THEN
GOTO AB.31
ELSE
GOTO AB.32
ENDIF
AB.27
AB.28
AB.29
AB.30
characteristics.
AB.31
SMI Session Key Counter := SMI Session Key Counter – 1
AB.32
Set 'Application Blocked' in Previous Transaction History (do not commit)

Application Block
AB.33
IF 'Script Counter' in Script Counter = 'F'
THEN
'Script Counter' in Script Counter := '0' (do not commit)
ELSE
'Script Counter' in Script Counter := 'Script Counter' in Script Counter + 1 (do not
commit)
ENDIF
AB.34
IF Rand = 'FFFFFFFFFFFFFFFF'
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
Rand is used for the verification of the MAC. In preparation of the next script
command (if any), Rand is incremented at this stage.
AB.35
AB.36
characteristics.

Application Unblock
6. Application Unblock
6.1. Application Unblock Command Message ................................................... 80
6.3. Application Unblock Processing.................................................................. 81

Application Unblock
Application Unblock Command Message
6.1. Application Unblock Command Message

The APPLICATION UNBLOCK command message is specified in Table 6.1.
Table 6.1—Application Unblock Command Message
Code Value
CLA '84'
INS '18'
P1 '00'
P2 '00'
Lc '08'
Data MAC
Le Not present

Table 6.2—Local Transient Data for Application Unblock
MAC
New SMI Key Flag

Application Unblock
Application Unblock Processing
6.3. Application Unblock Processing

The symbols in the diagram are labeled AU.x.
AU
APPLICATION UNBLOCK

Flag
2 3
Build response
P1-P2 NOK
SW12 = '6A86'
OK
4 5
Build response
Lc NOK
SW12 = '6700'
OK
6
7
Script Failed Flag Yes
Build response
set? SW12 = '6982'
No
8
Set Script Received in
PTH

Application Unblock
AU
9 11
Limits Status
12
Yes
Retrieve MAC
13
14
2 Build response
SW12 = '6985'
15

Application Unblock
AU
16
Session Key
Derivation
method
17
SMI CSK
No
key present?
19 22

Yes
18 20 23
Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
21 24
Flag = 1 Flag = 0

Application Unblock
AU
27
25
Verify NOK
MAC PTH
OK 28
New SMI Key

Flag = 1? 29
Build response
SW12 = '6982'
No
Yes
31 30
Commit persistent
Decrement CTRSMI data
32
Clear Application
Blocked in PTH
33
Increment Script
Counter

Application Unblock
AU
34
Increment Rand
35
Build response
SW12 = '9000'
36
Commit persistent
data

Application Unblock
AU.1
Challenge Flag
AU.2
IF P1|P2 = '0000'
THEN
GOTO AU.4
ELSE
GOTO AU.3
ENDIF
AU.3
AU.4
IF Lc = '08'
THEN
GOTO AU.6
ELSE
GOTO AU.5
ENDIF
AU.5
AU.6
THEN
GOTO AU.7
ELSE
GOTO AU.8
ENDIF
AU.7
AU.8
AU.9
THEN
GOTO AU.10
ELSE
GOTO AU.11
ENDIF
AU.10
Retrieve MAC from the APPLICATION UNBLOCK command message.

Application Unblock
AU.11
AU.12
AU.13
AU.14
AU.15
characteristics.
AU.16
THEN
GOTO AU.17
ELSE
GOTO AU.22
ENDIF
AU.17
THEN
GOTO AU.18
ELSE
GOTO AU.19
ENDIF
AU.18
AU.19
AU.20
AU.21
AU.22

Application Unblock
AU.23
AU.24
AU.25
Verify MAC on the APPLICATION UNBLOCK command.
IF MAC is correct
THEN
GOTO AU.26
ELSE
GOTO AU.27
ENDIF
AU.26
THEN
GOTO AU.31
ELSE
GOTO AU.32
ENDIF
AU.27
AU.28
AU.29
AU.30
characteristics.
AU.31
AU.32
Clear 'Application Blocked' in Previous Transaction History (do not commit)

Application Unblock
AU.33
THEN
ELSE
commit)
ENDIF
AU.34
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
AU.35
AU.36
characteristics.

Compute Cryptographic Checksum
7. Compute Cryptographic
Checksum
7.1. Compute Cryptographic Checksum Command Message ............................ 91
7.3. Compute Cryptographic Checksum Processing........................................... 92

Compute Cryptographic Checksum Command Message
7.1. Compute Cryptographic Checksum

Command Message
The COMPUTE CRYPTOGRAPHIC CHECKSUM command message is specified in
Table 7.1.
Table 7.1—Compute Cryptographic Checksum Command Message
Code Value
CLA '80'
INS '2A'
P1 '8E'
P2 '80'
Lc '04'
Data Unpredictable Number (Numeric)
Le '00'

Table 7.2—Local Transient Data for Compute Cryptographic Checksum
CVC3(Track1)
CVC3(Track2)

Compute Cryptographic Checksum Processing
7.3. Compute Cryptographic Checksum

Processing
The symbols in the diagram are labeled CCC.x.
CCC
COMPUTE CRYPTOGRAPHIC
CHECKSUM

Flag
2 3
Build response
P1-P2 NOK
SW12 = '6A86'
OK
4
5
Build response
Lc = 4? NOK
SW12 = '6700'
OK
6 7
Build response
Blocked? Yes
SW12 = '6985'
No

CCC
8 9
CCC command No
Build response
supported? SW12 = '6985'
Yes
10
Generate
CVC3(track 1)
11
Generate
CVC3(track 2)
12
Build response
SW12 = '9000'

CCC.1
Challenge Flag
CCC.2
IF P1|P2 = '8E80'
THEN
GOTO CCC.4
ELSE
GOTO CCC.3
ENDIF
CCC.3
CCC.4
IF Lc = '04'
THEN
GOTO CCC.6
ELSE
GOTO CCC.5
ENDIF
CCC.5
CCC.6
THEN
GOTO CCC.7
ELSE
GOTO CCC.8
ENDIF
CCC.7
CCC.8
IF 'Compute Cryptographic Checksum' in Application Control = Compute
Cryptographic Checksum Supported
THEN
GOTO CCC.10
ELSE
GOTO CCC.9
ENDIF
CCC.9

CCC.10
Generate CVC3(Track1) using the input data listed in Table 7.3.
Table 7.3—Input Data for CVC3(Track1) Generation
Data Object Length
IVCVC3(Track1) 2 bytes
Unpredictable Number (Numeric) 4 bytes
Application Transaction Counter 2 bytes
CCC.11
Generate CVC3(Track2) using the input data listed in Table 7.4.
Table 7.4—Input Data for CVC3(Track2) Generation
Data Object Length
IVCVC3(Track2) 2 bytes
Unpredictable Number (Numeric) 4 bytes
Application Transaction Counter 2 bytes
CCC.12
The response message is an EMV Format 2 constructed data object with tag equal to
'77' containing the TLV coded data objects specified in Table 7.5 followed by SW12
equal to '9000'.
Table 7.5—Compute Cryptographic Checksum Response Message Template
Tag Length Value
'9F61' 2 CVC3(Track2)
'9F60' 2 CVC3(Track1)
'9F36' 2 Application Transaction Counter

Exchange Relay Resistance Data
8. Exchange Relay Resistance

Data
8.1. Exchange Relay Resistance Data Command Message ................................ 97
8.3. Exchange Relay Resistance Data Processing .............................................. 98

Exchange Relay Resistance Data Command Message
8.1. Exchange Relay Resistance Data

Command Message
The EXCHANGE RELAY RESISTANCE DATA command message is specified in
Table 8.1.
Table 8.1—Exchange Relay Resistance Data Command Message
Code Value
CLA '80'
INS 'EA'
P1 '00'
P2 '00'
Lc '04'
Data Relay Resistance Related Data
Le '00'

Table 8.2—Local Transient Data for Exchange Relay Resistance Data

Exchange Relay Resistance Data Processing
8.3. Exchange Relay Resistance Data

Processing
The symbols in this diagram are labeled RRP.x.
RRP
EXCHANGE RELAY
RESISTANCE DATA
1
Flag
2 5
Build response
P1-P2 = '0000' No
SW12 = '6A86'
Yes
3 6
Build response
Lc = '04' No
SW12 = '6700'
Yes
RRP Counter >= 3 or

Internal authentication Yes
performed?
7
Build response
No SW12 = '6985'

RRP
Retrieve Relay Resistance

Related Data
RRP Counter :=
RRP Counter + 1
10
Set Device Relay

Resistance Entropy
11
Build response
SW12 = '9000'

RRP.1
Challenge Flag
RRP.2
IF P1|P2 = '0000'
THEN
GOTO RRP.3
ELSE
GOTO RRP.5
ENDIF
RRP.3
IF Lc = '04'
THEN
GOTO RRP.4
ELSE
GOTO RRP.6
ENDIF
RRP.4
IF RRP Counter ≥ '03' OR Internal Authentication Performed Flag is set
THEN
GOTO RRP.7
ELSE
GOTO RRP.8
ENDIF
RRP.5
RRP.6
RRP.7
RRP.8
Retrieve and save the following information from the EXCHANGE RELAY
RESISTANCE DATA command message:
Terminal Relay Resistance Entropy := Relay Resistance Related Data
RRP.9
RRP Counter := RRP Counter + 1
RRP.10
Copy 4 bytes of the ICC Dynamic Number into Device Relay Resistance Entropy:
Device Relay Resistance Entropy := ICC Dynamic Number[(4xRRP Counter)-3 :
4xRRP Counter]

RRP.11
Build the response.
The data object returned in the response message is a primitive data object with tag
'80' and length '0A' followed by SW12 equal to '9000'. The value field consists of the
concatenation without delimiters (tag and length) of the value fields of the data
objects specified in Table 8.3.
Table 8.3—Exchange Relay Resistance Data Response
Byte Value
1-4 Device Relay Resistance Entropy
5-6 Min Time For Processing Relay Resistance APDU
7-8 Max Time For Processing Relay Resistance APDU
9-10 Transmission Time For Relay Resistance R-APDU

First Generate AC
9. First Generate AC
9.1. First Generate AC Command Message...................................................... 103
9.3. First Generate AC Processing .................................................................... 105
9.3.1. Start .................................................................................................... 105
9.3.2. ARQC Requested ............................................................................... 127
9.3.3. TC Requested ..................................................................................... 132
9.3.4. AAC Decided ..................................................................................... 138
9.3.5. TC Decided ........................................................................................ 143
9.3.6. ARQC Decided .................................................................................. 148
9.3.9. No CDA - V2.1/V2.2 Host Backwards Compatibility ...................... 168
9.3.11. MAS4C .............................................................................................. 174

First Generate AC
First Generate AC Command Message
9.1. First Generate AC Command Message

The first GENERATE AC command message is specified in Table 9.1.
Table 9.1—First Generate AC Command Message
Code Value
CLA '80'
INS 'AE'
P1 Reference Control Parameter
P2 '00'
Lc Variable.
Data Transaction Related Data
Le '00'
Table 9.2 specifies the coding of the Reference Control Parameter.

Table 9.2—Reference Control Parameter Coding for First Generate AC
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
x x 'Cryptogram Type'
0 0 AAC
0 1 TC
1 0 ARQC
1 1 RFU
0 Other values RFU
x 'Combined DDA/AC Generation Requested'
0 0 0 0 Other values RFU

Table 9.3—Local Transient Data for First Generate AC
CVR V2.05
CVR V2.1/V2.2
CVR V1.1/V1.3
DAC/ICC Dyn Nr
Hash Result

First Generate AC
Local Transient Data
ICC Dynamic Data

Return Value
Terminal Type

First Generate AC
First Generate AC Processing
9.3. First Generate AC Processing
9.3.1. Start
Symbols in this diagram are labeled 1G.1.x.
1G.1
1st GENERATE AC

Flag
3 2
Build response NOK P1-P2
SW12 = '6A86'
OK
5
4
Build response NOK Lc
SW12 = '6700'
OK
6
Retreive transaction
related data from C-
APDU

First Generate AC
1G.1
1
14
No MAS4C?
Yes
15
Term
No Type = '34' AND
ATeC = '0000' ?
7
Yes
CTRAC ≥ Yes
LIMAC ?
No
8 10
Set AC Session Key Counter
Error Limit Exceeded in Increment CTRAC
9
Build response
SW12 = '6985'
2 MAS4C

First Generate AC
1G.1
2
11
Session Key
Derivation
MasterCard Proprietary EMV CSK
12 13
Derive AC Session
Derive AC Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
16
Acc 1 Temp = Acc 1
Acc 2 Temp = Acc 2
Cntr 1 Ttemp = Cntr 1
Cntr 2 Temp = Cntr 2
17
Amount Authorized 1 =
Amount Authorized
Amount Other 1 = Amount Other

First Generate AC
1G.1
18
Copy PIN
information to CVR
19
Copy Script Counter to
CVR
20
Copy PIN Try Counter
to CVR
21 22
Compare Terminal Set Terminal

PIN and Application NOK Erroneously Considers
PIN results Offline PIN OK in CVR
OK

First Generate AC
1G.1
4
23 24
Set PTL Exceeded in
PTC = 0 ? Yes
CVR
No
25
Domestic or Domestic
International?
international
27 26
Set International Set Domestic
Transaction in CVR Transaction in CVR
28
Copy Go Online On
Next Transaction from
PTH to CVR
29
Copy Issuer
Authentication Failed
from PTH to CVR
30
Copy Script Received
from PTH to CVR

First Generate AC
1G.1
5
31
Copy Script Failed from
PTH to CVR
32
Copy Last Online
Transaction Not Completed
from PTH to CVR
33
Copy Issuer Discretionary

data to CVR
34
Additional
Check Table is No
active?
Yes
35
Process Additional Check

Table
36
Check limits against all
Temp Accs and Cntrs
Set bits in CVR

First Generate AC
1G.1
6
37
No MTA Activated?
Yes
38
MTA
No Currency Code = Txn Currency
Code?
Yes
39
Check for CVM
transaction
40
Yes
CVM No
transaction?
41 42
Amount Amount
No Authorized > Authroized >
No
MTA CVM? MTA NoCVM?
Yes
Yes
43
Set MTA Limit Exceeded
in CVR

First Generate AC
1G.1
44
Max number
No of days offline
activated?
Yes
45
Check format of
Transaction Date
46
Format of NOK
Transaction Date
OK 47
Convert date in to
number of days
48 49
Current Date
Set Date Check Failed
+1 >= Last Online Txn No
in CVR
Date ?
Yes
50 51
Current Date
Set Number Of Days
– Last Online Txn Date Yes Offline Limit Exceeded
> Number Of Days
in CVR
Offline Limit?
No

First Generate AC
1G.1
8
52 53
Internal Auth. Yes
Set DDA Returned
Performed? in CVR
No
70
RRP Yes
Performed?
71
Unpredictable
Number = Terminal No
No Relay Resistance
Entropy
Yes
72
Relay
resistance is performed No
in Terminal Verification
Results?
Yes
73
Decline if
RRP performed
Do not decline
and Combined DDA/AC
not requested
Decline
AAC
9 dec

First Generate AC
1G.1
54
Application Yes
blocked ?
No
55
No
Offline PIN Yes
successful?
11 10 AAC
dec

First Generate AC
1G.1
10
58
56 57
Clear Upper and Lower
Offline PIN Clear Acc 1 and
Yes Cumulative Acc 1 Limit
reset Acc 1? Acc 1 Temp
Exceeded in CVR
No
61
59 60
Offline PIN Clear Acc 2 and
Yes Cumulative Acc 2 Limit
reset Acc 2? Acc 2 Temp
Exceeded in CVR
No
64
62 63
Offline PIN Clear Cntr 1 and
Yes Consecutive Cntr 1
reset Cntr 1? Cntr 1 Temp
Limit Exceeded in CVR
No
66 67
65
Offline PIN Clear Cntr 2 and
Yes Consecutive Cntr 2
reset Cntr 2? Cntr 2 Temp
Limit Exceeded in CVR
No
11

First Generate AC
1G.1
11
68
AAC
Cryptogram TC
requested
ARQC
AAC ARQC TC
dec req req

First Generate AC
1G.1.1
Challenge Flag
1G.1.2
IF 'Cryptogram Type' in Reference Control Parameter = RFU OR P2 ≠ '00'
THEN
GOTO 1G.1.3
ELSE
GOTO 1G.1.4
ENDIF
1G.1.3
1G.1.4
IF 'Use M/Chip 4 CDOL1' in Application Control is not set
THEN
IF (Lc >= 66) AND (Lc = CDOL1 Related Data Length)
THEN
GOTO 1G.1.6
ELSE
GOTO 1G.1.5
ENDIF
ELSE
IF (Lc >= 43) AND (Lc = CDOL1 Related Data Length)
THEN
GOTO 1G.1.6
ELSE
GOTO 1G.1.5
ENDIF
ENDIF
1G.1.5
1G.1.6
The transaction-related transient data objects are filled with the values given in the
Transaction Related Data:
CDOL1 Related Data := Transaction Related Data[1 : CDOL1 Related data Length]
Amount, Authorized (Numeric) := Transaction Related Data[1 : 6]
Amount, Other (Numeric) := Transaction Related Data[7 : 12]
Terminal Country Code := Transaction Related Data[13 : 14]
Terminal Verification Results := Transaction Related Data[15 : 19]
Transaction Currency Code := Transaction Related Data[20 : 21]
Transaction Date := Transaction Related Data[22 : 24]
Transaction Type := Transaction Related Data[25]
Unpredictable Number := Transaction Related Data[26 : 29]
Terminal Type := Transaction Related Data[30]

First Generate AC
Data Authentication Code := Transaction Related Data[31 : 32]

ICC Dynamic Number (Terminal) := Transaction Related Data[33 : 40]
CVM Results := Transaction Related Data[41 : 43]
IF 'Use M/Chip 4 CDOL1' in Application Control is not set
THEN
Transaction Time := Transaction Related Data[44 : 46]
Merchant Custom Data := Transaction Related Data[47 : 66]
ELSE
Transaction Time := '000000'
Merchant Custom Data := '0000000000000000000000000000000000000000'
ENDIF
1G.1.14
IF 'MAS4C Processing Flow' in Application Control is set
THEN
GOTO 1G.1.15
ELSE
GOTO 1G.1.7
ENDIF
1G.1.15
IF Terminal Type = '34' AND ATeC = '0000'
THEN
GOTO 1G.11.13 (MAS4C)
ELSE
GOTO 1G.1.7
ENDIF
1G.1.7
IF AC Session Key Counter ≥ AC Session Key Counter Limit
THEN
GOTO 1G.1.8
ELSE
GOTO 1G.1.10
ENDIF
1G.1.8
Set 'AC Session Key Counter Limit Exceeded' in Security Limits Status
1G.1.9
1G.1.10
AC Session Key Counter := AC Session Key Counter + 1

First Generate AC
1G.1.11
THEN
GOTO 1G.1.13
ELSE
GOTO 1G.1.12
ENDIF
1G.1.12
Derive AC Session Key using the MasterCard Proprietary SKD method.
1G.1.13
Derive AC Session Key using the EMV CSK method.
1G.1.16
Accumulator 1 Amount Temp := Accumulator 1 Amount
Counter 1 Number Temp := Counter 1 Number
1G.1.17
Amount, Authorized 1 := Amount, Authorized (Numeric)
Amount, Other 1 := Amount, Other (Numeric)
1G.1.18
'Offline PIN Verification Performed' in Card Verification Results := 'Offline PIN
Verification Performed' in PIN Verification Status
'Offline Encrypted PIN Verification Performed' in Card Verification Results :=

'Offline Encrypted PIN Verification Performed' in PIN Verification Status
'Offline PIN Verification Successful' in Card Verification Results := 'Offline PIN

Verification Successful' in PIN Verification Status
'Offline PIN Verification Not Performed' in Card Verification Results := NOT 'Offline
PIN Verification Performed' in PIN Verification Status
'Offline PIN Verification Failed' in Card Verification Results := (NOT 'Offline PIN
Verification Successful' in PIN Verification Status) AND 'Offline PIN Verification
Performed' in PIN Verification Status
'Offline Change PIN Result' in Card Verification Results := 'Offline Change PIN
Successful' in Offline Change PIN Status
1G.1.19
'Low Order Nibble Of Script Counter' in Card Verification Results := 'Script Counter'
in Script Counter

First Generate AC
1G.1.20
'Low Order Nibble Of PIN Try Counter' in Card Verification Results := 'Low Order
Nibble Of PIN Try Counter' in PIN Try Counter
1G.1.21
IF (((CVM Results [1][6 : 1] = 000001b OR CVM Results [1][6 : 1] = 000100b)
AND CVM Results [3] = '02')
OR ((CVM Results [1][6 : 1] = 000011b OR CVM Results [1][6 : 1] = 000101b)
AND CVM Results [3] = '00'))
AND 'Offline PIN Verification Successful' in PIN Verification Status is clear
THEN
GOTO 1G.1.22
ELSE
GOTO 1G.1.23
ENDIF
1G.1.22
Set 'Terminal Erroneously Considers Offline PIN OK' in Card Verification Results
1G.1.23
IF 'Low Order Nibble Of PIN Try Counter' in PIN Try Counter = 0000b
THEN
GOTO 1G.1.24
ELSE
GOTO 1G.1.25
ENDIF
1G.1.24
Set 'PTL Exceeded' in Card Verification Results
1G.1.25
IF Terminal Country Code = CRM Country Code
THEN
GOTO 1G.1.26
ELSE
GOTO 1G.1.27
ENDIF
1G.1.26
Set 'Domestic Transaction' in Card Verification Results
1G.1.27
Set 'International Transaction' in Card Verification Results
1G.1.28
'Go Online On Next Transaction Was Set' in Card Verification Results := 'Go Online
On Next Transaction' in Previous Transaction History
1G.1.29
'Issuer Authentication Failed' in Card Verification Results := 'Issuer Authentication
Failed' in Previous Transaction History

First Generate AC
1G.1.30
'Script Received' in Card Verification Results := 'Script Received' in Previous
Transaction History
1G.1.31
'Script Failed' in Card Verification Results := 'Script Failed' in Previous Transaction
History
1G.1.32
'Last Online Transaction Not Completed' in Card Verification Results := 'Last Online
Transaction Not Completed' in Previous Transaction History
1G.1.33
'Issuer Discretionary' in Card Verification Results := 'Issuer Discretionary' in CVR
Issuer Discretionary Data
1G.1.34
IF 'Additional Check Table' in Application Control is set
THEN
GOTO 1G.1.35
ELSE
GOTO 1G.1.36
ENDIF
1G.1.35
CALL ProcessAddCheckTable( )
1G.1.36
CALL CheckAccsCntrsLimitsSetCVR( )
1G.1.37
IF 'MTA Check' in Application Control is set
THEN
GOTO 1G.1.38
ELSE
GOTO 1G.1.44
ENDIF
1G.1.38
IF MTA Currency Code = Transaction Currency Code
THEN
GOTO 1G.1.39
ELSE
GOTO 1G.1.44
ENDIF
1G.1.39
Return Value := CALL CheckCVMTransaction( )

First Generate AC
1G.1.40
IF Return Value
THEN
GOTO 1G.1.41
ELSE
GOTO 1G.1.42
ENDIF
1G.1.41
THEN
GOTO 1G.1.43
ELSE
GOTO 1G.1.44
ENDIF
1G.1.42
IF Amount, Authorized (Numeric) > MTA NoCVM
THEN
GOTO 1G.1.43
ELSE
GOTO 1G.1.44
ENDIF
1G.1.43
1G.1.44
IF 'Maximum Number Of Days Offline Check' in Application Control is set
THEN
GOTO 1G.1.45
ELSE
GOTO 1G.1.52
ENDIF
1G.1.45
Return Value := CALL CheckFormatOfDate( )
1G.1.46
IF Return Value
THEN
GOTO 1G.1.47
ELSE
GOTO 1G.1.49
ENDIF

First Generate AC
1G.1.47
DaysElapsedPerMonth[1] := 0
DaysInYears := 365 * Transaction Date[1] + (Transaction Date[1] + 3) / 4

DaysInMonths := DaysElapsedPerMonth[Transaction Date[2]]
IF (Transaction Date[2] > 2 AND Transaction Date[1] MOD 4 = 0)

THEN
DaysInMonths := DaysInMonths + 1
ENDIF
Current Date In Days := DaysInYears + DaysInMonths + Transaction Date[3]
Note
The division used in this symbol is the truncated integer division.
1G.1.48
IF Current Date In Days + 1 ≥ Last Online Transaction Date
THEN
GOTO 1G.1.50
ELSE
GOTO 1G.1.49
ENDIF
1G.1.49
Set 'Date Check Failed' in Card Verification Results
1G.1.50
IF Current Date In Days > Number Of Days Off Line Limit + Last Online Transaction
Date
THEN
GOTO 1G.1.51
ELSE
GOTO 1G.1.52
ENDIF
1G.1.51
Set 'Number Of Days Offline Limit Exceeded' in Card Verification Results

First Generate AC
1G.1.52
IF Internal Authentication Performed Flag is set
THEN
GOTO 1G.1.53
ELSE
GOTO 1G.1.70
ENDIF
1G.1.53
Set 'DDA Returned' in Card Verification Results
1G.1.70
IF RRP Counter ≠ 0
THEN
GOTO 1G.1.71
ELSE
GOTO 1G.1.54
ENDIF
1G.1.71
IF Unpredictable Number = Terminal Relay Resistance Entropy
THEN
GOTO 1G.1.72
ELSE
GOTO 1G.4.1 (AAC Decided)
ENDIF
1G.1.72
IF 'Relay resistance performed' in Terminal Verification Results = RRP Performed
THEN
GOTO 1G.1.73
ELSE
ENDIF
1G.1.73
IF 'Combined DDA/AC Generation Requested' in Reference Control Parameter is
not set AND 'Decline If CDA Not Requested And RRP Performed' in Application
Control is set
THEN
ELSE
GOTO 1G.1.54
ENDIF

First Generate AC
1G.1.54
THEN
ELSE
GOTO 1G.1.55
ENDIF
1G.1.55
IF 'Offline PIN Verification Successful' in PIN Verification Status is set
THEN
GOTO 1G.1.56
ELSE
GOTO 1G.1.68
ENDIF
1G.1.56
IF 'Offline PIN Reset' in Accumulator 1 Control is set
THEN
GOTO 1G.1.57
ELSE
GOTO 1G.1.59
ENDIF
1G.1.57
Accumulator 1 Amount := '000000000000'
Accumulator 1 Amount Temp := '000000000000'
1G.1.58
Clear 'Lower Cumulative Accumulator 1 Limit Exceeded' in Card Verification Results
Clear 'Upper Cumulative Accumulator 1 Limit Exceeded' in Card Verification Results
1G.1.59
IF 'Offline PIN Reset' in Accumulator 2 Control is set
THEN
GOTO 1G.1.60
ELSE
GOTO 1G.1.62
ENDIF
1G.1.60
Accumulator 2 Amount := '000000000000'
1G.1.61

First Generate AC
1G.1.62
IF 'Offline PIN Reset' in Counter 1 Control is set
THEN
GOTO 1G.1.63
ELSE
GOTO 1G.1.65
ENDIF
1G.1.63
Counter 1 Number := '00'
Counter 1 Number Temp := '00'
1G.1.64
Clear 'Lower Consecutive Counter 1 Limit Exceeded' in Card Verification Results
Clear 'Upper Consecutive Counter 1 Limit Exceeded' in Card Verification Results
1G.1.65
IF 'Offline PIN Reset' in Counter 2 Control is set
THEN
GOTO 1G.1.66
ELSE
GOTO 1G.1.68
ENDIF
1G.1.66
Counter 2 Number := '00'
1G.1.67
1G.1.68
IF 'Cryptogram Type' in Reference Control Parameter = AAC
THEN
ELSE
IF 'Cryptogram Type' in Reference Control Parameter = ARQC
THEN
GOTO 1G.2.1 (ARQC Requested)
ELSE
GOTO 1G.3.1 (TC Requested)
ENDIF
ENDIF

First Generate AC
9.3.2. ARQC Requested

1G.2
ARQC
req
1
Determine Acc 1
Active Flag
2
Determine Acc 2
Active Flag
3
Determine Cntr 1
Active Flag
4
Determine Cntr 2
Active Flag
Do not decline CVR & CIAC Decline

Decline
1 AAC
dec

First Generate AC
1G.2
6
Include
No transaction on ARQC
request
Yes
7
Update temp
accumulators and
counters
8
temp Accs and Cntrs
Set bits in CVR
9
Use CIAC Online
No
to decide on ARQC
request
Yes
10
CVR & Online
CIAC Online
Decline
AAC 2
dec

First Generate AC
1G.2
11
Save Accs
No and Cntrs on ARQC
Response
Yes
12
Save active Accs
and Cntrs
ARQC
dec

First Generate AC
1G.2.1
CALL DetermineAccActiveFlag( 1 )
1G.2.2
1G.2.3
CALL DetermineCntrActiveFlag( 1 )
1G.2.4
1G.2.5
IF ('CVR Decisional Part' in Card Verification Results AND Card Issuer Action Code –
Decline) = '000000'
THEN
GOTO 1G.2.6
ELSE
ENDIF
1G.2.6
IF 'Include Transaction In CRM If ARQC Is Requested' in Application Control is set
THEN
GOTO 1G.2.7
ELSE
GOTO 1G.2.9
ENDIF
1G.2.7
1G.2.8
1G.2.9
IF 'Use CIAC-online To Decide On ARQC Request' in Application Control is set
THEN
GOTO 1G.2.10
ELSE
GOTO 1G.2.11
ENDIF
1G.2.10
Online) = '000000'
THEN
GOTO 1G.2.11
ELSE
ENDIF

First Generate AC
1G.2.11
IF 'Save Accumulators And Counters on ARQC Response' in Application Control is
set
THEN
GOTO 1G.2.12
ELSE
GOTO 1G.6.1 (ARQC Decided)
ENDIF
1G.2.12
CALL SaveActiveAccsCntrs( )

First Generate AC
9.3.3. TC Requested
1G.3
TC
req
1
Determine Acc 1
Active Flag
2
Determine Acc 2
Active Flag
3
Determine Cntr 1
Active Flag
4
Determine Cntr 2
Active Flag
5
CVR & Decline
CIACS Decline
Do Not Decline
6
Update temp
accumulators and
counters
1 AAC
dec

First Generate AC
1G.3
7
temp Accs and Cntrs
Set bits in CVR
Generate only TC/ Yes

AAC on TC req
No
No
Offline only Yes
terminal
9.1
RRP not
performed and
No
Decline if RRP
not performed
Yes
2 3 AAC
dec

First Generate AC
1G.3
2 3
13.1 10
RRP not CAT3 and
performed and Yes skip CRM for
Yes
Go online if RRP CAT3?
not performed
11
Set Skipped on CAT3 No
No in CVR
13 12
CVR & CVR &
Offline Offline
CIAC Online CIAC Default
Online 14 Decline
Save active Accs
and Cntrs
15
Save Accs
No and Cntrs on ARQC
Response
Yes
16
Save active Accs
and Cntrs
ARQC TC AAC
dec dec dec

First Generate AC
1G.3.1
1G.3.2
1G.3.3
1G.3.4
1G.3.5
IF ('CVR Decisional Part' in Card Verification Results AND Card Issuer Action Code
– Decline) = '000000'
THEN
GOTO 1G.3.6
ELSE
ENDIF
1G.3.6
1G.3.7
1G.3.8
IF 'Generate Only TC Or AAC On TC Request' in Application Control is set
THEN
GOTO 1G.3.10
ELSE
GOTO 1G.3.9
ENDIF
1G.3.9
IF Terminal Type = '23' OR Terminal Type = '26' OR Terminal Type = '36' OR
Terminal Type = '13' OR Terminal Type = '16'
THEN
GOTO 1G.3.9.1
ELSE
GOTO 1G.3.13.1
ENDIF

First Generate AC
1G.3.9.1
IF RRP Counter = 0 AND
'Decline If Unable To Go Online And RRP Not Performed' in Application
Control is set
THEN
ELSE
GOTO 1G.3.10
ENDIF
1G.3.10
IF Terminal Type = '26' AND
'Skip CIAC-Default On CAT3' in Application Control is set
THEN
GOTO 1G.3.11
ELSE
GOTO 1G.3.12
ENDIF
1G.3.11
Set 'CIAC-Default Skipped On CAT3' in Card Verification Results
1G.3.12
IF ('CVR Decisional Part' in Card Verification Results
AND Card Issuer Action Code – Default) = '000000'
THEN
GOTO 1G.3.14
ELSE
ENDIF
1G.3.13.1
'Go Online If RRP Not Performed' in Application Control is set
THEN
GOTO 1G.3.15
ELSE
GOTO 1G.3.13
ENDIF
1G.3.13
IF ('CVR Decisional Part' in Card Verification Results AND Card Issuer Action Code
– Online) = '000000'
THEN
GOTO 1G.3.14
ELSE
GOTO 1G.3.15
ENDIF

First Generate AC
1G.3.14
GOTO 1G.5.1 (TC Decided)
1G.3.15
set
THEN
GOTO 1G.3.16
ELSE
ENDIF
1G.3.16

First Generate AC
9.3.4. AAC Decided

1G.4
AAC
dec
1
Set AAC decided in
CVR
1a
Combined
Yes
DDA/AC? 1b
Set CDA returned in
No
CVR
2
Set AAC decided in
CID
AAC Logging? Yes

4
Write log
No
5
Enable
alternate Yes
interface? 6
Enable interface
No

First Generate AC
1G.4
7
No
Combined
DDA/AC
Yes
8
Other
Cryptogram
requested
AAC
9 11
Host Host
compatibility compatibility
M4R2 2.1/2.2 2.05 1.1/1.3 M4R2 2.1/2.2 2.05 1.1/1.3

AC AC AC AC CDA CDA CDA CDA

First Generate AC
1G.4.1
'AC Returned In First Generate AC' in Card Verification Results := AAC Returned In
First Generate AC
'AC Returned In Second Generate AC' in Card Verification Results := AC Not
Requested In Second Generate AC
1G.4.1a
IF 'Combined DDA/AC Generation Requested' in Reference Control Parameter is
set AND 'Cryptogram Type' in Reference Control Parameter = AAC
THEN
GOTO 1G.4.1b
ELSE
GOTO 1G.4.2
ENDIF
1G.4.1b
Set 'Combined DDA/AC Generation Returned In First Generate AC' in Card
Verification Results
1G.4.2
'Type Of Cryptogram' in Cryptogram Information Data := AAC
1G.4.3
IF 'AAC Logging' in Application Control is set
THEN
GOTO 1G.4.4
ELSE
GOTO 1G.4.5
ENDIF
1G.4.4
Create Temp Transaction Log Record as defined in Table 9.4.
Table 9.4—Temp Transaction Log Record
Data Object Length
Transaction Date 3
Transaction Time 3
The data objects defined by the Log Data Table are appended to the Temp
Transaction Log Record:
CALL AddAdditionalLogInfo( )
The Temp Transaction Log Record is added to the Transaction Log File (do not
commit)

First Generate AC
1G.4.5
IF 'Enable Alternate Interface After First Gen AC' in Application Control is set
OR
('Enable Alternate Interface After Successful Verify' in Application Control is set
AND 'Offline PIN Verification Successful' in PIN Verification Status is set)
THEN
GOTO 1G.4.6
ELSE
GOTO 1G.4.7
ENDIF
1G.4.6
'Interfaces Status' in Interface Enabling Switch := Contact And Contactless Interfaces
Enabled
1G.4.7
IF 'Combined DDA/AC Generation Requested' in Reference Control Parameter is set
THEN
GOTO 1G.4.8
ELSE
GOTO 1G.4.9
ENDIF
1G.4.8
THEN
GOTO 1G.4.11
ELSE
GOTO 1G.4.9
ENDIF
1G.4.9
IF 'Issuer Host Backwards Compatibility' in Application Control = V2.1/V2.2 Host
Backwards Compatibility
THEN
GOTO 1G.9.1 (No CDA - V2.1/V2.2 host backwards compatibility)
ELSE
IF 'Issuer Host Backwards Compatibility' in Application Control = V2.05 Host
THEN
GOTO 1G.10.1 (No CDA - V2.05 host backwards compatibility)
ELSE
IF 'Issuer Host Backwards Compatibility' in Application Control =
V1.1/V1.3 Host Backwards Compatibility
THEN
GOTO 1G.8.1 (No CDA – V1.1/V1.3 host backwards compatibility)
ELSE
GOTO 1G.7.1 (No CDA – no host backwards compatibility)
ENDIF
ENDIF
ENDIF

First Generate AC
1G.4.11
THEN
GOTO 1G.14.1 (CDA – V2.1/V2.2 host backwards compatibility)
ELSE
THEN
GOTO 1G.15.1 (CDA – V2.05 host backwards compatibility)
ELSE
THEN
ELSE
GOTO 1G.12.1 (CDA – no host backwards compatibility)
ENDIF
ENDIF
ENDIF

First Generate AC
9.3.5. TC Decided
1G.5
TC
dec
1
Set TC decided in
CVR
1a
Combined
Yes
DDA/AC? 1b
Set CDA returned in
CVR
No
Set TC decided in CID
TC Logging? Yes
4
Write log
No
5
Enable
alternate Yes
interface? 6
Enable interface
No

First Generate AC
1G.5
No
Combined
DDA/AC
Yes
8 10
Host Host
M4R2 2.1/2.2 2.05 1.1/1.3 M4R2 2.1/2.2 2.05 1.1/1.3


First Generate AC
1G.5.1
'AC Returned In First Generate AC' in Card Verification Results := TC Returned In
First Generate AC
1G.5.1a
THEN
GOTO 1G.5.1b
ELSE
GOTO 1G.5.2
ENDIF
1G.5.1b
Set 'Combined DDA/AC Generation Returned In First Generate AC' in
CardVerification Results
1G.5.2
'Type Of Cryptogram' in Cryptogram Information Data := TC
1G.5.3
IF 'TC Logging' in Application Control is set
THEN
GOTO 1G.5.4
ELSE
GOTO 1G.5.5
ENDIF
1G.5.4
Data Object Length
Transaction Date 3
Transaction Time 3
commit)

First Generate AC
1G.5.5
OR
OR
'Enable Alternate Interface After TC Generated' in Application Control is set
THEN
GOTO 1G.5.6
ELSE
GOTO 1G.5.7
ENDIF
1G.5.6
Enabled
1G.5.7
THEN
GOTO 1G.5.10
ELSE
GOTO 1G.5.8
ENDIF
1G.5.8
THEN
ELSE
THEN
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF

First Generate AC
1G.5.10
THEN
ELSE
THEN
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF

First Generate AC
9.3.6. ARQC Decided

1G.6
ARQC
dec
1
Set ARQC decided
in CVR
1a
Combined
Yes
DDA/AC? 1b
Set CDA returned in
CVR
No
2
Set ARQC decided in
CID
3
Pre-logging
Yes
enabled? 4
Write log
No
5
Enable
alternate Yes
interface? 6
Enable interface
No

First Generate AC
1G.6
7
Set Last Online
Transaction Not
Completed in PTH
No
Combined
DDA/AC
Yes
9 11
Host Host
M4R2 2.1/2.2 2.05 1.1/1.3 M4R2 2.1/2.2 2.05 1.1/1.3


First Generate AC
1G.6.1
'AC Returned In First Generate AC' in Card Verification Results := ARQC Returned
In First Generate AC
1G.6.1a
THEN
GOTO 1G.6.1b
ELSE
GOTO 1G.6.2
ENDIF
1G.6.1b
Set 'Combined DDA/AC Generation Returned In First Generate AC' in Card
1G.6.2
'Type Of Cryptogram' in Cryptogram Information Data := ARQC
1G.6.3
IF 'ARQC Pre-logging' in Application Control is set
THEN
GOTO 1G.6.4
ELSE
GOTO 1G.6.5
ENDIF
1G.6.4
Data Object Length
Transaction Date 3
Transaction Time 3
commit)

First Generate AC
1G.6.5
OR
THEN
GOTO 1G.6.6
ELSE
GOTO 1G.6.7
ENDIF
1G.6.6
Enabled
1G.6.7
Set 'Last Online Transaction Not Completed' in Previous Transaction History
1G.6.8
THEN
GOTO 1G.6.11
ELSE
GOTO 1G.6.9
ENDIF
1G.6.9
THEN
ELSE
THEN
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF

First Generate AC
1G.6.11
THEN
ELSE
THEN
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF

First Generate AC
9.3.7. No CDA – No Host Backwards Compatibility

1G.7
M4R2
AC
Build counters field
2 3
Encrypt? Yes Compute variant key
No 4
Encrypt field
No
Include Yes
counters?
6
Include Last
9 No
Online ATC?
Yes
Build input to AC
without counters
7 8
Build input to AC Build input to AC
with counters with counters and
Last Online ATC
10
Compute AC
11
CVN = '10'

First Generate AC
1G.7
12
EMV CSK
Session Key MasterCard Proprietary
Derivation
13 14
Set MasterCard
Set EMV CSK in CVN
Proprietary SKD in CVN
15
Yes
Include
counters?
16
No
Set Counters Included In
AC Computation in CVN
17
Set DAC / ICC

Dynamic Number

First Generate AC
1G.7
2
18
Include
Yes Last Online ATC No
in IAD?
19 20
Build IAD with Last Build IAD without Last

Online ATC Online ATC
21
Build response
SW12 = '9000'
22
Recover Torn
Yes
Transactions
Enabled?
23
No
Update recovery data
24
Commit persistent
data

First Generate AC
1G.7.1
CALL BuildCountersField( )
1G.7.2
IF 'Encrypt Offline Counters' in Application Control is set
THEN
GOTO 1G.7.3
ELSE
GOTO 1G.7.5
ENDIF
1G.7.3
Compute variant session key for Plaintext/Encrypted Counters encryption.
1G.7.4
Plaintext/Encrypted Counters := Encrypt (Plaintext/Encrypted Counters)
1G.7.5
IF 'Include Counters In AC' in Application Control is set
THEN
GOTO 1G.7.6
ELSE
GOTO 1G.7.9
ENDIF
1G.7.6
IF 'Include Last Online ATC in IAD' in Application Control is set
THEN
GOTO 1G.7.8
ELSE
GOTO 1G.7.7
ENDIF

First Generate AC
1G.7.7
Build the input for Application Cryptogram generation as defined in Table 9.7.
Table 9.7—Input for Application Cryptogram with Counters
Data Object Length
Amount, Other (Numeric) 6
Terminal Country Code 2
Terminal Verification Results 5
Transaction Date 3
Transaction Type 1
Unpredictable Number 4
Application Interchange Profile 2
Plaintext/Encrypted Counters 8 or 16
1G.7.8
Table 9.8—Input for Application Cryptogram with Counters and Last Online
ATC
Data Object Length
Transaction Date 3
Transaction Type 1
Last Online ATC 2

First Generate AC
1G.7.9
Table 9.9—Input for Application Cryptogram without Counters or Last Online
ATC
Data Object Length
Transaction Date 3
Transaction Type 1
1G.7.10
Compute Application Cryptogram
First AC := Application Cryptogram

Rand := Application Cryptogram
1G.7.11
Cryptogram Version Number := '10'
1G.7.12
THEN
GOTO 1G.7.13
ELSE
GOTO 1G.7.14
ENDIF
1G.7.13
'Session Key Used For AC Computation' in Cryptogram Version Number := EMV
CSK Session Key
1G.7.14
'Session Key Used For AC Computation' in Cryptogram Version Number :=
MasterCard Proprietary SKD Session Key
1G.7.15
THEN
GOTO 1G.7.16
ELSE
GOTO 1G.7.17
ENDIF

First Generate AC
1G.7.16
Set 'Counters Included In AC Computation' in Cryptogram Version Number
1G.7.17
IF ICC Dynamic Number (Terminal) = '0000000000000000'
THEN
DAC/ICC Dyn Nr := Data Authentication Code
ELSE
DAC/ICC Dyn Nr := ICC Dynamic Number (Terminal)[1 : 2]
ENDIF
1G.7.18
THEN
GOTO 1G.7.19
ELSE
GOTO 1G.7.20
ENDIF
1G.7.19
Build Issuer Application Data as defined in Table 9.10.
Table 9.10—Issuer Application Data with Last Online ATC
Data Object Length
Key Derivation Index 1
Cryptogram Version Number 1
DAC/ICC Dyn Nr 2
Last Online ATC 2
1G.7.20
Table 9.11—Issuer Application Data without Last Online ATC
Data Object Length
DAC/ICC Dyn Nr 2

First Generate AC
1G.7.21
Build the response.
equal to '9000'.
Table 9.12—Response
Tag Length Description
'9F27' 1 Cryptogram Information Data
'9F26' 8 Application Cryptogram
'9F10' 18, 20, 26 or 28 Issuer Application Data
1G.7.22
IF 'Torn Transaction Recovery' in Application Control is set
THEN
GOTO 1G.7.23
ELSE
GOTO 1G.7.24
ENDIF
1G.7.23
Clear CDA Transaction Flag (Recovery) (do not commit)
Clear RRP Performed Flag (Recovery) (do not commit)
Application Cryptogram (Recovery) := Application Cryptogram (do not commit)
Application Transaction Counter (Recovery) := Application Transaction Counter (do
not commit)
Issuer Application Data (Recovery) := Issuer Application Data (do not commit)
Cryptogram Information Data (Recovery) := Cryptogram Information Data (do not
commit)
Unpredictable Number (Recovery) := Unpredictable Number (do not commit)
1G.7.24
Commit all the persistent data objects that have a new value assigned but that have
not yet been committed, in one atomic operation.
characteristics.

First Generate AC
9.3.8. No CDA – V1.1/V1.3 Host Backwards

Compatibility
1G.8
1.1/1.3
AC
Compute 1.1/1.3 1
CVR
2
3
4
No 5
Encrypt field
6
Include Build input to AC 7
Yes
counters? with counters
No
Build input to AC 8
without counters
9
Compute AC

First Generate AC
1G.8
1
10
CVN = '10'
11
EMV CSK
Derivation
12 13
Set MasterCard
Set EMV CSK in CVN
14
Yes
Include
counters?
15
No
Build Issuer 16
Application Data
Build response 17
SW12 = '9000'

First Generate AC
1G.8
18
Recover Torn
Yes Transactions
Enabled?
19

No
Commit persistent 20
data

First Generate AC
1G.8.1
CALL Compute41.1CVR( )
1G.8.2
1G.8.3
THEN
GOTO 1G.8.4
ELSE
GOTO 1G.8.6
ENDIF
1G.8.4
1G.8.5
1G.8.6
THEN
GOTO 1G.8.7
ELSE
GOTO 1G.8.8
ENDIF
1G.8.7
Table 9.13—Input for Application Cryptogram with Counters (V1.1/V1.3 Host
Backwards Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6

First Generate AC
1G.8.8
Table 9.14—Input for Application Cryptogram without Counters (V1.1/V1.3 Host
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6
1G.8.9

1G.8.10
1G.8.11
THEN
GOTO 1G.8.12
ELSE
GOTO 1G.8.13
ENDIF
1G.8.12
'Session Key Used For AC Computation' in Cryptogram Version Number :=EMV
CSK Session Key
1G.8.13

First Generate AC
1G.8.14
THEN
GOTO 1G.8.15
ELSE
GOTO 1G.8.16
ENDIF
1G.8.15
1G.8.16
THEN
ELSE
ENDIF

Table 9.15—Issuer Application Data (V1.1/V1.3 Host Backwards Compatibility)
Data Object Length
CVR V1.1/V1.3 6
DAC/ICC Dyn Nr 2
1G.8.17
Build the response.
equal to '9000'.
Table 9.16—Response (V1.1/V1.3 Host Backwards Compatibility)
'9F10' 18 or 26 Issuer Application Data

First Generate AC
1G.8.18
THEN
GOTO 1G.8.19
ELSE
GOTO 1G.8.20
ENDIF
1G.8.19
not commit)
commit)
1G.8.20
characteristics.

First Generate AC
9.3.9. No CDA - V2.1/V2.2 Host Backwards

Compatibility
1G.9
2.1/2.2
AC
Compute 2.1/2.2 1
CVR
2
Adjust CID
3
Compute AC
Build 2.1/2.2 Issuer 4

Application Data
Build response 5
SW12 = '9000'
6
Recover Torn
Yes
Transactions
Enabled?

No
Commit persistent 8
data

First Generate AC
1G.9.1
1G.9.2
IF PIN Try Counter = '00'
THEN
IF 'Type Of Cryptogram' in Cryptogram Information Data = AAC OR 'Type Of
Cryptogram' in Cryptogram Information Data = TC
THEN
Set 'Advice Required' in Cryptogram Information Data
ENDIF
'Reason/Advice code' in Cryptogram Information Data := PIN Try Limit
Exceeded
ENDIF
1G.9.3
Table 9.17—Input for Application Cryptogram (V2.1/V2.2 Host Backwards
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.1/V2.2 4


1G.9.4
THEN
ELSE
ENDIF
Build Issuer Application Data V2.1/V2.2 as defined in Table 9.18.

First Generate AC
Table 9.18—Issuer Application Data V2.1/V2.2

Data Object Length
CVR V2.1/V2.2 4
DAC/ICC Dyn Nr 2
1G.9.5
Build the response.
equal to '9000'.
'9F10' 8 Issuer Application Data V2.1/V2.2
1G.9.6
THEN
GOTO 1G.9.7
ELSE
GOTO 1G.9.8
ENDIF
1G.9.7
not commit)
Issuer Application Data (Recovery) := Issuer Application Data V2.1/V2.2 (do not
commit)
commit)
1G.9.8
characteristics.

First Generate AC
9.3.10. No CDA – V2.05 Host Backwards Compatibility

1G.10
2.05
AC
Compute 2.05 1
CVR
2
Adjust CID
3
Compute AC
Build 2.05 Issuer 4

Application Data
Build response 5
SW12 = '9000'
6
Recover Torn
Yes
Transactions
7 Enabled?

No
Commit persistent 8
data

First Generate AC
1G.10.1
1G.10.2
IFPIN Try Counter = '00' AND 'Type Of Cryptogram' in Cryptogram Information
Data = AAC
THEN
Exceeded
ENDIF
1G.10.3
Build the input to AC as defined in Table 9.20.
Table 9.20—Input for Application Cryptogram (V2.05 Host Backwards
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.05 4


1G.10.4
THEN
ELSE
ENDIF

First Generate AC
Build Issuer Application Data V2.05 as defined in Table 9.21.

Table 9.21—Issuer Application Data V2.05
Data Object Length
'08' 1
CVR V2.05 4
DAC/ICC Dyn Nr 2
1G.10.5
Build the response.
equal to '9000'.
Table 9.22—Response (V2.05 Host Backwards Compatibility)
'9F10' 9 Issuer Application Data V2.05
1G.10.6
THEN
GOTO 1G.10.7
ELSE
GOTO 1G.10.8
ENDIF
1G.10.7
not commit)
Issuer Application Data (Recovery) := Issuer Application Data V2.05 (do not commit)
commit)
1G.10.8
characteristics.

First Generate AC
9.3.11. MAS4C
1G.11
MAS4C
13
Use
Yes MAS4C
Key?
No
14
CTRAC ≥
Yes
LIMAC ? 15
Error Limit Exceeded in
No Security Limits Status
17
16
Increment CTRAC
Build response
SW12 = '6985'
18
Session Key EMV CSK
Derivation
MasterCard Proprietary
19 20
Derive AC Session Key Derive AC Session
(MasterCard Proprietary Key (EMV CSK) from
SKD) from AC Master Key AC Master Key
1 2

First Generate AC
1G.11
21
CTRAC (MAS4C)
Yes
≥ LIMAC (MAS4C) ?
22
(MAS4C) Error Limit Exceeded
in Security Limits Status
No Common
24
Increment 23
CTRAC (MAS4C) Build response
SW12 = '6985'
25
Session Key EMV CSK
Derivation
26 27
Derive AC Session Key Derive AC Session Key

(MasterCard Proprietary SKD) (EMV CSK) from AC
from AC Master Key (MAS4C) Master Key (MAS4C)

First Generate AC
1G.11
2
Set AC Returned in 2nd Gen

AC in CVR to not requested
28
AC for MAS4C ARQC
AAC
2 29
Set AC Returned in 1st Gen Set AC Returned in 1st Gen

AC in CVR to AAC AC in CVR to ARQC
2.1 30
Set Type Of Cryptogram in Set Type Of Cryptogram in

CID to AAC CID to ARQC
Copy PIN Verification Status

to CVR
Copy PIN Change Status to

CVR

First Generate AC
1G.11
Build input to AC
7
EMV CSK
Derivation
8 9
Set CVN for MasterCard
Set CVN for EMV CSK
Proprietary SKD
10
Compute AC
11
Build Issuer Application
Data
12
Build response
SW12 = '9000'

First Generate AC
1G.11.13
IF 'Key for MAS4C Processing Flow' in Application Control = AC Master Key
(MAS4C)
THEN
GOTO 1G.11.21
ELSE
GOTO 1G.11.14
ENDIF
1G.11.14
THEN
GOTO 1G.11.15
ELSE
GOTO 1G.11.17
ENDIF
1G.11.15
1G.11.16
1G.11.17
1G.11.18
THEN
GOTO 1G.11.20
ELSE
GOTO 1G.11.19
ENDIF
1G.11.19
Derive AC Session Key from AC Master Key using the MasterCard Proprietary SKD
method.
1G.11.20
Derive AC Session Key from AC Master Key using the EMV CSK method.
1G.11.21
IF AC Session Key Counter (MAS4C) ≥ AC Session Key Counter Limit (MAS4C)
THEN
GOTO 1G.11.22
ELSE
GOTO 1G.11.24
ENDIF

First Generate AC
1G.11.22
Set 'AC Session Key Counter Limit (MAS4C) Exceeded' in Security Limits Status
Common
1G.11.23
1G.11.24
AC Session Key Counter (MAS4C) := AC Session Key Counter (MAS4C) + 1
1G.11.25
THEN
GOTO 1G.11.27
ELSE
GOTO 1G.11.26
ENDIF
1G.11.26
Derive AC Session Key from AC Master Key (MAS4C) using the MasterCard
Proprietary SKD method.
1G.11.27
Derive AC Session Key from AC Master Key (MAS4C) using the EMV CSK method.
1G.11.1
Set 'AC Returned In Second Generate AC' in Card Verification Results to AC Not
1G.11.28
IF 'AC for MAS4C' in Application Control = AAC
THEN
GOTO 1G.11.2
ELSE
GOTO 1G.11.29
ENDIF
1G.11.2
Set 'AC Returned In First Generate AC' in Card Verification Results to AAC
Returned In First Generate AC
1G.11.2.1
1G.11.29
Set 'AC Returned In First Generate AC' in Card Verification Results to ARQC
Returned In First Generate AC
1G.11.30
'Type Of Cryptogram' in Cryptogram Information Data := ARQC

First Generate AC
1G.11.3
Set 'Offline PIN Verification Performed' in Card Verification Results to 'Offline PIN
Verification Performed' in PIN Verification Status
Set 'Offline PIN Verification Successful' in Card Verification Results to 'Offline PIN
Verification Successful' in PIN Verification Status
Set 'Offline PIN Verification Not Performed' in Card Verification Results to NOT
'Offline PIN Verification Performed' in PIN Verification Status
Set 'Offline PIN Verification Failed' in Card Verification Results to (NOT 'Offline PIN
Verification Successful' in PIN Verification Status) AND 'Offline PIN Verification
Performed' in PIN Verification Status
1G.11.4
Set 'Offline Change PIN Result' in Card Verification Results to 'Offline Change PIN
Successful' in Offline Change PIN Status
1G.11.5
IF
(
('Include In Issuer Application Data' in Accumulator 1 Control = Include
Accumulator As Value OR 'Include In Issuer Application Data' in Accumulator
1 Control = Include As Balance)
AND
2 Control = Include As Balance)
)
OR
(
1 Control = Include As Balance OR 'Include In Issuer Application Data' in
Accumulator 2 Control = Include Accumulator As Value OR 'Include In Issuer
Application Data' in Accumulator 2 Control = Include As Balance)
AND
(('Include In Issuer Application Data' in Counter 1 Control = Include Counter
As Value OR 'Include In Issuer Application Data' in Counter 1 Control =
Include As Balance) AND ('Include In Issuer Application Data' in Counter 2
Control = Include Counter As Value OR 'Include In Issuer Application Data' in
Counter 2 Control = Include As Balance))
)
THEN
Plaintext/Encrypted Counters := '00000000000000000000000000000000'
ELSE
Plaintext/Encrypted Counters := '0000000000000000'
ENDIF

First Generate AC
1G.11.6
Table 9.23—Input for Application Cryptogram (MAS4C)
Data Object Length
Transaction Date 3
Transaction Type 1
1G.11.7
THEN
GOTO 1G.11.8
ELSE
GOTO 1G.11.9
ENDIF
1G.11.8
'Cryptogram Version' in Cryptogram Version Number := 0001b
CSK Session Key
1G.11.9
'Cryptogram Version' in Cryptogram Version Number := 0001b
1G.11.10
1G.11.11
THEN
ELSE
ENDIF

First Generate AC
IF 'Key for MAS4C Processing Flow' in Application Control = AC Master Key

(MAS4C)
THEN
Table 9.24—Issuer Application Data (MAS4C) with Key Derivation Index
(MAS4C)
Data Object Length
Key Derivation Index (MAS4C) 1
DAC/ICC Dyn Nr 2
ELSE
Table 9.25—Issuer Application Data (MAS4C)
Data Object Length
DAC/ICC Dyn Nr 2
ENDIF
1G.11.12
Build the response.
equal to '9000'.
Table 9.26—Response (MAS4C)

First Generate AC
9.3.12. CDA – No Host Backwards Compatibility

1G.12
M4R2
CDA
2 3
4
No
Encrypt field
No
Include Yes
counters?
9 6
Include Last
Build input to AC No
Online ATC? Yes
without counters
7 8
Last Online ATC
10
Compute AC

First Generate AC
1G.12
1
11
CVN = '10'
12
EMV CSK
Derivation
13 14
Set MasterCard
Set EMV CSK in CVN
15
Yes
Include
counters?
16
No
17
Set DAC / ICC

Dynamic Number

First Generate AC
1G.12
18
Include
in IAD?
19 20

21
Compute Hash
Result
21.1
No
RRP Yes
Performed?
22 22.1
Build ICC Dynamic Build ICC Dynamic
Data (No RRP) Data (RRP)

First Generate AC
1G.12
23
Compute Hash on
Dynamic Application
Data to be Signed
24
Compute RSA
Signature
25
Build response
SW12 = '9000'
26
Recover Torn
Yes
Transactions
Enabled?
27

No
28
Commit persistent
data

First Generate AC
1G.12.1
1G.12.2
THEN
GOTO 1G.12.3
ELSE
GOTO 1G.12.5
ENDIF
1G.12.3
1G.12.4
1G.12.5
THEN
GOTO 1G.12.6
ELSE
GOTO 1G.12.9
ENDIF
1G.12.6
THEN
GOTO 1G.12.8
ELSE
GOTO 1G.12.7
ENDIF

First Generate AC
1G.12.7
Data Object Length
Transaction Date 3
Transaction Type 1
1G.12.8
Table 9.28—Input for Application Cryptogram with Counters and with Last
Online ATC
Data Object Length
Transaction Date 3
Transaction Type 1
Last Online ATC 2

First Generate AC
1G.12.9
Table 9.29—Input for Application Cryptogram without Counters and without
Last Online ATC
Data Object Length
Transaction Date 3
Transaction Type 1
1G.12.10
Compute Application Cryptogram.

1G.12.11
1G.12.12
THEN
GOTO 1G.12.13
ELSE
GOTO 1G.12.14
ENDIF
1G.12.13
CSK Session Key
1G.12.14
1G.12.15
THEN
GOTO 1G.12.16
ELSE
GOTO 1G.12.17
ENDIF

First Generate AC
1G.12.16
1G.12.17
THEN
ELSE
ENDIF
1G.12.18
THEN
GOTO 1G.12.19
ELSE
GOTO 1G.12.20
ENDIF
1G.12.19
Data Object Length
DAC/ICC Dyn Nr 2
Last Online ATC 2
1G.12.20
Data Object Length
DAC/ICC Dyn Nr 2

First Generate AC
1G.12.21
Build the input for the computation of Hash Result as defined in Table 9.32.
Table 9.32—Input for Computation of Hash Result
Tag Length Value
– – PDOL values
– – CDOL1 Related Data
Compute Hash Result

1G.12.21.1
IF RRP Counter = 0
GOTO 1G.12.22
ELSE
GOTO 1G.12.22.1
ENDIF
1G.12.22
Build ICC Dynamic Data as defined in Table 9.33
Table 9.33—ICC Dynamic Data (No RRP)

Data Object Length
'08' (length of ICC Dynamic Number[9 : 16]) 1
ICC Dynamic Number[9 : 16] 8
Application Cryptogram 8
Hash Result 20
1G.12.22.1
Build ICC Dynamic Data as defined in Table 9.34.
Table 9.34—ICC Dynamic Data (RRP)
Data Object Length
Hash Result 20
Terminal Relay Resistance Entropy 4
Device Relay Resistance Entropy 4
Min Time For Processing Relay Resistance APDU 2
Max Time For Processing Relay Resistance APDU 2
Transmission Time For Relay Resistance R-APDU 2

First Generate AC
1G.12.23
Build Dynamic Application Data To Be Signed as defined in Table 9.35.
Table 9.35—Dynamic Application Data To Be Signed
Data Object Length
'05' (signed data format) 1
'01'(hash algorithm indicator) 1
'26' or '34' (length of ICC Dynamic 1
Data)
ICC Dynamic Data 38 or 52
Padding bytes 'BB' Length Of ICC Public Key Modulus – 63 or
Length Of ICC Public Key Modulus – 77
Compute hash over Dynamic Application Data To Be Signed.

1G.12.24
Compute the Signed Dynamic Application Data.
1G.12.25
Build the response.
equal to '9000'.
Tag Length Value
'9F4B' Length Of ICC Public Key Signed Dynamic Application Data
Modulus
1G.12.26
THEN
GOTO 1G.12.27
ELSE
GOTO 1G.12.28
ENDIF

First Generate AC
1G.12.27
Set CDA Transaction Flag (Recovery) (do not commit)
not commit)
commit)
Hash Result (Recovery) := Hash Result (do not commit)
THEN
SetRRP Performed Flag (Recovery) (do not commit)
Terminal Relay Resistance Entropy (Recovery) := Terminal Relay Resistance
Entropy (do not commit)
Device Relay Resistance Entropy (Recovery) := Device Relay Resistance Entropy
(do not commit)
ELSE
(The value of Terminal Relay Resistance Entropy (Recovery) and Device Relay
Resistance Entropy (Recovery) is not relevant)
ENDIF
1G.12.28
characteristics.

First Generate AC
9.3.13. CDA – V1.1/V1.3 Host Backwards Compatibility

1G.13 1.1/1.3
CDA
1
Compute 1.1/1.3
CVR
Encrypt? Yes
Compute variant key
No
5
Encrypt field
6
Include Yes
counters?
No
8 7
without counters with counters

First Generate AC
1G.13
Compute AC
10
CVN = '10'
11
EMV CSK
Derivation
12 13
Set MasterCard
Set EMV CSK in CVN
14
Yes
Include
counters?
15
Set Counters Included In No

First Generate AC
1G.13
16
Build Issuer
Application Data
17
Compute Hash
Result
17.1
No
RRP Yes
Performed?
18 18.1
19
Compute Hash on
Dynamic Application
Data to be Signed
20
Compute RSA
Signature

First Generate AC
1G.13
21
Build response
SW12 = '9000'
22
Recover Torn
Yes Transactions
Enabled?
23
No
24
Commit persistent
data

First Generate AC
1G.13.1
1G.13.2
1G.13.3
THEN
GOTO 1G.13.4
ELSE
GOTO 1G.13.6
ENDIF
1G.13.4
1G.13.5
1G.13.6
THEN
GOTO 1G.13.7
ELSE
GOTO 1G.13.8
ENDIF
1G.13.7
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6

First Generate AC
1G.13.8
Table 9.38—Input for Application Cryptogram without Counters (V1.1/V1.3 Host
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6
1G.13.9

1G.13.10
1G.13.11
THEN
GOTO 1G.13.12
ELSE
GOTO 1G.13.13
ENDIF
1G.13.12
Set EMV CSK Session Key in Cryptogram Version Number
1G.13.13
Set MasterCard Proprietary SKD Session Key in Cryptogram Version Number
1G.13.14
THEN
GOTO 1G.13.15
ELSE
GOTO 1G.13.16
ENDIF

First Generate AC
1G.13.15
1G.13.16
THEN
ELSE
ENDIF

Data Object Length
CVR V1.1/V1.3 6
DAC/ICC Dyn Nr 2
1G.13.17
Tag Length Value
– – PDOL Values
Compute Hash Result

1G.13.17.1
IF RRP Counter = 0
GOTO 1G.13.18
ELSE
GOTO 1G.13.18.1
ENDIF

First Generate AC
1G.13.18
Data Object Length
Hash Result 20
1G.13.18.1
Data Object Length
Hash Result 20
1G.13.19
Data Object Length
Data)

1G.13.20

First Generate AC
1G.13.21
Build the response.
equal to '9000'.
Tag Length Value
'9F4B' Length Of ICC Public Signed Dynamic Application Data
Key Modulus
1G.13.22
THEN
GOTO 1G.13.23
ELSE
GOTO 1G.13.24
ENDIF
1G.13.23
not commit)
commit)
THEN
(do not commit)
ELSE
ENDIF

First Generate AC
1G.13.24
characteristics.

First Generate AC
9.3.14. CDA – V2.1/V2.2 Host Backwards Compatibility

1G.14
2.1/2.2
CDA
1
Compute 2.1/2.2
CVR
Adjust CID
Compute AC
4
Build 2.1/2.2 Issuer
Application Data
5
Compute Hash
Result
5.1
No
RRP Yes
Performed?
6 6.1

First Generate AC
1G.14
1
7
Compute Hash on
Dynamic Application
Data to be Signed
8
Compute RSA
Signature
9
Build response
SW12 = '9000'
10
Recover Torn
Yes
Transactions
Enabled?
11

No
12
Commit persistent
data

First Generate AC
1G.14.1
1G.14.2
THEN
IF 'Type Of Cryptogram' in Cryptogram Information Data = AAC OR 'Type Of
Cryptogram' in Cryptogram Information Data = TC
THEN
ENDIF
Exceeded
ENDIF
1G.14.3
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.1/V2.2 4


1G.14.4
THEN
ELSE
ENDIF

First Generate AC

Data Object Length
CVR V2.1/V2.2 4
DAC/ICC Dyn Nr 2
1G.14.5
Tag Length Value
– – PDOL Values
Compute Hash Result

1G.14.5.1
IF RRP Counter = 0
GOTO 1G.14.6
ELSE
GOTO 1G.14.6.1
ENDIF
1G.14.6
Data Object Length
Hash Result 20

First Generate AC
1G.14.6.1
Data Object Length
Hash Result 20
1G.14.7
Data Object Length
Data)

1G.14.8

First Generate AC
1G.14.9
Build the response.
equal to '9000'.
Tag Length Value
Key Modulus
1G.14.10
THEN
GOTO 1G.14.11
ELSE
GOTO 1G.14.12
ENDIF
1G.14.11
not commit)
commit)
commit)
THEN
(do not commit)
ELSE
ENDIF

First Generate AC
1G.14.12
characteristics.

First Generate AC
9.3.15. CDA – V2.05 Host Backwards Compatibility

1G.15
2.05
CDA
1
Compute 2.05
CVR
Adjust CID
Compute AC
4
Build 2.05 Issuer
Application Date
5
Compute Hash
Result
5.1
No
RRP Yes
Performed?
6 6.1

First Generate AC
1G.15
1
7
Compute Hash on
Dynamic Application
Data to be Signed
8
Compute RSA
Signature
9
Build response
SW12 = '9000'
10
Recover Torn
Yes
Transactions
Enabled?
11
No
12
Commit persistent
data

First Generate AC
1G.15.1
1G.15.2
IFPIN Try Counter = '00' AND 'Type Of Cryptogram' in Cryptogram Information
Data = AAC
THEN
Exceeded
ENDIF
1G.15.3
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.05 4


1G.15.4
THEN
ELSE
ENDIF

First Generate AC

Data Object Length
'08' 1
CVR V2.05 4
DAC/ICC Dyn Nr 2
1G.15.5
Tag Length Value
– – PDOL Values
Compute Hash Result

1G.15.5.1
IF RRP Counter = 0
GOTO 1G.15.6
ELSE
GOTO 1G.15.6.1
ENDIF
1G.15.6
Table 9.55—ICC Dynamic Data
Data Object Length
Hash Result 20

First Generate AC
1G.15.6.1
Data Object Length
Hash Result 20
1G.15.7
Data Object Length
Data)

1G.15.8

First Generate AC
1G.15.9
Build the response.
equal to '9000'.
Tag Length Value
Modulus
1G.15.10
THEN
GOTO 1G.15.11
ELSE
GOTO 1G.15.12
ENDIF
1G.15.11
not commit)
commit)
THEN
(do not commit)
ELSE
ENDIF

First Generate AC
1G.15.12
characteristics.

Second Generate AC
10. Second Generate AC

10.1. Second Generate AC Command Message ................................................. 219
10.3. Second Generate AC Processing ............................................................... 221
10.3.1. Start .................................................................................................... 221
10.3.2. Unable To Go Online ......................................................................... 229
10.3.3. Issuer Authentication Data Present .................................................... 233
10.3.4. Issuer Authentication Data Not Present ............................................. 253
10.3.5. Decision AAC .................................................................................... 265
10.3.6. Decision TC ....................................................................................... 270

Second Generate AC
Second Generate AC Command Message
10.1. Second Generate AC Command Message

The second GENERATE AC command message is specified in Table 10.1.
Table 10.1—Second Generate AC Command Message
Code Value
CLA '80'
INS 'AE'
P2 '00'
Lc Var.
Data Transaction Related Data
Le '00'

Table 10.2—Reference Control Parameter Coding for the Second Generate AC
x x 'Cryptogram Type'
0 0 AAC
0 1 TC
1 0 Not Allowed
1 1 RFU
0 Other values RFU
x 'Combined DDA/AC Generation Requested'
0 0 0 0 Other values RFU

Second Generate AC

Table 10.3—Local Transient Data for the Second Generate AC
ARPC Response Code
CDOL2 Related Data
CVR V2.05
CVR V2.1/V2.2
CVR V1.1/V1.3
DAC/ICC Dyn Nr
Hash Result
ICC Dynamic Data
Return Value

Second Generate AC
Second Generate AC Processing
10.3. Second Generate AC Processing
10.3.1. Start
2G.1
2nd GENERATE AC
1
Flag
3
2
Build response
P1-P2 NOK
SW12 = '6A86'
OK
4
Partial
No authorization Yes
support
5 9
Test Lc NOK NOK Test Lc
OK
7 6
OK
Retrieve transaction Build response
related data without SW12 = '6700' 10
Amount Authorized
Retrieve transaction
8 related data with
Amount Authorized
Amount Authorized =
Amount Authorized 1
Amount Other =
Amount Other 1

Second Generate AC
2G.1
1
11
Copy Accs and Cntrs to

Accs Temp and Cntrs
Temp
12
Copy PTC to CVR
13
No PTC = 0 Yes
15 14
Clear PTL Exceeded in

Set PTL Exceeded in CVR
CVR
16
Copy Script Counter to
CVR
17
Copy Script Received from
PTH to CVR
18
Copy Script Failed from
PTH to CVR

Second Generate AC
2G.1
2
19
No MTA activated
Yes
20
Trans
Currency Code
No
= MTA Currency
Code
Yes
21
Clear MTA exceeded in
CVR
22
Check for CVM
transaction
23
No CVM transaction? Yes
24 26 25
Amount Amount
Set MTA Exceeded
Authorized > Yes Yes Authorized >
in CVR
MTA NoCVM MTA CVM
No No

Second Generate AC
2G.1
3
27
Partial
No authorization Yes
support
28
Yes
Amount Authorized <=
Amount Authorized 1
No
29
Amount Other <= No

Amount Other 1
Yes
30
App blocked? Yes
No
31
Auth. Resp.
Yes
Code
is Y3 or Z3
No
32
Issuer
No Authentication Yes
Data present
Unable to go Issuer Auth. Issuer Auth.

AAC decided
online Data not present Data present

Second Generate AC
2G.1.1
Challenge Flag
2G.1.2
IF ('Cryptogram Type' in Reference Control Parameter ≠ AAC AND
'Cryptogram Type' in Reference Control Parameter ≠ TC)
OR P2 ≠ '00'
THEN
GOTO 2G.1.3
ELSE
GOTO 2G.1.4
ENDIF
2G.1.3
2G.1.4
IF 'Partial Authorization' in Application Control is set
THEN
GOTO 2G.1.9
ELSE
GOTO 2G.1.5
ENDIF
2G.1.5
IF Lc ≠ 29
THEN
GOTO 2G.1.6
ELSE
GOTO 2G.1.7
ENDIF
2G.1.6
2G.1.7
CDOL2 Related Data := Transaction Related Data[1 : 29]

Issuer Authentication Data := Transaction Related Data[1 : 10]
Authorisation Response Code := Transaction Related Data[11 : 12]
Unpredictable Number := Transaction Related Data[18 : 21]
2G.1.8
Amount, Authorized (Numeric) := Amount, Authorized 1
Amount, Other (Numeric) := Amount, Other 1

Second Generate AC
2G.1.9
IF Lc ≠ 41
THEN
GOTO 2G.1.6
ELSE
GOTO 2G.1.10
ENDIF
2G.1.10
CDOL2 Related Data := Transaction Related Data[1 : 41]

Issuer Authentication Data := Transaction Related Data[1 : 10]
Authorisation Response Code := Transaction Related Data[11 : 12]
Unpredictable Number := Transaction Related Data[18 :21]
Amount, Authorized (Numeric) := Transaction Related Data[30 : 35]
Amount, Other (Numeric) := Transaction Related Data[36 : 41]
2G.1.11
2G.1.12
2G.1.13
IF 'Low Order Nibble Of PIN Try Counter' in PIN Try Counter = 0000b
THEN
GOTO 2G.1.14
ELSE
GOTO 2G.1.15
ENDIF
2G.1.14
2G.1.15
Clear 'PTL Exceeded' in Card Verification Results
2G.1.16
in Script Counter
2G.1.17
'Script Received' in Card Verification Results := 'Script Received' in Previous
Transaction History

Second Generate AC
2G.1.18
'Script Failed' in Card Verification Results := 'Script Failed' in Previous Transaction
History
2G.1.19
IF 'MTA Check' in Application Control is set
THEN
GOTO 2G.1.20
ELSE
GOTO 2G.1.27
ENDIF
2G.1.20
IF Transaction Currency Code = MTA Currency Code
THEN
GOTO 2G.1.21
ELSE
GOTO 2G.1.27
ENDIF
2G.1.21
Clear 'MTA Limit Exceeded' in Card Verification Results
2G.1.22
2G.1.23
IF Return Value
THEN
GOTO 2G.1.25
ELSE
GOTO 2G.1.24
ENDIF
2G.1.24
IF Amount, Authorized (Numeric) > MTA NoCVM
THEN
GOTO 2G.1.26
ELSE
GOTO 2G.1.27
ENDIF
2G.1.25
THEN
GOTO 2G.1.26
ELSE
GOTO 2G.1.27
ENDIF
2G.1.26

Second Generate AC
2G.1.27
IF 'Partial Authorization' in Application Control is set
THEN
GOTO 2G.1.28
ELSE
GOTO 2G.1.30
ENDIF
2G.1.28
IF Amount, Authorized (Numeric)  Amount, Authorized 1
THEN
GOTO 2G.1.29
ELSE
ENDIF
2G.1.29
IF Amount, Other (Numeric)  Amount, Other 1
THEN
GOTO 2G.1.30
ELSE
ENDIF
2G.1.30
THEN
ELSE
GOTO 2G.1.31
ENDIF
2G.1.31
IF Authorisation Response Code = Y3 OR Authorisation Response Code = Z3
THEN
GOTO 2G.2.1 (Unable to go online)
ELSE
GOTO 2G.1.32
ENDIF
2G.1.32
IF Issuer Authentication Data = '00000000000000000000'
THEN
Issuer Authentication Data is not present
GOTO 2G.4.1
ELSE
Issuer Authentication Data is present
GOTO 2G.3.1
ENDIF

Second Generate AC
10.3.2. Unable To Go Online

2G.2 Unable to go
online
Set Unable to go online indicated in CVR
2
Last Online Transaction Not Completed in PTH :=
Last Online Transaction Not Completed in CVR
3
Auth. Resp.
No
Code is Y3 and
TC
Yes
9
Accs
Yes
and Cntrs are
saved in 1st GEN
AC
No
4
Update temporary
accumulators and
counters
5
Check accumulators and
counters limits and set
and reset CVR
1
AAC decided

Second Generate AC
2G.2
8
RRP not
performed and
Yes
Decline if RRP
not performed
No
Yes CVR & CIAC-Default No

= '000000'
Save active accumulators

and counters
TC decided AAC decided

Second Generate AC
2G.2.1
Set 'Unable To Go Online Indicated' in Card Verification Results
2G.2.2
'Last Online Transaction Not Completed' in Previous Transaction History := 'Last
Online Transaction Not Completed' in Card Verification Results (do not commit)
2G.2.3
IF Authorisation Response Code ≠ Y3 OR 'Cryptogram Type' in Reference Control
Parameter = AAC
THEN
ELSE
GOTO 2G.2.9
ENDIF
2G.2.9
set
THEN
GOTO 2G.2.5
ELSE
GOTO 2G.2.4
ENDIF
2G.2.4
2G.2.5
CALL CheckAccsCntrsLimitsSetResetCVR( )
2G.2.8
'Decline If Unable To Go Online And RRP Not Performed' in Application
Control is set
THEN
ELSE
GOTO 2G.2.6
ENDIF
2G.2.6
Default) = '000000'
THEN
GOTO 2G.2.7
ELSE
ENDIF

Second Generate AC
2G.2.7

Second Generate AC
10.3.3. Issuer Authentication Data Present

2G.3
Issuer Authentication
Data Present
Set Issuer Auth Performed in CVR
EMV CSK
Derivation
3 4
Verify ARPC with Verify ARPC with

SKAC MKAC
5
ARPC NOK
Verification?
OK
7 6
Set Issuer Auth Failed in CVR
AC Session Key Counter = '0000' Set Issuer Auth Failed in PTH
Last Online Transaction Not
Completed in PTH := Last
8 Online Transaction Not
Clear Issuer Auth Failed in CVR and PTH Completed in CVR
Clear Last Online Transaction Not
Completed in PTH and CVR
1
AAC decided

Second Generate AC
2G.3
9
Reset Script
Counter with online Yes
response
10
Script Counter = '00'
No Script Counter in CVR = '0'
11
Max Number of
No days offline
activated?
Yes
12
Check format of
Transaction Date
13
Format of OK
Transaction Date
14
Last Online Txn Date =
NOK

Second Generate AC
2G.3
2
15
M/Chip 2 No
Yes
16
Clear Script Received in CVR and PTH 3
Clear Script Failed in CVR and PTH
17
No Terminal
requests TC
Yes
18
No
Issuer
requests TC
Yes
19
Acc 1 = '00 … 0'
Acc 2 = '00 … 0'
AAC decided
Cntr 1 = '00'
Cntr 2 = '00'
Acc 1 Temp = '00 … 0'
Acc 2 Temp = '00 … 0'
Cntr 1 Temp = '00'
Cntr 2 Temp = '00'
20
and reset CVR
TC decided

Second Generate AC
2G.3
3
21
Last Online ATC = ATC
22
Yes Set Go Online No
23 24
Set Go Online On Next Clear Go Online On Next

Transaction in CVR and PTH Transaction in CVR and PTH
25
Yes Update PTC No
26
PTC = PTC in ARPC Resp Code

PTC in CVR = PTC
27
PTC = 0 No
Yes
28 29
Set PTL Exceeded in CVR Clear PTL Exceeded in CVR

Second Generate AC
2G.3
30
Issuer Updates Yes
Received?
No
31 Issuer Updates Received

Decline if Issuer
Updates not Yes
received?
No AAC decided
32
Clear Script Received in CVR and PTH
33
Update
Accs/Cntrs
Set accs/cntrs to upper limits Reset accs/cntrs to zero Add transaction to Accs/Cntrs Do not update
5 6 7 8

Second Generate AC
2G.3
Set accs/cntrs to
upper limits 5
34
Acc 1 eligible ? Yes

35
Acc 1 = Acc 1 Upper Limit
Acc 1 Temp = Acc1 Upper Limit
No
36

37
Acc 2 Temp = Acc 2 Upper Limit
No
38
Cntr 1 eligible Yes

39
Cntr 1 = Cntr 1 Upper Limit
Cntr 1 Temp = Cntr 1 Upper Limit
No
40
Cntr 2 eligible Yes

41
No

Second Generate AC
2G.3
Reset accs/cntrs
to zero 6
42
Acc 1 eligible Yes

43
Acc 1 = '000 ...0'
Acc 1 Temp = '000 ...0'
No
44
Acc 2 eligible Yes

45
Acc 2 = '000 ...0'
Acc 2 Temp = '000 ...0'
No
46
Cntr 1 eligible Yes

47
Cntr 1 = '00'
Cntr 1 Temp = '00'
No
48
Cntr 2 Eligible Yes

49
Cntr 2 = '00'
No
Cntr 2 Temp = '00'

Second Generate AC
2G.3 Add transaction

To Accs/Cntrs 7
50
Acc 1 eligible No 51
Clear Acc 1 Active Flag

Yes
52

Yes
54
Cntr 1 eligible No 55
Clear Cntr 1 Active Flag

Yes
56
Cntr 2 Eligible No 57

Yes
58
Update temporary
accumulators and counters
59
and counters

Second Generate AC
2G.3
8
60
and reset CVR
61
Terminal
No
requests TC
Yes
62
Issuer
No Yes
requests TC
AAC decided TC decided

Second Generate AC
2G.3
Issuer Updates Received
63
Terminal and Issuer No
both request TC or AAC
Yes
64

Clear Script Failed Flag
AAC decided
65
Increment Script Counter
66
Copy Script Counter to CVR

Second Generate AC
2G.3
67
Process Issuer Updates
68
Check temp accumulators
and temp counters limits and
set and reset CVR
69
Issuer requests TC No
Yes
TC decided AAC decided

Second Generate AC
2G.3.1
Set 'Issuer Authentication Performed' in Card Verification Results.
2G.3.2
THEN
GOTO 2G.3.3
ELSE
GOTO 2G.3.4
ENDIF
2G.3.3
Verify 'Authorization Response Cryptogram' with AC Session Key
2G.3.4
Verify 'Authorization Response Cryptogram' with AC Master Key
2G.3.5
IF 'Authorization Response Cryptogram' successfully verified
THEN
GOTO 2G.3.7
ELSE
GOTO 2G.3.6
ENDIF
2G.3.6
Set 'Issuer Authentication Failed' in Card Verification Results
Set 'Issuer Authentication Failed' in Previous Transaction History
GOTO 2G.5.1(AAC Decided)
2G.3.7
AC Session Key Counter := '0000'
2G.3.8
Clear 'Issuer Authentication Failed' in Previous Transaction History (do not commit)
Clear 'Last Online Transaction Not Completed' in Previous Transaction History (do
not commit)
Clear 'Last Online Transaction Not Completed' in Card Verification Results
2G.3.9
IF 'Reset Script Counter With Online Response' in Application Control is set
THEN
GOTO 2G.3.10
ELSE
GOTO 2G.3.11
ENDIF

Second Generate AC
2G.3.10
Script Counter := '00' (do not commit)
Clear 'Low Order Nibble Of Script Counter' in Card Verification Results
2G.3.11
THEN
GOTO 2G.3.12
ELSE
GOTO 2G.3.15
ENDIF
2G.3.12
2G.3.13
IF Return Value
THEN
GOTO 2G.3.14
ELSE
GOTO 2G.3.15
ENDIF
2G.3.14
Last Online Transaction Date := Current Date In Days (do not commit)
2G.3.15
Backwards Compatibility OR 'Issuer Host Backwards Compatibility' in
Application Control = V2.05 Host Backwards Compatibility
THEN
GOTO 2G.3.16
ELSE
GOTO 2G.3.21
ENDIF
2G.3.16
Clear 'Script Received' in Card Verification Results
Clear 'Script Failed' in Card Verification Results
Clear 'Script Received' in Previous Transaction History (do not commit)
Clear 'Script Failed' in Previous Transaction History (do not commit)
2G.3.17
IF 'Cryptogram Type' in Reference Control Parameter = TC
THEN
GOTO 2G.3.18
ELSE
ENDIF

Second Generate AC
2G.3.18
IF 'ARPC Response Code' in Issuer Authentication Data is '3030' OR 'ARPC Response
Code' in Issuer Authentication Data is '3031' OR 'ARPC Response Code' in Issuer
Authentication Data is '3038'
THEN
GOTO 2G.3.19
ELSE
ENDIF
2G.3.19
Accumulator 1 Amount := '000000000000' (do not commit)
Counter 1 Number := '00' (do not commit)
2G.3.20
2G.3.21
Last Online ATC := Application Transaction Counter (do not commit)
2G.3.22
IF 'Set Go Online On Next Transaction' in ARPC Response Code is set
THEN
GOTO 2G.3.23
ELSE
GOTO 2G.3.24
ENDIF
2G.3.23
Set 'Go Online On Next Transaction Was Set' in Card Verification Results
Set 'Go Online On Next Transaction' in Previous Transaction History (do not commit)
2G.3.24
Clear 'Go Online On Next Transaction Was Set' in Card Verification Results
Clear 'Go Online On Next Transaction' in Previous Transaction History (do not
commit)
2G.3.25
IF 'Update PIN Try Counter' in ARPC Response Code is set
THEN
GOTO 2G.3.26
ELSE
GOTO 2G.3.30
ENDIF

Second Generate AC
2G.3.26
'Low Order Nibble Of PIN Try Counter' in PIN Try Counter := 'PIN Try Counter' in
ARPC Response Code (do not commit)
2G.3.27
THEN
GOTO 2G.3.28
ELSE
GOTO 2G.3.29
ENDIF
2G.3.28
2G.3.29
Clear 'PTL Exceeded' in Card Verification Results
2G.3.30
IF Issuer Updates Received Flag is set
THEN
GOTO 2G.3.63
ELSE
GOTO 2G.3.31
ENDIF
2G.3.31
IF 'Decline If Issuer Updates Not Received' in ARPC Response Code is set
THEN
ELSE
GOTO 2G.3.32
ENDIF
2G.3.32

Second Generate AC
2G.3.33
IF 'Update Accumulators/Counters' in ARPC Response Code = Do Not Update
Accumulators/Counters
THEN
GOTO 2G.3.60
in ARPC Response Code = Set
ELSE IF 'Update Accumulators/Counters'
Accumulators/Counters To Upper Offline Limits
THEN
GOTO 2G.3.34
ELSE IF 'Update Accumulators/Counters' in ARPC Response Code = Reset
Accumulators/Counters To Zero
THEN
GOTO 2G.3.42
ELSE
GOTO 2G.3.50
ENDIF
ENDIF
ENDIF
2G.3.34
IF 'Accumulator 1 Not Eligible' in ARPC Response Code is set
THEN
GOTO 2G.3.36
ELSE
GOTO 2G.3.35
ENDIF
2G.3.35
Accumulator 1 Amount := Accumulator 1 Upper Limit (do not commit)
Accumulator 1 Amount Temp := Accumulator 1 Upper Limit
2G.3.36
THEN
GOTO 2G.3.38
ELSE
GOTO 2G.3.37
ENDIF
2G.3.37
2G.3.38
IF 'Counter 1 Not Eligible' in ARPC Response Code is set
THEN
GOTO 2G.3.40
ELSE
GOTO 2G.3.39
ENDIF

Second Generate AC
2G.3.39
Counter 1 Number := Counter 1 Upper Limit (do not commit)
Counter 1 Number Temp := Counter 1 Upper Limit
2G.3.40
THEN
GOTO 2G.3.60
ELSE
GOTO 2G.3.41
ENDIF
2G.3.41
2G.3.42
THEN
GOTO 2G.3.44
ELSE
GOTO 2G.3.43
ENDIF
2G.3.43
2G.3.44
THEN
GOTO 2G.3.46
ELSE
GOTO 2G.3.45
ENDIF
2G.3.45
2G.3.46
THEN
GOTO 2G.3.48
ELSE
GOTO 2G.3.47
ENDIF
2G.3.47

Second Generate AC
2G.3.48
THEN
GOTO 2G.3.60
ELSE
GOTO 2G.3.49
ENDIF
2G.3.49
2G.3.50
THEN
GOTO 2G.3.51
ELSE
GOTO 2G.3.52
ENDIF
2G.3.51
Clear Accumulator 1 Active Flag
2G.3.52
THEN
GOTO 2G.3.53
ELSE
GOTO 2G.3.54
ENDIF
2G.3.53
2G.3.54
THEN
GOTO 2G.3.55
ELSE
GOTO 2G.3.56
ENDIF
2G.3.55
Clear Counter 1 Active Flag
2G.3.56
THEN
GOTO 2G.3.57
ELSE
GOTO 2G.3.58
ENDIF

Second Generate AC
2G.3.57
2G.3.58
2G.3.59
2G.3.60
2G.3.61
THEN
GOTO 2G.3.62
ELSE
ENDIF
2G.3.62
IF 'Approve Online Transaction' in ARPC Response Code is set
THEN
ELSE
ENDIF
2G.3.63
IF ('Cryptogram Type' in Reference Control Parameter = TC AND 'Approve Online
Transaction' in ARPC Response Code is set) OR ('Cryptogram Type' in Reference
Control Parameter = AAC AND 'Approve Online Transaction' in ARPC Response
Code is not set)
THEN
GOTO 2G.3.64
ELSE
ENDIF
2G.3.64
Clear Script Failed Flag
2G.3.65
THEN
ELSE
commit)
ENDIF

Second Generate AC
2G.3.66
in Script Counter
2G.3.67
CALL ProcessIssuerUpdates( )
2G.3.68
CALL CheckTempAccsCntrsLimitsSetResetCVR( )
2G.3.69
IF 'Approve Online Transaction' in ARPC Response Code is set
THEN
ELSE
ENDIF

Second Generate AC
10.3.4. Issuer Authentication Data Not Present

2G.4
Issuer Authentication
Data Not Present
1
Accept without No
ARPC
2
Yes
Last Online Transaction Not
3
Completed in PTH := Last
Clear Last Online Transaction Not Online Transaction Not
Completed in PTH and CVR Completed in CVR
4
Terminal
No
requests TC
Yes
5
AAC decided
Clear Issuer Auth Failed in CVR and PTH
Clear Script Received in CVR and PTH
6
Reset Script
Counter with online Yes
response
7
Script Counter = '00'
No Script Counter in CVR = '0'

Second Generate AC
2G.4
Max Number of
No days offline
activated?
Yes
9
Check format of
Transaction Data
10
Format of OK
Transaction Date
11
Last Online Txn Date =
NOK Current Date In Days
12
Update
Accs/Cntrs
Set accs/cntrs to upper limits Reset accs/cntrs to zero Add transaction to Accs/Cntrs Do not update
2 3 4 5

Second Generate AC
2G.4
Set accs/cntrs to
upper limits 2
13

14
No
Acc 1 Temp = Acc1 Upper Limit
15

16
No Acc 2 Temp = Acc 2 Upper Limit
17
Cntr 1 eligible Yes
18
No
19
Cntr 2 eligible Yes 20

No

Second Generate AC
2G.4
Reset accs/cntrs
to zero 3
21
Acc 1 eligible Yes

22
Acc 1 = '000 ...0'
No
Acc 1 Temp = '000 ...0'
23
Acc 2 eligible Yes

24
Acc 2 = '000 ...0'
No Acc 2 Temp = '000 ...0'
25
Cntr 1 eligible Yes

26
Cntr 1 = '00'
No
Cntr 1 Temp = '00'
27
Cntr 2 Eligible Yes

29
Cntr 2 = '00'
No
Cntr 2 Temp = '00'

Second Generate AC
2G.4 Add transaction

To Accs/Cntrs 3
29

Yes
31

Yes
33
Cntr 1 eligible No 34

Yes
35
Cntr 2 Eligible No
36

Yes
37
Update temporary
accumulators and counters
38
and counters

Second Generate AC
2G.4
5
39
counters limits and set and
reset CVR
40
Yes Set Go Online No
41 42
Set Go Online On Next Clear Go Online On Next

Transaction in CVR and PTH Transaction in CVR and PTH
43
Last Online ATC = ATC
44
Issuer Yes
No
requests TC
AAC decided TC decided

Second Generate AC
2G.4.1
IF 'Accept Online Transactions Without ARPC' in Application Control is set
THEN
GOTO 2G.4.3
ELSE
GOTO 2G.4.2
ENDIF
2G.4.2
2G.4.3
Clear 'Last Online Transaction Not Completed' in Previous Transaction History (do
not commit)
Clear 'Last Online Transaction Not Completed' in Card Verification Results
2G.4.4
THEN
GOTO 2G.4.5
ELSE
ENDIF
2G.4.5
Clear 'Issuer Authentication Failed' in Previous Transaction History (do not commit)
2G.4.6
IF 'Reset Script Counter With Online Response' in Application Control is set
THEN
GOTO 2G.4.7
ELSE
GOTO 2G.4.8
ENDIF
2G.4.7
Script Counter := '00' (do not commit)
Clear 'Low Order Nibble Of Script Counter' in Card Verification Results

Second Generate AC
2G.4.8
THEN
GOTO 2G.4.9
ELSE
GOTO 2G.4.12
ENDIF
2G.4.9
2G.4.10
IF Return Value
THEN
GOTO 2G.4.11
ELSE
GOTO 2G.4.12
ENDIF
2G.4.11
Last Online Transaction Date := Current Date In Days (do not commit)
2G.4.12
IF 'Update Accumulators/Counters' in Default ARPC Response Code = Do Not Update
Accumulators/Counters
THEN
GOTO 2G.4.39
in Default ARPC Response Code = Set
ELSE IF 'Update Accumulators/Counters'
Accumulators/Counters To Upper Offline Limits
THEN
GOTO 2G.4.13
ELSE IF 'Update Accumulators/Counters' in Default ARPC Response Code = Reset
Accumulators/Counters To Zero
THEN
GOTO 2G.4.21
ELSE
GOTO 2G.4.29
ENDIF
ENDIF
ENDIF
2G.4.13
IF 'Accumulator 1 Not Eligible' in Default ARPC Response Code is set
THEN
GOTO 2G.4.15
ELSE
GOTO 2G.4.14
ENDIF

Second Generate AC
2G.4.14
2G.4.15
THEN
GOTO 2G.4.17
ELSE
GOTO 2G.4.16
ENDIF
2G.4.16
2G.4.17
IF 'Counter 1 Not Eligible' in Default ARPC Response Code is set
THEN
GOTO 2G.4.19
ELSE
GOTO 2G.4.18
ENDIF
2G.4.18
2G.4.19
THEN
GOTO 2G.4.39
ELSE
GOTO 2G.4.20
ENDIF
2G.4.20
2G.4.21
THEN
GOTO 2G.4.23
ELSE
GOTO 2G.4.22
ENDIF
2G.4.22

Second Generate AC
2G.4.23
THEN
GOTO 2G.4.25
ELSE
GOTO 2G.4.24
ENDIF
2G.4.24
2G.4.25
THEN
GOTO 2G.4.27
ELSE
GOTO 2G.4.26
ENDIF
2G.4.26
2G.4.27
THEN
GOTO 2G.4.39
ELSE
GOTO 2G.4.28
ENDIF
2G.4.28
2G.4.29
THEN
GOTO 2G.4.30
ELSE
GOTO 2G.4.31
ENDIF
2G.4.30

Second Generate AC
2G.4.31
THEN
GOTO 2G.4.32
ELSE
GOTO 2G.4.33
ENDIF
2G.4.32
2G.4.33
THEN
GOTO 2G.4.34
ELSE
GOTO 2G.4.35
ENDIF
2G.4.34
2G.4.35
THEN
GOTO 2G.4.36
ELSE
GOTO 2G.4.37
ENDIF
2G.4.36
2G.4.37
2G.4.38
2G.4.39
2G.4.40
IF 'Set Go Online On Next Transaction' in Default ARPC Response Code is set
THEN
GOTO 2G.4.41
ELSE
GOTO 2G.4.42
ENDIF

Second Generate AC
2G.4.41
Set 'Go Online On Next Transaction Was Set' in Card Verification Results
Set 'Go Online On Next Transaction' in Previous Transaction History (do not commit)
2G.4.42
Clear 'Go Online On Next Transaction Was Set' in Card Verification Results
Clear 'Go Online On Next Transaction' in Previous Transaction History (do not
commit)
2G.4.43
Last Online ATC := Application Transaction Counter (do not commit)
2G.4.44
IF 'Approve Online Transaction' in Default ARPC Response Code is set
THEN
ELSE
ENDIF

Second Generate AC
10.3.5. Decision AAC

2G.5
AAC
dec
1
Set AAC decided in
CVR
1a 1b
Combined Set CDA returned in
Yes
DDA/AC? CVR
No
2
Set AAC decided in
CID
No AAC Logging?
Yes
4
Create Current
Transaction Log
Record
Pre-logging? Yes
6
No 7 Overwrite last record in
Add Current Transaction Transaction Log File with
Log Record to Current Transaction Log
Transaction Log File Record

Second Generate AC
2G.5
1
8
Combined
No
DDA/AC
Yes
9
Terminal
No requests
AAC?
Yes
11
Host
compatibility
M4R2 2.1/2.2 2.05 1.1/1.3

CDA CDA CDA CDA
12
Host
compatibility
M4R2 2.1/2.2 2.05 1.1/1.3

AC AC AC AC

Second Generate AC
2G.5.1
'AC Returned In Second Generate AC' in Card Verification Results := AAC Returned
In Second Generate AC
2G.5.1a
AND 'Cryptogram Type' in Reference Control Parameter = AAC
THEN
GOTO 2G.5.1b
ELSE
GOTO 2G.5.2
ENDIF
2G.5.1b
Set 'Combined DDA/AC Generation Returned In Second Generate AC' in Card
2G.5.2
2G.5.3
IF 'AAC Logging' in Application Control is set
THEN
GOTO 2G.5.4
ELSE
GOTO 2G.5.8
ENDIF
2G.5.4
Data Object Length
Transaction Date 3
Transaction Time 3

Second Generate AC
2G.5.5
THEN
GOTO 2G.5.6
ELSE
GOTO 2G.5.7
ENDIF
2G.5.6
The most recent record in the Transaction Log File is overwritten with the Temp
Transaction Log Record (do not commit).
2G.5.7
commit).
2G.5.8
THEN
GOTO 2G.5.9
ELSE
GOTO 2G.5.12
ENDIF
2G.5.9
THEN
GOTO 2G.5.11
ELSE
GOTO 2G.5.12
ENDIF

Second Generate AC
2G.5.11
THEN
ELSE
THEN
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF
2G.5.12
THEN
ELSE
THEN
GOTO 2G.10.1 (No CDA – V2.05 host backwards compatibility)
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF

Second Generate AC
10.3.6. Decision TC
2G.6 TC
dec
1
Set TC decided in
CVR
1a 1b
Combined Set CDA returned in
Yes
DDA/AC? CVR
No
Set TC decided in CID
No TC Logging?
Yes
4
Create Current
Transaction Log
Record
Pre-logging? Yes
6
No
7 Overwrite last record in
Add Current Transaction Transaction Log File with
Log Record to Current Transaction Log
Transaction Log File Record

Second Generate AC
2G.6
1
12
Enable
alternate Yes
interface? 13
Enable interface
No
No
Combined
DDA/AC
Yes
10
Host
compatibility
M4R2 2.1/2.2 2.05 1.1/1.3

CDA CDA CDA CDA
11
Host
compatibility
M4R2 2.1/2.2 2.05 1.1/1.3

AC AC AC AC

Second Generate AC
2G.6.1
'AC Returned In Second Generate AC' in Card Verification Results := TC Returned In
Second Generate AC
2G.6.1a
THEN
GOTO 2G.6.1b
ELSE
GOTO 2G.6.2
ENDIF
2G.6.1b
Set 'Combined DDA/AC Generation Returned In Second Generate AC' in Card
2G.6.2
'Type Of Cryptogram' in Cryptogram Information Data := TC
2G.6.3
IF 'TC Logging' in Application Control is set
THEN
GOTO 2G.6.4
ELSE
GOTO 2G.6.12
ENDIF
2G.6.4
Data Object Length
Transaction Date 3
Transaction Time 3

Second Generate AC
2G.6.5
THEN
GOTO 2G.6.6
ELSE
GOTO 2G.6.7
ENDIF
2G.6.6
The most recent record in the Transaction Log File is overwritten with the Temp
Transaction Log Record (do not commit).
2G.6.7
commit).
2G.6.12
IF 'Enable Alternate Interface After TC Generated' in Application Control is set
THEN
GOTO 2G.6.13
ELSE
GOTO 2G.6.8
ENDIF
2G.6.13
Enabled
2G.6.8
THEN
GOTO 2G.6.10
ELSE
GOTO 2G.6.11
ENDIF

Second Generate AC
2G.6.10
THEN
ELSE
THEN
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF
2G.6.11
THEN
ELSE
THEN
GOTO 2G.10.1 (No CDA – V2.05 host backwards compatibility)
ELSE
THEN
ELSE
ENDIF
ENDIF
ENDIF

Second Generate AC
10.3.7. No CDA – No Host Backwards Compatibility

2G.7
M4R2
AC
2
Session Key
Derivation
CTRAC ≥ LIMAC Yes
4
No
Set AC Session Key
6
Counter Error Limit
Increment CTRAC Exceeded in Security
Limits Status
7 5
Derive AC Session Build response
Key (MasterCard SW12 = '6985'
Proprietary)

Second Generate AC
2G.7
1
8 9
10
No
Encrypt field
11
No
Include Yes
counters?
12
Include Last
15 No Online ATC? Yes
Build input to AC
without counters
13 14
Last Online ATC
16
Compute AC
17
CVN = '10'

Second Generate AC
2G.7
2
18
EMV CSK
Derivation
19 20
Set MasterCard
Set EMV CSK in CVN
21
Yes
Include
counters?
22
No
23
Set DAC / ICC

Dynamic Number

Second Generate AC
2G.7
24
Include
in IAD?
25 26

27
Build response
SW12 = '9000'
28
Recover Torn
Yes Transactions
Enabled?
29
No
30
Commit persistent
data

Second Generate AC
2G.7.1
2G.7.2
IF 'Session Key Derivation' in Application Control = MasterCard Proprietary SKD
THEN
GOTO 2G.7.3
ELSE
GOTO 2G.7.8
ENDIF
2G.7.3
THEN
GOTO 2G.7.4
ELSE
GOTO 2G.7.6
ENDIF
2G.7.4
2G.7.5
2G.7.6
2G.7.7
Derive AC Session Key using the MasterCard Proprietary method
2G.7.8
THEN
GOTO 2G.7.9
ELSE
GOTO 2G.7.11
ENDIF
2G.7.9
2G.7.10

Second Generate AC
2G.7.11
THEN
GOTO 2G.7.12
ELSE
GOTO 2G.7.15
ENDIF
2G.7.12
THEN
GOTO 2G.7.14
ELSE
GOTO 2G.7.13
ENDIF
2G.7.13
Data Object Length
Transaction Date 3
Transaction Type 1

Second Generate AC
2G.7.14
ATC
Data Object Length
Transaction Date 3
Transaction Type 1
Last Online ATC 2
2G.7.15
Table 10.8—Input for Application Cryptogram without Counters and Last
Online ATC
Data Object Length
Transaction Date 3
Transaction Type 1
2G.7.16
2G.7.17

Second Generate AC
2G.7.18
THEN
GOTO 2G.7.19
ELSE
GOTO 2G.7.20
ENDIF
2G.7.19
CSK Session Key
2G.7.20
2G.7.21
THEN
GOTO 2G.7.22
ELSE
GOTO 2G.7.23
ENDIF
2G.7.22
2G.7.23
THEN
ELSE
ENDIF
2G.7.24
THEN
GOTO 2G.7.25
ELSE
GOTO 2G.7.26
ENDIF

Second Generate AC
2G.7.25
Data Object Length
DAC/ICC Dyn Nr 2
Last Online ATC 2
2G.7.26
Data Object Length
DAC/ICC Dyn Nr 2
2G.7.27
Build the response.
'77' containing the TLV coded data objects specified in Table 10.11 followed by
Tag Length Value
2G.7.28
THEN
GOTO 2G.7.29
ELSE
GOTO 2G.7.30
ENDIF

Second Generate AC
2G.7.29
not commit)
commit)
2G.7.30
Commit all the persistent data objects, that have a new value assigned but that have
characteristics.

Second Generate AC

Compatibility
2G.8
1.1/1.3
AC
1
Compute 1.1/1.3
CVR
3
Session Key
EMV CSK
Derivation
CTRAC ≥ LIMAC Yes
5
No Set AC Session Key
7 Counter Error Limit
Exceeded in Security
Increment CTRAC Limits Status
8 6
Proprietary)

Second Generate AC
2G.8
1
9 10
11
No
Encrypt field
12
Include Yes
counters?
No
14 13
without counters with counters
15
Compute AC
16
CVN = '10'

Second Generate AC
2G.8
2
17
EMV CSK
Derivation
18 19
Set MasterCard
Set EMV CSK in CVN
20
Yes
Include
counters?
21
No
22
Build Issuer
Application Data
23
Build response
SW12 = '9000'

Second Generate AC
2G.8
24
Recover Torn
Yes Transactions
Enabled?
25
No
26
Commit persistent
data

Second Generate AC
2G.8.1
2G.8.2
2G.8.3
THEN
GOTO 2G.8.4
ELSE
GOTO 2G.8.9
ENDIF
2G.8.4
THEN
GOTO 2G.8.5
ELSE
GOTO 2G.8.7
ENDIF
2G.8.5
2G.8.6
2G.8.7
2G.8.8
2G.8.9
THEN
GOTO 2G.8.10
ELSE
GOTO 2G.8.12
ENDIF
2G.8.10
2G.8.11

Second Generate AC
2G.8.12
THEN
GOTO 2G.8.13
ELSE
GOTO 2G.8.14
ENDIF
2G.8.13
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6
2G.8.14
Table 10.13—Input for Application Cryptogram without Counters (V1.1/V1.3
Host Backwards Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6
2G.8.15

Second Generate AC
2G.8.16
2G.8.17
THEN
GOTO 2G.8.18
ELSE
GOTO 2G.8.19
ENDIF
2G.8.18
CSK Session Key
2G.8.19
2G.8.20
THEN
GOTO 2G.8.21
ELSE
GOTO 2G.8.22
ENDIF
2G.8.21
2G.8.22
THEN
ELSE
ENDIF

Data Object Length
CVR V1.1/V1.3 6
DAC/ICC Dyn Nr 2

Second Generate AC
2G.8.23
Build the response.
Tag Length Value
2G.8.24
THEN
GOTO 2G.8.25
ELSE
GOTO 2G.8.26
ENDIF
2G.8.25
not commit)
commit)
2G.8.26
characteristics.

Second Generate AC

Compatibility
2G.9
2.1/2.2
AC
1
Compute 2.1/2.2
CVR
Adjust CID
3
Session Key
EMV CSK
Derivation
CTRAC ≥ LIMAC Yes
5
No
7 Set AC Session Key
Counter Error Limit
Limits Status
8 6
Proprietary)

Second Generate AC
2G.9
Compute AC
10
Application Data
11
Build response
SW12 = '9000'
12
Recover Torn
Yes Transactions
Enabled?
13
No
14
Commit persistent
data

Second Generate AC
2G.9.1
2G.9.2
THEN
Exceeded
ELSE IF 'Unable To Go Online Indicated' in Card Verification Results is not set
AND ('Issuer Authentication Performed' in Card Verification Results is not set OR
('Issuer Authentication Performed' in Card Verification Results is set AND 'Issuer
Authentication Failed' in Card Verification Results is set))
THEN
'Reason/Advice code' in Cryptogram Information Data := Issuer
ENDIF
ENDIF
2G.9.3
THEN
GOTO 2G.9.4
ELSE
GOTO 2G.9.9
ENDIF
2G.9.4
THEN
GOTO 2G.9.5
ELSE
GOTO 2G.9.7
ENDIF
2G.9.5
2G.9.6
2G.9.7
2G.9.8

Second Generate AC
2G.9.9
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.1/V2.2 4

2G.9.10
THEN
ELSE
ENDIF

Data Object Length
CVR V2.1/V2.2 4
DAC/ICC Dyn Nr 2
2G.9.11
Build the response.

Second Generate AC

Tag Length Value
2G.9.12
THEN
GOTO 2G.9.13
ELSE
GOTO 2G.9.14
ENDIF
2G.9.13
not commit)
commit)
commit)
2G.9.14
characteristics.

Second Generate AC
10.3.10. No CDA – V2.05 Host Backwards

Compatibility
2G.10
2.05
AC
1
Compute 2.05
CVR
Adjust CID
3
Session Key
EMV CSK
Derivation
CTRAC ≥ LIMAC Yes
5
No
Counter Error Limit
Limits Status
8
6
Derive AC Session
Key (MasterCard Build response
Proprietary) SW12 = '6985'

Second Generate AC
2G.10
Compute AC
10
Build 2.05 Issuer
Application Date
11
Build response
SW12 = '9000'
12
Recover Torn
Yes Transactions
Enabled?
13

No
14
Commit persistent
data

Second Generate AC
2G.10.1
2G.10.2
IF'Cryptogram Type' in Reference Control Parameter = TC
AND 'Type Of Cryptogram' in Cryptogram Information Data = AAC
AND 'Unable To Go Online Indicated' in Card Verification Results is not set
THEN
'Reason/Advice code' in Cryptogram Information Data := Issuer Authentication
Failed
ENDIF
2G.10.3
THEN
GOTO 2G.10.4
ELSE
GOTO 2G.10.9
ENDIF
2G.10.4
THEN
GOTO 2G.10.5
ELSE
GOTO 2G.10.7
ENDIF
2G.10.5
2G.10.6
2G.10.7
2G.10.8

Second Generate AC
2G.10.9
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.05 4

2G.10.10
THEN
ELSE
ENDIF

Data Object Length
'08' 1
CVR V2.05 4
DAC/ICC Dyn Nr 2

Second Generate AC
2G.10.11
Build the response.
Tag Length Value
2G.10.12
THEN
GOTO 2G.10.13
ELSE
GOTO 2G.10.14
ENDIF
2G.10.13
not commit)
commit)
2G.10.14
characteristics.

Second Generate AC
10.3.11. CDA – No Host Backwards Compatibility

2G.11
M4R2
CDA
2
Session Key
Derivation
EMV CSK
CTRAC ≥ LIMAC Yes
4
No
Set AC Session Key
6
Counter Error Limit
Limits Status
7 5
Proprietary)

Second Generate AC
2G.11
1
8 9
10
No
Encrypt field
11
No
Include Yes
counters?
12
Include Last
15 No Online ATC? Yes
Build input to AC
without counters
13 14
Last Online ATC
16
Compute AC
17
CVN = '10'

Second Generate AC
2G.11
18
EMV CSK
Derivation
19 20
Set MasterCard
Set EMV CSK in CVN
21
Yes
Include
counters?
22
No
23
Set DAC / ICC

Dynamic Number

Second Generate AC
2G.11
24
Include
in IAD?
25 26

27
Compute Hash
Result
28
Build ICC Dynamic
Data
29
Compute Hash on
Dynamic Application
Data to be Signed
30
Compute RSA
Signature

Second Generate AC
2G.11
4
31
Build response
SW12 = '9000'
32
Recover Torn
Yes Transactions
Enabled?
33

No
34
Commit persistent
data

Second Generate AC
2G.11.1
2G.11.2
THEN
GOTO 2G.11.3
ELSE
GOTO 2G.11.8
ENDIF
2G.11.3
THEN
GOTO 2G.11.4
ELSE
GOTO 2G.11.6
ENDIF
2G.11.4
2G.11.5
2G.11.6
2G.11.7
2G.11.8
THEN
GOTO 2G.11.9
ELSE
GOTO 2G.11.10
ENDIF
2G.11.9
2G.11.10

Second Generate AC
2G.11.11
THEN
GOTO 2G.11.12
ELSE
GOTO 2G.11.15
ENDIF
2G.11.12
THEN
GOTO 2G.11.14
ELSE
GOTO 2G.11.13
ENDIF
2G.11.13
Data Object Length
Transaction Date 3
Transaction Type 1

Second Generate AC
2G.11.14
ATC
Data Object Length
Transaction Date 3
Transaction Type 1
Last Online ATC 2
2G.11.15
Table 10.24—Input for Application Cryptogram without Counters or Last Online
ATC
Data Object Length
Transaction Date 3
Transaction Type 1
2G.11.16
2G.11.17

Second Generate AC
2G.11.18
THEN
GOTO 2G.11.19
ELSE
GOTO 2G.11.20
ENDIF
2G.11.19
CSK Session Key
2G.11.20
2G.11.21
THEN
GOTO 2G.11.22
ELSE
GOTO 2G.11.23
ENDIF
2G.11.22
2G.11.23
THEN
ELSE
ENDIF
2G.11.24
THEN
GOTO 2G.11.25
ELSE
GOTO 2G.11.26
ENDIF

Second Generate AC
2G.11.25
Data Object Length
DAC/ICC Dyn Nr 2
Last Online ATC 2
2G.11.26
Data Object Length
DAC/ICC Dyn Nr 2
2G.11.27
Tag Length Value
– – PDOL Values
Compute Hash Result


Second Generate AC
2G.11.28
Data Object Length
Hash Result 20
2G.11.29
Data Object Length
'26' (length of ICC Dynamic Data) 1
ICC Dynamic Data 38
Padding bytes 'BB' Length Of ICC Public Key Modulus – 63

2G.11.30
2G.11.31
Build the response.
Tag length Value
Modulus

Second Generate AC
2G.11.32
THEN
GOTO 2G.11.33
ELSE
GOTO 2G.11.34
ENDIF
2G.11.33
not commit)
commit)
2G.11.34
characteristics.

Second Generate AC
10.3.12. CDA – V1.1/V1.3 Host Backwards

Compatibility
2G.12
1.1/1.3
CDA
1
Compute 1.1/1.3
CVR
3
Session Key
EMV CSK
Derivation
CTRAC ≥ LIMAC Yes
5
7 Counter Error Limit
Exceeded in Security
Increment CTRAC
Limits Status
8
6
Derive AC Session

Second Generate AC
2G.12
9 10
11
No
Encrypt field
12 13
Include Yes
Build input to AC
counters? with counters
No
14
Build input to AC
without counters
15
Compute AC
16
CVN = '10'

Second Generate AC
2G.12
17
EMV CSK
Derivation
18 19
Set MasterCard
Set EMV CSK in CVN
20
Yes
Include
counters?
21
No
22
Build Issuer
Application Data
23
Compute Hash
Result

Second Generate AC
2G.12
24
Build ICC Dynamic
Data
25
Compute Hash on
Dynamic Application
Data to be Signed
26
Compute RSA
Signature
27
Build response
SW12 = '9000'
28
Recover Torn
Yes Transactions
Enabled?
29
No
30
Commit persistent
data

Second Generate AC
2G.12.1
2G.12.2
2G.12.3
THEN
GOTO 2G.12.4
ELSE
GOTO 2G.12.9
ENDIF
2G.12.4
THEN
GOTO 2G.12.5
ELSE
GOTO 2G.12.7
ENDIF
2G.12.5
2G.12.6
2G.12.7
2G.12.8
2G.12.9
THEN
GOTO 2G.12.10
ELSE
GOTO 2G.12.12
ENDIF
2G.12.10
2G.12.11

Second Generate AC
2G.12.12
THEN
GOTO 2G.12.13
ELSE
GOTO 2G.12.14
ENDIF
2G.12.13
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6
2G.12.14
Table 10.32—Input for Application Cryptogram without Counters (V1.1/V1.3
Host Backwards Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V1.1/V1.3 6

Second Generate AC
2G.12.15
2G.12.16
2G.12.17
THEN
GOTO 2G.12.18
ELSE
GOTO 2G.12.19
ENDIF
2G.12.18
CSK Session Key
2G.12.19
2G.12.20
THEN
GOTO 2G.12.21
ELSE
GOTO 2G.12.22
ENDIF
2G.12.21
2G.12.22
THEN
ELSE
ENDIF

Data Object Length
CVR V1.1/V1.3 6
DAC/ICC Dyn Nr 2

Second Generate AC
2G.12.23
Tag Length Value
– – PDOL Values
Compute Hash Result

2G.12.24
Data Object Length
Hash Result 20
2G.12.25
Data Object Length
ICC Dynamic Data 38

2G.12.26

Second Generate AC
2G.12.27
Build the response.
Tag length Value
Key Modulus
2G.12.28
THEN
GOTO 2G.12.29
ELSE
GOTO 2G.12.30
ENDIF
2G.12.29
not commit)
commit)
2G.12.30
characteristics.

Second Generate AC
10.3.13. CDA – V2.1/V2.2 Host Backwards

Compatibility
2G.13
2.1/2.2
CDA
1
Compute 2.1/2.2
CVR
Adjust CID
3
Session Key
EMV CSK
Derivation
CTRAC ≥ LIMAC Yes
5
7
Counter Error Limit
Limits Status
8
6
Derive AC Session
Build response
Key (MasterCard
SW12 = '6985'
Proprietary)

Second Generate AC
2G.13
Compute AC
10
Application Data
11
Compute Hash
Result
12
Build ICC Dynamic
Data
13
Compute Hash on
Dynamic Application
Data to be Signed
14
Compute RSA
Signature

Second Generate AC
2G.13
15
Build response
SW12 = '9000'
16
Recover Torn
Yes Transactions
Enabled?
17
No
18
Commit persistent
data

Second Generate AC
2G.13.1
2G.13.2
IF PINTry Counter = '00'
THEN
Exceeded
ELSE IF 'Unable To Go Online Indicated' in Card Verification Results is not set
THEN
'Reason/Advice code' in Cryptogram Information Data := Issuer
ENDIF
ENDIF
2G.13.3
THEN
GOTO 2G.13.4
ELSE
GOTO 2G.13.9
ENDIF
2G.13.4
THEN
GOTO 2G.13.5
ELSE
GOTO 2G.13.7
ENDIF
2G.13.5
2G.13.6
2G.13.7
2G.13.8

Second Generate AC
2G.13.9
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.1/V2.2 4

2G.13.10
THEN
ELSE
ENDIF

Data Object Length
CVR V2.1/V2.2 4
DAC/ICC Dyn Nr 2

Second Generate AC
2G.13.11
Tag Length Value
– – PDOL Values
Compute Hash Result

2G.13.12
Data Object Length
Hash Result 20
2G.13.13
Data Object Length
ICC Dynamic Data 38

2G.13.14

Second Generate AC
2G.13.15
Build the response.
Tag Length Value
Key Modulus
2G.13.16
THEN
GOTO 2G.13.17
ELSE
GOTO 2G.13.18
ENDIF
2G.13.17
not commit)
commit)
commit)
2G.13.18
characteristics.

Second Generate AC
10.3.14. CDA – V2.05 Host Backwards Compatibility

2G.14
2.05
CDA
1
Compute 2.05
CVR
Adjust CID
3
Session Key
EMV CSK
Derivation
CTRAC ≥ LIMAC Yes
5
No
Counter Error Limit
Limits Status
8
6
Derive AC Session

Second Generate AC
2G.14
Compute AC
10
Build 2.05 Issuer
Application Data
11
Compute Hash
Result
12
Build ICC Dynamic
Data
13
Compute Hash on
Dynamic Application
Data to be Signed
14
Compute RSA
Signature

Second Generate AC
2G.14
15
Build response
SW12 = '9000'
16
Recover Torn
Yes Transactions
Enabled?
17
Update recovery data No
18
Commit persistent
data

Second Generate AC
2G.14.1
2G.14.2
IF'Cryptogram Type' in Reference Control Parameter = TC
AND 'Type Of Cryptogram' in Cryptogram Information Data = AAC
AND 'Unable To Go Online Indicated' in Card Verification Results is not set
THEN
'Reason/Advice code' in Cryptogram Information Data := Issuer Authentication
Failed
ENDIF
2G.14.3
THEN
GOTO 2G.14.4
ELSE
GOTO 2G.14.9
ENDIF
2G.14.4
THEN
GOTO 2G.14.5
ELSE
GOTO 2G.14.7
ENDIF
2G.14.5
2G.14.6
2G.14.7
2G.14.8

Second Generate AC
2G.14.9
Compatibility)
Data Object Length
Transaction Date 3
Transaction Type 1
CVR V2.05 4

2G.14.10
THEN
ELSE
ENDIF

Data Object Length
'08' 1
CVR V2.05 4
DAC/ICC Dyn Nr 2

Second Generate AC
2G.14.11
Tag Length Value
– – PDOL Values
Compute Hash Result

2G.14.12
Data Object Length
Hash Result 20
2G.14.13
Data Object Length
ICC Dynamic Data 38

2G.14.14

Second Generate AC
2G.14.15
Build the response.
Tag Length Value
Key Modulus
2G.14.16
THEN
GOTO 2G.14.17
ELSE
GOTO 2G.14.18
ENDIF
2G.14.17
not commit)
commit)
2G.14.18
characteristics.

Get Challenge
11. Get Challenge

11.1. Get Challenge Command Message ............................................................ 339
11.2. Get Challenge Processing .......................................................................... 340

Get Challenge
Get Challenge Command Message
11.1. Get Challenge Command Message

The GET CHALLENGE command message is specified in Table 11.1.
Table 11.1—Get Challenge Command Message
Code Value
CLA '00'
INS '84'
P1 '00'
P2 '00'
Lc Not present
Data Not present
Le '00'

Get Challenge
Get Challenge Processing
11.2. Get Challenge Processing

Symbols in this diagram are labeled GC.x.
GC
GET CHALLENGE
1
Flag
2
P1-P2 NOK
3
Build response
OK SW12 = '6A86'
4
Compute
challenge
5
Set Get Challenge
Flag
6
Build response
SW12 = '9000'

Get Challenge
Get Challenge Processing
GC.1
Challenge Flag
GC.2
IF P1|P2 ≠ '0000'
THEN
GOTO GC.3
ELSE
GOTO GC.4
ENDIF
GC.3
GC.4
Compute the ICC Unpredictable Number. The pseudo-random number generator
used for this computation is proprietary and left to the implementation provided it
passes MasterCard's security evaluation.
GC.5
Set 'Successful Get Challenge' in Get Challenge Flag
GC.6
Build the response.
The response message is the ICC Unpredictable Number as shown in Table 11.2,
followed by SW12 equal to '9000'.
Table 11.2—Get Challenge Response
Data Object Length
ICC Unpredictable Number 8

Get Data
12. Get Data

12.1. Get Data Command Message..................................................................... 343
12.3. Get Data Processing ................................................................................... 346

Get Data
Get Data Command Message
12.1. Get Data Command Message

The GET DATA command message is specified in Table 12.1.
Table 12.1—Get Data Command Message
Code Value
CLA '80'
INS 'CA'
P1|P2 tag
Lc not present
Data not present
Le '00'
Single byte tags are preceded with a leading '00' byte to fill P1|P2.
Table 12.2 lists the tag values supported in the GET DATA command message
Table 12.2—Supported P1|P2 Values for Get Data Command
P1|P2 Data Length
'DF3B' Accumulator 1 Amount 6
'DF11' Accumulator 1 Control (Contact) 1
'DF12' Accumulator 1 Control (Contactless) 1
'00C9' Accumulator 1 Currency Code 2
'00D1' Accumulator 1 Currency Conversion Table 25
'DF28' Accumulator 1 CVR Dependency Data (Contact) 3
'DF29' Accumulator 1 CVR Dependency Data (Contactless) 3
'00CA' Accumulator 1 Lower Limit 6
'00CB' Accumulator 1 Upper Limit 6
'DF13' Accumulator 2 Amount 6
'DF16' Accumulator 2 Currency Code 2
'DF17' Accumulator 2 Currency Conversion Table 25
'DF2A' Accumulator 2 CVR Dependency Data (Contact) 3
'DF2B' Accumulator 2 CVR Dependency Data (Contactless) 3
'DF18' Accumulator 2 Lower Limit 6
'DF19' Accumulator 2 Upper Limit 6
'00D3' Additional Check Table 18
'00D5' Application Control (Contact) 6
'00D7' Application Control (Contactless) 6
'0094' Application File Locator (Contact) Variable
'00D9' Application File Locator (Contactless) Variable
'0082' Application Interchange Profile (Contact) 2
'00D8' Application Interchange Profile (Contactless) 2
'9F7E' Application Life Cycle Data 48
'00C3' Card Issuer Action Code (Contact) – Decline 3
'00C4' Card Issuer Action Code (Contact) – Default 3

Get Data
Get Data Command Message
P1|P2 Data Length

'00C5' Card Issuer Action Code (Contact) – Online 3
'00CF' Card Issuer Action Code (Contactless) – Decline 3
'00CD' Card Issuer Action Code (Contactless) – Default 3
'00CE' Card Issuer Action Code (Contactless) – Online 3
'00C7' CDOL1 Related Data Length 1
'DF1A' Counter 1 Control (Contact) 1
'DF1B' Counter 1 Control (Contactless) 1
'DF2C' Counter 1 CVR Dependency Data (Contact) 3
'DF2D' Counter 1 CVR Dependency Data (Contactless) 3
'9F14' Counter 1 Lower Limit 1
'DF1C' Counter 1 Number 1
'9F23' Counter 1 Upper Limit 1
'DF1D' Counter 2 Control (Contact) 1
'DF1E' Counter 2 Control (Contactless) 1
'DF2E' Counter 2 CVR Dependency Data (Contact) 3
'DF2F' Counter 2 CVR Dependency Data (Contactless) 3
'DF1F' Counter 2 Lower Limit 1
'DF20' Counter 2 Number 1
'DF21' Counter 2 Upper Limit 1
'00C8' CRM Country Code 2
'DF3C' CVR Issuer Discretionary Data (Contact) 1
'DF3D' CVR Issuer Discretionary Data (Contactless) 1
'00D6' Default ARPC Response Code 2
'DF30' Interface Enabling Switch 1
'DF73' Linked Application Index 1
'00DE' Log Data Table 9
'9F4F' Log Format Variable
'DF04' Max Time For Processing Relay Resistance APDU (Contact) 2
'DF74' Max Time For Processing Relay Resistance APDU 2
(Contactless)
'DF05' Min Time For Processing Relay Resistance APDU (Contact) 2
'DF75' Min Time For Processing Relay Resistance APDU 2
(Contactless)
'DF24' MTA Currency Code 2
'DF22' MTA CVM (Contact) 6
'DF23' MTA CVM (Contactless) 6
'DF25' MTA NoCVM (Contact) 6
'DF26' MTA NoCVM (Contactless) 6
'DF27' Number Of Days Off Line Limit 2
'9F50' Offline Accumulator Balance 1 6
'9F7A' Offline Counter Balance 1 1
'9F59' Offline Counter Balance 2 1
'9F17' PIN Try Counter 1
'00C6' PIN Try Limit 1
'DF3F' Read Record Filter (Contact) Variable
'DF40' Read Record Filter (Contactless) Variable

Get Data
P1|P2 Data Length

'DF02' Security Limits Status (Contact) 1
'DF35' Security Limits Status (Contactless) 1
'DF37' Security Limits Status Common 1
'DF0B' Transmission Time For Relay Resistance R-APDU (Contact) 2
'DF76' Transmission Time For Relay Resistance R-APDU 2
(Contactless)

Table 12.3—Local Transient Data for Get Data

Get Data
Get Data Processing
12.3. Get Data Processing

The symbols in the diagram are labeled GD.x.
GD
GET DATA
1
Flag
2
Acc 1 Yes
Amount
3
No Show? Yes
4
No
Acc 2 Yes
Amount
5
No
Show? Yes
6
No
Cntr 1 Yes
Number
7
Show? Yes
No
8 No
Cntr 2 Yes
Number
9
Show? Yes
No
No
10 11
SW12 = '6985' SW12 = '9000'

Get Data
Get Data Processing
GD
1
12
Balance? Yes
14
13
No Build response
allowed? No
SW12 = '6985'
Yes
15
Balance?
16 17
Compute Acc 1 Build response
Acc 1
balance SW12 = '9000'
18 19
Compute Acc 2 Build response
Acc 2
20 21
Compute Cntr 1 Build response
Cntr 1
22 23
Compute Cntr 2 Build response
2 Cntr 2

Get Data
Get Data Processing
GD
2
24
OK P1-P2 NOK
26 25
SW12 = '9000' SW12 = '6A88'

Get Data
Get Data Processing
GD.1
Challenge Flag
GD.2
IF P1|P2 = 'DF3B'
THEN
GOTO GD.3
ELSE
GOTO GD.4
ENDIF
GD.3
IF 'Show' in Accumulator 1 Control is set
THEN
GOTO GD.11
ELSE
GOTO GD.10
ENDIF
GD.4
IF P1|P2 = 'DF13'
THEN
GOTO GD.5
ELSE
GOTO GD.6
ENDIF
GD.5
IF 'Show' in Accumulator 2 Control is set
THEN
GOTO GD.11
ELSE
GOTO GD.10
ENDIF
GD.6
IF P1|P2 = 'DF1C'
THEN
GOTO GD.7
ELSE
GOTO GD.8
ENDIF

Get Data
Get Data Processing
GD.7
IF 'Show' in Counter 1 Control is set
THEN
GOTO GD.11
ELSE
GOTO GD.10
ENDIF
GD.8
IF P1|P2 = 'DF20'
THEN
GOTO GD.9
ELSE
GOTO GD.12
ENDIF
GD.9
IF 'Show' in Counter 2 Control is set
THEN
GOTO GD.11
ELSE
GOTO GD.10
ENDIF
GD.10
GD.11
Build the response message template containing the requested data object, TLV-
coded.
Build the R-APDU consisting of the response message template and SW12 equal to
'9000'.
GD.12
Check if the data object indicated in the command is the Offline Accumulator Balance
1, Offline Accumulator Balance 2, Offline Counter Balance 1 or Offline Counter
Balance 2.
IF P1|P2 = '9F50' OR P1|P2 = '9F58' OR P1|P2 = '9F7A' OR P1|P2 = '9F59'

THEN
GOTO GD.13
ELSE
GOTO GD.24
ENDIF

Get Data
Get Data Processing
GD.13
IF 'Allow Retrieval Of Balance' in Application Control is set
THEN
GOTO GD.15
ELSE
GOTO GD.14
ENDIF
GD.14
GD.15
IF P1|P2 = '9F50'
THEN
GOTO GD.16
ELSE IF P1|P2 = '9F58'
THEN
GOTO GD.18
ELSE IF P1|P2 = '9F7A'
THEN
GOTO GD.20
ELSE
GOTO GD.22
ENDIF
ENDIF
ENDIF
GD.16
IF Accumulator 1 Amount < Accumulator 1 Upper Limit
THEN
Offline Accumulator Balance 1 := Accumulator 1 Upper Limit – Accumulator 1
Amount
ELSE
Offline Accumulator Balance 1 := '000000000000'
ENDIF
GD.17
Build the response message template containing the Offline Accumulator Balance 1,
TLV-coded.
'9000'.
GD.18
IF Accumulator 2 Amount < Accumulator 2 Upper Limit
THEN
Offline Accumulator Balance 2 := Accumulator 2 Upper Limit – Accumulator 2
Amount
ELSE
Offline Accumulator Balance 2 := '000000000000'
ENDIF

Get Data
Get Data Processing
GD.19
Build the response message template containing the Offline Accumulator Balance 2,
TLV-coded.
'9000'.
GD.20
IF Counter 1 Number < Counter 1 Upper Limit
THEN
Offline Counter Balance 1 := Counter 1 Upper Limit – Counter 1 Number
ELSE
Offline Counter Balance 1 := '00'
ENDIF
GD.21
Build the response message template containing the Offline Counter Balance 1, TLV-
coded.
'9000'.
GD.22
IF Counter 2 Number < Counter 2 Upper Limit
THEN
Offline Counter Balance 2 := Counter 2 Upper Limit – Counter 2 Number
ELSE
Offline Counter Balance 2 := '00'
ENDIF
GD.23
Build the response message template containing the Offline Counter Balance 2, TLV-
coded.
'9000'.
GD.24
IF P1|P2 is an accepted tag (as listed in Table 12.2)
THEN
GOTO GD.26
ELSE
GOTO GD.25
ENDIF
GD.25
GD.26
Build the response message template containing the requested data object, TLV-
coded.
'9000'.

Get Processing Options
13. Get Processing Options

13.1. Get Processing Options Command Message ............................................. 354
13.3. Get Processing Options Processing ........................................................... 355

Get Processing Options Command Message
13.1. Get Processing Options Command

Message
The GET PROCESSING OPTIONS command message is specified in Table 13.1.
Table 13.1—Get Processing Options Command Message
Code Value
CLA '80'
INS 'A8'
P1 '00'
P2 '00'
Lc '02' or '07'
Data PDOL Related Data
Le '00'
Table 13.2 specifies the PDOL Related Data when the MAS4C Transaction Flow is
not activated.
Table 13.2—PDOL Related Data When MAS4C Transaction Flow is Not
Activated
Tag Length
'83' '00'
Table 13.3 specifies the PDOL Related Data when the MAS4C Transaction Flow is
activated.
Table 13.3—PDOL Related Data when MAS4C Transaction Flow is Activated
Tag Length Value
'83' '05' Value of '9F40' (Additional Terminal
Capabilities)

Table 13.4—Local Transient Data for Get Processing Options
PDOL Related Data

Get Processing Options Processing
13.3. Get Processing Options Processing

Symbols in this diagram are labeled GPO.x.
GPO
GET PROCESSING
OPTIONS
1
Update Get
Challenge Flag
3
2
Build response
P1-P2 NOK
SW12 = '6A86'
OK
4
Clear transaction related

volatile data elements
5
Yes MAS4C No
6 7
Lc = 7? No No Lc = 2?
8
Build response
SW12 = '6700'
Yes Yes
1 2

GPO
1 2
9 10
Test PDOL NOK NOK Test PDOL
data data
OK OK
12 11 12a
Retrieve ATeC Build response
Set PDOL Values
Set PDOL Values SW12 = '6985'
OK
13 14
Build response
Test ATC NOK
SW12 = '6985'
OK

GPO
15
Increment Application
Transaction Counter
16
Compute ICC Dynamic

Number
17
Build Response
SW12 = '9000'

GPO.1
Challenge Flag
GPO.2
IF P1|P2 ≠ '0000'
THEN
GOTO GPO.3
ELSE
GOTO GPO.4
ENDIF
GPO.3
GPO.4
Clear the global transient data objects. The global transient data objects are listed in
chapter 4.
GPO.5
IF 'MAS4C Processing Flow' in Application Control is set
THEN
GOTO GPO.6
ELSE
GOTO GPO.7
ENDIF
GPO.6
IF Lc = 7
THEN
GOTO GPO.9
ELSE
GOTO GPO.8
ENDIF
GPO.7
IF Lc = 2
THEN
GOTO GPO.10
ELSE
GOTO GPO.8
ENDIF
GPO.8

GPO.9
IF PDOL Related Data[1 : 2] = '8305'
THEN
GOTO GPO.12
ELSE
GOTO GPO.11
ENDIF
GPO.10
IF PDOL Related Data = '8300'
THEN
GOTO GPO.12a
ELSE
GOTO GPO.11
ENDIF
GPO.11
GPO.12
ATeC := PDOL Related Data[3 : 4]
PDOL Values := PDOL Related Data[3 : 7]
GPO.12a
Store empty byte string in PDOL Values
GPO.13
IF Application Transaction Counter >= Application Transaction Counter Limit
THEN
GOTO GPO.14
ELSE
GOTO GPO.15
ENDIF
GPO.14
GPO.15
Application Transaction Counter := Application Transaction Counter + 1
GPO.16
Compute the ICC Dynamic Number using the ICC Dynamic Number Master Key as
follows:
ICC Dynamic Number := (IDNL | IDNR)
Where:
IDNL := DES3(MKIDN)[(ATC | 'FF' | '00' | '00' | '00' | '00' | '00')]
IDNR := DES3(MKIDN)[(ATC | '00' | '00' | '00' | '00' | '00' | '00')]

GPO.17
Build the response.
equal to '9000'.
Table 13.5—Get Processing Options Response
'82' 2 Application Interchange Profile
'94' variable Application File Locator

Internal Authenticate
14. Internal Authenticate

14.1. Internal Authenticate Command message ................................................. 362
14.3. Internal Authenticate Processing ............................................................... 363

Internal Authenticate Command message
14.1. Internal Authenticate Command message

The INTERNAL AUTHENTICATE command message is specified in Table 14.1.
Table 14.1—Internal Authenticate Command Message
Code Value
CLA '00'
INS '88'
P1 '00'
P2 '00'
Lc '04'
Data DDOL Related Data
Le '00'

Table 14.2—Local Transient Data for Internal Authenticate
DDOL Related Data
ICC Dynamic Data

Internal Authenticate Processing
14.3. Internal Authenticate Processing

Symbols in this diagram are labeled IA.x.
IA
INTERNAL
AUTHENTICATE
1
Flag
3
2
Build response
P1-P2 NOK
SW12 = '6A86'
OK
5
4
Build response
Lc NOK
SW12 = '6700'
6
7
Internal
Authentication Yes
Build response
Performed Flag SW12 = '6985'
set?
No

IA
8
Retrieve DDOL
Related Data
Build ICC Dynamic

Data
10
Build Dynamic
Application Data to
be Signed
11
Sign Dynamic
Application Data to
be Signed
12
Set Internal
Authentication
Performed Flag
13
Build response
SW12 = '9000'

IA.1
Challenge Flag
IA.2
IF P1|P2 ≠ '0000'
THEN
GOTO IA.3
ELSE
GOTO IA.4
ENDIF
IA.3
IA.4
IF Lc ≠ '04'
THEN
GOTO IA.5
ELSE
GOTO IA.6
ENDIF
IA.5
IA.6
IF Internal Authentication Performed Flag is set
THEN
GOTO IA.7
ELSE
GOTO IA.8
ENDIF
IA.7
IA.8
Unpredictable Number := DDOL Related Data
IA.9
ICC Dynamic Data := '08' | ICC Dynamic Number[9 : 16]

IA.10
Data Object Length
ICC Dynamic Data 9
IA.11
The Dynamic Application Data To Be Signed is signed as specified in [SECURITY].
IA.12
Set Internal Authentication Performed Flag
IA.13
Build the response.
equal to '9000'.
Table 14.4—Internal Authenticate Response
Tag Length Value
Key Modulus

Issuer Updates
15. Issuer Updates

15.1. Issuer Updates Command Message ........................................................... 368
15.3. Issuer Updates Processing.......................................................................... 369

Issuer Updates
Issuer Updates Command Message
15.1. Issuer Updates Command Message

The ISSUER UPDATES command message is specified in Table 15.1.
Table 15.1—Issuer Updates Command Message
Code Value
CLA '84'
INS 'D4'
P1 '00'
P2 '00'
Lc Var.
Data Issuer Updates Data and MAC (See Table 15.2)
Le Not present
Table 15.2—Command Data

Value Length
Issuer Updates Data Lc - 8
MAC 8

Table 15.3—Local Transient Data for Issuer Updates
MAC
New SMI Key Flag

Issuer Updates
Issuer Updates Processing
15.3. Issuer Updates Processing

Symbols in this diagram are labeled IU.x.
IU
ISSUER UPDATES
1
Flag
3
2
Build response
P1-P2 NOK
SW12 = '6A86'
OK
4 5
Build response
Lc NOK
SW12 = '6700'
OK
6 7
Script Failed Yes
Build response
Flag set? SW12 = '6982'
No
8
Set Script Failed
Flag
9
PTH

Issuer Updates
IU
10
Set Script Received in PTH
11 13
Set SMI Session Key
CTRSMI < LIMSMI No Counter Limit Exceeded in
14
Yes
Build response
12 SW12 = '6985'
Retrieve MAC and
Issuer Updates Data 15
Commit persistent
data

Issuer Updates
IU
16
Session Key
Derivation
method
17
SMI CSK
No
key present?
19 22

Yes
18 20 23
Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
21 24
Flag = 1 Flag = 0

Issuer Updates
IU
3
25
Verify NOK
MAC
OK
27
Build response
26 SW12 = '6982'
New SMI Key
Flag = 1? 28
Commit persistent
No
Yes data
29
Decrement CTRSMI
30
Check format of Issuer
Updates Data
31
Format of Issuer NOK 36
Updates Data
Build response
SW12 = '6985'
OK
32
37
Set Issuer Updates
Received Flag Commit persistent
data

Issuer Updates
IU
33
Increment Rand
34
Build response
SW12 = '9000'
35
Commit persistent
data

Issuer Updates
IU.1
Challenge Flag
IU.2
IF P1|P2 ≠ '0000'
THEN
GOTO IU.3
ELSE
GOTO IU.4
ENDIF
IU.3
IU.4
IF Lc < 11
THEN
GOTO IU.5
ELSE
GOTO IU.6
ENDIF
IU.5
IU.6
THEN
GOTO IU.7
ELSE
GOTO IU.8
ENDIF
IU.7
IU.8
IU.9
IU.10

Issuer Updates
IU.11
THEN
GOTO IU.12
ELSE
GOTO IU.13
ENDIF
IU.12
Retrieve MAC and Issuer Updates Data from the ISSUER UPDATES command
message.
IU.13
IU.14
IU.15
characteristics.
IU.16
THEN
GOTO IU.17
ELSE
GOTO IU.22
ENDIF
IU.17
THEN
GOTO IU.18
ELSE
GOTO IU.19
ENDIF
IU.18
IU.19
IU.20

Issuer Updates
IU.21
IU.22
IU.23
IU.24
IU.25
Verify the MAC on the ISSUER UPDATES command.
IF the MAC is correct

THEN
GOTO IU.26
ELSE
GOTO IU.27
ENDIF
IU.26
THEN
GOTO IU.29
ELSE
GOTO IU.30
ENDIF
IU.27
IU.28
characteristics.
IU.29
IU.30
Return Value := CALL CheckIssuerUpdates( )

Issuer Updates
IU.31
IF Return Value
THEN
GOTO IU.32
ELSE
GOTO IU.36
ENDIF
IU.32
Set Issuer Updates Received Flag
IU.33
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
IU.34
IU.35
characteristics.
IU.36
IU.37
characteristics.

Offline Change PIN
16. Offline Change PIN

16.1. Offline Change PIN Command Message ................................................... 379
16.3. Offline Change PIN Processing ................................................................. 380
16.3.1. Start .................................................................................................... 380
16.3.2. Encrypted PIN .................................................................................... 382
16.3.3. Plaintext PIN ...................................................................................... 388

Offline Change PIN
Offline Change PIN Command Message
16.1. Offline Change PIN Command Message

The OFFLINE CHANGE PIN command message is specified in Table 16.1.
Table 16.1—Offline Change PIN Command Message
Code Value
CLA '80'
INS 'D2'
P1 '00'
P2 '80': plaintext
'88': encrypted
Lc var.
Data PIN Related Data
Le Not present
PIN Related Data contains the PIN block in plaintext or encrypted form, constructed
according to [EMV BOOK 3]. If the command is accepted, the PIN is updated with a
new value.

Table 16.2—Local Transient Data for Offline Change PIN
PIN Related Data
Recovered Data

Offline Change PIN
Offline Change PIN Processing
16.3. Offline Change PIN Processing
16.3.1. Start
The symbols in this diagram are labeled OCP.1.x.
OCP.1
OFFLINE CHANGE PIN
1
Flag
2
P1 NOK
OK
3
'88' P2 NOK
4
Build response
SW12 = '6A86'
'80'
encrypted plaintext

Offline Change PIN
OCP.1.1
Challenge Flag
OCP.1.2
IF P1 = '00'
THEN
GOTO OCP.1.3
ELSE
GOTO OCP.1.4
ENDIF
OCP.1.3
IF P2 = '80'
THEN
GOTO OCP.3.1 (Plaintext PIN)
ELSE IF P2 = '88'
THEN
GOTO OCP.2.1 (Encrypted PIN)
ELSE
GOTO OCP.1.4
ENDIF
ENDIF
OCP.1.4

Offline Change PIN
16.3.2. Encrypted PIN

OCP.2
encrypted
1 2
Encrypted
Build response
Offline Change PIN No
SW12 = '6985'
activated?
Yes
3 4
Build response
PIN Status NOK
SW12 = '6985'
OK
5
DDA Key
DDA or Dedicated Dedicated
Key
6 8 7
Build response
Lc NOK NOK Lc
SW12 = '6700'
OK OK
1 2

Offline Change PIN
OCP.2
1 2
9 11 10
Challenge Build response Challenge
No No
available? SW12 = '6985' available?
Yes Yes
12 13
PIN PIN
Decipherments Decipherments
Yes Yes
Error Cntr Limit Error Cntr Limit
reached? reached?
14
Set PIN Decipherments Error
Counter Limit Exceeded in No
No Security Limits Status Common
16 15 18
Increment PIN Decipherments Build response Increment PIN Decipherments
Error Counter SW12 = '6984' Error Counter
17 19
Decrypt PIN Related Data Decrypt PIN Related Data

Offline Change PIN
OCP.2
20
Challenge NOK
OK
21 22
Build response
Format NOK
SW12 = '6985'
OK 23
Decrement PIN Decipherments
Error Counter
24 25
Build response
Format PIN NOK
SW12 = '6984'
OK 26
Update PIN
27
Set PIN Change Status
28
Build response
SW12 = '9000'

Offline Change PIN
OCP.2.1
IF 'Encrypted Offline Change PIN' in Application Control is set
THEN
GOTO OCP.2.3
ELSE
GOTO OCP.2.2
ENDIF
OCP.2.2
OCP.2.3
IF 'Offline PIN Verification Successful' in PIN Verification Status is set AND
'Offline Change PIN Successful' in Offline Change PIN Status is not set
THEN
GOTO OCP.2.5
ELSE
GOTO OCP.2.4
ENDIF
OCP.2.4
OCP.2.5
IF 'Key For Offline Encrypted PIN Verification' in Application Control = DDA Key
THEN
GOTO OCP.2.6
ELSE
GOTO OCP.2.7
ENDIF
OCP.2.6
IF Lc = Length Of ICC Public Key Modulus
THEN
GOTO OCP.2.9
ELSE
GOTO OCP.2.8
ENDIF
OCP.2.7
IF Lc = Length Of ICC PIN Encipherment Public Key Modulus
THEN
GOTO OCP.2.10
ELSE
GOTO OCP.2.8
ENDIF
OCP.2.8
Build R-APDU consisting of SW12 equal to '6700'

Offline Change PIN
OCP.2.9
IF 'Challenge Availability' in Get Challenge Flag is set
THEN
GOTO OCP.2.12
ELSE
GOTO OCP.2.11
ENDIF
OCP.2.10
THEN
GOTO OCP.2.13
ELSE
GOTO OCP.2.11
ENDIF
OCP.2.11
OCP.2.12
IF PIN Decipherments Error Counter ≥ PIN Decipherments Error Counter Limit
THEN
GOTO OCP.2.14
ELSE
GOTO OCP.2.16
ENDIF
OCP.2.13
THEN
GOTO OCP.2.14
ELSE
GOTO OCP.2.18
ENDIF
OCP.2.14
Set 'PIN Decipherments Error Counter Limit Exceeded' in Security Limits Status
Common
OCP.2.15
OCP.2.16
PIN Decipherments Error Counter := PIN Decipherments Error Counter + 1
OCP.2.17
The PIN Related Data is decrypted with the ICC Private Key to obtain the Recovered
Data.
Refer to [SECURITY] for more details.
OCP.2.18

Offline Change PIN
OCP.2.19
The PIN Related Data is decrypted with the ICC PIN Encipherment Private Key to
obtain the Recovered Data.
OCP.2.20
IF Recovered Data[10 : 17] = ICC Unpredictable Number
THEN
GOTO OCP.2.21
ELSE
GOTO OCP.2.22
ENDIF
OCP.2.21
IF Recovered Data[1] = '7F'
THEN
GOTO OCP.2.23
ELSE
GOTO OCP.2.22
ENDIF
OCP.2.22
OCP.2.23
PIN Decipherments Error Counter := PIN Decipherments Error Counter – 1
OCP.2.24
IF (Recovered Data[2][8 : 5] = '2') AND
(Recovered Data[2][4 : 1] >= '4') AND
(Recovered Data[2][4 : 1] <= 'C') AND
(Recovered Data[9] = 'FF')
THEN
GOTO OCP.2.26
ELSE
GOTO OCP.2.25
ENDIF
OCP.2.25
OCP.2.26
Reference PIN := Recovered Data[2 : 9]
OCP.2.27
Set 'Offline Change PIN Successful' in Offline Change PIN Status
OCP.2.28

Offline Change PIN
16.3.3. Plaintext PIN

OCP.3
plaintext
1
2
Plaintext
Build response
Offline Change PIN No
SW12 = '6985'
activated?
Yes
3 4
Build response
Lc NOK
SW12 = '6700'
OK
5 6
Build response
PIN Status NOK
SW12 = '6985'
OK
7 8
Build response
Format NOK
SW12 = '6984'
OK

Offline Change PIN
OCP.3
Update PIN
10
Set PIN Change
Status
11
Build response
SW12 = '9000'

Offline Change PIN
OCP.3.1
IF 'Plaintext Offline Change PIN' in Application Control is set
THEN
GOTO OCP.3.3
ELSE
GOTO OCP.3.2
ENDIF
OCP.3.2
OCP.3.3
IF Lc = '08'
THEN
GOTO OCP.3.5
ELSE
GOTO OCP.3.4
ENDIF
OCP.3.4
OCP.3.5
'Offline PIN Verification Successful' in PIN Verification Status is set AND
IF
'Offline Change PIN Successful' in Offline Change PIN Status is not set
THEN
GOTO OCP.3.7
ELSE
GOTO OCP.3.6
ENDIF
OCP.3.6
OCP.3.7
IF (PIN Related Data [1][8 : 5] = '2') AND
(PIN Related Data [1][4 : 1] >= '4') AND
(PIN Related Data [1][4 : 1] <= 'C') AND
(PIN Related Data [8] = 'FF')
THEN
GOTO OCP.3.9
ELSE
GOTO OCP.3.8
ENDIF
OCP.3.8
OCP.3.9
Reference PIN := PIN Related Data

Offline Change PIN
OCP.3.10
Set 'Offline Change PIN Successful' in Offline Change PIN Status
OCP.3.11

PIN Change/Unblock
17. PIN Change/Unblock

17.1. PIN Change/Unblock Command Message ................................................ 393
17.3. PIN Change/Unblock Processing ............................................................... 394
17.3.1. Start .................................................................................................... 394
17.3.2. PIN Unblock ...................................................................................... 396
17.3.3. PIN Change ........................................................................................ 405

PIN Change/Unblock
PIN Change/Unblock Command Message
17.1. PIN Change/Unblock Command Message

The PIN CHANGE/UNBLOCK command message is specified in Table 17.1.
Table 17.1—PIN Change/Unblock Command Message
Code Value
CLA '84'
INS '24'
P1 '00'
P2 '00' for PIN Unblock
'02' for PIN Change
Lc '08' for PIN Unblock
'10' for PIN Change
Le Not present
If P2 equals '00', the PIN Related Data only contains a MAC as shown in Table 17.2.
If the command is accepted, the PIN Try Counter is set to the PIN Try Limit and there
is no PIN update.
Table 17.2—PIN Related Data if P2 = '00'
Value Length
MAC 8
If P2 equals '02', the PIN Related Data contains the Enciphered New PIN Block and a
MAC as shown in Table 17.3.
If the command is accepted, the PIN is updated with a new PIN value and PIN Try
Counter is set to the PIN Try Limit.
Table 17.3—PIN Related Data if P2 = '02'
Value Length
Enciphered New PIN Block 8
MAC 8

Table 17.4—Local Transient Data for PIN Change/Unblock
MAC
New PIN Block
New SMI Key Flag
PIN Related Data

PIN Change/Unblock
PIN Change/Unblock Processing
17.3. PIN Change/Unblock Processing
17.3.1. Start
The symbols in this diagram are labeled PCU.1.x.
PCU.1
PIN CHANGE/UNBLOCK
1
Flag
2
'0000' P1-P2 Other
3
Build response
'0002' SW12 = '6A86'
PIN Unblock PIN Change

PIN Change/Unblock
PCU.1.1
Challenge Flag
PCU.1.2
IF P1 = '00' AND P2 = '00'
THEN
GOTO PCU.2.1 (PIN Unblock)
ELSE IF P1 = '00' AND P2 = '02'
THEN
GOTO PCU.3.1 (PIN Change)
ELSE
GOTO PCU.1.3
ENDIF
ENDIF
PCU.1.3

PIN Change/Unblock
17.3.2. PIN Unblock

PCU.2
PIN UNBLOCK
2
1
Build response
Lc NOK
SW12 = '6700'
OK
3 4
Script Failed Yes
Build response
Flag set? SW12 = '6982'
No
5
Set Script Received
in PTH

PIN Change/Unblock
PCU.2
6 7
Limits Status
9
Yes
Retrieve MAC 10
11
Build response
SW12 = '6985'
2
12
Commit persistent
data

PIN Change/Unblock
PCU.2
13
Session Key
Derivation
method
14
SMI CSK
No
key present?
16 19

Yes
15 17 20
Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
18 21
Flag = 1 Flag = 0

PIN Change/Unblock
PCU.2
24
22
Verify NOK
MAC PTH
OK 25
New SMI Key

Flag = 1? 26
Build response
No
Yes
SW12 = '6982'
28
Decrement CTRSMI
27
Commit persistent
data

PIN Change/Unblock
PCU.2
29
Set PTC to PTL
30
Increment script
counter
31
Increment Rand
32
Build response
SW12 = '9000'
33
Commit persistent
data

PIN Change/Unblock
PCU.2.1
IF Lc = '08'
THEN
GOTO PCU.2.3
ELSE
GOTO PCU.2.2
ENDIF
PCU.2.2
PCU.2.3
THEN
GOTO PCU.2.4
ELSE
GOTO PCU.2.5
ENDIF
PCU.2.4
PCU.2.5
PCU.2.6
THEN
GOTO PCU.2.8
ELSE
GOTO PCU.2.7
ENDIF
PCU.2.7
PCU.2.8
Retrieve MAC from the PIN CHANGE/UNBLOCK command message.
PCU.2.9
PCU.2.10
PCU.2.11

PIN Change/Unblock
PCU.12
characteristics.
PCU.2.13
THEN
GOTO PCU.2.14
ELSE
GOTO PCU.2.19
ENDIF
PCU.2.14
THEN
GOTO PCU.2.15
ELSE
GOTO PCU.2.16
ENDIF
PCU.2.15
PCU.2.16
PCU.2.17
PCU.2.18
PCU.2.19
PCU.2.20
PCU.2.21
PCU.2.22
Verify MAC on the PIN CHANGE/UNBLOCK command.

PIN Change/Unblock
IF MAC is correct
THEN
GOTO PCU.2.23
ELSE
GOTO PCU.2.24
ENDIF
PCU.2.23
THEN
GOTO PCU.2.28
ELSE
GOTO PCU.2.29
ENDIF
PCU.2.24
PCU.2.25
PCU.2.26
PCU.2.27
characteristics.
PCU.2.28
PCU.2.29
PIN Try Counter := PIN Try Limit (do not commit)
PCU.2.30
THEN
ELSE
commit)
ENDIF

PIN Change/Unblock
PCU.2.31
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
PCU.2.32
PCU.2.33
characteristics.

PIN Change/Unblock
17.3.3. PIN Change

PCU.3
PIN CHANGE
1 2
Build response
Lc NOK
SW12 = '6700'
OK
3 4
Script Failed Yes
Build response
Flag set? SW12 = '6982'
No
5
Set Script Received
in PTH

PIN Change/Unblock
PCU.3
6 7
Limits Status
9
Yes
Retrieve MAC and

10
encrypted PIN block
11
Build response
2 SW12 = '6985'
12
Commit persistent
data

PIN Change/Unblock
PCU.3
13
Session Key
Derivation
method
14
SMI CSK
No
key present?
16 19

Yes
15 17 20
Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
18 21
Flag = 1 Flag = 0

PIN Change/Unblock
PCU.3
24
22
Verify NOK Set Script Failed in PTH
MAC
OK 25
New SMI Key

Flag = 1? 26
Build response
No
SW12 = '6982'
Yes
28
27
Decrement CTRSMI
Commit persistent
data

PIN Change/Unblock
PCU.3
29
Session Key
EMV CSK MCI
Derivation
method
30
SMC CSK
No
key present?
31 33
Derive SMC Session
Derive SMC Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
Yes
32 34
SMC CSK key present SMC CSK key present

flag = 1 flag = 0
35
Decrypt PIN block

PIN Change/Unblock
PCU.3
5
36
Format NOK
37
Set Script Failed in PTH

OK
41
Set PTC to PTL

38
Update PIN
39
43 Build response
SW12 = '6988'
Increment script
counter
40
44 Commit persistent
data
Increment Rand
45
Build response
SW12 = '9000'
46
Commit persistent
data

PIN Change/Unblock
PCU.3.1
IF Lc = '10'
THEN
GOTO PCU.3.3
ELSE
GOTO PCU.3.2
ENDIF
PCU.3.2
PCU.3.3
THEN
GOTO PCU.3.4
ELSE
GOTO PCU.3.5
ENDIF
PCU.3.4
PCU.3.5
PCU.3.6
THEN
GOTO PCU.3.8
ELSE
GOTO PCU.3.7
ENDIF
PCU.3.7
PCU.3.8
Retrieve MAC (PIN Related Data[Lc-7 : Lc]) and Enciphered New PIN Block (PIN
Related Data[1 : Lc-8]).
PCU.3.9
PCU.3.10
PCU.3.11

PIN Change/Unblock
PCU.3.12
characteristics.
PCU.3.13
THEN
GOTO PCU.3.14
ELSE
GOTO PCU.3.19
ENDIF
PCU.3.14
THEN
GOTO PCU.3.15
ELSE
GOTO PCU.3.16
ENDIF
PCU.3.15
PCU.3.16
PCU.3.17
PCU.3.18
PCU.3.19
PCU.3.20
PCU.3.21

PIN Change/Unblock
PCU.3.22
Verify MAC on the PIN CHANGE/UNBLOCK command.
IF MAC is correct
THEN
GOTO PCU.3.23
ELSE
GOTO PCU.3.24
ENDIF
PCU.3.23
THEN
GOTO PCU.3.28
ELSE
GOTO PCU.3.29
ENDIF
PCU.3.24
PCU.3.25
PCU.3.26
PCU.3.27
characteristics.
PCU.3.28
PCU.3.29
THEN
GOTO PCU.3.30
ELSE
GOTO PCU.3.33
ENDIF

PIN Change/Unblock
PCU.3.30
IF SMC CSK Key Present Flag is set
THEN
GOTO PCU.3.35
ELSE
GOTO PCU.3.31
ENDIF
PCU.3.31
Derive new SMC Session Key according to the EMV CSK method.
PCU.3.32
Set SMC CSK Key Present Flag
PCU.3.33
Derive new SMC Session Key according to the MasterCard Proprietary SKD method.
PCU.3.34
Clear SMC CSK Key Present Flag
PCU.3.35
Decrypt Enciphered New PIN Block.
Refer to [SECURITY] for details
PCU.3.36
IF (New PIN Block[1][8 : 5] = '2') AND
(New PIN Block[1][4 : 1] >= '4') AND
(New PIN Block[1][4 : 1] <= 'C') AND
(New PIN Block[8] = 'FF')
THEN
GOTO PCU.3.41
ELSE
GOTO PCU.3.37
ENDIF
PCU.3.37
PCU.3.38
PCU.3.39
PCU.3.40
characteristics.

PIN Change/Unblock
PCU.3.41
PIN Try Counter := PIN Try Limit (do not commit)
PCU.3.42
Reference PIN := New PIN Block (do not commit)
PCU.3.43
THEN
ELSE
commit)
ENDIF
PCU.3.44
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
PCU.3.45
PCU.3.46
characteristics.

Put Data
18. Put Data

18.1. Put Data Command Message ..................................................................... 417
18.3. Put Data Processing ................................................................................... 420

Put Data
Put Data Command Message
18.1. Put Data Command Message

The PUT DATA command message is specified in Table 18.1.
Table 18.1—Put Data Command Message
Code Value
CLA '84'
INS 'DA'
P1|P2 tag
Lc var.
Data New Data Value and MAC (See Table 18.2)
Le Not present
Table 18.2—Command Data

Value Length
New Data Value Lc - 8
MAC 8
Table 18.3 lists the tag values supported in the PUT DATA command and the
corresponding value of Lc. Single byte tags are preceded with a leading '00' byte to
fill P1|P2.
Table 18.3—P1|P2 Values Supported by PUT DATA Command
P1|P2 Data Length
'DF3A' AC Session Key Counter Limit (Contact) 2
'DF34' AC Session Key Counter Limit (Contactless) 2
'DF78' AC Session Key Counter Limit (MAS4C) 2
'DF3B' Accumulator 1 Amount 6
'00C9' Accumulator 1 Currency Code 2
'00D1' Accumulator 1 Currency Conversion Table 25
'DF28' Accumulator 1 CVR Dependency Data (Contact) 3
'DF29' Accumulator 1 CVR Dependency Data (Contactless) 3
'00CA' Accumulator 1 Lower Limit 6
'00CB' Accumulator 1 Upper Limit 6
'DF13' Accumulator 2 Amount 6
'DF16' Accumulator 2 Currency Code 2
'DF17' Accumulator 2 Currency Conversion Table 25
'DF2A' Accumulator 2 CVR Dependency Data (Contact) 3
'DF2B' Accumulator 2 CVR Dependency Data (Contactless) 3
'DF18' Accumulator 2 Lower Limit 6
'DF19' Accumulator 2 Upper Limit 6

Put Data
Put Data Command Message
P1|P2 Data Length

'00D3' Additional Check Table 18
'00D5' Application Control (Contact) 6
'00D7' Application Control (Contactless) 6
'0094' Application File Locator (Contact) Variable
'00D9' Application File Locator (Contactless) Variable
'0082' Application Interchange Profile (Contact) 2
'00D8' Application Interchange Profile (Contactless) 2
'00C3' Card Issuer Action Code (Contact) – Decline 3
'00C4' Card Issuer Action Code (Contact) – Default 3
'00C5' Card Issuer Action Code (Contact) – Online 3
'00CF' Card Issuer Action Code (Contactless) – Decline 3
'00CD' Card Issuer Action Code (Contactless) – Default 3
'00CE' Card Issuer Action Code (Contactless) – Online 3
'00C7' CDOL1 Related Data Length 1
'DF1A' Counter 1 Control (Contact) 1
'DF1B' Counter 1 Control (Contactless) 1
'DF2C' Counter 1 CVR Dependency Data (Contact) 3
'DF2D' Counter 1 CVR Dependency Data (Contactless) 3
'9F14' Counter 1 Lower Limit 1
'DF1C' Counter 1 Number 1
'9F23' Counter 1 Upper Limit 1
'DF1D' Counter 2 Control (Contact) 1
'DF1E' Counter 2 Control (Contactless) 1
'DF2E' Counter 2 CVR Dependency Data (Contact) 3
'DF2F' Counter 2 CVR Dependency Data (Contactless) 3
'DF1F' Counter 2 Lower Limit 1
'DF20' Counter 2 Number 1
'DF21' Counter 2 Upper Limit 1
'00C8' CRM Country Code 2
'DF3C' CVR Issuer Discretionary Data (Contact) 1
'DF3D' CVR Issuer Discretionary Data (Contactless) 1
'00D6' Default ARPC Response Code 2
'DF30' Interface Enabling Switch 1
'DF38' IVCVC3(Track1) (Contact) 2
'00DC' IVCVC3(Track1) (Contactless) 2
'DF39' IVCVC3(Track2) (Contact) 2
'00DD' IVCVC3(Track2) (Contactless) 2
'DF07' Linked Application Data Variable
'DF73' Linked Application Index 1
'DF04' Max Time For Processing Relay Resistance APDU (Contact) 2
'DF74' Max Time For Processing Relay Resistance APDU 2
(Contactless)
'DF05' Min Time For Processing Relay Resistance APDU (Contact) 2
'DF75' Min Time For Processing Relay Resistance APDU 2
(Contactless)
'DF24' MTA Currency Code 2
'DF22' MTA CVM (Contact) 6

Put Data
P1|P2 Data Length

'DF23' MTA CVM (Contactless) 6
'DF25' MTA NoCVM (Contact) 6
'DF26' MTA NoCVM (Contactless) 6
'DF27' Number Of Days Off Line Limit 2
'9F7A' Offline Counter Balance 1 1
'9F59' Offline Counter Balance 2 1
'DF36' PIN Decipherments Error Counter Limit 2
'00C6' PIN Try Limit 1
'DF3F' Read Record Filter (Contact) Variable
'DF40' Read Record Filter (Contactless) Variable
'DF32' SMI Session Key Counter Limit (Contact) 2
'DF33' SMI Session Key Counter Limit (Contactless) 2
'DF0B' Transmission Time For Relay Resistance R-APDU (Contact) 2
'DF76' Transmission Time For Relay Resistance R-APDU 2
(Contactless)

Table 18.4—Local Transient Data for Put Data
MAC
New Data Value
New SMI Key Flag

Put Data
Put Data Processing
18.3. Put Data Processing

The symbols in this diagram are labeled PD.x.
PD
PUT DATA
1
Flag
3
2
Build response
P1-P2 NOK
SW12 = '6A88'
OK
4 5
Build response
Lc NOK
SW12 = '6700'
OK
6 7
Script Failed Yes
Build response
Flag set? SW12 = '6982'
No
8
Set Script Received
in PTH

Put Data
Put Data Processing
PD
9 11
Limits Status
12
Yes
10
Retrieve MAC 13
14
Build response
SW12 = '6985'
2 15
Commit persistent
data

Put Data
Put Data Processing
PD
16
Session Key
Derivation
method
17
SMI CSK
No
key present?
19 22

Yes
18 20 23
Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
21 24
Flag = 1 Flag = 0

Put Data
Put Data Processing
PD
3
25 27
Verify NOK Set Script Failed in PTH
MAC
OK 28
New SMI Key

Flag = 1? 29
Build response
Yes
SW12 = '6982'
No
31
Decrement CTRSMI 30
Commit persistent
data
32 33
Acc 1 Update Acc 1
Yes
balance ? balance
No
34 35
Acc 2 Update Acc 2
Yes
balance ? balance
No
4 5

Put Data
Put Data Processing
PD
4
37 36
Update Cntr 1 Cntr 1
Yes
balance balance ?
No
39 38
Update Cntr 2 Cntr 2
Yes
balance balance ?
No
60
Linked
Application Yes
Data ?
No
40
PTL ? Yes
41
Value < 16 No
No
Yes
46
Update data
5 6 7

Put Data
Put Data Processing
PD
7
61

:= New Data Value
62
Version
NOK
Number?
OK
63
Find Target
Application
64
Target
Application No
Found?
Yes
65
Target
Yes Data ID = '0000'
?
No
8 9 6

Put Data
Put Data Processing
PD
8
66
Block Status =
Yes
Block ?
67
No
Block Target
Application
68
Block Status =
No
Unblock ?
Yes
69
Unblock Target
Application
6 5

Put Data
Put Data Processing
PD
5 9 6
70
Target
Data ID = '00A5' No
?
Yes
71
Update FCI Proprietary

Template of Target
Application
47 42
Increment script
counter
48 43
Increment Rand Set Script Failed Flag
49 44
SW12 = '9000' SW12 = '6985'
50 45
Commit persistent
data

Put Data
Put Data Processing
PD.1
Challenge Flag
PD.2
IF P1|P2 is an accepted tag (as listed in Table 18.3)
THEN
GOTO PD.4
ELSE
GOTO PD.3
ENDIF
PD.3
PD.4
For fixed length data objects:
IF Lc-8 <= data length
THEN
GOTO PD.6
ELSE
GOTO PD.5
ENDIF
Partial update (i.e. Lc-8 < data length) is supported for all fixed length data objects.
For partial updates, the first Lc-8 bytes of stored data are overwritten and the
remaining bytes are left unchanged.
For variable length data objects (Application File Locator (Contact), Application File
Locator (Contactless), Linked Application Data, Read Record Filter (Contact) and
Read Record Filter (Contactless)):
IF Lc-8 <= max allowed data length
THEN
GOTO PD.6
ELSE
GOTO PD.5
ENDIF
The value of max allowed data length is 32 for the Application File Locator
(Contact), Application File Locator (Contactless), Read Record Filter (Contact) and
Read Record Filter (Contactless).
When the Application File Locator (Contact) or Application File Locator

(Contactless) is updated, M/Chip Advance must then use a new length L in the TLV
representation of the Application File Locator in the GET PROCESSING OPTIONS
command response data. The value of L is Lc-8.

Put Data
Put Data Processing
When the Read Record Filter (Contact) or Read Record Filter (Contactless) is
updated, M/Chip Advance must then use a new length L in the TLV representation of
the Read Record Filter in the GET DATA command response data. The value of L is
Lc-8. The new value of the Read Record Filter completely replaces the old one for
the processing of the READ RECORD command.
For the Linked Application Data max allowed data length is 247.
PD.5
PD.6
THEN
GOTO PD.7
ELSE
GOTO PD.8
ENDIF
PD.7
PD.8
PD.9
THEN
GOTO PD.10
ELSE
GOTO PD.11
ENDIF
PD.10
Retrieve MAC and New Data Value from the PUT DATA command message.
PD.11
PD.12
PD.13
PD.14

Put Data
Put Data Processing
PD.15
characteristics.
PD.16
THEN
GOTO PD.17
ELSE
GOTO PD.22
ENDIF
PD.17
THEN
GOTO PD.18
ELSE
GOTO PD.19
ENDIF
PD.18
PD.19
PD.20
PD.21
PD.22
PD.23
PD.24

Put Data
Put Data Processing
PD.25
Verify the MAC on the PUT DATA command.
IF the MAC is correct

THEN
GOTO PD.26
ELSE
GOTO PD.27
ENDIF
PD.26
THEN
GOTO PD.31
ELSE
GOTO PD.32
ENDIF
PD.27
PD.28
PD.29
PD.30
characteristics.
PD.31
PD.32
Check if the data object indicated in the command is the Offline Accumulator Balance
1.
IF P1|P2 = '9F50'
THEN
GOTO PD.33
ELSE
GOTO PD.34
ENDIF

Put Data
Put Data Processing
PD.33
Accumulator 1 Upper Limit := New Data Value (do not commit)
Note
When the Offline Accumulator Balance 1 is partially updated, the Accumulator 1
Amount is reset, while the first Lc-8 bytes of the Accumulator 1 Upper Limit are
overwritten and the remaining bytes are left unchanged.
PD.34
Check if the data object indicated in the command is the Offline Accumulator
Balance 2.
IF P1|P2 = '9F58'
THEN
GOTO PD.35
ELSE
GOTO PD.36
ENDIF
PD.35
Accumulator 2 Upper Limit := New Data Value (do not commit)
Note
When the Offline Accumulator Balance 2 is partially updated, the Accumulator 2
Amount is reset, while the first Lc-8 bytes of the Accumulator 2 Upper Limit are
overwritten and the remaining bytes are left unchanged.
PD.36
Check if the data object indicated in the command is the Offline Counter Balance 1.
IF P1|P2 = '9F7A'
THEN
GOTO PD.37
ELSE
GOTO PD.38
ENDIF
PD.37
Counter 1 Upper Limit := New Data Value (do not commit)
PD.38
Check if the data object indicated in the command is the Offline Counter Balance 2.
IF P1|P2 = '9F59'
THEN
GOTO PD.39
ELSE
GOTO PD.60
ENDIF

Put Data
Put Data Processing
PD.39
Counter 2 Upper Limit := New Data Value (do not commit)
PD.60
Check if the data object indicated in the command is Linked Application Data.
IF P1|P2 = 'DF07'
THEN
GOTO PD.61
ELSE
GOTO PD.40
ENDIF
PD.40
Check if the data object indicated in the command is the PIN Try Limit.
IF P1|P2 = '00C6'
THEN
GOTO PD.41
ELSE
GOTO PD.46
ENDIF
PD.41
IF New Data Value < 16
THEN
GOTO PD.46
ELSE
GOTO PD.42
ENDIF
PD.46
Data Object indicated by P1|P2 := New Data Value (do not commit)
PD.61
Linked Application Data := New Data Value
PD.62
IF 'Version Number' in Linked Application Data = '00'
THEN
GOTO PD.63
ELSE
GOTO PD.42
ENDIF

Put Data
Put Data Processing
PD.63
Addressing the target application is as follows:
IF 'Target Application' in Linked Application Data = '00'
THEN
The target application is the application currently selected.
ELSE IF 'Target Application' in Linked Application Data = 'FF’
THEN
The target application is the application with AID indicated in 'AID' in Linked
Application Data (which may be the currently selected application).
Full match is required between the two AIDs.
ELSE
The target application is the application with Linked Application Index equal to
'Target Application' in Linked Application Data.
ENDIF
PD.64
IF target application found
THEN
GOTO PD.65
ELSE
GOTO PD.42
ENDIF
PD.65
IF 'Target Data ID' in Linked Application Data = '0000'
AND target application is M/Chip Advance
THEN
GOTO PD.66
ELSE
GOTO PD.70
ENDIF
PD.66
IF 'New Value' in Linked Application Data = '01'
THEN
GOTO PD.67
ELSE
GOTO PD.68
ENDIF
PD.67
Block target application:
Set 'Application Blocked' in Previous Transaction History (do not commit)

Put Data
Put Data Processing
PD.68
IF 'New Value' in Linked Application Data = '00'
THEN
GOTO PD.69
ELSE
GOTO PD.42
ENDIF
PD.69
Unblock target application:
Clear 'Application Blocked' in Previous Transaction History (do not commit)
PD.70
IF 'Target Data ID' in Linked Application Data = '00A5'
THEN
GOTO PD.71
ELSE
GOTO PD.42
ENDIF
PD.71
Replace the value field of the FCI Proprietary Template (tag 'A5') in the File Control
Information of the target application with the 'New Value' in Linked Application Data.
Update the length of the FCI Proprietary Template in the File Control Information to
reflect the replacement.
Update the length of the File Control Information to reflect the replacement.
Note
If the 'New Value' in Linked Application Data is empty (zero length), FCI Proprietary
Template (tag 'A5') value and length in the File Control Information is 'A500'.
PD.42
PD.43
PD.44
PD.45
characteristics.

Put Data
Put Data Processing
PD.47
THEN
ELSE
commit)
ENDIF
PD.48
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
PD.49
PD.50
characteristics.

Read Record
19. Read Record

19.1. Read Record Command Message .............................................................. 438
19.3. Read Record Processing ............................................................................ 439

Read Record
Read Record Command Message
19.1. Read Record Command Message

The READ RECORD command message is specified in Table 19.1.
Table 19.1—Read Record Command Message
Code Value
CLA '00'
INS 'B2'
P1 Record Number
Lc Not present
Data Not present
Le '00'

Table 19.2—Reference Control Parameter Coding for Read Record
x x x x x 'SFI'
1 0 0 P1 is a record number
M/Chip Advance supports the READ RECORD command as specified in [EMV], but
it is extended by this specification to support the reading of records beyond the range
1 to 10. This is necessary to allow the command to be used to read the Transactions
Log File, within SFI 11.

Table 19.3—Local Transient Data for Read Record Command
Record Number
Return Value

Read Record
Read Record Processing
19.3. Read Record Processing

The symbols in this diagram are labeled RR.x.
RR
READ RECORD

Flags
2
P1-P2 NOK
3
Build response
SW12 = '6A86'
OK
4
Payment System SFI Other
5
Processing out of
scope
EMV
6
File
Supported?
No 7
Build response
SW12 = '6A82'
Yes
2 1

Read Record
RR
8
Record No
found? 9
Build response
SW12 = '6A83'
Yes
10
Check if record is
in Read Record Filter
11
Record in
Read Record Yes
Filter?
No
12 13
SW12 = '9000' SW12 = '6985'

Read Record
RR
Payment System
14
SFI = 11 Yes
14.1
Allowed? No
Yes
15
No Record
No
Found?
Yes
16 17 17.1
Build response Build response Build response
SW12 = '9000' SW12 = '6A83' SW12 = '6985'

Read Record
RR
18
File
Yes
Supported?
No
20 19
Build response Processing out of
SW12 = '6A82' scope

Read Record
RR.1
Challenge Flag
RR.2
IF (P1 = '00') OR ((P2 AND '07') ≠ '04')
THEN
GOTO RR.3
ELSE
GOTO RR.4
ENDIF
RR.3
RR.4
IF ('SFI' in Reference Control Parameter > 0) AND ('SFI' in Reference Control
Parameter < 11)
THEN
GOTO RR.6
Reference Control Parameter > 10) AND ('SFI' in Reference Control
ELSE IF ('SFI' in
Parameter < 21)
THEN
GOTO RR.14
ELSE
GOTO RR.5
ENDIF
ENDIF
RR.5
The file to read is neither an EMV file nor a payment system specific file. The
platform may still support this file (e.g. issuer-specific files). This would be in
addition to the functionality needed for M/Chip Advance. This is allowed but outside
the scope of this specification.
RR.6
Verify if the 'SFI' in Reference Control Parameter corresponds to a supported record
file. The way M/Chip Advance checks that the record file is supported is proprietary
and left to the implementation.
IF 'SFI' in Reference Control Parameter corresponds to a supported record file
THEN
GOTO RR.8
ELSE
GOTO RR.7
ENDIF
RR.7

Read Record
RR.8
Verify if there is a record corresponding to Record Number. The way M/Chip
Advance checks that the record is supported is proprietary and left to the
implementation.
IF there is a record corresponding to Record Number
THEN
GOTO RR.10
ELSE
GOTO RR.9
ENDIF
RR.9
RR.10
Return Value := CALL CheckIfRecordInFilter( )
RR.11
IF Return Value
THEN
GOTO RR.13
ELSE
GOTO RR.12
ENDIF
RR.12
Build the response.
The response message consists of the record followed by SW12 equal to '9000'.
Note
Records in files with an SFI in the range 1 to 10 must follow the '70' template.
However, the application does not interpret this value. It is the responsibility of the
issuer to format each record correctly at personalization, or when a record is updated.
RR.13
RR.14
IF 'SFI' in Reference Control Parameter = 11
THEN
GOTO RR.14.1
ELSE
GOTO RR.18
ENDIF
RR.14.1
IF 'Allow Retrieval Of Transaction Log Records' in Application Control is set
THEN
GOTO RR.15
ELSE
GOTO RR.17.1
ENDIF

Read Record
RR.15
Verify if there is a record corresponding to Record Number.
The way M/Chip Advance checks that the record corresponding to Record Number is
supported or empty is proprietary and outside the scope of the specification.
THEN
GOTO RR.16
ELSE
GOTO RR.17
ENDIF
RR.16
Build the response.
Refer to chapter 4 for the relationship between Record Number and the Transaction
Log Record in the response.
The response message consists of the Transaction Log Record followed by SW12
equal to '9000'.
RR.17
RR.17.1
RR.18
Verify if the 'SFI' in Reference Control Parameter corresponds to a supported record
file. The way M/Chip Advance checks that the record file is supported is proprietary
and left to the implementation.
IF the 'SFI' in Reference Control Parameter corresponds to a supported record file
THEN
GOTO RR.19
ELSE
GOTO RR.20
ENDIF
RR.19
The platform may support this file, but this would be in addition to the functionality
needed for M/Chip Advance. This is allowed but is outside the scope of the
specification.
RR.20

Recover AC
20. Recover AC
20.1. Recover AC Command Message ............................................................... 447
20.3. Recover AC Processing ............................................................................. 448

Recover AC
Recover AC Command Message
20.1. Recover AC Command Message

The RECOVER AC command message is specified in Table 20.1.
Table 20.1—Recover AC Command Message
Code Value
CLA '80'
INS 'D0'
P1 '00'
P2 '00'
Lc '04'
Data Unpredictable Number
Le '00'

Table 20.2—Local Transient Data for Recover AC Command
ICC Dynamic Data

Recover AC
Recover AC Processing
20.3. Recover AC Processing

Symbols in this diagram are labeled RA.x.
RA
RECOVER AC
Update Get
Challenge Flag
3
2
Build response NOK P1-P2
SW12 = '6A86'
OK
5
4
Build response NOK Test Lc
SW12 = '6700'
OK
7 6
Build response No Recovery enabled?
SW12 = '6985'
Yes
9
8
Matching
Build response No Unpredictable
SW12 = '6A88'
Number?
Yes

Recover AC
RA
11 10
Build response Yes

Recover AC
SW12 = '6985' Performed Flag set
No
12
Set Recover AC
Performed Flag
13
Retrieve Issuer
Application Data
14
No
Torn transaction
was CDA?
15
Build response
SW12 = '9000'
Yes

Recover AC
RA
15.1
RRP
No
Performed Yes
(Recovery)
?
16 16.1
17
Compute Hash on
Dynamic Application
Data to be Signed
18
Compute RSA
Signature
19
Build response
SW12 = '9000'

Recover AC
RA.1
Challenge Flag
RA.2
IF P1|P2 ≠ '0000'
THEN
GOTO RA.3
ELSE
GOTO RA.1.4
ENDIF
RA.3
RA.1.4
IF Lc ≠ 4
THEN
GOTO RA.5
ELSE
GOTO RA.6
ENDIF
RA.5
RA.6
IF 'Torn Transaction Recovery' in Application Control is set AND Application
Transaction Counter (Recovery) ≠ '0000'
THEN
GOTO RA.8
ELSE
GOTO RA.7
ENDIF
RA.7
RA.8
IF Unpredictable Number = Unpredictable Number (Recovery)
THEN
GOTO RA.10
ELSE
GOTO RA.9
ENDIF
RA.9

Recover AC
RA.10
IF Recover AC Performed Flag is set
THEN
GOTO RA.11
ELSE
GOTO RA.12
ENDIF
RA.11
RA.12
Set Recover AC Performed Flag
RA.13
Retrieve Issuer Application Data (Recovery).
Note
Issuer Application Data (Recovery) is of variable length.
RA.14
IF CDA Transaction Flag (Recovery) is set
THEN
GOTO RA.16
ELSE
GOTO RA.15
ENDIF
RA.15
Build the response.
equal to '9000'.
Table 20.3—Response (No CDA)
'9F27' 1 Cryptogram Information Data (Recovery)
'9F36' 2 Application Transaction Counter (Recovery)
'9F26' 8 Application Cryptogram (Recovery)
'9F10' var. Issuer Application Data (Recovery)
RA.15.1
IF RRP Performed Flag (Recovery) is clear
GOTO RA.16
ELSE
GOTO RA.16.1
ENDIF

Recover AC
RA.16
Data Object Length
Cryptogram Information Data (Recovery) 1
Application Cryptogram (Recovery) 8
Hash Result (Recovery) 20
RA.16.1
Data Object Length
Cryptogram Information Data (Recovery) 1
Application Cryptogram (Recovery) 8
Hash Result (Recovery) 20
Terminal Relay Resistance Entropy (Recovery) 4
Device Relay Resistance Entropy (Recovery) 4
RA.17
Data Object Length
Data)
Unpredictable Number (Recovery) 4

RA.18

Recover AC
RA.19
Build the response.
equal to '9000'.
Table 20.7—Response (CDA)
Tag Length Value
'9F27' 1 Cryptogram Information Data (Recovery)
'9F36' 2 Application Transaction Counter (Recovery)
Key Modulus
'9F10' Var. Issuer Application Data (Recovery)

Update Record
21. Update Record

21.1. Update Record Command Message ........................................................... 456
21.3. Update Record Processing ......................................................................... 457

Update Record
Update Record Command Message
21.1. Update Record Command Message

The UPDATE RECORD command message is specified in Table 21.1.
Table 21.1—Update Record Command Message
Code Value
CLA '84'
INS 'DC'
P1 Record Number
Lc var.
Data New Record Value and MAC (See Table 21.2)
Le Not present
Table 21.2—Command data

Value Length
New Record Value Lc - 8
MAC 8
The Reference Control Parameter of the command message is coded according to

Table 21.3.
Table 21.3—Reference Control Parameter Coding for Update Record Command
x x x x x 'SFI'
1 0 0 P1 is a record number

Table 21.4—Local Transient Data for Update Record
MAC
New Record Value
Record Number

Update Record
Update Record Processing
21.3. Update Record Processing

The symbols in this diagram are labeled UR.x.
UR
UPDATE RECORD
1
Flag
3
2
Build response
P1-P2 NOK
SW12 = '6A86'
OK
5
4
payment
system
SFI other out of scope
6 EMV
Yes SFI = 11?

9 10
file Build response
NOK
No supported? SW12 = '6A82'
7 8
Build response
out of scope OK
SW12 = '6985'
11 12
record Build response
NOK
supported? SW12 = '6A83'
OK

Update Record
UR
1
13 14
Build response
Lc NOK
SW12 = '6700'
OK
15 16
Script Failed Yes
Build response
Flag set? SW12 = '6982'
No
17
Set Script Received
in PTH
18 20
Set SMI Session Key Counter Limit
CTRSMI < LIMSMI No
Exceeded in Security Limits Status
21
Yes
22
19
Retrieve MAC
23
Build response
SW12 = '6985'
24
2
Commit persistent
data

Update Record
UR
25
Session Key
Derivation
method
26
SMI CSK
No
key present?
28 31

Yes
27 29 32
Derive SMI Session
Key (MasterCard
Key (EMV CSK)
Proprietary SKD)
30 33
Flag = 1 Flag = 0

Update Record
UR
36
34
Verify NOK
MAC PTH
OK 37
New SMI Key

Flag = 1? 38
Build response
No
Yes
SW12 = '6982'
40
39
Decrement CTRSMI
Commit persistent
data
41
Update Record

Update Record
UR
42
Increment script
counter
43
Increment Rand
44
Build response
SW12 = '9000'
45
Commit persistent
data

Update Record
UR.1
Challenge Flag
UR.2
IF (P1 = '00') OR ((P2 AND '07') ≠ '04')
THEN
GOTO UR.3
ELSE
GOTO UR.4
ENDIF
UR.3
UR.4
IF ('SFI' in Reference Control Parameter > 0) AND ('SFI' in Reference Control
Parameter < 11)
THEN
GOTO UR.9
Reference Control Parameter > 10) AND ('SFI' in Reference Control
ELSE IF ('SFI' in
Parameter < 21)
THEN
GOTO UR.6
ELSE
GOTO UR.5
ENDIF
ENDIF
UR.5
The file to update is neither an EMV file nor a payment system file. Support is
implementation specific and is not specified here.
UR.6
IF 'SFI' in Reference Control Parameter = 11
THEN
GOTO UR.7
ELSE
GOTO UR.8
ENDIF
UR.7
UR.8
Support is implementation specific and is not specified here.

Update Record
UR.9
IF 'SFI' in Reference Control Parameter corresponds to a supported record file
THEN
GOTO UR.11
ELSE
GOTO UR.10
ENDIF
UR.10
UR.11
THEN
GOTO UR.13
ELSE
GOTO UR.12
ENDIF
UR.12
UR.13
IF Lc–8 <= reserved length for record
THEN
GOTO UR.15
ELSE
GOTO UR.14
ENDIF
Note
The reserved length is a record attribute that indicates the memory allocated for the
record. It cannot be modified by the UPDATE RECORD command. It must be equal
to or greater than the length needed for correct personalization of the record, and may
be different for each record. The memory allocated remains available to store new
data using the UPDATE RECORD command. The representation of the reserved
length is not externally visible and is implementation specific.
UR.14
UR.15
THEN
GOTO UR.16
ELSE
GOTO UR.17
ENDIF
UR.16

Update Record
UR.17
UR.18
THEN
GOTO UR.19
ELSE
GOTO UR.20
ENDIF
UR.19
Retrieve MAC and New Record Value from the UPDATE RECORD command
message.
UR.20
UR.21
'Script Failed' in Previous Transaction History (do not commit)
Set
UR.22
UR.23
UR.24
characteristics.
UR.25
THEN
GOTO UR.26
ELSE
GOTO UR.31
ENDIF
UR.26
THEN
GOTO UR.27
ELSE
GOTO UR.28
ENDIF
UR.27

Update Record
UR.28
UR.29
UR.30
UR.31
UR.32
UR.33
UR.34
Verify the MAC on the UPDATE RECORD command.
IF MAC is correct
THEN
GOTO UR.35
ELSE
GOTO UR.36
ENDIF
UR.35
THEN
GOTO UR.40
ELSE
GOTO UR.41
ENDIF
UR.36
UR.37
UR.38

Update Record
UR.39
characteristics.
UR.40
UR.41
Value of record indicated by Record Number := New Record Value (do not commit)
Note
The UPDATE RECORD command replaces the current record by a new record, even
if those records are of different sizes. Partial update of a record is not supported.
New Record Value is the value that will be returned by the READ RECORD.
Records in files with an SFI in the range 1 to 10 must follow the'70' template. As a
consequence, New Record Value must follow the '70' template. However, the
application does not interpret this value. It is the responsibility of the issuer to
correctly format New Record Value.
UR.42
THEN
ELSE
commit)
ENDIF
UR.43
THEN
Rand := '0000000000000000'
ELSE
Rand := Rand + 1
ENDIF
UR.44
UR.45
characteristics.

Verify
22. Verify
22.1. Verify Command Message ........................................................................ 468
22.3. Verify Processing ....................................................................................... 469
22.3.1. Start .................................................................................................... 469
22.3.2. Encrypted PIN .................................................................................... 471
22.3.3. Plaintext PIN ...................................................................................... 480

Verify
Verify Command Message
22.1. Verify Command Message

The VERIFY command message is specified in Table 22.1.
Table 22.1—Verify Command Message
Code Value
CLA '00'
INS '20'
P1 '00'
P2 '80': plaintext
'88': encrypted
Lc var.
Le Not present

Table 22.2—Local Transient Data for Verify
PIN Related Data
Recovered Data

Verify
Verify Processing
22.3. Verify Processing
22.3.1. Start
The symbols in this diagram are labeled VY.1.x.
VY.1
VERIFY
1
Flag
2
'0088' P1-P2 Other
'0080'
Build response
SW12 = '6A86'
encrypted plaintext

Verify
Verify Processing
VY.1.1
Challenge Flag
VY.1.2
IF P1 ≠ '00'
THEN
GOTO VY.1.3
ELSE
IF P2 = '80'
THEN
GOTO VY.3.1 (Plaintext PIN)
ELSE IF P2 = '88'
THEN
GOTO VY.2.1 (Encrypted PIN)
ELSE
GOTO VY.1.3
ENDIF
ENDIF
ENDIF
VY.1.3

Verify
Verify Processing
22.3.2. Encrypted PIN
VY.2
encrypted
Reset PVS
2
encrypted
No
supported?
3
Build response
SW12 = '6985'
Yes
4
DDA Key
DDA or Dedicated Dedicated
Key
5 7 6
Build response
Lc NOK NOK Lc
SW12 = '6700'
OK OK
1 2

Verify
Verify Processing
VY.2
1 2
8 10 9
Build response
PTC = '00' Yes Yes PTC = '00'
SW12 = '6983'
No No
11 13 12
Challenge Build response Challenge
No No
available? SW12 = '6985' available?
Yes Yes
14 15
PIN PIN
Decipherments Decipherments
Yes Yes
Error Cntr Limit Error Cntr Limit
reached? reached?
16
Set PIN Decipherments Error
Counter Limit Exceeded in
No No
17
Build response
SW12 = '6984'
3 4

Verify
Verify Processing
VY.2
3 4
18 23
Increment PIN Decipherments Increment PIN Decipherments
Error Counter Error Counter
19 24
Decrement PTC Decrement PTC
20 25
Set Offline PIN Verification Set Offline PIN Verification

Performed in PVS Performed in PVS
21 26
Set Offline Encrypted PIN Set Offline Encrypted PIN

Verification Performed in PVS Verification Performed in PVS
22 27
Decrypt PIN Related Data Decrypt PIN Related Data

Verify
Verify Processing
VY.2
28
Challenge NOK
OK
29
Format NOK
OK
30
Decrement PIN Decipherments
Error Counter
31
PIN NOK
35
OK Build response
SW12 = '63Cx'

Verify
Verify Processing
VY.2
32
PTC = PTL
33
Set Offline PIN
Verification Successful in
PVS
34
Build response
SW12 = '9000'

Verify
Verify Processing
VY.2.1
PIN Verification Status := '00'
VY.2.2
IF 'Offline Encrypted PIN Verification' in Application Control is set
THEN
GOTO VY.2.4
ELSE
GOTO VY.2.3
ENDIF
VY.2.3
VY.2.4
IF 'Key For Offline Encrypted PIN Verification' in Application Control = DDA Key
THEN
GOTO VY.2.5
ELSE
GOTO VY.2.6
ENDIF
VY.2.5
IF Lc = Length Of ICC Public Key Modulus
THEN
GOTO VY.2.8
ELSE
GOTO VY.2.7
ENDIF
VY.2.6
IF Lc = Length Of ICC PIN Encipherment Public Key Modulus
THEN
GOTO VY.2.9
ELSE
GOTO VY.2.7
ENDIF
VY.2.7
Build R-APDU consisting of SW12 equal to '6700'
VY.2.8
THEN
GOTO VY.2.10
ELSE
GOTO VY.2.11
ENDIF

Verify
Verify Processing
VY.2.9
THEN
GOTO VY.2.10
ELSE
GOTO VY.2.12
ENDIF
VY.2.10
VY.2.11
THEN
GOTO VY.2.14
ELSE
GOTO VY.2.13
ENDIF
VY.2.12
THEN
GOTO VY.2.15
ELSE
GOTO VY.2.13
ENDIF
VY.2.13
VY.2.14
THEN
GOTO VY.2.16
ELSE
GOTO VY.2.18
ENDIF
VY.2.15
THEN
GOTO VY.2.16
ELSE
GOTO VY.2.23
ENDIF
VY.2.16
Set 'PIN Decipherments Error Counter Limit Exceeded' in Security Limits Status
Common
VY.2.17

Verify
Verify Processing
VY.2.18
VY.2.19
PIN Try Counter := PIN Try Counter – 1
VY.2.20
Set 'Offline PIN Verification Performed' in PIN Verification Status
VY.2.21
Set 'Offline Encrypted PIN Verification Performed' in PIN Verification Status
VY.2.22
The PIN Related Data is decrypted with the ICC Private Key to obtain the Recovered
Data.
VY.2.23
VY.2.24
VY.2.25
VY.2.26
Set 'Offline Encrypted PIN Verification Performed' in PIN Verification Status
VY.2.27
The PIN Related Data is decrypted with the ICC PIN Encipherment Private Key to
obtain the Recovered Data.
VY.2.28
IF Recovered Data[10-17] = ICC Unpredictable Number
THEN
GOTO VY.2.29
ELSE
GOTO VY.2.35
ENDIF
VY.2.29
IF Recovered Data[1] = '7F'
THEN
GOTO VY.2.30
ELSE
GOTO VY.2.35
ENDIF
VY.2.30
PIN Decipherments Error Counter := PIN Decipherments Error Counter – 1

Verify
Verify Processing
VY.2.31
IF (Recovered Data[2][8 : 5] = '2') AND
(Recovered Data[2][4 : 1] >= '4') AND
(Recovered Data[2][4 : 1] <= 'C') AND
(Recovered Data[9] = 'FF') AND
(Recovered Data[2 : 9] = Reference PIN)
THEN
GOTO VY.2.32
ELSE
GOTO VY.2.35
ENDIF
VY.2.32
PIN Try Counter := PIN Try Limit
VY.2.33
Set 'Offline PIN Verification Successful' in PIN Verification Status
VY.2.34
VY.2.35
Build R-APDU consisting of SW12 equal to '63Cx', where x is 'Low Order Nibble Of
PIN Try Counter' in PIN Try Counter.

Verify
Verify Processing
22.3.3. Plaintext PIN

VY.3
plaintext
Reset PVS
2 3
plaintext Build response
No
supported? SW12 = '6985'
Yes
5
4
Build response
Lc NOK
SW12 = '6700'
OK
6 7
PTL Build response
Yes
exceeded? SW12 = '6983'
No
8
Decrement PTC

Verify
Verify Processing
VY.3
9
Set Offline PIN Verification
Performed in PVS
10 11
Build response
PIN NOK
SW12 = '63Cx'
OK
12
PTC = PTL
13
Set Offline PIN Verification
Successful in PVS
14
Build response
SW12 = '9000'

Verify
Verify Processing
VY.3.1
PIN Verification Status := '00'
VY.3.2
IF 'Offline Plaintext PIN Verification' in Application Control is set
THEN
GOTO VY.3.4
ELSE
GOTO VY.3.3
ENDIF
VY.3.3
VY.3.4
IF Lc = '08'
THEN
GOTO VY.3.6
ELSE
GOTO VY.3.5
ENDIF
VY.3.5
VY.3.6
THEN
GOTO VY.3.7
ELSE
GOTO VY.3.8
ENDIF
VY.3.7
VY.3.8
VY.3.9

Verify
Verify Processing
VY.3.10
IF (PIN Related Data[1][8 : 5] = '2') AND
(PIN Related Data[1][4 : 1] >= '4') AND
(PIN Related Data[1][4 : 1] <= 'C') AND
(PIN Related Data[8] = 'FF') AND
(PIN Related Data = Reference PIN)
THEN
GOTO VY.3.12
ELSE
GOTO VY.3.11
ENDIF
VY.3.11
Build R-APDU consisting of SW12 equal to '63Cx', where x is 'Low Order Nibble Of
PIN Try Counter' in PIN Try Counter.
VY.3.12
PIN Try Counter := PIN Try Limit
VY.3.13
Set 'Offline PIN Verification Successful' in PIN Verification Status
VY.3.14

Subroutines
23. Subroutines
23.1. Overview .................................................................................................... 485
23.2. Add Additional Log Info ........................................................................... 486
23.3. Add transaction Amount to Temporary Accumulator ............................... 487
23.4. Build Counters Field .................................................................................. 489
23.5. Check Accumulators and Counters Limits and Set CVR .......................... 494
23.6. Check Accumulators and Counters Limits and Set/Reset CVR ................ 496
23.7. Check for CVM Transaction ...................................................................... 497
23.8. Check Format of Issuer Updates Data ....................................................... 498
23.9. Check Format of Transaction Date ............................................................ 499
23.10. Check If Record Is in Read Record Filter .................................................. 500
23.11. Check Temp Accumulators and Temp Counters Limits and Set/Reset CVR
501
23.12. Compute M/Chip 2.05 CVR ...................................................................... 503
23.13. Compute M/Chip 2.2 CVR ........................................................................ 504
23.14. Compute M/Chip 4 1.1 CVR ..................................................................... 505
23.15. Determine Accumulator Active Flag ......................................................... 507
23.16. Determine Counter Active Flag ................................................................. 509
23.17. Process Additional Check Table ................................................................ 511
23.18. Process Issuer Updates ............................................................................... 512
23.19. Recognize Currency ................................................................................... 515
23.20. Save Active Accumulators and Counters .................................................. 516
23.21. Update Temporary Accumulators and Counters........................................ 517

Subroutines
Overview
23.1. Overview
Table 23.1—Function Declaration

Title Function Ddeclaration
Add Additional Log Info FUNCTION AddAdditionalLogInfo( )
Add transaction Amount to FUNCTION AddAmountToTempAccumulator( x )
Temporary Accumulator
Build Counters Field FUNCTION BuildCountersField( )
Check Accumulators and Counters FUNCTION CheckAccsCntrsLimitsSetCVR( )
Limits and Set CVR
Check Accumulators and Counters FUNCTION
Limits and Set/Reset CVR CheckAccsCntrsLimitsSetResetCVR( )
Check for CVM Transaction FUNCTION CheckCVMTransaction( ) AS
BOOLEAN
Check Format of Issuer Updates Data FUNCTION CheckIssuerUpdates( ) AS BOOLEAN
Check Format of Transaction Date FUNCTION CheckFormatOfDate( ) AS BOOLEAN
Check If Record Is in Read Record FUNCTION CheckIfRecordInFilter( ) AS
Filter BOOLEAN
Check Temp Accumulators and Temp FUNCTION
Counters Limits and Set/Reset CVR CheckTempAccsCntrsLimitsSetResetCVR( )
Compute M/Chip 2.05 CVR FUNCTION Compute2.05CVR( )
Compute M/Chip 2.2 CVR FUNCTION Compute2.2CVR( )
Compute M/Chip 4 1.1 CVR FUNCTION Compute41.1CVR( )
Determine Accumulator Active Flag FUNCTION DetermineAccActiveFlag( x )
Determine Counter Active Flag FUNCTION DetermineCntrActiveFlag( x )
Process Additional Check Table FUNCTION ProcessAddCheckTable( )
Process Issuer Updates FUNCTION ProcessIssuerUpdates( )
Recognize Currency FUNCTION RecognizeCurrency( x ) AS BOOLEAN
Save Active Accumulators and FUNCTION SaveActiveAccsCntrs( )
Counters
Update Temporary Accumulators and FUNCTION UpdateTempAccsCntrs( )
Counters

Subroutines
Add Additional Log Info
23.2. Add Additional Log Info
23.2.1. Description
Append blocks extracted from CDOL1 Related Data to the current transaction log.
The blocks are defined in the Log Data Table. The maximum number of blocks is 4.
23.2.2. Computation
FUNCTION AddAdditionalLogInfo( )
IF ('Count Of Data Entries' in Log Data Table = 0 OR 'Count Of Data Entries' in Log
Data Table > 4)
THEN
EXIT FUNCTION
ENDIF
AdditionalLogLength := 0
FOR i := 1 TO 'Count Of Data Entries' in Log Data Table

IF ('Data Position i' in Log Data Table = 0 OR 'Data Length i' in Log Data Table =
0)
THEN
EXIT FUNCTION
ENDIF
Log Data Table + 'Data Length i' in Log Data Table >
IF 'Data Position i' in
CDOL1 Related Data Length + 1
THEN
EXIT FUNCTION
ENDIF
IF (AdditionalLogLength + 'Data Length i' in Log Data Table) > 32
THEN
EXIT FUNCTION
ENDIF
Temp Transaction Log Record[44 + AdditionalLogLength : 43 +
AdditionalLogLength + 'Data Length i' in Log Data Table] := CDOL1 Related
Data['Data Position i' in Log Data Table : 'Data Position i' in Log Data Table +
'Data Length i' in Log Data Table -1]
AdditionalLogLength := AdditionalLogLength + 'Data Length i' in Log Data
Table
NEXT
EXIT FUNCTION
END FUNCTION

Subroutines
Add transaction Amount to Temporary Accumulator
23.3. Add transaction Amount to Temporary

Accumulator
23.3.1. Description
Add the amount of the transaction to an accumulator and places the result in a
temporary accumulator. This function is only called when the currency of a
transaction is supported by the accumulator. The currency is supported if it is:
 The currency of the accumulator,
 Or it is present in the currency conversion table of the accumulator.
23.3.2. Input arguments

x: temporary accumulator identifier:
 1 for temporary accumulator 1,
 2 for temporary accumulator 2.
23.3.3. Computation
FUNCTION AddAmountToTempAccumulator( x )
IF Transaction Currency Code = Accumulator x Currency Code

THEN
IF Amount, Authorized (Numeric) + Accumulator x Amount > 999999999999
THEN
Accumulator x Amount Temp := 999999999999
EXIT FUNCTION
ELSE
Accumulator x Amount Temp := Amount, Authorized (Numeric) +
Accumulator x Amount
EXIT FUNCTION
ENDIF
ENDIF
FOR i := 1 TO 5
IF Transaction Currency Code = 'Currency Code i' in Accumulator x Currency
Conversion Table
THEN
Exponent := 'Conversion Exponent i'[7 : 1] in Accumulator x Currency
Conversion Table
IF 'Conversion Exponent i'[8] in Accumulator x Currency Conversion Table =
0
THEN
IF (Amount,Authorized (Numeric) * 'Conversion Rate i' in Accumulator x
Currency Conversion Table * (10Êxponent)) + Accumulator x
Amount > 999999999999
THEN

Subroutines
Add transaction Amount to Temporary Accumulator
EXIT FUNCTION
ELSE
Accumulator x Amount Temp := (Amount, Authorized (Numeric) *
'Conversion Rate i' in Accumulator x Currency Conversion Table *
(10Êxponent)) + Accumulator x Amount
EXIT FUNCTION
ENDIF
ELSE
IF (Amount, Authorized (Numeric) * 'Conversion Rate i' in Accumulator x
Currency Conversion Table / (10Êxponent)) + Accumulator x Amount
> 999999999999
THEN
EXIT FUNCTION
ELSE
(Accumulator x Amount Temp := Amount, Authorized (Numeric) *
'Conversion Rate i' in Accumulator x Currency Conversion Table /
(10Êxponent)) + Accumulator x Amount
EXIT FUNCTION
ENDIF
ENDIF
ENDIF
NEXT
EXIT FUNCTION
END FUNCTION
Note
The division is of a BCD coded number by powers of 10 and is the truncated integer
division so it can be implemented as a right shift.

Subroutines
Build Counters Field
23.4. Build Counters Field
23.4.1. Description
Fill in the counters field in Issuer Application Data. The Counters Field comprises
one or two parts.
Part 1 of the Counters Field (bytes 1 to 8) is always present. The first six bytes may
contain (i.e. are eligible for):
 Accumulator/balance value
 One or both counter/balance value(s)
 'FF' padding
Byte 7 may contain:
 counter/balance value if the Part 1 is being use for an accumulator
 'FF' padding
Byte 8 may contain:
 maximum time for Relay Resistance APDU processing
 'FF' padding
Part 2 of the Counters Field (bytes 9 to 16) is present if not all accumulator/balance or
counter/balance values could fit in Part 1. If present, the length of Part 2 is 8 bytes.
The first six bytes may contain:
 accumulator/balance value
 counter/balance value
 'FF' padding
Byte 7 may contain:
 counter/balance value if the Part 2 is being used for an accumulator
 'FF' padding
Byte 8 may contain:
 minimum time for Relay Resistance APDU processing
 'FF' padding
The rule to fill the Counters Field is as follows:

1. If selected for inclusion, put accumulator 1/balance 1 at first available and
eligible bytes,
2. If selected for inclusion, put accumulator 2/balance 2 at first available and
eligible bytes,
3. If selected for inclusion, put counter 1/balance 1 at first available and eligible
byte,
4. If selected for inclusion, put counter 2/balance 2 at first available and eligible
byte,
5. Pad first part (always present) with 'FF'
6. If present, pad second part with 'FF'
7. If RRP is performed, byte 8 of Part 1 is replaced with the maximum time for
Relay Resistance APDU processing in units of milliseconds and if Part 2 is
present, byte 8 of Part 2 is replaced with the minimum time for Relay
Resistance APDU processing in units of milliseconds. If the time for either
exceeds 255ms, then a value of 255 is used. Note that the RRP related data is

Subroutines
only included in the counters field generated during the 1st Generate AC
command.
23.4.2. Computation
FUNCTION BuildCountersField( )
AccumulatorSlot1Available := TRUE
AccumulatorSlot2Available := TRUE
CounterSlot1Available := TRUE
Plaintext/Encrypted Counters := 'FFFFFFFFFFFFFFFF'
SELECT CASE 'Include In Issuer Application Data' in Accumulator 1 Control

CASE Include Accumulator As Value
Plaintext/Encrypted Counters[1 : 6] := Accumulator 1 Amount
AccumulatorSlot1Available := FALSE
CASE Include As Balance
IF Accumulator 1 Amount > Accumulator 1 Upper Limit
THEN
AccumulatorBalance := '000000000000'
ELSE
AccumulatorBalance := Accumulator 1 Upper Limit - Accumulator 1 Amount
ENDIF
Plaintext/Encrypted Counters[1 : 6] := AccumulatorBalance
CASE ELSE
END SELECT
SELECT CASE 'Include In Issuer Application Data' in Accumulator 2 Control

CASE Include Accumulator As Value
IF AccumulatorSlot1Available = TRUE
THEN
ELSE
Plaintext/Encrypted Counters := Plaintext/Encrypted Counters 
'FFFFFFFFFFFFFFFF'
ENDIF
IF Accumulator 2 Amount > Accumulator 2 Upper Limit
THEN
AccumulatorBalance := '000000000000'
ELSE
AccumulatorBalance := Accumulator 2 Upper Limit - Accumulator 2 Amount
ENDIF
THEN

Subroutines

ELSE
'FFFFFFFFFFFFFFFF'
ENDIF
CASE ELSE
END SELECT
SELECT CASE 'Include In Issuer Application Data' in Counter 1 Control

CASE Include Counter As Value
THEN
Plaintext/Encrypted Counters[1] := Counter 1 Number
ELSE
ENDIF
CounterSlot1Available := FALSE
IF Counter 1 Number > Counter 1 Upper Limit
THEN
CounterBalance := '00'
ELSE
CounterBalance := Counter 1 Upper Limit - Counter 1 Number
ENDIF
THEN
Plaintext/Encrypted Counters[1] := CounterBalance
ELSE
ENDIF
CounterSlot1Available := FALSE
CASE ELSE
END SELECT
SELECT CASE 'Include In Issuer Application Data' in Counter 2 Control

CASE Include Counter As Value
THEN
IF CounterSlot1Available = TRUE
THEN
ELSE
ENDIF
ELSE

Subroutines
THEN
ELSE
THEN
'FFFFFFFFFFFFFFFF'
ELSE
ENDIF
ENDIF
ENDIF
IF Counter 2 Number > Counter 2 Upper Limit
THEN
CounterBalance := '00'
ELSE
CounterBalance := Counter 2 Upper Limit - Counter 2 Number
ENDIF
THEN
THEN
ELSE
ENDIF
ELSE
THEN
ELSE
THEN
'FFFFFFFFFFFFFFFF'
ELSE
ENDIF
ENDIF
ENDIF
CASE ELSE
END SELECT

Subroutines
IF 'Include RRP Data in Counters' in Application Control is set

AND RRP Counter ≠ 0
AND 'AC Returned In Second Generate AC' in Card Verification Results = AC
Not Requested In Second Generate AC
THEN
Plaintext/Encrypted Counters[8] := MIN('FF', Max Time For Processing Relay
Resistance APDU / 10)
IF AccumulatorSlot2Available = FALSE
THEN
Plaintext/Encrypted Counters[16] := MIN('FF', Min Time For Processing Relay
Resistance APDU / 10)
ENDIF
ENDIF
EXIT FUNCTION
END FUNCTION

Subroutines
Check Accumulators and Counters Limits and Set CVR
23.5. Check Accumulators and Counters Limits

and Set CVR
23.5.1. Description
Check the values of the two accumulators and the two counters stored in temporary
variables against the corresponding lower and upper limits and set the limit exceeded
bits in the CVR.
23.5.2. Computation
FUNCTION CheckAccsCntrsLimitsSetCVR( )
IF Accumulator 1 Amount Temp > Accumulator 1 Upper Limit

THEN
Set'Upper Cumulative Accumulator 1 Limit Exceeded' in Card Verification
Results
ENDIF
IF Accumulator 1 Amount Temp > Accumulator 1 Lower Limit

THEN
Set 'Lower Cumulative Accumulator 1 Limit Exceeded' in Card Verification
Results
ENDIF
IF Counter 1 Number Temp > Counter 1 Upper Limit

THEN
Set 'Upper Consecutive Counter 1 Limit Exceeded' in Card Verification Results
ENDIF
IF Counter 1 Number Temp > Counter 1 Lower Limit

THEN
Set 'Lower Consecutive Counter 1 Limit Exceeded' in Card Verification Results
ENDIF
IF Accumulator 2 Amount Temp > Accumulator 2 Upper Limit

THEN
Results
ENDIF
IF Accumulator 2 Amount Temp > Accumulator 2 Lower Limit

THEN
Results
ENDIF
IF Counter 2 Number Temp > Counter 2 Upper Limit

Subroutines
Check Accumulators and Counters Limits and Set CVR
THEN
ENDIF
IF Counter 2 Number Temp > Counter 2 Lower Limit

THEN
ENDIF
EXIT FUNCTION
END FUNCTION

Subroutines
Check Accumulators and Counters Limits and Set/Reset CVR
23.6. Check Accumulators and Counters Limits

and Set/Reset CVR
23.6.1. Description
variables against the corresponding lower and upper limits and set or reset the limit
exceeded bits in the CVR.
23.6.2. Computation
FUNCTION CheckAccsCntrsLimitsSetResetCVR( )

EXIT FUNCTION
END FUNCTION

Subroutines
Check for CVM Transaction
23.7. Check for CVM Transaction
23.7.1. Description
Check if the transaction is performed with cardholder verification. The transaction is
a CVM transaction if it is performed with:
 successful offline PIN,
 or online PIN,
 or signature.
23.7.2. Output
Boolean:
 True if the transaction is done with cardholder verification (CVM transaction)
 False if the transaction is done without cardholder verification (noCVM
transaction)
23.7.3. Computation
FUNCTION CheckCVMTransaction( ) AS BOOLEAN
IF (((CVM Results[1] AND 'BF') = '1E' AND CVM Results[3] = '00')

OR ((CVM Results[1] AND 'BF') = '02' AND CVM Results[3] = '00')
OR ('Offline PIN Verification Successful' in PIN Verification Status is set))
THEN
CheckCVMTransaction := TRUE
ELSE
CheckCVMTransaction := FALSE
ENDIF
EXIT FUNCTION
END FUNCTION

Subroutines
Check Format of Issuer Updates Data
23.8. Check Format of Issuer Updates Data
23.8.1. Description
Check if Issuer Updates Data is correctly formatted.
23.8.2. Output
Boolean:
 True if Issuer Updates Data is correctly formatted
 False if Issuer Updates Data is not correctly formatted
23.8.3. Computation
FUNCTION CheckIssuerUpdates( ) AS BOOLEAN
IF 'Update Type' in Issuer Updates Data  Update Accumulators And Counters

THEN
CheckIssuerUpdates := FALSE
EXIT FUNCTION
ENDIF
UpdatesLength := 3
FOR i := 1 TO 6
IF Issuer Updates Data[2][i] = 1b
THEN
UpdatesLength := UpdatesLength + 6
ENDIF
NEXT
FOR i := 1 TO 6
IF Issuer Updates Data[3][i] = 1b
THEN
UpdatesLength := UpdatesLength + 1
ENDIF
NEXT
IF Length(Issuer Updates Data) = UpdatesLength
THEN
CheckIssuerUpdates := TRUE
EXIT FUNCTION
ELSE
CheckIssuerUpdates := FALSE
EXIT FUNCTION
ENDIF
END FUNCTION
Note
The Length(Issuer Updates Data) is the length in bytes of the Issuer Updates Data.

Subroutines
Check Format of Transaction Date
23.9. Check Format of Transaction Date
23.9.1. Description
Check if the format of the transaction date is correct. The transaction date is correctly
formatted if:
 the year is between 0 and 88,
 the month is between 1 and 12,
 and the day is between 1 and 31.
23.9.2. Output
Boolean:
 True if the format of the transaction date is correct
 False if the format of the transaction date is not correct
23.9.3. Computation
FUNCTION CheckFormatOfDate( ) AS BOOLEAN
IF (Transaction Date[1] > '88' OR Transaction Date[1][4 : 1] > 9)

THEN
CheckFormatOfDate := FALSE
EXIT FUNCTION
ENDIF
IF (Transaction Date[2] = '00' OR Transaction Date[2] > '12' OR Transaction

Date[2][4 : 1] > 9)
THEN
EXIT FUNCTION
ENDIF
IF (Transaction Date[3] = '00' OR Transaction Date[3] > '31' OR Transaction

Date[3][4 : 1] > 9)
THEN
EXIT FUNCTION
ENDIF
CheckFormatOfDate := TRUE
EXIT FUNCTION
END FUNCTION

Subroutines
Check If Record Is in Read Record Filter
23.10. Check If Record Is in Read Record Filter
23.10.1. Description
When attempting to read a record in a file with SFI in the range 1 to 10, check if the
record is referenced in the Read Record Filter. If the record is referenced in the Read
Record Filter, it can not be read with the READ RECORD command on the active
interface.
If the length of the Read Record Filter is less than 4 bytes, all records can be read. If
the length of the Read Record Filter is not a multiple of 4 bytes, the last byte(s) are
discarded.
23.10.2. Output
Boolean:
 True if record is referenced in the Read Record Filter
 False if the record is not referenced in the Read Record Filter
23.10.3. Computation
FUNCTION CheckIfRecordInFilter( ) AS BOOLEAN
NumberOfEntries := Length(Read Record Filter) / 4

IF NumberOfEntries = 0
THEN
CheckIfRecordInFilter := FALSE
EXIT FUNCTION
ENDIF
FOR i := 1 TO NumberOfEntries
Entry := Read Record Filter[(i*4-3) : i*4]
IF (Reference Control Parameter[8 : 4] = Entry[1][8 : 4] AND Record Number >=
Entry[2] AND Record Number <= Entry[3])
THEN
CheckIfRecordInFilter := TRUE
EXIT FUNCTION
ENDIF
NEXT
CheckIfRecordInFilter := FALSE
EXIT FUNCTION
END FUNCTION
Note
The Length(Read Record Filter) is the length in bytes of the data value of the Read
Record Filter. The division is the truncated integer division.

Subroutines
Check Temp Accumulators and Temp Counters Limits and Set/Reset CVR
23.11. Check Temp Accumulators and Temp

Counters Limits and Set/Reset CVR
variables against the corresponding lower and upper limits stored in temporary
variables and set or reset the limit exceeded bits in the CVR.
FUNCTION CheckTempAccsCntrsLimitsSetResetCVR( )

IF Accumulator 1 Amount Temp > Accumulator 1 Upper Limit Temp

THEN
Results
ENDIF
IF Accumulator 1 Amount Temp > Accumulator 1 Lower Limit Temp

THEN
Results
ENDIF
IF Counter 1 Number Temp > Counter 1 Upper Limit Temp

THEN
ENDIF
IF Counter 1 Number Temp > Counter 1 Lower Limit Temp

THEN
ENDIF

Subroutines
Check Temp Accumulators and Temp Counters Limits and Set/Reset CVR
IF Accumulator 2 Amount Temp > Accumulator 2 Upper Limit Temp

THEN
Results
ENDIF
IF Accumulator 2 Amount Temp > Accumulator 2 Lower Limit Temp

THEN
Set'Lower Cumulative Accumulator 2 Limit Exceeded' in Card Verification
Results
ENDIF
IF Counter 2 Number Temp > Counter 2 Upper Limit Temp

THEN
ENDIF
IF Counter 2 Number Temp > Counter 2 Lower Limit Temp

THEN
ENDIF
EXIT FUNCTION
END FUNCTION

Subroutines
Compute M/Chip 2.05 CVR
23.12. Compute M/Chip 2.05 CVR
Map the CVR into M/Chip 2.05 format.
FUNCTION Compute2.05CVR( )
CVR V2.05 := '00000000'

'Length' in CVR V2.05 := '03'
'AC Returned In Second Generate AC' in CVR V2.05 := 'AC Returned In Second
Generate AC' in Card Verification Results
'AC Returned In First Generate AC' in CVR V2.05 := 'AC Returned In First Generate
AC' in Card Verification Results
'Offline PIN Verification Performed' in CVR V2.05 := 'Offline PIN Verification
Performed' in Card Verification Results
'Offline PIN Verification Failed' in CVR V2.05 := 'Offline PIN Verification Failed' in
'Unable To Go Online' in CVR V2.05 := 'Unable To Go Online Indicated' in Card
'PTL Exceeded' in CVR V2.05 := 'PTL Exceeded' in Card Verification Results
'Maximum Offline Transaction Amount Exceeded' in CVR V2.05 := 'MTA Limit
Exceeded' in Card Verification Results
'LCOL Or LCOTA Exceeded' in CVR V2.05 := ('Lower Consecutive Counter 1 Limit
Exceeded' in Card Verification Results OR 'Lower Cumulative Accumulator 1 Limit
Exceeded' in Card Verification Results OR 'Lower Consecutive Counter 2 Limit
Exceeded' in Card Verification Results)
'UCOL Or UCOTA Exceeded' in CVR V2.05 := ('Upper Consecutive Counter 1 Limit
Exceeded' in Card Verification Results OR 'Upper Cumulative Accumulator 1 Limit
Exceeded' in Card Verification Results OR 'Upper Consecutive Counter 2 Limit
'Last Online Transaction Not Completed' in CVR V2.05 := 'Last Online Transaction
Not Completed' in Card Verification Results
EXIT FUNCTION
END FUNCTION

Subroutines
Compute M/Chip 2.2 CVR
23.13. Compute M/Chip 2.2 CVR
Map the CVR into M/Chip 2.2 format.
CVR V2.1/V2.2 := '00000000'

'Length' in CVR V2.1/V2.2 := '03'
'AC Returned In Second Generate AC' in CVR V2.1/V2.2 := 'AC Returned In Second
'AC Returned In First Generate AC' in CVR V2.1/V2.2 := 'AC Returned In First
'Offline PIN Verification Performed' in CVR V2.1/V2.2 := 'Offline PIN Verification
'Offline PIN Verification Failed' in CVR V2.1/V2.2 := 'Offline PIN Verification
Failed' in Card Verification Results
'Unable To Go Online' in CVR V2.1/V2.2 := 'Unable To Go Online Indicated' in Card
'PTL Exceeded' in CVR V2.1/V2.2 := 'PTL Exceeded' in Card Verification Results
'LCOL Or LCOTA Exceeded' in CVR V2.1/V2.2 := ('Lower Consecutive Counter 1
Limit Exceeded' in Card Verification Results OR 'Lower Cumulative Accumulator 1
Limit Exceeded' in Card Verification Results OR 'Lower Consecutive Counter 2 Limit
'UCOL Or UCOTA Exceeded' in CVR V2.1/V2.2 := ('Upper Consecutive Counter 1
Limit Exceeded' in Card Verification Results OR 'Upper Cumulative Accumulator 1
Limit Exceeded' in Card Verification Results OR 'Upper Consecutive Counter 2 Limit
'Last Online Transaction Not Completed' in CVR V2.1/V2.2 := 'Last Online
Transaction Not Completed' in Card Verification Results
EXIT FUNCTION
END FUNCTION

Subroutines
Compute M/Chip 4 1.1 CVR
23.14. Compute M/Chip 4 1.1 CVR
Map the CVR into M/Chip 4 version 1.1 format.
CVR V1.1/V1.3 := '000000000000'

'AC Returned In Second Generate AC' in CVR V1.1/V1.3 := 'AC Returned In Second
'AC Returned In First Generate AC' in CVR V1.1/V1.3 := 'AC Returned In First
'Offline PIN Verification Performed' in CVR V1.1/V1.3 := 'Offline PIN Verification
'Offline PIN Verification Successful' in CVR V1.1/V1.3 := 'Offline PIN Verification
Successful' in Card Verification Results
'Issuer Authentication Performed' in CVR V1.1/V1.3 := 'Issuer Authentication
'CIAC-Default Skipped On CAT3' in CVR V1.1/V1.3 := 'CIAC-Default Skipped On
CAT3' in Card Verification Results
'Low Order Nibble Of Script Counter' in CVR V1.1/V1.3 := 'Low Order Nibble Of
Script Counter' in Card Verification Results
'Low Order Nibble Of PIN Try Counter' in CVR V1.1/V1.3 := 'Low Order Nibble Of
PIN Try Counter' in Card Verification Results
'Unable To Go Online Indicated' in CVR V1.1/V1.3 := 'Unable To Go Online
Indicated' in Card Verification Results
'Offline PIN Verification Not Performed' in CVR V1.1/V1.3 := 'Offline PIN
Verification Not Performed' in Card Verification Results
'Offline PIN Verification Failed' in CVR V1.1/V1.3 := 'Offline PIN Verification
Failed' in Card Verification Results
'PTL Exceeded' in CVR V1.1/V1.3 := 'PTL Exceeded' in Card Verification Results
'International Transaction' in CVR V1.1/V1.3 := 'International Transaction' in Card
'Domestic Transaction' in CVR V1.1/V1.3 := 'Domestic Transaction' in Card
'Terminal Erroneously Considers Offline PIN OK' in CVR V1.1/V1.3 := 'Terminal
Erroneously Considers Offline PIN OK' in Card Verification Results
'Lower Consecutive Offline Limit Exceeded' in CVR V1.1/V1.3 := 'Lower
Consecutive Counter 1 Limit Exceeded' in Card Verification Results
'Upper Consecutive Offline Limit Exceeded' in CVR V1.1/V1.3 := 'Upper Consecutive
Counter 1 Limit Exceeded' in Card Verification Results
'Lower Cumulative Offline Limit Exceeded' in CVR V1.1/V1.3 := 'Lower Cumulative
Accumulator 1 Limit Exceeded' in Card Verification Results
'Upper Cumulative Offline Limit Exceeded' in CVR V1.1/V1.3 := 'Upper Cumulative
Accumulator 1 Limit Exceeded' in Card Verification Results

Subroutines
Compute M/Chip 4 1.1 CVR
'Go Online On Next Transaction Was Set' in CVR V1.1/V1.3 := 'Go Online On Next
Transaction Was Set' in Card Verification Results
Issuer Authentication Failed in CVR V1.1/V1.3 := Issuer Authentication Failed in
'Script Received' in CVR V1.1/V1.3 := 'Script Received' in Card Verification Results
'Script Failed' in CVR V1.1/V1.3 := 'Script Failed' in Card Verification Results
'Match Found In Additional Check Table' in CVR V1.1/V1.3 := 'Match Found In
Additional Check Table' in Card Verification Results
'No Match Found In Additional Check Table' in CVR V1.1/V1.3 := 'No Match Found
In Additional Check Table' in Card Verification Results
'DDA Returned' in CVR V1.1/V1.3 := 'DDA Returned' in Card Verification Results
'Combined DDA/AC Generation Returned In First Generate AC' in CVR V1.1/V1.3 :=

' Combined DDA/AC Generation Returned In First Generate AC' in Card Verification
Results
'Combined DDA/AC Generation Returned In Second Generate AC' in CVR V1.1/V1.3

:= ' Combined DDA/AC Generation Returned In Second Generate AC' in Card
'Offline Encrypted PIN Verification Performed' in CVR V1.1/V1.3 := 'Offline

Encrypted PIN Verification Performed' in Card Verification Results
EXIT FUNCTION
END FUNCTION
Note
Since the position of the bits of the CVR V1.1/V1.3 and the bits of the Card
Verification Results appearing in the assignations is identical, this can be efficiently
implemented by masking the Card Verification Results and copying the masked value
in the CVR V1.1/V1.3.

Subroutines
Determine Accumulator Active Flag
23.15. Determine Accumulator Active Flag
Determine if an accumulator will be active for the transaction and sets the
corresponding active flag. Only accumulators with the active flag set may be updated
by the transaction.
23.15.2. Input arguments

x: accumulator identifier:
 1 for accumulator 1
 2 for accumulator 2.
FUNCTION DetermineAccActiveFlag( x )
Return Value := CALL RecognizeCurrency( x )

IF Return Value = FALSE
THEN
EXIT FUNCTION
ENDIF
SELECT CASE 'Accumulation Mode' in Accumulator x Control

CASE Never
EXIT FUNCTION
CASE Accumulate CVM transactions
THEN
EXIT FUNCTION
ENDIF
CASE Accumulate NoCVM transactions
IF Return Value = TRUE
THEN
EXIT FUNCTION
ENDIF
CASE Always
END SELECT

Subroutines
Determine Accumulator Active Flag
IF 'Use CVR Dependency' in Accumulator x Control is set

THEN
IF 'Input Byte Number' in Accumulator x CVR DependencyData > 6 OR 'Input
Byte Number' in Accumulator x CVR Dependency Data = 0
THEN
EXIT FUNCTION
ENDIF
IF Card Verification
Results['Input Byte Number'] AND 'Condition Mask' in
Accumulator x CVR Dependency Data  'Comparison Value' in Accumulator x
CVR Dependency Data
THEN
EXIT FUNCTION
ENDIF
ENDIF
Set Accumulator x Active Flag

EXIT FUNCTION
END FUNCTION

Subroutines
Determine Counter Active Flag
23.16. Determine Counter Active Flag
Determine if a counter will be active for the transaction and sets the corresponding
active flag. Only counters with the active flag set may be updated by the transaction.
23.16.2. Input Arguments

x: counter identifier:
 1 for counter 1,
 2 for counter 2.
FUNCTION DetermineCntrActiveFlag( x )
IF 'Count Even When Cumulated' in Counter x Control is not set

THEN
IF Accumulator 1 Active Flag = TRUE OR Accumulator 2 Active Flag = TRUE
THEN
EXIT FUNCTION
ENDIF
SELECT CASE 'Counting Mode' in Counter x Control

CASE Never
EXIT FUNCTION
CASE Count CVM transactions
THEN
EXIT FUNCTION
ENDIF
CASE Count NoCVM transactions
IF Return Value = TRUE
THEN
EXIT FUNCTION
ENDIF
CASE Always
END SELECT

Subroutines
Determine Counter Active Flag
IF 'Use CVR Dependency' in Counter x Control is set

THEN
IF 'Input Byte Number' in Counter x CVR Dependency Data > 6 OR 'Input Byte
Number' in Counter x CVR Dependency Data = 0
THEN
EXIT FUNCTION
ENDIF
IF Card Verification
Results['Input Byte Number'] AND 'Condition Mask' in
Counter x CVR Dependency Data  'Comparison Value' in Counter x CVR
Dependency Data
THEN
EXIT FUNCTION
ENDIF
ENDIF
Set Counter x Active Flag

EXIT FUNCTION
END FUNCTION

Subroutines
Process Additional Check Table
23.17. Process Additional Check Table
Compares a segment extracted from CDOL1 Related Data with entries in the
Additional Check Table.
The segment to extract is parameterized in the Additional Check Table. Before
comparison with the set of entries, the extracted segment is masked with a value also
present in the Additional Check Table.
If a match is found between the masked segment and the entries, a bit in the
decisional part of the Card Verification Results is set. If not match is found, another
bit set.
FUNCTION ProcessAddCheckTable( )
IF 'Position In CDOL1 Related Data' in Additional Check Table = '00'

OR 'Position In CDOL1 Related Data' in Additional Check Table + 'Length
In CDOL1
Related Data' in Additional Check Table -1 > CDOL1 Related Data Length
OR 'Length In CDOL1 Related Data' in Additional Check Table * 'Number Of Entries'
in Additional Check Table > 15
OR 'Length In CDOL1 Related Data' in Additional Check Table = '00'
OR 'Number Of Entries' in Additional Check Table < 2
THEN
EXIT FUNCTION
ENDIF
MaskedValue := CDOL1 Related Data ['Position In CDOL1 Related Data' in

Additional Check Table : 'Position In CDOL1 Related Data' in Additional Check
Table + 'Length In CDOL1 Related Data' in Additional Check Table -1] AND 'Bit
Mask' in Additional Check Table
FOR i := 2 TO 'Number Of Entries' in Additional Check Table

Entry := Additional Check Table [4 + ((i -1) * 'Length In CDOL1 Related Data' in
Additional Check Table) : 4 + (i * 'Length In CDOL1 Related Data' in Additional
Check Table) -1]
IF MaskedValue = Entry
THEN
Set 'Match Found In Additional Check Table' in Card Verification Results
EXIT FUNCTION
ENDIF
ENDFOR
Set 'No Match Found In Additional Check Table' in Card Verification Results
EXIT FUNCTION
END FUNCTION

Subroutines
23.18. Process Issuer Updates
Process Issuer Updates Data. Byte 2 identifies accumulator data and byte 3 identifies
counters data present in the Issuer Updates Data.
FUNCTION ProcessIssuerUpdates( )
Position =4
IF 'Accumulator 1 Amount Included' in Issuer Updates Data is set
THEN
Accumulator 1 Amount Temp := Issuer Updates Data[Position : Position + 6]
Accumulator 1 Amount := Issuer Updates Data[Position : Position + 6] (do not
commit)
Position := Position + 6
ELSE
ENDIF
IF 'Accumulator 1 Lower Limit Included' in Issuer Updates Data is set
THEN
Accumulator 1 Lower Limit Temp := Issuer Updates Data[Position : Position + 6]
Accumulator 1 Lower Limit := Issuer Updates Data[Position : Position + 6] (do
not commit)
ELSE
Accumulator 1 Lower Limit Temp := Accumulator 1 Lower Limit
ENDIF
IF 'Accumulator 1 Upper Limit Included' in Issuer Updates Data is set
THEN
Accumulator 1 Upper Limit Temp := Issuer Updates Data[Position : Position + 6]
Accumulator 1 Upper Limit := Issuer Updates Data[Position : Position + 6] (do
not commit)
ELSE
Accumulator 1 Upper Limit Temp := Accumulator 1 Upper Limit
ENDIF
IF 'Accumulator 2 Amount Included' in Issuer Updates Data is set

THEN
Accumulator 2 Amount Temp := Issuer Updates Data[Position : Position + 6]
Accumulator 2 Amount := Issuer Updates Data[Position : Position + 6] (do not
commit)
ELSE

Subroutines
ENDIF
IF 'Accumulator 2 Lower Limit Included' in Issuer Updates Data is set
THEN
Accumulator 2 Lower Limit Temp := Issuer Updates Data[Position : Position + 6]
Accumulator 2 Lower Limit := Issuer Updates Data[Position : Position + 6] (do
not commit)
ELSE
Accumulator 2 Lower Limit Temp := Accumulator 2 Lower Limit
ENDIF
IF 'Accumulator 2 Upper Limit Included' in Issuer Updates Data is set
THEN
Accumulator 2 Upper Limit Temp := Issuer Updates Data[Position : Position + 6]
Accumulator 2 Upper Limit := Issuer Updates Data[Position : Position + 6] (do
not commit)
ELSE
Accumulator 2 Upper Limit Temp := Accumulator 2 Upper Limit
ENDIF
IF 'Counter 1 Number Included' in Issuer Updates Data is set

THEN
Counter 1 Number Temp := Issuer Updates Data[Position : Position + 1]
Counter 1 Number := Issuer Updates Data[Position : Position + 1] (do not
commit)
ELSE
ENDIF
IF 'Counter 1 Lower Limit Included' in Issuer Updates Data is set
THEN
Counter 1 Lower Limit Temp := Issuer Updates Data[Position : Position + 1]
Counter 1 Lower Limit := Issuer Updates Data[Position : Position + 1] (do not
commit)
ELSE
Counter 1 Lower Limit Temp := Counter 1 Lower Limit
ENDIF
IF 'Counter 1 Upper Limit Included' in Issuer Updates Data is set
THEN
Counter 1 Upper Limit Temp := Issuer Updates Data[Position : Position + 1]
Counter 1 Upper Limit := Issuer Updates Data[Position : Position + 1] (do not
commit)
ELSE
Counter 1 Upper Limit Temp := Counter 1 Upper Limit
ENDIF

Subroutines
IF 'Counter 2 Number Included' in Issuer Updates Data is set

THEN
Counter 2 Number Temp := Issuer Updates Data[Position : Position + 1]
Counter 2 Number := Issuer Updates Data[Position : Position + 1] (do not
commit)
ELSE
ENDIF
IF 'Counter 2 Lower Limit Included' in Issuer Updates Data is set
THEN
Counter 2 Lower Limit Temp := Issuer Updates Data[Position : Position + 1]
Counter 2 Lower Limit := Issuer Updates Data[Position : Position + 1] (do not
commit)
ELSE
Counter 2 Lower Limit Temp := Counter 2 Lower Limit
ENDIF
IF 'Counter 2 Upper Limit Included' in Issuer Updates Data is set
THEN
Counter 2 Upper Limit Temp := Issuer Updates Data[Position : Position + 1]
Counter 2 Upper Limit := Issuer Updates Data[Position : Position + 1] (do not
commit)
ELSE
Counter 2 Upper Limit Temp := Counter 2 Upper Limit
ENDIF
EXIT FUNCTION
END FUNCTION

Subroutines
Recognize Currency
23.19. Recognize Currency
Recognize if the currency of a transaction is supported by an accumulator. The
currency is supported if it is:
 The currency of the accumulator,
 Or it is present in the currency conversion table of the accumulator.
23.19.2. Input Arguments

x: accumulator identifier:
 1 for accumulator 1,
 2 for accumulator 2.
23.19.3. Output
Boolean:
 True if the currency of the transaction is supported by accumulator x
 False if the currency of the transaction is not supported by accumulator x
FUNCTION RecognizeCurrency( x ) AS BOOLEAN
IF Transaction Currency Code = Accumulator x Currency Code

THEN
RecognizeCurrency := TRUE
EXIT FUNCTION
ENDIF
FOR i := 1 TO 5
IF Transaction Currency Code = 'Currency Code i' in Accumulator x Currency
Conversion Table
THEN
RecognizeCurrency := TRUE
EXIT FUNCTION
ENDIF
NEXT
RecognizeCurrency := FALSE
EXIT FUNCTION
END FUNCTION

Subroutines
Save Active Accumulators and Counters
23.20. Save Active Accumulators and Counters
Save the values stored in the temporary variables in the two accumulators and the two
counters.
FUNCTION SaveActiveAccsCntrs( )
IF Accumulator 1 Active Flag is set

THEN
Accumulator 1 Amount := Accumulator 1 Amount Temp (do not commit)
ENDIF

THEN
Accumulator 2 Amount := Accumulator 2 Amount Temp (do not commit)
ENDIF
IF Counter 1 Active Flag is set

THEN
Counter 1 Number := Counter 1 Number Temp (do not commit)
ENDIF
IF Counter 2 Active Flag is set

THEN
Counter 2 Number := Counter 2 Number Temp (do not commit)
ENDIF
EXIT FUNCTION
END FUNCTION

Subroutines
Update Temporary Accumulators and Counters
23.21. Update Temporary Accumulators and

Counters
Update the two accumulators and the two counters in temporary variables, according
to the transaction characteristics and personalization settings. The function calls the
AddAmountToTempAccumulator( x ) function to add the amount of the transaction to
a temporary accumulator.
FUNCTION UpdateTempAccsCntrs( )

THEN
Call AddAmountToTempAccumulator( 1 )
ENDIF

THEN
Call AddAmountToTempAccumulator( 2 )
ENDIF
IF Counter 1 Active Flag is set AND Amount, Authorized (Numeric)  '000000000000'

THEN
IF Counter 1 Number = 'FF'
THEN
Counter 1 Number Temp := 'FF'
ELSE
Counter 1 Number Temp := Counter 1 Number + 1
ENDIF
ENDIF
IF Counter 2 Active Flag is set AND Amount, Authorized (Numeric)  '000000000000'

THEN
IF Counter 2 Number = 'FF'
THEN
Counter 2 Number Temp := 'FF'
ELSE
Counter 2 Number Temp := Counter 2 Number + 1
ENDIF
ENDIF
EXIT FUNCTION
END FUNCTION

Data Dictionary
24. Data Dictionary

AC Master Key (Contact) .......................................................................................... 523
AC Master Key (Contactless) .................................................................................... 523
AC Master Key (MAS4C) ......................................................................................... 523
AC Session Key ......................................................................................................... 523
AC Session Key Counter (Contact) ........................................................................... 523
AC Session Key Counter (Contactless) ..................................................................... 524
AC Session Key Counter (MAS4C) .......................................................................... 524
AC Session Key Counter Limit (Contact) ................................................................. 524
AC Session Key Counter Limit (Contactless) ........................................................... 524
AC Session Key Counter Limit (MAS4C) ................................................................ 524
Accumulator 1 Active Flag ........................................................................................ 525
Accumulator 1 Amount.............................................................................................. 525
Accumulator 1 Amount Temp ................................................................................... 525
Accumulator 1 Control (Contact) .............................................................................. 525
Accumulator 1 Control (Contactless) ........................................................................ 526
Accumulator 1 Currency Code .................................................................................. 526
Accumulator 1 Currency Conversion Table .............................................................. 526
Accumulator 1 CVR Dependency Data (Contact) ..................................................... 528
Accumulator 1 CVR Dependency Data (Contactless) ............................................... 528
Accumulator 1 Lower Limit ...................................................................................... 528
Accumulator 1 Lower Limit Temp ............................................................................ 529
Accumulator 1 Upper Limit ....................................................................................... 529
Accumulator 1 Upper Limit Temp ............................................................................ 529
Accumulator 2 Active Flag ........................................................................................ 529
Accumulator 2 Amount.............................................................................................. 529
Accumulator 2 Amount Temp ................................................................................... 529
Accumulator 2 Control (Contact) .............................................................................. 530
Accumulator 2 Control (Contactless) ........................................................................ 530
Accumulator 2 Currency Code .................................................................................. 531
Accumulator 2 Currency Conversion Table .............................................................. 531
Accumulator 2 CVR Dependency Data (Contact) ..................................................... 532
Accumulator 2 CVR Dependency Data (Contactless) ............................................... 532
Accumulator 2 Lower Limit ...................................................................................... 533
Accumulator 2 Lower Limit Temp ............................................................................ 533
Accumulator 2 Upper Limit ....................................................................................... 533
Accumulator 2 Upper Limit Temp ............................................................................ 533
Additional Check Table ............................................................................................. 533
AID ............................................................................................................................ 534
Amount, Authorized (Numeric) ................................................................................. 534
Amount, Authorized 1 ............................................................................................... 534
Amount, Other (Numeric) .......................................................................................... 535
Amount, Other 1 ........................................................................................................ 535
Application Control (Contact) ................................................................................... 535
Application Control (Contactless) ............................................................................. 537

Data Dictionary
Application Cryptogram ............................................................................................ 539

Application Cryptogram (Recovery) ......................................................................... 539
Application File Locator (Contact) ............................................................................ 539
Application File Locator (Contactless) ...................................................................... 539
Application Interchange Profile (Contact) ................................................................. 540
Application Interchange Profile (Contactless) ........................................................... 540
Application Life Cycle Data ...................................................................................... 540
Application Transaction Counter ............................................................................... 541
Application Transaction Counter (Recovery) ............................................................ 541
Application Transaction Counter Limit ..................................................................... 541
ARPC Response Code ............................................................................................... 542
ATeC .......................................................................................................................... 542
Authorisation Response Code .................................................................................... 542
Card Issuer Action Code (Contact) – Decline ........................................................... 543
Card Issuer Action Code (Contact) – Default ............................................................ 544
Card Issuer Action Code (Contact) – Online ............................................................. 545
Card Issuer Action Code (Contactless) – Decline ..................................................... 546
Card Issuer Action Code (Contactless) – Default ...................................................... 547
Card Issuer Action Code (Contactless) – Online ....................................................... 548
Card Verification Results ........................................................................................... 549
CDA Transaction Flag (Recovery) ............................................................................ 550
CDOL1 ....................................................................................................................... 551
CDOL1 Related Data ................................................................................................. 551
CDOL1 Related Data Length..................................................................................... 551
CDOL2 ....................................................................................................................... 552
CDOL2 Related Data ................................................................................................. 552
Counter 1 Active Flag ................................................................................................ 552
Counter 1 Control (Contact) ...................................................................................... 553
Counter 1 Control (Contactless) ................................................................................ 553
Counter 1 CVR Dependency Data (Contact) ............................................................. 554
Counter 1 CVR Dependency Data (Contactless) ....................................................... 554
Counter 1 Lower Limit .............................................................................................. 554
Counter 1 Lower Limit Temp .................................................................................... 555
Counter 1 Number...................................................................................................... 555
Counter 1 Number Temp ........................................................................................... 555
Counter 1 Upper Limit ............................................................................................... 555
Counter 1 Upper Limit Temp .................................................................................... 555
Counter 2 Active Flag ................................................................................................ 555
Counter 2 Control (Contact) ...................................................................................... 556
Counter 2 Control (Contactless) ................................................................................ 556
Counter 2 CVR Dependency Data (Contact) ............................................................. 557
Counter 2 CVR Dependency Data (Contactless) ....................................................... 557
Counter 2 Lower Limit .............................................................................................. 557
Counter 2 Lower Limit Temp .................................................................................... 558
Counter 2 Number...................................................................................................... 558
Counter 2 Number Temp ........................................................................................... 558
Counter 2 Upper Limit ............................................................................................... 558
Counter 2 Upper Limit Temp .................................................................................... 558
CRM Country Code ................................................................................................... 559

Data Dictionary
Cryptogram Information Data.................................................................................... 559

Cryptogram Information Data (Recovery)................................................................. 559
Cryptogram Version Number .................................................................................... 560
Cryptogram Version Number V2.x............................................................................ 560
Current Date In Days ................................................................................................. 560
CVC3(Track1) ........................................................................................................... 560
CVC3(Track2) ........................................................................................................... 561
CVM Results.............................................................................................................. 561
CVR Issuer Discretionary Data (Contact) ................................................................. 561
CVR Issuer Discretionary Data (Contactless) ........................................................... 561
CVR V2.05 ................................................................................................................ 562
CVR V2.1/V2.2 ......................................................................................................... 563
CVR V1.1/V1.3 ......................................................................................................... 564
DAC/ICC Dyn Nr ...................................................................................................... 565
Data Authentication Code .......................................................................................... 565
DDOL ........................................................................................................................ 565
DDOL Related Data ................................................................................................... 565
Default ARPC Response Code .................................................................................. 566
Device Relay Resistance Entropy .............................................................................. 566
Device Relay Resistance Entropy (Recovery) ........................................................... 566
DRDOL ...................................................................................................................... 567
Dynamic Application Data To Be Signed ................................................................. 567
Enciphered New PIN Block ....................................................................................... 567
File Control Information ............................................................................................ 567
First AC ...................................................................................................................... 567
Get Challenge Flag .................................................................................................... 568
Hash Result ................................................................................................................ 568
Hash Result (Recovery) ............................................................................................. 568
ICC Dynamic Data ..................................................................................................... 568
ICC Dynamic Number ............................................................................................... 569
ICC Dynamic Number (Terminal) ............................................................................. 569
ICC Dynamic Number Master Key (Contact) ........................................................... 570
ICC Dynamic Number Master Key (Contactless) ..................................................... 570
ICC PIN Encipherment Private Key .......................................................................... 570
ICC Private Key ......................................................................................................... 570
ICC Unpredictable Number ....................................................................................... 570
Interface Enabling Switch .......................................................................................... 571
Interface Identifier (Contact) ..................................................................................... 571
Interface Identifier (Contactless) ............................................................................... 571
Internal Authentication Performed Flag .................................................................... 571
Issuer Application Data.............................................................................................. 572
Issuer Application Data V2.05 ................................................................................... 572
Issuer Application Data V2.1/V2.2 ............................................................................ 573
Issuer Application Data (Recovery)........................................................................... 573
Issuer Authentication Data ......................................................................................... 573
Issuer Updates Data ................................................................................................... 574
Issuer Updates Received Flag .................................................................................... 575
IVCVC3(Track1) (Contact) ....................................................................................... 575
IVCVC3(Track1) (Contactless) ................................................................................. 575

Data Dictionary
IVCVC3(Track2) (Contact) ....................................................................................... 575

IVCVC3(Track2) (Contactless) ................................................................................. 575
KDCVC3 (Contact) ................................................................................................... 576
KDCVC3 (Contactless) ............................................................................................. 576
Key Derivation Index (Contact)................................................................................. 576
Key Derivation Index (Contactless)........................................................................... 576
Key Derivation Index (MAS4C) ................................................................................ 576
Last Online ATC ........................................................................................................ 576
Last Online Transaction Date .................................................................................... 577
Length Of ICC PIN Encipherment Public Key Modulus .......................................... 577
Length Of ICC Public Key Modulus ......................................................................... 577
Linked Application Data ............................................................................................ 578
Linked Application Index .......................................................................................... 579
Log Data Table .......................................................................................................... 579
Log Format................................................................................................................. 580
MAC .......................................................................................................................... 580
Max Time For Processing Relay Resistance APDU (Contact) ................................. 580
Max Time For Processing Relay Resistance APDU (Contactless) ........................... 580
Merchant Custom Data .............................................................................................. 580
Min Time For Processing Relay Resistance APDU (Contact) .................................. 581
Min Time For Processing Relay Resistance APDU (Contactless) ............................ 581
MTA Currency Code ................................................................................................. 581
MTA CVM (Contact) ................................................................................................ 581
MTA CVM (Contactless) .......................................................................................... 581
MTA NoCVM (Contact)............................................................................................ 582
MTA NoCVM (Contactless)...................................................................................... 582
New Data Value ......................................................................................................... 582
New PIN Block .......................................................................................................... 582
New Record Value ..................................................................................................... 582
New SMI Key Flag .................................................................................................... 582
Number Of Days Off Line Limit ............................................................................... 583
Offline Accumulator Balance 1 ................................................................................. 583
Offline Accumulator Balance 2 ................................................................................. 583
Offline Change PIN Status......................................................................................... 584
Offline Counter Balance 1 ......................................................................................... 584
Offline Counter Balance 2 ......................................................................................... 584
PDOL ......................................................................................................................... 585
PDOL Related Data ................................................................................................... 585
PDOL Values ............................................................................................................. 585
PIN Decipherments Error Counter............................................................................. 585
PIN Decipherments Error Counter Limit ................................................................... 585
PIN Related Data ....................................................................................................... 585
PIN Try Counter ........................................................................................................ 586
PIN Try Limit ............................................................................................................ 586
PIN Verification Status .............................................................................................. 586
Plaintext/Encrypted Counters .................................................................................... 587
Previous Transaction History..................................................................................... 587
Rand ........................................................................................................................... 587
Read Record Filter (Contact) ..................................................................................... 587

Data Dictionary
Read Record Filter (Contactless) ............................................................................... 588

Record Number .......................................................................................................... 588
Recover AC Performed Flag ...................................................................................... 588
Recovered Data .......................................................................................................... 588
Reference Control Parameter ..................................................................................... 588
Reference PIN ............................................................................................................ 589
Relay Resistance Related Data .................................................................................. 589
Return Value .............................................................................................................. 589
RRP Counter .............................................................................................................. 589
RRP Performed Flag (Recovery) ............................................................................... 589
Script Counter ............................................................................................................ 590
Script Failed Flag ....................................................................................................... 590
Security Limits Status (Contact) ................................................................................ 590
Security Limits Status (Contactless) .......................................................................... 590
Security Limits Status Common ................................................................................ 591
Signed Dynamic Application Data ............................................................................ 591
SMC CSK Key Present Flag ...................................................................................... 591
SMC Master Key (Contact) ....................................................................................... 591
SMC Master Key (Contactless) ................................................................................. 591
SMC Session Key ...................................................................................................... 592
SMI CSK Key Present Flag ....................................................................................... 592
SMI Master Key (Contact)......................................................................................... 592
SMI Master Key (Contactless)................................................................................... 592
SMI Session Key........................................................................................................ 592
SMI Session Key Counter (Contact).......................................................................... 593
SMI Session Key Counter (Contactless).................................................................... 593
SMI Session Key Counter Limit (Contact) ................................................................ 593
SMI Session Key Counter Limit (Contactless) .......................................................... 593
Temp Transaction Log Record .................................................................................. 593
Terminal Country Code ............................................................................................. 594
Terminal Relay Resistance Entropy........................................................................... 594
Terminal Relay Resistance Entropy (Recovery)........................................................ 594
Terminal Type ............................................................................................................ 594
Terminal Verification Results .................................................................................... 594
Transaction Currency Code ....................................................................................... 595
Transaction Date ........................................................................................................ 596
Transaction Related Data ........................................................................................... 596
Transaction Time ....................................................................................................... 596
Transaction Type ....................................................................................................... 596
Transmission Time For Relay Resistance R-APDU (Contact).................................. 596
Transmission Time For Relay Resistance R-APDU (Contactless)............................ 596
Unpredictable Number ............................................................................................... 597
Unpredictable Number (Numeric) ............................................................................. 597
Unpredictable Number (Recovery) ............................................................................ 597

Data Dictionary

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key used to derive the AC Session Key when the contact
If the MasterCard Proprietary SKD is used, the AC Master Key
(Contact) is also used for ARPC verification.
AC Master Key (Contactless)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key used to derive the AC Session Key when the
If the MasterCard Proprietary SKD is used, the AC Master Key
(Contactless) is also used for ARPC verification.
AC Master Key (MAS4C)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key used to derive the AC Session Key when MAS4C
processing flow is active and 'Key for MAS4C Processing Flow' in
Application Control equals AC Master Key (MAS4C).
AC Session Key
Tag: –
Length: 16
Format: b
Type: Global transient
Description: ICC session key for the generation of the Application Cryptogram.
If EMV CSK derivation is used, the AC Session Key is also used for
ARPC verification.
A variant of the AC Session Key is also used to encrypt counters in
the Issuer Application Data if this option is selected.
AC Session Key Counter (Contact)

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Counts the number of AC Session Key derivations over the contact
interface since the application last successfully validated an ARPC
over the contact interface.

Data Dictionary

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Counts the number of AC Session Key derivations over the
contactless interface since the application last successfully validated
an ARPC over the contactless interface.
AC Session Key Counter (MAS4C)

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Counts the number of AC Session Key derivations that has been done
using AC Master Key (MAS4C) key.
AC Session Key Counter Limit (Contact)

Tag: 'DF3A'
Length: 2
Format: b
Type: Persistent
Description: Limits the number of AC Session Key derivations over the contact
over the contact interface.
AC Session Key Counter Limit (Contactless)

Tag: 'DF34'
Length: 2
Format: b
Type: Persistent
Description: Limits the number of AC Session Key derivations over the contactless
over the contactless interface.
AC Session Key Counter Limit (MAS4C)

Tag: 'DF78'
Length: 2
Format: b
Type: Persistent
Description: Limits the number of AC Session Key derivations that can be done
using AC Master Key (MAS4C) key.

Data Dictionary

Tag: –
Length: 1 bit
Format: b
Description: Indicates if Accumulator 1 Amount is to be accumulated during this
transaction. Its value is defined during the first GENERATE AC
based on Accumulator 1 Control and transaction related data.
Tag: 'DF3B'
Length: 6
Format: n12
Type: Persistent
Description: Represents the cumulative amount of transactions accepted offline
and fulfilling the criteria specified in Accumulator 1 Control.

Tag: –
Length: 6
Format: n12
Type: Local transient
Description: Temporary variable containing the updated value in volatile memory
of Accumulator 1 Amount.

Tag: 'DF11'
Length: 1
Format: b
Type: Persistent
Description: Holds configuration information that controls the use and operation
of Accumulator 1 when the contact interface is active.
Byte 1
b8-7 Accumulation Mode
00: Never
01: Accumulate CVM transactions
10: Accumulate NoCVM transactions
11: Always
b6 Use CVR Dependency
b5 RFU
b4 Offline PIN Reset
b3 Show
b2-1 Include In Issuer Application Data
00: Do Not Include
01: Include Accumulator As Value
10: Include As Balance
11: RFU

Data Dictionary

Tag: 'DF12'
Length: 1
Format: b
Type: Persistent
of Accumulator 1 when the contactless interface is active.
Byte 1
00: Never
11: Always
b5 RFU
b3 Show
00: Do Not Include
11: RFU

Tag: 'C9'
Length: 2
Format: n3
Type: Persistent
Description: Indicates the currency code of Accumulator 1.

Tag: 'D1'
Length: 25
Format: b
Type: Persistent
Description: Holds a table of currency conversion values in order to convert the
transaction amount from the transaction currency to the currency of
Accumulator 1.
If the currency code of the transaction amount = Currency Code i and
Conversion Exponent i[8] = 0b, then the transaction amount in the
currency of Accumulator 1 is defined by transaction amount *
Conversion Rate i * (10 to the power Conversion Exponent i[7 : 1]).
Conversion Rate i / (10 to the power Conversion Exponent i[7 : 1]).
Where i = 1 to 5.
Note that the format of Conversion Rate i is n4.

Data Dictionary
Byte 1-2
Currency Code 1
Byte 3-4
Conversion Rate 1
Byte 5
Conversion Exponent 1
Byte 6-7
Currency Code 2
Byte 8-9
Conversion Rate 2
Byte 10
Byte 11-12
Currency Code 3
Byte 13-14
Conversion Rate 3
Byte 15
Byte 16-17
Currency Code 4
Byte 18-19
Conversion Rate 4
Byte 20
Byte 21-22
Currency Code 5
Byte 23-24
Conversion Rate 5
Byte 25

Data Dictionary

Tag: 'DF28'
Length: 3
Format: b
Type: Persistent
Description: Contains Card Verification Results comparison data to determine if
Accumulator 1 becomes active if a given Card Verification Results
pattern occurs when the contact interface is active.
If (Condition Mask AND CVR [Input Byte Number]) = Comparison
Value then the condition is satisfied for the use of Accumulator 1.
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: 'DF29'
Length: 3
Format: b
Type: Persistent
pattern occurs when the contactless interface is active.
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: 'CA'
Length: 6
Format: n12
Type: Persistent
Description: Accumulator 1 Amount and Accumulator 1 Amount Temp are
checked against this limit and if they are greater, the relevant Card
Verification Results bit is set.

Data Dictionary

Tag: –
Length: 6
Format: n12
of Accumulator 1 Lower Limit.

Tag: 'CB'
Length: 6
Format: n12
Type: Persistent
checked against this limit and if they are greater, the relevant Card

Tag: –
Length: 6
Format: n12

Tag: –
Length: 1 bit
Format: b
Description: Indicates if Accumulator 2 is to be accumulated during this
transaction. Its value is defined during the first GENERATE AC
based on Accumulator 2 Control and transaction related data.
Tag: 'DF13'
Length: 6
Format: n12
Type: Persistent
Description: Represents the cumulative amount of transactions accepted offline
and fulfilling the criteria specified in Accumulator 2 Control.

Tag: –
Length: 6
Format: n12
of Accumulator 2 Amount.

Data Dictionary

Tag: 'DF14'
Length: 1
Format: b
Type: Persistent
of Accumulator 2 when the contact interface is active.
Byte 1
00: Never
11: Always
b5 RFU
b3 Show
00: Do Not Include
11: RFU

Tag: 'DF15'
Length: 1
Format: b
Type: Persistent
of Accumulator 2 when the contactless interface is active.
Byte 1
00: Never
11: Always
b5 RFU
b3 Show
00: Do Not Include
11: RFU

Data Dictionary

Tag: 'DF16'
Length: 2
Format: n3
Type: Persistent
Description: Indicates the currency code of Accumulator 2.

Tag: 'DF17'
Length: 25
Format: b
Type: Persistent
Description: Holds a table of currency conversion values in order to convert the
transaction amount from the transaction currency to the currency of
Accumulator 2.
Conversion Rate i * (10 to the power Conversion Exponent i[7 : 1]).
Conversion Rate i / (10 to the power Conversion Exponent i[7 : 1]).
Where i = 1 to 5.
Note that the format of Conversion Rate i is n4.
Byte 1-2
Currency Code 1
Byte 3-4
Conversion Rate 1
Byte 5
Byte 6-7
Currency Code 2
Byte 8-9
Conversion Rate 2
Byte 10
Byte 11-12
Currency Code 3
Byte 13-14
Conversion Rate 3
Byte 15
Byte 16-17
Currency Code 4
Byte 18-19
Conversion Rate 4

Data Dictionary
Byte 20
Byte 21-22
Currency Code 5
Byte 23-24
Conversion Rate 5
Byte 25

Tag: 'DF2A'
Length: 3
Format: b
Type: Persistent
pattern occurs when the contact interface is active.
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: 'DF2B'
Length: 3
Format: b
Type: Persistent
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Data Dictionary

Tag: 'DF18'
Length: 6
Format: n12
Type: Persistent
checked against this value and if they are greater, the relevant Card

Tag: –
Length: 6
Format: n12

Tag: 'DF19'
Length: 6
Format: n12
Type: Persistent
checked against this value and if they are greater, the relevant Card

Tag: –
Length: 6
Format: n12
of Accumulator 2 Upper Limit.
Additional Check Table

Tag: 'D3'
Length: 18
Format: b
Type: Persistent
Description: Contains values that are compared to values given by the terminal in
CDOL1 Related Data. The result of the comparison is reflected in the
decision-making part of the Card Verification Results.
The check with the Additional Check Table is only performed if
activated by the Application Control.

Data Dictionary
AID
Byte 1
Position In CDOL1 Related Data
Byte 2
Length In CDOL1 Related Data
Byte 3
Number Of Entries
Byte 4-18
Entries
Entries contains the concatenation of the values used for the comparison, optionally padded
with 'FF' to make up 15 bytes. The first value is used as a bit mask.
Entries consist of the following:
 Bit Mask with length equal to Length In CDOL1 Related Data
 Value 1 with length equal to Length In CDOL1 Related Data
 ...
 Value Number Of Entries - 1 with length equal to Length In CDOL1 Related Data
 Padding with 'FF' of length equal to 15 – Number Of Entries * Length In CDOL1 Related
Data
AID
Tag: '4F'
Length: Variable, 5 - 16 bytes
Format: b
Type: Persistent
Description: As in [EMV]

Tag: '9F02'
Length: 6
Format: n12
Description: The Amount, Authorized (Numeric) is received from the terminal in
the first and optionally also in the second GENERATE AC.
It is used during CRM and as input for the Application Cryptogram
calculation.
Amount, Authorized 1
Tag: –
Length: 6
Format: n12
Description: Holds a copy of Amount, Authorized (Numeric) received during the
first GENERATE AC command

Data Dictionary

Tag: '9F03'
Length: 6
Format: n12
Description: The Amount, Other (Numeric) is received from the terminal in the
first and optionally also in the second GENERATE AC.
It is used as input for the Application Cryptogram calculation.
Amount, Other 1
Tag: –
Length: 6
Format: n12
Description: Holds a copy of Amount, Other (Numeric) received during the first
GENERATE AC command

Tag: 'D5'
Length: 6
Format: b
Type: Persistent
Description: The Application Control (Contact) activates or de-activates functions
in the application when the contact interface is active.
This activation or de-activation is dynamic. The Application Control
(Contact) can be modified with a PUT DATA command during the
application lifetime, and, in such a case, the behavior of the
application is modified.
The PUT DATA command applied to the Application Control
(Contact) may be used to switch from one session key derivation
method to the other. In this case, the switch applies immediately for
subsequent script commands.
Byte 1
b8 Accept Online Transactions Without ARPC
b7 Skip CIAC-Default On CAT3
b6 RFU
b5 Key For Offline Encrypted PIN Verification
0: DDA Key
1: Dedicated Key
b4 Offline Encrypted PIN Verification
b3 Offline Plaintext PIN Verification
b2 Session Key Derivation
0: MasterCard Proprietary SKD
1: EMV CSK
b1 Encrypt Offline Counters

Data Dictionary
Byte 2
b8-4 RFU
b3 Additional Check Table
b2 Allow Retrieval Of Balance
b1 Include Counters In AC
Byte 3
b8-7 Compute Cryptographic Checksum
00: RFU
01: Compute Cryptographic Checksum Supported
10: Compute Cryptographic Checksum Not Supported
11: RFU
b6 Decline If CDA Not Requested And RRP Performed
b5 Go Online If RRP Not Performed
b4 Decline If Unable To Go Online And RRP Not Performed
b3 Use M/Chip 4 CDOL1
b2 Enable Alternate Interface After TC Generated
b1 Enable Alternate Interface After Successful Verify
Byte 4
b8 Include Transaction In CRM If ARQC Is Requested
b7 Use CIAC-online To Decide On ARQC Request
b6 Generate Only TC Or AAC On TC Request
b5 MTA Check
b4 Maximum Number Of Days Offline Check
b3 Include RRP Data in Counters
b2 Plaintext Offline Change PIN
b1 Encrypted Offline Change PIN
Byte 5
b8 AAC Logging
b7 TC Logging
b6 ARQC Pre-logging
b5 Include Last Online ATC in IAD
b4-2 Issuer Host Backwards Compatibility
000: No Host Backwards Compatibility
001: V2.1/V2.2 Host Backwards Compatibility
010: V2.05 Host Backwards Compatibility
1xx: RFU
b1 Partial Authorization

Data Dictionary
Byte 6
b8 Enable Alternate Interface After First Gen AC
b7 Save Accumulators And Counters on ARQC Response
b6 AC for MAS4C
0: AAC
1:ARQC
b5 Key for MAS4C Processing Flow
0: AC Master Key
1: AC Master Key (MAS4C)
b4 Torn Transaction Recovery
b3 MAS4C Processing Flow
b2 Reset Script Counter With Online Response
b1 Allow Retrieval Of Transaction Log Records

Tag: 'D7'
Length: 6
Format: b
Type: Persistent
Description: The Application Control (Contactless) activates or de-activates
functions in the application when the contactless interface is active.
This activation or de-activation is dynamic. The Application Control
(Contactless) can be modified with a PUT DATA command during
the application lifetime, and, in such a case, the behavior of the
application is modified.
The PUT DATA command applied to the Application Control
(Contactless) may be used to switch from one session key derivation
method to the other. In this case, the switch applies immediately for
subsequent script commands.
Byte 1
b8 Accept Online Transactions Without ARPC
b7 Skip CIAC-Default On CAT3
b6 RFU
b5 Key For Offline Encrypted PIN Verification
0: DDA Key
1: Dedicated Key
b3 Offline Plaintext PIN Verification
b2 Session Key Derivation
0: MasterCard Proprietary SKD
1: EMV CSK
b1 Encrypt Offline Counters
Byte 2
b8-4 RFU
b3 Additional Check Table
b2 Allow Retrieval Of Balance
b1 Include Counters In AC

Data Dictionary
Byte 3
b8-7 Compute Cryptographic Checksum
00: RFU
01: Compute Cryptographic Checksum Supported
10: Compute Cryptographic Checksum Not Supported
11: RFU
b6 Decline If CDA Not Requested And RRP Performed
b5 Go Online If RRP Not Performed
b4 Decline If Unable To Go Online And RRP Not Performed
b3 Use M/Chip 4 CDOL1
b2 Enable Alternate Interface After TC Generated
b1 Enable Alternate Interface After Successful Verify
Byte 4
b8 Include Transaction In CRM If ARQC Is Requested
b7 Use CIAC-online To Decide On ARQC Request
b6 Generate Only TC Or AAC On TC Request
b5 MTA Check
b4 Maximum Number Of Days Offline Check
b3 Include RRP Data in Counters
b2 Plaintext Offline Change PIN
b1 Encrypted Offline Change PIN
Byte 5
b8 AAC Logging
b7 TC Logging
b6 ARQC Pre-logging
b5 Include Last Online ATC in IAD
b4-2 Issuer Host Backwards Compatibility
000: No Host Backwards Compatibility
010: V2.05 Host Backwards Compatibility
1xx: RFU
b1 Partial Authorization
Byte 6
b8 Enable Alternate Interface After First Gen AC
b7 Save Accumulators And Counters on ARQC Response
b6 AC for MAS4C Processing Flow
0: AAC
1:ARQC
b5 Key for MAS4C Processing Flow
0: AC Master Key
1: AC Master Key (MAS4C)
b4 Torn Transaction Recovery
b3 MAS4C Processing Flow
b2 Reset Script Counter With Online Response
b1 Allow Retrieval Of Transaction Log Records

Data Dictionary
Tag: '9F26'
Length: 8
Format: b
Description: The Application Cryptogram is generated during first and second
GENERATE AC. It is used to authenticate the transaction to the
issuer.
Application Cryptogram (Recovery)

Tag: –
Length: 8
Format: b
Type: Persistent
Description: A persistent copy of the Application Cryptogram for transaction
recovery.
Application File Locator (Contact)

Tag: '94'
Length: Variable
Format: b
Type: Persistent
Description: Application File Locator returned in response to the GET
PROCESSING OPTIONS command when the contact interface is
active.
Refer to [EMV] for a description of the Application File Locator
(Contact).
A memory space of at least 32 bytes must be available for the
Application File Locator (Contact).
Application File Locator (Contactless)

Tag: 'D9'
Length: Variable
Format: b
Type: Persistent
Description: Application File Locator returned in response to the GET
PROCESSING OPTIONS command when the contactless interface
is active.
Refer to [EMV BOOK C2] for a description of the Application File
Locator (Contactless).
A memory space of at least 32 bytes must be available for the
Application File Locator (Contact).

Data Dictionary

Tag: '82'
Length: 2
Format: b
Type: Persistent
Description: Application Interchange Profile returned in response to the GET
PROCESSING OPTIONS command when the contact interface is
active.
Refer to [EMV] for a description of the Application Interchange
Profile (Contact).
Application Interchange Profile (Contactless)

Tag: 'D8'
Length: 2
Format: b
Type: Persistent
Description: Application Interchange Profile returned in response to the GET
PROCESSING OPTIONS command when the contactless interface
is active.
Refer to [EMV BOOK C2] for a description of the Application
Interchange Profile (Contactless).
Application Life Cycle Data

Tag: '9F7E'
Length: 48
Format: b
Type: Persistent
Description: The purpose of the Application Life Cycle Data is to uniquely
identify the application code and the application issuer.
The way in which these data elements are stored in the application is
left to the implementation. Sub-elements may be coded in the
application itself (i.e. in the code) whilst others are set as part of
personalization.
Byte 1
Version Number
'04' for M/Chip Advance
Byte 2-8
Type Approval ID
The seven bytes reserved for the Type Approval ID contain an identifier given by MasterCard
when the application passes the Type Approval process.
Byte 9-28
Application Issuer ID
Twenty bytes are reserved to identify the application issuer, which is usually the card issuer.
Using this value, the issuer can identify the personalizer and the personalization batch.
Format and content are application issuer-specific.

Data Dictionary
Byte 29-48
Application Code ID
The last 20 bytes are used to uniquely identify the application code. This identifier supports
differentiation between different application behavior. Typically, this data element contains
the identifier of the application provider, and the identifier of the application code. It is the
responsibility of the application provider to ensure that this data element always differentiates
between the two different application behaviors. The easiest way to implement this feature is
to modify the value of this data element each time there is a modification to the:
 Application (version identifier)
 Application code (release identifier)
 Platform on which the application is actually running (e.g. virtual machine version x or y)
 Hardware on which the platform or the application is actually running
Format and content are implementation-specific.

Tag: '9F36'
Length: 2
Format: b
Type: Persistent
Application Transaction Counter (Recovery)

Tag: –
Length: 2
Format: b
Type: Persistent
Description: A persistent copy of the Application Transaction Counter for
transaction recovery.
Application Transaction Counter Limit

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Limits the number of transactions processed by the application.
When the Application Transaction Counter has reached the
Application Transaction Counter Limit, the application no longer
processes transactions.

Data Dictionary
ARPC Response Code
ARPC Response Code

Tag: –
Length: 2
Format: b
Description: Informs the application about the actions decided by the issuer. The
ARPC Response Code is sent to the application in the Issuer
Authentication Data (last two bytes).
Byte 1
b8 Accumulator 1 Not Eligible
b7 Counter 1 Not Eligible
b4-1 PIN Try Counter
Byte 2
b8-7 RFU
b6 Decline If Issuer Updates Not Received
b5 Approve Online Transaction
b4 Update PIN Try Counter
b3 Set Go Online On Next Transaction
b2-1 Update Accumulators/Counters
00: Do Not Update Accumulators/Counters
01: Set Accumulators/Counters To Upper Offline Limits
10: Reset Accumulators/Counters To Zero
11: Add Transaction To Accumulators/Counters
ATeC
Tag: –
Length: 2
Format: b
Description: Holds the first two bytes of the Additional Terminal Capabilities that
are passed to the card from the terminal as part of the PDOL Related
Data in the GET PROCESSING OPTIONS command.

Tag: '8A'
Length: 2
Format: an

Data Dictionary

Tag: 'C3'
Length: 3
Format: b
Type: Persistent
Description: The Card Issuer Action Codes (Contact) are compared to the
decisional part of the Card Verification Results to take decisions
when the contact interface is active.
Card Issuer Action Code (Contact) – Decline is used to set the
situations when a contact transaction is always declined at the first
GENERATE AC.
Byte 1
b8 Last Online Transaction Not Completed
b7 Unable To Go Online Indicated
b6 Offline PIN Verification Not Performed
b5 Offline PIN Verification Failed
b4 PTL Exceeded
b3 International Transaction
b2 Domestic Transaction
b1 Terminal Erroneously Considers Offline PIN OK
Byte 2
b8 Lower Consecutive Counter 1 Limit Exceeded
b7 Upper Consecutive Counter 1 Limit Exceeded
b6 Lower Cumulative Accumulator 1 Limit Exceeded
b5 Upper Cumulative Accumulator 1 Limit Exceeded
b4 Go Online On Next Transaction Was Set
b3 Issuer Authentication Failed
b2 Script Received
b1 Script Failed
Byte 3
b4 MTA Limit Exceeded
b3 Number Of Days Offline Limit Exceeded
b2 Match Found In Additional Check Table
b1 No Match Found In Additional Check Table

Data Dictionary

Tag: 'C4'
Length: 3
Format: b
Type: Persistent
Card Issuer Action Code (Contact) – Default is used to set the
situations when a contact transaction is declined if the terminal is not
online capable, or if a connection to the issuer is not possible.
Byte 1
b4 PTL Exceeded
Byte 2
b2 Script Received
b1 Script Failed
Byte 3

Data Dictionary

Tag: 'C5'
Length: 3
Format: b
Type: Persistent
Card Issuer Action Code (Contact) – Online is used to set the
situations when a contact transaction goes online if the terminal is
online capable.
If the option 'Use CIAC-online To Decide On ARQC Request' is
used, then the Card Issuer Action Codes (Contact) – Online is also
used to decline an online request over the contact interface.
Byte 1
b4 PTL Exceeded
Byte 2
b2 Script Received
b1 Script Failed
Byte 3

Data Dictionary

Tag: 'CF'
Length: 3
Format: b
Type: Persistent
Description: The Card Issuer Action Codes (Contactless) are compared to the
when the contactless interface is active.
Card Issuer Action Code (Contactless) – Decline is used to set the
situations when a contactless transaction is always declined at the
first GENERATE AC.
Byte 1
b4 PTL Exceeded
Byte 2
b2 Script Received
b1 Script Failed
Byte 3

Data Dictionary

Tag: 'CD'
Length: 3
Format: b
Type: Persistent
Card Issuer Action Code (Contactless) – Default is used to set the
situations when a contactless transaction is declined if the terminal is
not online capable, or if a connection to the issuer is not possible.
Byte 1
b4 PTL Exceeded
Byte 2
b2 Script Received
b1 Script Failed
Byte 3

Data Dictionary

Tag: 'CE'
Length: 3
Format: b
Type: Persistent
Card Issuer Action Code (Contactless) – Online is used to set the
situations when a contactless transaction goes online if the terminal is
online capable.
If the option 'Use CIAC-online To Decide On ARQC Request' is
used, then the Card Issuer Action Codes (Contactless) – Online is
also used to decline an online request over the contactless interface.
Byte 1
b4 PTL Exceeded
Byte 2
b2 Script Received
b1 Script Failed
Byte 3

Data Dictionary

Tag: '9F52'
Length: 6
Format: b
Description: The purpose of the Card Verification Results is to:
 Inform the issuer about the "context" of a transaction, as part of
the Issuer Application Data.
 Take the decision, on behalf of the issuer, to accept a transaction
offline, go online to the issuer, or decline offline.
The first three bytes of the Card Verification Results are used for
information only.
Bytes 4 to 6 are used for information and decision-making. They are
checked against the Card Issuer Action Code – Decline, Card Issuer
Action Code – Online and Card Issuer Action Code – Default during
CRM.
Byte 1-3
CVR Informative Part
Byte 4-6
CVR Decisional Part
Byte 1
b8-7 AC Returned In Second Generate AC
00: AAC Returned In Second Generate AC
01: TC Returned In Second Generate AC
10: AC Not Requested In Second Generate AC
11: RFU
b6-5 AC Returned In First Generate AC
00: AAC Returned In First Generate AC
01: TC Returned In First Generate AC
10: ARQC Returned In First Generate AC
11: RFU
b4 Date Check Failed
b3 Offline PIN Verification Performed
b2 Offline Encrypted PIN Verification Performed
b1 Offline PIN Verification Successful
Byte 2
b8 DDA Returned
b7 Combined DDA/AC Generation Returned In First Generate AC
b6 Combined DDA/AC Generation Returned In Second Generate AC
b5 Issuer Authentication Performed
b4 CIAC-Default Skipped On CAT3
b3 Offline Change PIN Result
b2-1 Issuer Discretionary
Byte 3
b8-5 Low Order Nibble Of Script Counter
b4-1 Low Order Nibble Of PIN Try Counter

Data Dictionary
Byte 4
b4 PTL Exceeded
Byte 5
b2 Script Received
b1 Script Failed
Byte 6

Tag: –
Length: 1 bit
Format: b
Type: Persistent
Description: The CDA Transaction Flag (Recovery) is used to record whether or
not the transaction stored for recovery was done with CDA.

Data Dictionary
CDOL1
CDOL1
Tag: '8C'
Length: Variable
Format: b
Type: Persistent
Description: Tells the terminal what data is needed in the first GENERATE AC.
The CDOL1 is not interpreted by M/Chip Advance and is stored in a
record referenced in the AFL.
M/Chip Advance supports the following initial values:
 If 'Use M/Chip 4 CDOL1' in Application Control is set:
'9F02069F03069F1A0295055F2A029A039C019F37049F35019
F45029F4C089F3403'
 If 'Use M/Chip 4 CDOL1' in Application Control is not set:
'9F02069F03069F1A0295055F2A029A039C019F37049F35019
F45029F4C089F34039F21039F7C14'
M/Chip Advance allows the extension of CDOL1 with additional data
elements (i.e. append new data elements to the CDOL1 initial
content).
CDOL1 Related Data

Tag: –
Length: Variable
Format: b
Description: The CDOL1 Related Data is used to compute the intermediate hash
result during the calculation of the Signed Dynamic Application
Data.
CDOL1 Related Data Length

Tag: 'C7'
Length: 1
Format: b
Type: Persistent
Description: Length of CDOL1 Related Data.
If no extension to CDOL1 Related Data is used, CDOL1 Related
Data Length value is '2B' (If 'Use M/Chip 4 CDOL1' in Application
Control is set) or '42' (If 'Use M/Chip 4 CDOL1' in Application
Control is not set).
M/Chip Advance allows the extension of this value by at least ten
bytes. The maximum value is implementation specific.
The personalization value for CDOL1 Related Data Length must be
consistent with the personalization value for CDOL1.

Data Dictionary
CDOL2
CDOL2
Tag: '8D'
Length: 12 or 18
Format: b
Type: Persistent
Description: Tells the terminal what data is needed in second GENERATE AC.
The CDOL2 is not interpreted by M/Chip Advance and is stored in a
record referenced in the AFL.
If partial authorization is not supported, then the value of CDOL2 is
'910A8A0295059F37049F4C08'.
If partial authorization is supported, then the value of CDOL2 is
'910A8A0295059F37049F4C089F02069F0306'.
CDOL2 Related Data

Tag: –
Length: 29 or 41
Format: b
Description: The CDOL2 Related Data is used to compute the intermediate hash
result during the calculation of the Signed Dynamic Application
Data.

Tag: –
Length: 1 bit
Format: b
Description: Indicates if Counter 1 is to be incremented during this transaction.
Its value is defined during the first GENERATE AC based on
Counter 1 Control and transaction related data.

Data Dictionary

Tag: 'DF1A'
Length: 1
Format: b
Type: Persistent
of Counter 1 when the contact interface is active.
Byte 1
b8-7 Counting Mode
00: Never
01: Count CVM transactions
10: Count NoCVM transactions
11: Always
b5 Count Even When Cumulated
b3 Show
00: Do Not Include
01: Include Counter As Value
11: RFU

Tag: 'DF1B'
Length: 1
Format: b
Type: Persistent
of Counter 1 when the contactless interface is active.
Byte 1
b8-7 Counting Mode
00: Never
11: Always
b3 Show
00: Do Not Include
11: RFU

Data Dictionary

Tag: 'DF2C'
Length: 3
Format: b
Type: Persistent
Counter 1 becomes active if a given Card Verification Results pattern
occurs when the contact interface is active.
Value then the condition is satisfied for the use of Counter 1.
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: 'DF2D'
Length: 3
Format: b
Type: Persistent
occurs when the contactless interface is active.
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: '9F14'
Length: 1
Format: b
Type: Persistent
Description: If the Counter 1 Number or Counter 1 Number Temp have exceeded
this limit, the relevant CVR bit is set.

Data Dictionary

Tag: –
Length: 1
Format: b
of Counter 1 Lower Limit.
Counter 1 Number
Tag: 'DF1C'
Length: 1
Format: b
Type: Persistent
Description: Represents the number of transactions accepted offline and fulfilling
the criteria specified in Counter 1 Control.

Tag: –
Length: 1
Format: b
Description: Temporary variable containing the updated value of Counter 1
Number.

Tag: '9F23'
Length: 1
Format: b
Type: Persistent
this limit, the relevant Card Verification Results bit is set.

Tag: –
Length: 1
Format: b
of Counter 1 Upper Limit.

Tag: –
Length: 1 bit
Format: b
Description: Indicates if Counter 2 is to be incremented during this transaction.

Data Dictionary

Tag: 'DF1D'
Length: 1
Format: b
Type: Persistent
of Counter 2 when the contact interface is active.
Byte 1
b8-7 Counting Mode
00: Never
11: Always
b3 Show
00: Do Not Include
11: RFU

Tag: 'DF1E'
Length: 1
Format: b
Type: Persistent
of Counter 2 when the contactless interface is active.
Byte 1
b8-7 Counting Mode
00: Never
11: Always
b3 Show
00: Do Not Include
11: RFU

Data Dictionary

Tag: 'DF2E'
Length: 3
Format: b
Type: Persistent
occurs when the contact interface is active.
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: 'DF2F'
Length: 3
Format: b
Type: Persistent
Counter 2 becomes active when a given Card Verification Results
Byte 1
Input Byte Number
Byte 2
Condition Mask
Byte 3
Comparison Value

Tag: 'DF1F'
Length: 1
Format: b
Type: Persistent

Data Dictionary

Tag: –
Length: 1
Format: b
of Counter 2 Lower Limit.
Counter 2 Number
Tag: 'DF20'
Length: 1
Format: b
Type: Persistent
Description: The Counter 2 Number represents the number of transactions
accepted offline and fulfilling the criteria specified in Counter 2
Control.

Tag: –
Length: 1
Format: b
Description: Temporary variable containing the updated value of Counter 2
Number.

Tag: 'DF21'
Length: 1
Format: b
Type: Persistent

Tag: –
Length: 1
Format: b
of Counter 2 Upper Limit.

Data Dictionary
CRM Country Code
CRM Country Code

Tag: 'C8'
Length: 2
Format: n3
Type: Persistent
Description: The CRM Country Code is used to differentiate between domestic
transactions (when the CRM Country Code matches the Terminal
Country Code) and international transactions (when the CRM
Country Code does not match the Terminal Country Code). This may
impact CRM, depending on the Card Issuer Action Codes settings.

Tag: '9F27'
Length: 1
Format: b
Byte 1
b8-7 Type Of Cryptogram
00: AAC
01: TC
10: ARQC
11: RFU
b6-5 Payment System-specific Cryptogram
b4 Advice Required
b3-1 Reason/Advice code
000: No Information Given
001: Service Not Allowed
010: PIN Try Limit Exceeded
011: Issuer Authentication Failed
1xx: RFU
Cryptogram Information Data (Recovery)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: A persistent copy of the Cryptogram Information Data used for

Data Dictionary

Tag: –
Length: 1
Format: b
Description: The Cryptogram Version Number informs the issuer about the
algorithm and data used for the Application Cryptogram computation
during online transactions (in the authorization request) and after
transaction completion in the clearing record.
The Cryptogram Version for M/Chip Advance is set to 0001b.
Byte 1
b8-5 Cryptogram Version
b4 RFU
b3-2 Session Key Used For AC Computation
00: MasterCard Proprietary SKD Session Key
10: EMV CSK Session Key
b1 Counters Included In AC Computation
Cryptogram Version Number V2.x

Tag: –
Length: 1
Format: b
Type: Persistent
Description: Holds the Cryptogram Version Number if V2.05 or V2.1/V2.2 issuer
host backward compatibility is used.

Tag: –
Length: 2
Format: b
Description: Current date stored as the number of days elapsed from a reference
date.
CVC3(Track1)
Tag: '9F60'
Length: 2
Format: b
Description: Cryptogram returned in the response to the COMPUTE
CRYPTOGRAPHIC CHECKSUM command. The CVC3(Track1) is
generated based on the IVCVC3(Track1), the Application
Transaction Counter and the Unpredictable Number (Numeric).

Data Dictionary
CVC3(Track2)
CVC3(Track2)
Tag: '9F61'
Length: 2
Format: b
Description: Cryptogram returned in the response to the COMPUTE
CRYPTOGRAPHIC CHECKSUM command. The CVC3(Track2) is
generated based on the IVCVC3(Track2), the Application
Transaction Counter and the Unpredictable Number (Numeric).
CVM Results
Tag: '9F34'
Length: 3
Format: b
CVR Issuer Discretionary Data (Contact)

Tag: 'DF3C'
Length: 1
Format: b
Type: Persistent
Description: Issuer discretionary data object of which the two least significant bits
are copied in the Card Verification Results when the contact interface
is active.
Byte 1
b8-3 RFU
CVR Issuer Discretionary Data (Contactless)

Tag: 'DF3D'
Length: 1
Format: b
Type: Persistent
Description: Issuer discretionary data object of which the two least significant bits
are copied in the Card Verification Results when the contactless
Byte 1
b8-3 RFU

Data Dictionary
CVR V2.05
CVR V2.05
Tag: –
Length: 4
Format: b
Description: Card Verification Results used in case V2.05 host backwards
compatibility is required.
Byte 1
Length
Byte 2
11: RFU
11: RFU
b4 Not Used
b1 Unable To Go Online
Byte 3
b7 PTL Exceeded
b6-1 Not Used
Byte 4
b8-4 Not Used
b3 LCOL Or LCOTA Exceeded
b2 UCOL Or UCOTA Exceeded
b1 Maximum Offline Transaction Amount
Exceeded

Data Dictionary
CVR V2.1/V2.2
CVR V2.1/V2.2
Tag: –
Length: 4
Format: b
Description: Card Verification Results used in case V2.1/V2.2 host backwards
Byte 1
Length
Byte 2
10: AC Not Requested In Second Generate
AC
11: RFU
11: RFU
b4 Not Used
b1 Unable To Go Online
Byte 3
b7 PTL Exceeded
b6-1 Not Used
Byte 4
b8-4 Not Used
b3 LCOL Or LCOTA Exceeded
b2 UCOL Or UCOTA Exceeded
b1 Not Used

Data Dictionary
CVR V1.1/V1.3
CVR V1.1/V1.3
Tag: –
Length: 6
Format: b
Byte 1
11: RFU
11: RFU
b4 RFU
b2 Offline Encrypted PIN Verification Performed
Byte 2
b8 DDA Returned
b7 Combined DDA/AC Generation Returned In First Generate
AC
b6 Combined DDA/AC Generation Returned In Second
Generate AC
b5 Issuer Authentication Performed
b4 CIAC-Default Skipped On CAT3
b3-1 RFU
Byte 3
b8-5 Low Order Nibble Of Script Counter
Byte 4
b8 RFU
b4 PTL Exceeded

Data Dictionary
DAC/ICC Dyn Nr
Byte 5
b8 Lower Consecutive Offline Limit Exceeded
b7 Upper Consecutive Offline Limit Exceeded
b6 Lower Cumulative Offline Limit Exceeded
b5 Upper Cumulative Offline Limit Exceeded
b2 Script Received
b1 Script Failed
Byte 6
b8-3 RFU
DAC/ICC Dyn Nr
Tag: –
Length: 2
Format: b
Description: A temporary variable used to hold either the Data Authentication
Code or the first two bytes of the ICC Dynamic Number (Terminal)
prior to building the Issuer Application Data.
Data Authentication Code

Tag: '9F45'
Length: 2
Format: b
DDOL
Tag: '9F49'
Length: 3
Format: b
Type: Persistent
Description: Tells the terminal what data is needed for the INTERNAL
AUTHENTICATE command data. The DDOL is not interpreted by
M/Chip Advance and is stored in a record referenced in the AFL.
The value of the DDOL is '9F3704'.
DDOL Related Data

Tag: –
Length: 4
Format: b
Description: A temporary variable containing data as specified by the data object
list DDOL and sent by the terminal to the card, during the
INTERNAL AUTHENTICATE command.

Data Dictionary

Tag: 'D6'
Length: 2
Format: b
Type: Persistent
Description: The Default ARPC Response Code replaces the ARPC Response
Code, if:
 Issuer Authentication Data is not present in an online transaction,
and
 The 'Accept Online Transactions Without ARPC' bit in the
Application Control is set, and
 The transaction is approved by the terminal and issuer (i.e.
Authorization Response Code < > 'Y3' or 'Z3' and the terminal
requests a TC).
Byte 1
b4-1 RFU
Byte 2
b8-6 RFU
b5 Approve Online Transaction
b4 RFU
b3 Set Go Online On Next Transaction
b2-1 Update Accumulators/Counters
00: Do Not Update Offline Accumulators/Counters
01: Set Accumulators/Counters To Upper Offline Limits
10: Reset Accumulators/Counters To Zero
11: Add Transaction To Accumulators/Counters

Tag: –
Length: 4
Format: b
Description: Device Relay Resistance Entropy is a 4-byte random number returned
in the response to the EXCHANGE RELAY RESISTANCE DATA
command. It is constructed by selecting 4 bytes of the ICC Dynamic
Number.
Device Relay Resistance Entropy (Recovery)

Tag: –
Length: 4
Format: b
Type: Persistent
Description: A persistent copy of the Device Relay Resistance Entropy for

Data Dictionary
DRDOL
DRDOL
Tag: '9F51'
Length: 3
Format: b
Type: Persistent
Description: Tells the terminal what data is needed for the RECOVER AC
command data.
The value of the DRDOL is '9F3704'.

Tag: –
Length: NIC
Format: b
Description: Temporary variable used whilst building the Signed Dynamic
Application Data.

Tag: –
Length: 8
Format: b
Description: Temporary variable that contains the enciphered PIN data sent by the
terminal during a PIN CHANGE/UNBLOCK command
File Control Information

Tag: '6F'
Length: Variable, 10 - 252 bytes
Type: Persistent
Description: The application does not interpret the File Control Information. It
simply returns it in the response to the select signal.
First AC
Tag: –
Length: 8
Format: b
Description: M/Chip Advance stores the Application Cryptogram generated during
the first GENERATE AC in First AC. First AC is used during the
second GENERATE AC for ARPC verification.

Data Dictionary
Get Challenge Flag
Get Challenge Flag

Tag: –
Length: 2 bits
Format: b
Description: The Get Challenge Flag is used to ensure that a VERIFY command
with encrypted PIN is only accepted if it directly follows the GET
CHALLENGE command.
The Get Challenge Flag has no external visibility. Therefore, the
implementation of this functionality can vary from the one described
in these specifications.
Byte 1
b8-3 RFU
b2 Challenge Availability
b1 Successful Get Challenge
Hash Result
Tag: –
Length: 20
Format: b
Application Data.
Hash Result (Recovery)

Tag: –
Length: 20
Format: b
Type: Persistent
Description: A persistent copy of the Hash Result used for transaction recovery.
ICC Dynamic Data

Tag: –
Length: 9, 38 or 52
Format: b
Application Data. During DDA using the INTERNAL
AUTHENTICATE command, only the first 9 bytes are used.
During CDA using the GENERATE AC or RECOVER AC
commands 38 bytes are used if RRP data are not included or all 52
bytes if RRP data are included.

Data Dictionary
ICC Dynamic Number
Byte 1
Length Of ICC Dynamic Number[9 : 16]
Byte 2-9
ICC Dynamic Number[9 : 16]
Byte 10
Byte 11-18
Byte 19-38
Hash Result
Byte 39-42
Byte 43-46
Byte 47-48
Min Time For Processing Relay Resistance APDU
Byte 49-50
Max Time For Processing Relay Resistance APDU
Byte 51-52
Transmission Time For Relay Resistance R-APDU
ICC Dynamic Number

Tag: –
Length: 16
Format: b
Description: Time-variant number generated by the ICC, to be captured by the
terminal.
M/Chip Advance computes the ICC Dynamic Number in the GET
PROCESSING OPTIONS command. It is used as input for the
calculation of the Signed Dynamic Application Data and for the
generation of the Device Relay Resistance Entropy in the response to
the EXCHANGE RELAY RESISTANCE DATA command.

Tag: '9F4C'
Length: 8
Format: b
Description: The ICC Dynamic Number captured by the terminal and sent to the
application in GENERATE AC commands.
If the ICC Dynamic Number (Terminal) is not all zeroes, M/Chip
Advance uses the first two bytes to build the Issuer Application Data.

Data Dictionary

Tag: –
Length: 16
Format: b
Type: Persistent
Description: Triple DES key for ICC Dynamic Number generation when the
contact interface is active.
ICC Dynamic Number Master Key (Contactless)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: Triple DES key for ICC Dynamic Number generation when the
ICC PIN Encipherment Private Key

Tag: –
Length: Implementation specific
Format: b
Type: Persistent
Description: RSA private key for PIN decipherment during the VERIFY
command with encrypted offline PIN.
ICC Private Key

Tag: –
Length: Implementation specific
Format: b
Type: Persistent
Description: RSA private key for dynamic signature generation during the
GENERATE AC command.
The key may also be used for PIN decipherment during the VERIFY
command with encrypted offline PIN.
ICC Unpredictable Number

Tag: –
Length: 8
Format: b
Description: M/Chip Advance computes the ICC Unpredictable Number in the
GET CHALLENGE command. It is checked against data sent by the
terminal in the VERIFY command (offline encrypted PIN).

Data Dictionary

Tag: 'DF30'
Length: 1
Format: b
Type: Persistent
Description: Contains flags that indicate if an interface is enabled.
Byte 1
b8-3 RFU
b2-1 Interfaces Status
00: RFU
01: Contactless Interface Disabled
10: Contact Interface Disabled
11: Contact And Contactless Interfaces Enabled
Interface Identifier (Contact)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: Identifies the contact interface in the Transaction Log. In the
Transaction Log the Interface Identifier is identified with tag 'DF3E'.
Interface Identifier (Contactless)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: Identifies the contactless interface in the Transaction Log. In the
Transaction Log the Interface Identifier is identified with tag 'DF3E'.
Internal Authentication Performed Flag

Tag: –
Length: 1 bit
Format: b
Description: M/Chip Advance uses the Internal Authentication Performed Flag to
limit the computation of a DDA signature to occur only once per
transaction (i.e. per Application Transaction Counter).
The Internal Authentication Performed Flag has no external
visibility. Therefore, the implementation of this functionality can
vary from the one described in these specifications. The Internal
Authentication Performed Flag is used in the GENERATE AC to set
a bit in the Card Verification Results.

Data Dictionary

Tag: '9F10'
Length: 18, 20, 26 or 28
Format: b
Description: The Issuer Application Data informs the issuer about the application
during online transactions (in the authorization request) and after
transaction completion in the clearing record.
Note that the presence of the Last Online ATC is optional dependent
on the personalization of the Application Control.
Byte 1
Byte 2
Byte 3-8
Byte 9-10
DAC/ICC Dynamic Number
Byte 11-18/26
Byte 19/27-20/28
Last Online ATC

Tag: '9F10'
Length: 9
Format: b
Description: The Issuer Application Data V2.05 is used to inform the issuer about
the application during online transactions (in the authorization
request) and after transaction completion in the clearing record in
case of V2.05 front-end compatibility.
The Issuer Application Data V2.05 is the concatenation (without
TLV coding) of the data elements indicated below.
Byte 1
Length
Byte 2
Byte 3
Byte 4-7
Byte 8-9

Data Dictionary

Tag: '9F10'
Length: 8
Format: b
Description: The Issuer Application Data V2.1/V2.2 is used to inform the issuer
about the application during online transactions (in the authorization
request) and after transaction completion in the clearing record in
case of V2.1/2.2 front-end compatibility.
The Issuer Application Data V2.1/V2.2 is the concatenation (without
TLV coding) of the data elements indicated below.
Byte 1
Byte 2
Byte 3-6
Byte 7-8
Issuer Application Data (Recovery)

Tag: –
Length: Variable up to 28
Format: b
Type: Persistent
Description: The Issuer Application Data stored for recovery of a torn transaction.

Tag: '91'
Length: 10
Format: b
Byte 1-8
Authorization Response Cryptogram
Byte 9-10
ARPC Response Code

Data Dictionary
Issuer Updates Data
Issuer Updates Data

Tag: –
Length: Variable up to 45
Format: b
Description: The Issuer Updates Data is received in the ISSUER UPDATES
command. It contains new values of accumulators, counters and
limits. M/Chip Advance will perform the updates in the second
GENERATE AC, provided Issuer authentication is successful and
the Application Cryptogram returned is the one requested by the
Issuer in the ARPC Response Code.
The 'Accumulators And Counters' field is of variable length and
contains the new values of accumulators, counters and limits, as
identified in byte 2 and byte 3.
Byte 1
b8-1 Update Type
'01': Update Accumulators And Counters
Other values: RFU
Byte 2
b8-7 RFU
b6 Accumulator 2 Upper Limit Included
b5 Accumulator 2 Lower Limit Included
b4 Accumulator 2 Amount Included
b3 Accumulator 1 Upper Limit Included
b2 Accumulator 1 Lower Limit Included
b1 Accumulator 1 Amount Included
Byte 3
b8-7 RFU
b6 Counter 2 Upper Limit Included
b5 Counter 2 Lower Limit Included
b4 Counter 2 Number Included
b3 Counter 1 Upper Limit Included
b2 Counter 1 Lower Limit Included
b1 Counter 1 Number Included
Byte 4 up to 45
Accumulators And Counters Related Data

Data Dictionary

Tag: –
Length: 1 bit
Format: b
Description: M/Chip Advance sets the Issuer Updates Received Flag when Issuer
Updates Data are received in the ISSUER UPDATES command. The
Issuer Updates Received Flag has no external visibility. Therefore,
the implementation of this functionality can vary from the one
described in these specifications. If the Issuer Updates Received Flag
is set, M/Chip Advance will perform the updates in the second
GENERATE AC, provided Issuer authentication is successful and
the Application Cryptogram returned is the one requested by the
Issuer in the ARPC Response Code.
Tag: 'DF38'
Length: 2
Format: b
Type: Persistent
Description: Issuer proprietary static data object that is used as input for the
generation of the CVC3(Track1) cryptogram when the contact
Tag: 'DC'
Length: 2
Format: b
Type: Persistent
generation of the CVC3(Track1) cryptogram when the contactless
Tag: 'DF39'
Length: 2
Format: b
Type: Persistent
generation of the CVC3(Track2) cryptogram when the contact
Tag: 'DD'
Length: 2
Format: b
Type: Persistent
generation of the CVC3(Track2) cryptogram when the contactless

Data Dictionary
KDCVC3 (Contact)
KDCVC3 (Contact)
Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC derived key for CVC3 generation when the contact interface is
used. KDCVC3 (Contact) is used directly to compute the dynamic
CVC3. No session key is used.
KDCVC3 (Contactless)
Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC derived key for CVC3 generation when the contactless interface
is used. KDCVC3 (Contactless) is used directly to compute the
dynamic CVC3. No session key is used.
Key Derivation Index (Contact)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: Issuer-specific.
Key Derivation Index (Contactless)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: Issuer-specific.
Key Derivation Index (MAS4C)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: Issuer-specific. Used in MAS4C processing flow when AC Master
Key (MAS4C) is used to derive AC Session Key.
Last Online ATC

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Contains the Application Transaction Counter on which the last
completed online transaction took place.

Data Dictionary

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Contains the date on which the last completed online transaction took
place. The date is stored as a number of days elapsed since a
reference date.
Length Of ICC PIN Encipherment Public Key Modulus

Tag: –
Length: 1
Format: b
Type: Persistent
Description: As a minimum, M/Chip Advance must accept any RSA key with
modulus length in the range 96 to176, for both DDA and PIN
verification. The storage format of the RSA keys is implementation
specific (RSA computations may optionally use the CRT).
Abbreviated to Npe.
Length Of ICC Public Key Modulus

Tag: –
Length: 1
Format: b
Type: Persistent
Description: As a minimum, M/Chip Advance must accept any RSA key with
modulus length in the range 96 to 176, for both DDA and PIN
verification. The storage format of the RSA keys is implementation
specific (RSA computations may optionally use the CRT).
Abbreviated to Nic.

Data Dictionary

Tag: 'DF07'
Length: Variable
Format: b
Description: Data object included in the value field of the PUT DATA command
to update the value of a data object in another application on the card.
Byte 1
Version Number
'00', other values are RFU
Byte 2
Target Application
'00': The target application is this application
'yy': The target application is the application with Linked Application Index equal to 'yy'.
'FF': The target application is the application with AID equal to the AID indicated in the
next two fields below, which may be the currently selected application. Full match is
required between the two AIDs.
Byte 3
Length of AID
'Length of AID' is only present if 'Target Application' = 'FF'
Byte 4 – 4+'Length of AID'-1

AID
'AID' is only present if 'Target Application' = 'FF'
Byte 3 – 4 or Byte 4+'Length of AID' – 6+'Length of AID'-1

Target Data ID
Identifier of data to update (see below)
Byte 5 – Variable or Byte 6+'Length of AID' – Variable

New Value
Value of data to update
The following table lists the supported values for 'Target Data ID':
Target Data ID Name Length New Value
'0000' Block status 1 '00': Unblocked
'01': Blocked
Other values RFU
'00A5' FCI Proprietary Template Variable Not interpreted

Data Dictionary

Tag: 'DF73'
Length: 1
Format: b
Type: Persistent
Description: The Linked Application Index is used in the Linked Application Data
of a PUT DATA command to identify the target application.
Log Data Table

Tag: 'DE'
Length: 9
Format: b
Type: Persistent
Description: The Log Data Table contains information necessary to support
extensions to the transaction log data stored in the Log of
Transactions
The Log Data Table is the concatenation (without TLV coding) of
the data elements identified as below.
The maximum number of data entries (n) is 4. The total length of the
additional transaction log data must be less than or equal to 32 bytes.
Byte 1
Count Of Data Entries
Byte 2
Data Position 1
Byte 3
Data Length 1
Byte 4
Data Position 2
Byte 5
Data Length 2
Byte 6
Data Position 3
Byte 7
Data Length 3
Byte 8
Data Position 4
Byte 9
Data Length 4

Data Dictionary
Log Format
Log Format
Tag: '9F4F'
Length: Variable
Format: b
Type: Persistent
Description: The Log Format identifies the content of records in the Log Of
Transactions. The Log Format is not interpreted by M/Chip Advance
and is returned in response to a GET DATA command.
The following DOL provides the data elements identified in the Log
Format, and the order in which they appear without the additional
information defined by the Log Data Table:
'9F27019F02065F2A029A039F36029F5206DF3E019F21039F7C14'
The length of the Log Format is variable. If no additional
information is defined by the Log Data Table, then the length of the
Log Format is 26 bytes. A memory space of at least 48 bytes must
be available for the Log Format.
MAC
Tag: –
Length: 8
Format: b
Description: A temporary variable used to hold the MAC where data
authentication is needed.
Max Time For Processing Relay Resistance APDU (Contact)

Tag: 'DF04'
Length: 2
Format: b
Type: Persistent
Description: 2 byte binary value in units of hundreds of microseconds that
represents the maximum time for processing the EXCHANGE
RELAY RESISTANCE DATA command when the contact interface
is used.
Max Time For Processing Relay Resistance APDU (Contactless)

Tag: 'DF74'
Length: 2
Format: b
Type: Persistent
represents the maximum time for processing the EXCHANGE
RELAY RESISTANCE DATA command when the contactless
interface is used.
Merchant Custom Data

Tag: '9F7C'
Length: 20
Format: b
Description: Proprietary merchant data to be stored in the Transaction Log File.

Data Dictionary

Tag: 'DF05'
Length: 2
Format: b
Type: Persistent
represents the minimum time for processing the EXCHANGE
RELAY RESISTANCE DATA command when the contact interface
is used.
Min Time For Processing Relay Resistance APDU (Contactless)

Tag: 'DF75'
Length: 2
Format: b
Type: Persistent
represents the minimum time for processing the EXCHANGE
RELAY RESISTANCE DATA command when the contactless
interface is used.
MTA Currency Code

Tag: 'DF24'
Length: 2
Format: n3
Type: Persistent
Description: The transaction currency code for which maximum transaction
amount check is to be applied.
MTA CVM (Contact)

Tag: 'DF22'
Length: 6
Format: n12
Type: Persistent
Description: The maximum transaction amount for contact CVM transactions.
When the transaction amount is greater than MTA CVM (Contact),
the relevant bit in the Card Verification Results is set.
MTA CVM (Contactless)

Tag: 'DF23'
Length: 6
Format: n12
Type: Persistent
Description: The maximum transaction amount for contactless CVM transactions.
When the transaction amount is greater than MTA CVM
(Contactless), the relevant bit in the Card Verification Results is set.

Data Dictionary
MTA NoCVM (Contact)
MTA NoCVM (Contact)

Tag: 'DF25'
Length: 6
Format: n12
Type: Persistent
Description: The maximum transaction amount for contact no CVM transactions.
When the transaction amount is greater than MTA NoCVM (Contact),
the relevant bit in the Card Verification Results is set.
MTA NoCVM (Contactless)

Tag: 'DF26'
Length: 6
Format: n12
Type: Persistent
Description: The maximum transaction amount for contactless no CVM
transactions. When the transaction amount is greater than MTA CVM
(Contactless), the relevant bit in the Card Verification Results is set.
New Data Value

Tag: –
Length: Variable
Format: b
Description: A temporary variable used to hold the new data value during a PUT
DATA command.
New PIN Block

Tag: –
Length: 8
Format: b
Description: A temporary variable used to hold the new PIN block value during a
PIN CHANGE/UNBLOCK command.
New Record Value

Tag: –
Length: Variable
Format: b
Description: A temporary variable used to hold the new record value during an
UPDATE RECORD command.
New SMI Key Flag

Tag: –
Length: 1 bit
Format: b
Description: This flag is set when a new SMI Session Key is generated. It is used
to indicate whether the SMI Session Key Counter has to be adjusted.

Data Dictionary

Tag: 'DF27'
Length: 2
Format: b
Type: Persistent
Description: The maximum number of days that the application can perform
transactions off-line. If the limit is exceeded, the relevant bit in the
Card Verification Results is set.

Tag: '9F50'
Length: 6
Format: n12
Description: Represents the amount of offline spending available as determined by
Accumulator 1.
The Offline Accumulator Balance 1 is retrievable by the GET DATA
command, if allowed by the Application Control, and is computed as
follows:
Offline Accumulator Balance 1 := Accumulator 1 Upper Limit -
Accumulator 1 Amount.
If Accumulator 1 Upper Limit < Accumulator 1 Amount the value
returned by the GET DATA command for the Offline Accumulator
Balance 1 is '000000000000'.

Tag: '9F58'
Length: 6
Format: n12
Description: Represents the amount of offline spending available as determined by
Accumulator 2.
The Offline Accumulator Balance 2 is retrievable by the GET DATA
follows:
Offline Accumulator Balance 2 := Accumulator 2 Upper Limit -
Accumulator 2 Amount.
If Accumulator 2 Upper Limit < Accumulator 2 Amount the value
returned by the GET DATA command for the Offline Accumulator
Balance 2 is '000000000000'.

Data Dictionary

Tag: –
Length: 1
Format: b
Description: The Offline Change PIN Status contains the result of the OFFLINE
CHANGE PIN command. It is set in the OFFLINE CHANGE PIN
command and is used in the GENERATE AC command to set one bit
in the Card Verification Results. The Offline Change PIN Status has
no external visibility. Therefore, the implementation of this
functionality can vary from the one described in these specifications.
Byte 1
b8 Offline Change PIN Successful
b7-1 RFU

Tag: '9F7A'
Length: 1
Format: b
Description: Represents the number of remaining offline transactions as
determined by Counter 1.
The Offline Counter Balance 1 is retrievable by the GET DATA
follows:
Offline Counter Balance 1 := Counter 1 Upper Limit - Counter 1
Number. If Counter 1 Upper Limit < Counter 1 Number the value
returned by the GET DATA command for the Offline Counter
Balance 1 is 0.

Tag: '9F59'
Length: 1
Format: b
Description: Represents the number of remaining offline transactions as
determined by Counter 2.
The Offline Counter Balance 2 is retrievable by the GET DATA
follows:
Offline Counter Balance 2 := Counter 2 Upper Limit - Counter 2
Number. If Counter 2 Upper Limit < Counter 2 Number the value
returned by the GET DATA command for the Offline Counter
Balance 2 is 0.

Data Dictionary
PDOL
PDOL
Tag: '9F38'
Length: 0 or 3
Format: b
Type: Persistent
Description: Contains a list of terminal resident data objects needed in the
processing of the GET PROCESSING OPTIONS command. If
MAS4C is not activated, PDOL is not present. If MAS4C is
activated, the value of PDOL is '9F4005'.
PDOL Related Data

Tag: –
Length: 2 or 7
Format: b
Description: A temporary variable containing data as specified by PDOL and sent
by the terminal to the card, during the GET PROCESSING
OPTIONS command.
PDOL Values
Tag: –
Length: 0 or 5
Format: b
Description: PDOL Values is used to compute the intermediate hash result during
the calculation of the Signed Dynamic Application Data.
PIN Decipherments Error Counter

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Counts the number of unsuccessful offline PIN decryptions in the
application lifetime.
PIN Decipherments Error Counter Limit

Tag: 'DF36'
Length: 2
Format: b
Type: Persistent
Description: Limits the number of unsuccessful offline PIN decryptions in the
application lifetime.
PIN Related Data

Tag: –
Length: 8 or Nic or Npe
Format: b
Description: Temporary variable containing the PIN block in plaintext or
encrypted form.

Data Dictionary
PIN Try Counter
PIN Try Counter

Tag: '9F17'
Length: 1
Format: b
Type: Persistent
Description: Indicates the number of PIN tries remaining.
Byte 1
b8-5 RFU
PIN Try Limit

Tag: 'C6'
Length: 1
Format: b
Type: Persistent
Description: Indicates the number of PIN tries allowed.
Byte 1
b8-5 RFU
b4-1 Low Order Nibble Of PIN Try Limit
PIN Verification Status

Tag: –
Length: 3 bits
Format: b
Description: Indicates whether the offline PIN has been verified during the
processing of the current transaction.
The PIN Verification Status contains the result of offline PIN
verification. It is set in the VERIFY command and is used in the
GENERATE AC command to set bits in the Card Verification
Results. It is used in OFFLINE CHANGE PIN command to
determine whether to permit a PIN to be changed and to determine
whether to reset offline counters.
The PIN Verification Status has no external visibility. Therefore, the
Byte 1
b8-4 RFU
Performed

Data Dictionary
Tag: –
Length: 8 or 16
Description: Temporary variable containing offline counters in a plaintext or
encrypted format. It is used as input to the Application Cryptogram
calculation and it is included in the Issuer Application Data.
Previous Transaction History

Tag: –
Length: 1
Format: b
Type: Persistent
Description: The Previous Transaction History is used to store information about
the previous transactions in non-volatile memory.
Byte 1
b8-7 RFU
b5 Application Blocked
b4 Go Online On Next Transaction
b2 Script Received
b1 Script Failed
Rand
Tag: –
Length: 8
Format: b
Description: M/Chip Advance stores the Application Cryptogram generated during
the first GENERATE AC in Rand. Rand is incorporated into the
computation of the MAC that protects the integrity of a script.
Read Record Filter (Contact)

Tag: 'DF3F'
Length: Variable
Format: b
Type: Persistent
Description: Read Record Filter used to prevent reading records when the contact
interface is active. It is coded like an Application File Locator.
Records identified in the Read Record Filter cannot be read with the
READ RECORD command. Refer to [EMV] for a description of the
Application File Locator coding.
A memory space of at least 32 bytes must be available for the Read
Record Filter (Contact).

Data Dictionary

Tag: 'DF40'
Length: Variable
Format: b
Type: Persistent
Description: Read Record Filter used to prevent reading records when the
contactless interface is active. It is coded like an Application File
Locator. Records identified in the Read Record Filter cannot be read
with the READ RECORD command. Refer to [EMV] for a
description of the Application File Locator coding.
A memory space of at least 32 bytes must be available for the Read
Record Filter (Contactless).
Record Number
Tag: –
Length: 1
Format: b
Description: Temporary variable used to indicate the record number of the target
record during an UPDATE RECORD command.
Recover AC Performed Flag

Tag: –
Length: 1 bit
Format: b
Description: M/Chip Advance uses the Recover AC Performed Flag to limit the
computation of RECOVER AC responses to occur only once per
transaction (i.e. per Application Transaction Counter).
The Recover AC Performed Flag has no external visibility.
Therefore, the implementation of this functionality can vary from the
one described in these specifications.
Recovered Data
Tag: –
Length: Variable
Format: b
Description: Temporary variable containing the PIN related data after decryption
during OFFLINE CHANGE PIN and VERIFY commands.

Tag: –
Length: 1
Format: b
Description: Temporary variable used to indicate additional information about the
operation of the command. This variable takes on the value of P2 for
READ RECORD or UPDATE RECORD commands or the value of
P1 for first and second GENERATE AC commands, after the
command APDU is received.

Data Dictionary
Reference PIN
Reference PIN
Tag: –
Length: 8
Format: b
Type: Persistent
Description: Structured PIN block containing the cardholder PIN.

Tag: –
Length: 4 bytes
Format: b
Description: Temporary variable containing command data of the EXCHANGE
RELAY RESISTANCE DATA command.
Return Value
Tag: –
Length: 1
Format: b
Description: Temporary variable containing data to be returned from a subroutine.
Return Value has values of either true or false.
RRP Counter
Tag: –
Length: 1
Format: b
Description: RRP Counter counts the number of EXCHANGE RELAY
RESISTANCE DATA commands after a GET PROCESSING
OPTIONS command.
RRP Performed Flag (Recovery)

Tag: –
Length: 1
Format: b
Type: Persistent
Description: The RRP Performed Flag (Recovery) is used to record whether or not
the transaction stored for recovery was done with RRP.

Data Dictionary
Script Counter
Script Counter
Tag: –
Length: 1
Format: b
Type: Persistent
Description: Indicates the number of script commands processed previously. The
low order nibble is included in the information part of the Card
Verification Results.
Byte 1
b8-5 RFU
b4-1 Script Counter
Script Failed Flag

Tag: –
Length: 1 bit
Format: b
Description: M/Chip Advance uses the Script Failed Flag to reject subsequent
script commands received in the same transaction once a script
command has failed.
The Script Failed Flag has no external visibility. Therefore, the
Security Limits Status (Contact)

Tag: 'DF02'
Length: 1
Format: b
Type: Persistent
Description: Indicates whether the limit for a contact security counter has been
reached.
Byte 1
b8 AC Session Key Counter Limit Exceeded
b7 SMI Session Key Counter Limit Exceeded
b6-1 RFU
Security Limits Status (Contactless)

Tag: 'DF35'
Length: 1
Format: b
Type: Persistent
Description: Indicates whether the limit for a contactless security counter has been
reached
Byte 1
b8 AC Session Key Counter Limit Exceeded
b7 SMI Session Key Counter Limit Exceeded
b6-1 RFU

Data Dictionary

Tag: 'DF37'
Length: 1
Format: b
Type: Persistent
Description: Indicates whether the limit for a common (interface independent)
security counter has been reached.
Byte 1
b8 PIN Decipherments Error Counter Limit Exceeded
b7 AC Session Key Counter Limit (MAS4C) Exceeded
b6-1 RFU

Tag: '9F4B'
Length: NIC
Format: b
SMC CSK Key Present Flag

Tag: –
Length: 1 bit
Format: b
Description: In the PIN CHANGE/UNBLOCK command, the SMC CSK Key
Present Flag is used to indicate if the SMC Session Key is already
present in the key container and so does not have to be re-derived.
It is set to 1b if an SMC CSK session key is derived in the PIN
CHANGE/UNBLOCK command, and set to 0b if a MasterCard
Proprietary SKD session key is derived in the PIN
CHANGE/UNBLOCK.
SMC Master Key (Contact)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key for secure messaging for confidentiality when the
contact interface is active.
SMC Master Key (Contactless)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key for secure messaging for confidentiality when the

Data Dictionary
SMC Session Key
SMC Session Key

Tag: –
Length: 16
Format: b
Description: For MasterCard Proprietary SKD, a new SMC Session Key has to be
derived for each PIN CHANGE/UNBLOCK.
For EMV CSK, the SMC Session Key has to be derived for the PIN
CHANGE/UNBLOCK, unless it is already available.
The SMC Session Key is used to decrypt the encrypted PIN block.
SMI CSK Key Present Flag

Tag: –
Length: 1 bit
Format: b
Description: In each script command, the SMI CSK Key Present Flag is used to
indicate if the SMI Session Key is already present in the key
container, and so does not have to be re-derived.
It is set to 1b if an SMI CSK session key is derived in the script
command, and set to 0b if a MasterCard Proprietary SKD session key
is derived in the script command.
SMI Master Key (Contact)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key for secure messaging for integrity when the contact
SMI Master Key (Contactless)

Tag: –
Length: 16
Format: b
Type: Persistent
Description: ICC master key for secure messaging for integrity when the
SMI Session Key

Tag: –
Length: 16
Format: b
Description: For MasterCard Proprietary SKD, a new SMI Session Key has to be
derived for each script command.
For EMV CSK, the SMI Session Key has to be derived for a script
command, unless it is already available.
The SMI Session Key is used to verify the SMI MAC.

Data Dictionary

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Counts the number of secure messaging for integrity session key
derivations over the contact interface that are not followed by
successful validation of a secure messaging MAC, over the lifetime
of the card, and is used to limit this number to the SMI Session Key
Counter Limit (Contact).
SMI Session Key Counter (Contactless)

Tag: –
Length: 2
Format: b
Type: Persistent
Description: Counts the number of secure messaging for integrity session key
derivations over the contactless interface that are not followed by
of the card, and is used to limit this number to the SMI Session Key
Counter Limit (Contactless).
SMI Session Key Counter Limit (Contact)

Tag: 'DF32'
Length: 2
Format: b
Type: Persistent
Description: Limits the number of secure messaging for integrity session key
derivations over the contact interface that are not followed by a
of the card.
SMI Session Key Counter Limit (Contactless)

Tag: 'DF33'
Length: 2
Format: b
Type: Persistent
Description: Limits the number of secure messaging for integrity session key
derivations over the contactless interface that are not followed by a
of the card.

Tag: –
Length: Variable
Format: b
Description: Used to build a transaction log record before it is stored in the
Transaction Log File.

Data Dictionary

Tag: '9F1A'
Length: 2
Format: n3

Tag: –
Length: 4
Format: b
Description: Transient data object used to store the relay resistance entropy of the
terminal included in the value field of the EXCHANGE RELAY
RESISTANCE DATA command.
Terminal Relay Resistance Entropy (Recovery)

Tag: –
Length: 4
Format: b
Type: Persistent
Description: A persistent copy of the Terminal Relay Resistance Entropy for
Terminal Type
Tag: '9F35'
Length: 1
Format: n2

Tag: '95'
Length: 5
Format: b
Byte 1
b8 Offline Data Authentication Was Not Performed
b7 SDA Failed
b6 ICC Data Missing
b5 Card Appears On Terminal Exception File
b4 DDA Failed
b3 CDA Failed
b2-1 RFU

Data Dictionary
Byte 2
b8 ICC And Terminal Have Different Application Versions
b7 Expired Application
b6 Application Not Yet Effective
b5 Requested Service Not Allowed For Card Product
b4 New Card
b3-1 RFU
Byte 3
b8 Cardholder Verification Was Not Successful
b7 Unrecognised CVM
b6 PIN Try Limit Exceeded
b5 PIN Entry Required And PIN Pad Not Present Or Not Working
b4 PIN Entry Required, PIN Pad Present, But PIN Was Not Entered
b3 Online PIN Entered
b2-1 RFU
Byte 4
b8 Transaction Exceeded Floor Limit
b7 Lower Consecutive Offline Limit Exceeded
b6 Upper Consecutive Offline Limit Exceeded
b5 Transaction Selected Randomly For Online Processing
b4 Merchant Forced Transaction Online
b3-1 RFU
Byte 5
b8 Default TDOL Used
b6 Script Processing Failed Before Final Generate AC
b5 Script Processing Failed After Final Generate AC
b4 Relay Resistance Threshold Exceeded
b3 Relay Resistance Time Limits Exceeded
b2-1 Relay Resistance Performed
00: Relay resistance protocol not supported (not used by this
version of the specification)
01: RRP Not Performed
10: RRP Performed
11: RFU

Tag: '5F2A'
Length: 2
Format: n3

Data Dictionary
Transaction Date
Transaction Date
Tag: '9A'
Length: 3
Format: n6 YYMMDD

Tag: –
Length: Variable
Format: b
Description: Temporary variable containing the first and second GENERATE AC
command data.
Transaction Time
Tag: '9F21'
Length: 3
Format: n6 HHMMSS
Transaction Type
Tag: '9C'
Length: 1
Format: n2
Transmission Time For Relay Resistance R-APDU (Contact)

Tag: 'DF0B'
Length: 2
Format: b
Type: Persistent
Description: Transmission Time For Relay Resistance R-APDU (Contact)
represents the time taken to send the EXCHANGE RELAY
RESISTANCE DATA R-APDU when the contact interface is used.
It is a 2 byte binary value in units of hundreds of microseconds.
Transmission Time For Relay Resistance R-APDU (Contactless)

Tag: 'DF76'
Length: 2
Format: b
Type: Persistent
Description: Transmission Time For Relay Resistance R-APDU (Contactless)
represents the time taken to send the EXCHANGE RELAY
RESISTANCE DATA R-APDU when the contactless interface is
used. It is a 2 byte binary value in units of hundreds of
microseconds.

Data Dictionary
Tag: '9F37'
Length: 4
Format: b

Tag: '9F6A'
Length: 4
Format: n8
Description: Temporary variable containing an unpredictable number in a numeric
format used during the processing of the COMPUTE
CRYPTOGRAPHIC CHECKSUM command.
Unpredictable Number (Recovery)

Tag: –
Length: 4
Format: b
Type: Persistent
Description: A persistent copy of the Unpredictable Number for transaction
recovery.


MACA Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MACA Manual

Uploaded by

Copyright:

Available Formats

M/Chip Advance Card

The information contained in this document is proprietary and confidential to

This material may not be duplicated, published, or disclosed, in whole or in part,

Implementation of this M/Chip Advance Card Application Specification requires a

MasterCard makes no representations or warranties of any kind, express or implied,

©2015 MasterCard – Proprietary and Confidential

©2015 MasterCard – Proprietary and Confidential

3.4. Select Processing ......................................................................................... 36

©2015 MasterCard – Proprietary and Confidential

8.3. Exchange Relay Resistance Data Processing .............................................. 98

©2015 MasterCard – Proprietary and Confidential

13. Get Processing Options ................................................... 353

©2015 MasterCard – Proprietary and Confidential

21.3. Update Record Processing ......................................................................... 457

©2015 MasterCard – Proprietary and Confidential

23.12. Compute M/Chip 2.05 CVR ...................................................................... 503

©2015 MasterCard – Proprietary and Confidential

1. Using This Manual

©2015 MasterCard – Proprietary and Confidential

1.3. Related Information

[EMV BOOK 1] Integrated Circuit Card Specification for Payment Systems:

©2015 MasterCard – Proprietary and Confidential

©2015 MasterCard – Proprietary and Confidential

LCOTA Lower Cumulative Offline Transaction Amount

©2015 MasterCard – Proprietary and Confidential

1.5. Specification Language

Procedure start Procedure return decision

task complex task Subroutine call

connector complex decision state transition

©2015 MasterCard – Proprietary and Confidential

An explanation of the task performed by symbol VY.1.1 is provided as follows:

©2015 MasterCard – Proprietary and Confidential

1.6. Notational Conventions

1.6.1. Hexadecimal Notational Convention

1.6.2. Binary Notational Convention

1.6.3. Decimal Notational Convention

1.6.4. Data Object Notational Convention

Transient data objects:

©2015 MasterCard – Proprietary and Confidential

In a few exceptional cases, an index is used to identify a sub-element of a data object.

 Ranges of bytes are expressed with the x : y notational convention:

 Ranges of bits are expressed with the y : x notational convention:

©2015 MasterCard – Proprietary and Confidential

 Functionality of a certain complexity and appearing more than once is

 The notational convention NOT is used for bit inversion.

©2015 MasterCard – Proprietary and Confidential

1.6.7. State Notational Convention

1.6.8. C-APDU Notational Convention

©2015 MasterCard – Proprietary and Confidential

1.7. Data Object Format

1.8. Specification Principles

©2015 MasterCard – Proprietary and Confidential

1.9. Revision History

Version 1.2  Implemented Relay Resistant Protocol (RRP)

©2015 MasterCard – Proprietary and Confidential

2. General Card Requirements

©2015 MasterCard – Proprietary and Confidential

2.2. State Machine Interface

State machine to card link

state machine interface

©2015 MasterCard – Proprietary and Confidential

2.3. The ICC interface

The application layer on the contactless interface must be compliant with

2.4. Multiple Logical Channels