EMV Card Risk Management Commands

• Card Risk Management DOL 1 (CDOL1):
9F 02 06 9F 03 06 9F 1A 02 95 05 5F 2A 02 9A 03
9C 01 9F 37 04 9F 35 01 9F 45 02 9F 4C 08 9F 34
03
• 9F02.6 Amount, Authorized (numeric)
• 9F03.6 Amount, Other (numeric)
• 9F1A.2 Terminal Country Code
• 95.5 Terminal Verification Results
• 5F2A.2 Transaction Currency Code
• 9A. 3 Transaction Date
• 9C.1 Transaction Type
• 9F37.4 Unpredictable Number
• 9F35. 1 Terminal Type
• 9F45.2 Data Authentication Code (DAC)
• 9F4C.8 ICC Dynamic Number
• 9F34.3 CVM Results

Card Risk Management DOL 2 (CDOL2): 910A8A0295059F37049F4C08
• 91.10 Issuer Authentication Data
• 8A. 2 Authorization Response Code
• 95.5 Terminal Verification Results
• 9F37.4 Unpredictable Number
• 9F4C.8 ICC Dynamic Number
• IAC-Default: BC50BC8800
offline data authentication was not performed
ICC data missing
• card appears on terminal exception file
• DDA failed
• CDA failed
• expired application
• requested service not allowed for card product
• cardholder verification was not successful
PIN try limit exceeded
• PIN required and PIN pad not present or not working
• PIN required, PIN pad present, but PIN was not entered
• online PIN is entered
• transaction exceeds floor limit
• merchant forced transaction online
• IAC-Denial: 0000000000
• IAC-Online: BC70BC9800
offline data authentication was not performed
ICC data missing
• card appears on terminal exception file
• DDA failed
• CDA failed
• expired application
• application not yet effective
• requested service not allowed for card product
• cardholder verification was not successful
PIN try limit exceeded
• PIN required and PIN pad not present or not working
• PIN required, PIN pad present, but PIN was not entered
• online PIN is entered
• transaction exceeds floor limit
• transaction selected randomly for online processing
• merchant forced transaction online
CA Public Key Index: 5 (05)
• Issuer Public Key Certificate:
ED BD 79 94 06 7B 12 46 39 D0 B3 CF 89 1E EA AC
5A A1 44 45 09 9F ED 3E C5 E1 99 BD AC EF 5B 01
4D C8 02 60 55 C4 55 6A 97 01 62 D8 AC 61 29 A5
F8 1F 0E 11 86 2E 02 05 E1 AD 18 BB 98 12 39 88
2D 22 35 58 8D 4A 68 59 25 18 BA DB 01 74 C9 C0
59 4A ED 35 E6 41 D2 E1 80 9F C2 BE 69 63 61 16
6F BC B8 B8 E4 64 4A 5B 83 69 9B 6C 49 37 74 52
9E FE DC FC 76 8A D8 D9 55 CE 63 C3 E3 E5 91 50
F9 B5 F1 31 F1 C5 48 7A E7 ED D4 C5 B4 4B 99 30
Seventy eight
16 1F CA 6C E5 7C 91 6F EA CA 65 6E 20 20 EA C7
14 F4 EB DA 6D 1B 48 42 92 46 30 F3 3F 61 70 47
• Issuer Public Key Remainder:
C9 BC 26 10 83 1D F1 A7 A2 A6 DB E9 E6 33 40 1A
0F 54 40 57 56 BD E3 49 F8 15 8E 2C 22 3C 03 0A
45 B6 F7 ED
Issuer Public Key Exponent: 03
ICC Public Key Certificate:
91 7D 25 34 98 48 68 E3 4D 43 52 09 74 8C 5F 91
2C B1 E2 80 18 74 83 87 20 53 6F 75 B6 DD 2D C2
71 5A 71 08 93 E5 AD A3 1D D7 63 D1 69 BF FF 83
20 25 39 99 D7 9D E2 F8 B7 69 68 39 05 F4 C6 16
1D 3A 6E AB CF 56 F6 D4 5D 65 7A C6 B2 D9 4A 55
30 59 44 66 BD EA B8 53 06 80 80 6F 81 91 F3 A9
B1 06 10 E8 73 9B 95 E5 19 8C 62 39 60 59 50 73
72 06 52 E0 A4 07 BF FC B1 5B 66 64 60 EE CB D5
AE 3D B8 99 B0 70 70 7A F6 AA A9 9E D8 E6 07 CD
1C D8 FB 3E B0 8F E2 64 31 0A 1D 58 91 97 DC 60
24 C0 3E 1A 59 D4 10 7F E8 3D 69 08 6B 01 DC 03
ICC Public Key Exponent: 03
Dynamic Data Authentication DOL (DDOL): 9F3704
• 9F37.4 Unpredictable Number
Static Data Authentication Tag List: 82
82 Application Interchange Profile
• Track 2 Equivalent Data: 5225980034347618D21112011018600000208F
• Primary Account Number: 5225980034347618
• Field separator: D
• Expiration Date: 11.2021
• Service code: 201 (International, use chip where feasible; Normal transaction authorization; No restrictions)
Discretionary data: 1018600000208
Pad to ensure whole bytes: F
• Track 1 Discretionary Data: 31303138363030303030323038 ‘1018600000208’

Offline authentication of card data in accordance with the capabilities of the terminal and the card.
• the card indicates that DDA and CDA offline authentication methods are supported

the terminal supports SDA, DDA, and CDA offline authentication methods
• the CDA method will be used for offline data authentication
• the Issuer’s public key is being restored
• the public key of the payment system used to verify the Issuer’s key certificate is searched for using the following parameters:
• RID the payment system: A000000004
• the index key of the payment system (CA Public Key Index): 5 (05)
• payment system key module length: 176
• the only suitable public key of the payment system was found, which is used to verify the Issuer’s public key certificate
• the Issuer’s public key certificate is recognized as valid, and the validity period of the certificate and the Issuer’s public key are extracted from it:
certificate validity period: 12.2022
public key Exhibitor: 03
• public key module:
AD E0 57 07 5A D8 60 50 4D 53 8A 04 3C 01 05 4E
D2 CB 84 83 56 93 D4 D1 23 04 25 3D E5 D7 D6 7C
07 6F 01 FF FC 4F 33 46 35 39 7B EE 8C 70 32 61
34 5B B6 76 D0 66 F6 F3 AC CE 3C 4C 1D 43 68 37
BD DD 15 38 7C 6D A3 4F 4F 56 5E 66 F8 B9 A8 56
53 85 79 E0 4B 28 82 61 10 BC 49 AB 97 48 AB
C1 2B F8 B8 51 86 26 52 60 6C 78 16 FB CE 2C 6D
73 C2 A6 1B B1 F0 FA 49 33 13 44 58 99 F9 3F A9
0C 37 ED 86 E9 97 89 10 38 84 E1 96 C9 BC 26 10
83 1D F1 A6 A7 DB A2 E9 E6 33 40 1A 54 0F 40 57
56 BD E3 49 F8 15 8E 03 22 2C 0A 3C 45 F7 B6 ED
the card’s public key certificate is verified
• the certificate of the card’s public key is recognized as valid, and the certificate’s validity period and the card’s public key are extracted from it:
certificate validity period: 11.2021
public key Exhibitor: 03
• public key module:
B6 DF E9 32 85 59 70 45 39 35 3E 8D 19 F9 FA 51
F3 8A C2 D1 54 64 67 35 76 31 2E 32 2C CF EF 43
3C A4 C5 E1 BD 96 CB 6E 20 55 54 EE 1F 4A 3E 0D
45 AE 26 C2 A2 EF E2 B7 0E FF DA 91 3A 6C ED 53
CE AF C0 27 3C 7E 46 52 61 3D 77 FB 9A 97 EE 23
61 A7 1D B0 1C 7F 96 AF E0 65 D7 4E 45 7A 6C 90
9E 73 A4 68 BF F1 D2 7B F9 11 E2 64 59 7D 0C 01
1D 15 56 63 D1 B4 B6 7C AF BF D3 76 CA 3C DA 49
• the offline authentication method for CDA data will be applied after the first GENERATE AC command is executed (until the reasons why this method could not be applied are found)

Check restrictions on the processing of the transaction.
• verification of matching version numbers of card and terminal applications is never performed
• application usage control is performed according to the attributes defined in the Application Usage Control object

the terminal is not an ATM and it is determined that operations are allowed in devices other than ATMs
• the transaction type is associated with the purchase of goods (services), the country code of the Issuer matches the country code of the terminal and
transactions for purchasing goods (services) within the country are allowed
• app usage control has shown that there are no restrictions on using the payment app to complete a transaction
• an Application Effective Date object is defined on the card, which indicates that the application can already be used
• an Application Expiration Date object is defined on the card, which indicates that the application has not expired yet

Verification of the cardholder.
• verification of the cardholder is performed using the CVM list, which defines the verification rules (total rules: 6)
• the verification rule of the cardholder with the number 1 is processed

execution condition: the transaction is related to cash withdrawal at an ATM
• verification method: online PIN verification
• the condition for executing the method of verification is not satisfied (the wrong type of transaction, or type of terminal)
• the verification rule of the cardholder with the number 2 is processed
• execution condition: the terminal supports the cardholder verification method
• verification method: offline verification of the pin code in encrypted form
getting the number of remaining PIN attempts
• issuing the GET DATA command to get the value of the PIN Try Counter payment application object
• command execution time: 31 msec
• number of remaining PIN attempts: 3
presenting an encrypted PIN code to the card
• issue the GET CHALLENGE command to get a random number used for PIN encryption
• command execution time: 47 msec
• the command returned a random number: 752818BC06BF70C5
encrypting the PIN code on the card key used to encrypt the PIN code
• issue the VERIFY command to verify the PIN code of the payment application in encrypted form
• command execution time: 281 msec
• incorrect PIN code was presented (the remaining counter is 2)
• the verification rule of the cardholder with the number 3 is processed
• execution condition: the terminal supports the cardholder verification method
• verification method: offline verification of the PIN code in plain text
getting the number of remaining PIN attempts
• issuing the GET DATA command to get the value of the PIN Try Counter payment application object
• command execution time: 31 msec
• number of remaining PIN attempts: 2
presenting an unencrypted PIN code to the card
• issue the VERIFY command to verify the PIN code of the payment application in plain text
• command execution time: 63 msec
• incorrect PIN code was presented (the counter for the remaining charges is 1)
• the verification rule of the cardholder with the number 4 is processed
• execution condition: the terminal supports the cardholder verification method
• verification method: online PIN verification
• verification method completed successfully
• CVM list processing is complete

Risk management procedures performed by the terminal.

checking the payment limit in offline mode:
• the amount of the payment transaction: 20.00
• the maximum value of the amount of the payment in offline mode (Terminal Floor Limit): 1000.00
• the payment transaction amount is less than the maximum payment amount (no special transaction execution situation was detected)
• the payment application supports the transaction log, but the check for “split sales” is never performed in the current version of the program
performing a random transaction selection procedure for online processing:
target percentage: 20
random percentage: 53
• the threshold value of the payment amount for biased selection used in the random transaction selection procedure for online processing: 500.00
• the transaction does not meet the biased selection criteria (the transaction is selected for online processing regardless of the amount of the payment transaction)
• the transaction is not selected for online processing
• offline spending speed is not checked because the card does not have a Lower Sequential Offline Limit object

Evaluation of the results of the procedures performed by the terminal (making a decision on further processing of the transaction).
• during the checks performed by the terminal, the following special situations were detected (the corresponding bits are set in the TVR):
• online PIN is entered
• to determine whether a transaction needs to be rejected from the acquirer’s point of view, use the following TAC-Denial: 0000000000
• according to the policy of the acquirer and the Issuer, the transaction is not rejected (no matching features were found in TVR and TAC-Denial or IAC-Denial)
• the following TAC-Online is used to determine whether the Issuer needs to authorize the transaction from the acquirer’s point of view: FC509C8800

offline data authentication was not performed
• SDA failed
ICC data missing
• card appears on terminal exception file
• DDA failed
• CDA failed
• expired application
• requested service not allowed for card product
• cardholder verification was not successful
• PIN required and PIN pad not present or not working
• PIN required, PIN pad present, but PIN was not entered
• online PIN is entered
• transaction exceeds floor limit
• merchant forced transaction online
• found matching the following attributes in TVR and TAC-Online:
• online PIN is entered
• in accordance with the acquirer’s policy, an ARQC cryptogram (online transaction authorization) must be requested from the payment application)
• the CDA method is used for offline data authentication, so the first GENERATE AC command requests the Signed Dynamic Application Data 13 certificate. Issue the first GENERATE AC command to perform a transaction in contact mode.
• the GENERATE AC command is issued with the following parameters:
• the requested cryptogram: ARQC
• in response you are requesting a certificate Signed Dynamic Application Data
• to make a decision about executing a transaction with a command, the data listed in CDOL1 is passed:
00 00 00 00 20 00 00 00 00 00 00 00 06 43 00 00
04 00 00 06 43 19 02 12 00 DC 6E 0B 1C 22 00 00
00 00 00 00 00 00 00 00 02 03 00
interpretation of data according to CDOL1:
• Amount, Authorized (numeric) (9F02. 6): 20.00
• Amount, Other (numeric) (9F03. 6): 0.00
Terminal Country Code (9F1A. 2): 0643
Terminal Verification Results (95.5): 0000040000
• online PIN is entered
• Transaction Currency Code (5F2A. 2): 0643
• Transaction Date (9A. 3): 12.02.2019
• Transaction Type (9C. 1): 00 (purchase of goods or services)
• Unpredictable Number (9F37. 4): DC6E0B1C
Terminal Type (9F35. 1): 22
Attended, Offline with online capability
• Operational control is provided by Merchant
• Data Authentication Code (DAC) (9F45. 2): 0000
ICC Dynamic Number (9F4C.8): 0000000000000000
CVM Results (9F34. 3): 020300
• Enciphered PIN verified online
• If terminal supports the CVM
• Unknown CVM Result
command execution time: 344 msec
• the following data was received in response to the command:
77 81 A2 9F 27 01 80 9F 36 02 00 39 9F 4B 81 80
11 CB AF 7B 74 63 52 12 4B 99 E9 C6 54 67 DB 9E
24 3C 7B 49 F6 E5 A5 E5 0D 2D F1 5F 47 54 0B 5C
FF DC C6 F7 D8 26 64 90 38 54 B1 A0 B2 F3 9B 2D
87 51 84 9B F6 5A 2D 9E C1 63 75 81 41 E0 F4 50
86 D6 C5 A0 A0 4A 05 B4 7D 82 16 1C 2E B8 43
A7 1F 5C 44 56 88 D6 C9 5A 5B B9 CE B2 11 3D 05
20 40 C7 B8 89 35 70 54 37 12 7B 5C 71 5D C9 C8
EE 6C 0B 41 A4 CF B0 7D 26 07 70 75 1C D5 3B 00
9F 10 12 01 10 A4 40 01 12 00 00 00 00 00 00 00
04 20 00 00 FF
interpretation of the resulting TLV structure:
• 77.162 Response Message Template Format 2
• 9F27.1 Cryptogram Information Data (CID)
• 9F36. 2 Application Transaction Counter (ATC)
• 9F4B. 128 Signed Dynamic Application Data
• 9F10.18 Issuer Application Data
the data received in response to the command is analyzed
• Cryptogram Information Data: 80
ARQC (authorization Request Cryptogram – Online authorization requested)
• ATC: 0039
Signed Dynamic Application Data:
11 CB AF 7B 74 63 52 12 4B 99 E9 C6 54 67 DB 9E
24 3C 7B 49 F6 E5 A5 E5 0D 2D F1 5F 47 54 0B 5C
FF DC C6 F7 D8 26 64 90 38 54 B1 A0 B2 F3 9B 2D
87 51 84 9B F6 5A 2D 9E C1 63 75 81 41 E0 F4 50
86 4A D6 C5 A0 A0 A0 05 82 16 7D B4 1C 2E B8 43
A7 1F 5C 44 56 88 D6 C9 5A 5B B9 CE B2 11 3D 05
20 40 C7 B8 89 35 70 54 37 12 7B 5C 71 5D C9 C8
EE 6C 0B 41 A4 CF B0 7D 26 07 70 75 1C D5 3B 00
• Issuer Application Data: 0110A44001120000000000000004200000FF
• Derivation key index: 1
• Cryptogram Version Number: 16
• The Card Verification Results:
• AC returned in First Generate AC: ARQC
• AC returned in Second Generate AC second Generate AC not requested
• Offline PIN verification performed
• CDA returned in First Generate AC
• Script Counter: 0
PIN Try Counter: 1
• Offline PIN verification failed
• Domestic transaction
• DAC/ICC Dynamic Number 2 Bytes: 0000
• Counters: 00000004200000FF
• no errors were detected in the data received in response to the command
the Signed Dynamic Application Data certificate is verified
• the Signed Dynamic Application Data certificate is recognized as valid
• the certificate defines the following ICC Dynamic Number: 5CA0B7A2ED4ABEB0
• the payment application cryptogram was extracted from the certificate: 1CECDF76E8151DD9
• the offline authentication method for CDA data was successful

Verification of the payment application cryptogram provided by the first GENERATE AC command, using the application data and the specified key value to calculate the cryptograms.
• verification of the payment application cryptogram with this RID is not implemented
Online processing (emulation of terminal actions when a transaction must be sent to the Issuer for authorization).
• a situation that must be simulated at the user’s request during online processing: the terminal requests approval of the transaction (with the emulation of the “Unable to go Online” state»)
• to determine whether a transaction needs to be rejected from the acquirer’s point of view in the “Unable to go Online” state, use the following TAC-Default: FC509C8800

offline data authentication was not performed
• SDA failed
ICC data missing
• card appears on terminal exception file
• DDA failed
• CDA failed
• expired application
• requested service not allowed for card product
• cardholder verification was not successful
• PIN required and PIN pad not present or not working
• PIN required, PIN pad present, but PIN was not entered
• online PIN is entered
• transaction exceeds floor limit
• merchant forced transaction online
• found matching the following attributes in TVR and TAC-Default:
• online PIN is entered
• in accordance with the acquirer’s policy, the transaction must be rejected

Issue a second GENERATE AC command to make a final decision about processing the transaction after online processing.
• the GENERATE AC command is issued with the following parameters:
• the requested cryptogram: AAC
• the response does not request a Signed Dynamic Application Data certificate
• the data listed in CDOL2 is passed to make a decision about executing a transaction with the command:
00 00 00 00 00 00 00 00 00 00 5A 33 00 00 04 00
0B 00 6E DC 1C 5C A0 B7 A2 ED 4A B0 BE

interpretation of data in accordance with CDOL2:
Issuer Authentication Data (91.10): 00000000000000000000
• Issuer Authentication Data not received by terminal
• Authorization Response Code (8A. 2): ‘Z3’
Terminal Verification Results (95.5): 0000040000
• online PIN is entered
• Unpredictable Number (9F37. 4): DC6E0B1C
ICC Dynamic Number (9F4C.8): 5CA0B7A2ED4ABEB0
command execution time: 172 msec
• the following data was received in response to the command:
77 29 9F 27 01 9F 02 00 36 00 39 08 5C 9F 26 96
26 33 C9 B4 1B 95 9F 01 10 10 12 24 40 01 52 00
00 5C A0 00 00 00 04 20 00 00 FF
interpretation of the resulting TLV structure:
• 77.41 Response Message Template Format 2
• 9F27.1 Cryptogram Information Data (CID)
• 9F36. 2 Application Transaction Counter (ATC)
• 9F26. 8 Application Cryptogram
• 9F10.18 Issuer Application Data
the data received in response to the command is analyzed
• Cryptogram Information Data: 00
• AAC (Application Authentication Cryptogram – Transaction declined)
• ATC: 0039
• Application Cryptogram: 5C9626331B95C9B4
• Issuer Application Data: 01102440015200005CA000000004200000FF
• Derivation key index: 1
• Cryptogram Version Number: 16
• The Card Verification Results:
• AC returned in First Generate AC: ARQC
• AC returned in Second Generate AC: AAC
• Offline PIN verification performed
• CDA returned in First Generate AC
• Script Counter: 0
PIN Try Counter: 1
• Unable to go online
• Offline PIN verification failed
• Domestic transaction
• DAC/ICC Dynamic Number 2 Bytes: 5CA0
• Counters: 00000004200000FF
• no errors were detected in the data received in response to the command

Verification of the payment application cryptogram provided by the second GENERATE AC command, using the application data and the specified key value to calculate the cryptograms.
• verification of the payment application cryptogram with this RID is not implemented
Verification of the payment card in contact mode is completed, since all required operations with the card have been completed. The following actions were performed during the verification process:
• the payment application is selected on the card using the SELECT command
• issued the GET PROCESSING OPTIONS command to initiate a transaction and get the information needed to complete it
• data was read from the payment application file records

the Issuer’s public key was restored
• restored the public key of the card
offline authentication of card data was successfully completed
• the verification method of the cardholder “Presenting a PIN code for transmitting it to the Issuer” was performed»
• GET DATA commands were issued to get information about payment application objects
• the first GENERATE AC command was issued to perform a transaction in contact mode
• a second GENERATE AC command was issued to complete the transaction in contact mode