RUPAY DEVICE VALIDATION TEST

PLAN
(VERSION 2.4.14)
 uPay Device Validation Test Pla

Document History

Version Date Revision History

(DD/MM/YY)

0.1 02/13/2013 First Draft Version

0.2 03/01/2013 Changes incorporated after initial review

1.0 03/19/2013 Release version

1.1 03/21/2013 Release version

1.2 04/12/2013 Release version

1.3 04/16/2013 Release version

1.4 17/01/2014 Modified the test cases

1.5 15/04/2014 Structured the pass criteria

1.6 15/05/2014 Added 3 new test cases, Renamed test case id

1.7 19/06/2014 Some cases corrected

1.8 25/06/2014 Manual pass criteria updated

1.9 24/08/2014 DCI card Assigned

2.0 19/05/2015 Document history format changed

2.1 24/11/2016 UPI & JCB for PoS /RuPay ATM test cases added

2.2 15/12/2016 UPI.DEV.P.029 corrected

2.3 02/01/2017 UPI & JCB test cases corrected

2.4 11/01/2017 UPI.DEV.P 25 card log pass criteria corrected

2.4.1 06/06/2017 AID for RuPay Card images are aligned

Card numbers updated
Tests: RUPAY.DEV.P.063, RUPAY.DEV.P.064
RUPAY.DEV.P.043, RUPAY.DEV.P.044 is removed
due to the change of CA Keys to 5D.

2/241 Confidential
uPay Device Validation Test Pla

2.4.2 06/06/2017 Updated Image number in RUPAY.DEV.P.065 and

RUPAY.DEV.A.041 from Image 39 to Image 40

2.4.3 09/06/2017 Added ATM test cases for RuPay and gap analysis with
other international card schemes

2.4.4 12/06/2017 Modified the PAN of MRuPay and VRuPay. Deleted the
additional tests Cash Withdrawal and Card to Card Fund
Transfer – Beneficiary card number with Minimum
length for MRuPay and VRuPay

2.4.5 16/06/2017 Added the test card ID for MRuPay and VRuPay and
corrected some typos

2.4.6 19/06/2017 Updated the PAN and amount of few test cases

2.4.7 26/06/2017 New test RUPAY.DEV.A.047 added

Short description modified for test case
RUPAY.DEV.A.041
Beneficiary card number has been updated for tests
RUPAY.DEV.A.059, RUPAY.DEV.A.063
Card image updated for tests: RUPAY.DEV.A.066,
RUPAY.DEV.A.067
RUPAY.DEV.A.JCB002, RUPAY.DEV.A.JCB003 are
deleted
UPI test cases revisited and modified

2.4.8 27/06/2017 Typo in test case id New test RUPAY.DEV.A.068

2.4.9 30/06/2017 Updated JCB and UPI images as per NPCI request
Updated PDOL values pass criteria for tests
RUPAY.DEV.P.021, RUPAY.DEV.A.018

2.4.10 26/07/2017 Updated procedure and terminal display message for

RUPAY.DEV.A.047, RUPAY.DEV.A.068,
RUPAY.DEV.A.M003, RUPAY.DEV.A.V003

2.4.11 07/02/2018 Updated pass criteria, Procedure for ATM test cases
based on the observation during certification / testing
phase.

2.4.12 26/03/2018 Added Micro ATM functionality

2.4.13 19/06/2018 Added a test for POS and ATM using qSPARC Card

3/241 Confidential
uPay Device Validation Test Pla

2.4.14 19/03/2019 Updated PAN number for test case RUPAY.DEV.P.006

Test case RUPAY.DEV.070, RUPAY.DEV.071 is renamed
as RUPAY.DEV.P.070, RUPAY.DEV.P.071

4/241 Confidential
uPay Device Validation Test Pla

TABLE OF CONTENTS

1 Introduction .......................................................................................... 10
1.1 Scope ....................................................................................................... 10
1.2 Audience ................................................................................................... 10
1.3 Reference documents ................................................................................... 10
1.4 Terminology ............................................................................................... 10
2 Device Validation Test ............................................................................. 11
2.1 Purpose .................................................................................................... 11
2.2 Test Environment ........................................................................................ 11
2.3 Test Case Structure ...................................................................................... 12
3 Test Cases ............................................................................................ 13
3.1 PoS Certification Test Scenarios ....................................................................... 13
3.1.1 RUPAY.DEV.P.001 - Basic RUPAY Card ........................................................................ 13
3.1.2 RUPAY.DEV.P.002 - T= 1 Card .................................................................................. 14
3.1.3 RUPAY.DEV.P.003 - DDA Successful Card ..................................................................... 15
3.1.4 RUPAY.DEV.P.004 - CDA Successful Card ..................................................................... 17
3.1.5 RUPAY.DEV.P.005 - Domestic Only Card ...................................................................... 18
3.1.6 RUPAY.DEV.P.006 - PAN Maximum Length Card ............................................................. 19
3.1.7 RUPAY.DEV.P.007 - PAN SN Not Present ...................................................................... 20
3.1.8 RUPAY.DEV.P.008 - PAN SN Equal to 15 ...................................................................... 21
3.1.9 RUPAY.DEV.P.009 - Extended AID (1) ......................................................................... 22
3.1.10 RUPAY.DEV.P.010 - Extended AID (2) ......................................................................... 24
3.1.11 RUPAY.DEV.P.011 - Blocked Card .............................................................................. 25
3.1.12 RUPAY.DEV.P.012 - PIN Is Blocked ............................................................................. 26
3.1.13 RUPAY.DEV.P.013 - PIN of 6 digits ............................................................................. 27
3.1.14 RUPAY.DEV.P.014 - Partial PIN entry ......................................................................... 28
3.1.15 RUPAY.DEV.P.015 - Offline Enciphered PIN .................................................................. 29
3.1.16 RUPAY.DEV.P.016 - Offline Enciphered PIN – Wrong PIN entry ........................................... 30
3.1.17 RUPAY.DEV.P.017 - Expired Application ...................................................................... 32
3.1.18 RUPAY.DEV.P.018 - Issuer Application Data of 32 Bytes ................................................... 33
3.1.19 RUPAY.DEV.P.019 - Application Blocked ..................................................................... 34
3.1.20 RUPAY.DEV.P.020 - Single Application Blocked in multiple AID card ................................... 34
3.1.21 RUPAY.DEV.P.021 - PDOL ....................................................................................... 36
3.1.22 RUPAY.DEV.P.022 - Offline Plaintext PIN .................................................................... 37
3.1.23 RUPAY.DEV.P.023 - Offline Plaintext PIN - Wrong PIN entry.............................................. 38
3.1.24 RUPAY.DEV.P.024 - Leap Year Expiration Date ............................................................. 39
3.1.25 RUPAY.DEV.P.025 - Script Processing (1) – Single script command ...................................... 40
3.1.26 RUPAY.DEV.P.026 - Script Processing (2) – Multiple script commands .................................. 41
3.1.27 RUPAY.DEV.P.027 - DDA (ICC Public Key Exponent 2^16+1) .............................................. 43
3.1.28 RUPAY.DEV.P.028 - Offline Enciphered PIN (ICC Public Key Exponent 2^16+1) ....................... 44
3.1.29 RUPAY.DEV.P.029 - Issuer Authentication Data ............................................................. 45
3.1.30 RUPAY.DEV.P.030 - Inconsistent PAN between Chip and Magnetic stripe .............................. 46
3.1.31 RUPAY.DEV.P.031 - Purchase with Cash Back Transaction ................................................ 47
3.1.32 RUPAY.DEV.P.032 - Unknown AID .............................................................................. 48
3.1.33 RUPAY.DEV.P.033 - ATM Only Card ............................................................................ 49
3.1.34 RUPAY.DEV.P.034 - Fallback Not Allowed .................................................................... 49
3.1.35 RUPAY.DEV.P.035 - PAN RuPay (SDA Successful card) ..................................................... 51

5/241 Confidential
uPay Device Validation Test Pla

3.1.36 RUPAY.DEV.P.036 - SDA Failed Card .......................................................................... 52

3.1.37 RUPAY.DEV.P.037 - DDA Failed Card .......................................................................... 53
3.1.38 RUPAY.DEV.P.038 - CDA Failed Card .......................................................................... 54
3.1.39 RUPAY.DEV.P.039 - Purchase with Cash back Transaction with Purchase Only Card ................. 55
3.1.40 RUPAY.DEV.P.040 - Cash at POS Transaction ................................................................ 56
3.1.41 RUPAY.DEV.P.041 - Terminal failure Reversal............................................................... 57
3.1.42 RUPAY.DEV.P.042 - Reversal with Issuer Script Results ................................................... 58
3.1.43 RUPAY.DEV.P.043 - Fallback when chip fails ................................................................ 60
3.1.44 RUPAY.DEV.P.044 - Void......................................................................................... 60
3.1.45 RUPAY.DEV.P.045 - Void Reversal with Issuer Script Results ............................................. 62
3.1.46 RUPAY.DEV.P.046 - Refund ..................................................................................... 63
3.1.47 RUPAY.DEV.P.047 - Reversal when AAC/TC not received ................................................. 64
3.1.48 RUPAY.DEV.P.048 - Combination CVM – Offline Plaintext PIN and Signature .......................... 65
3.1.49 RUPAY.DEV.P.049 - Combination CVM – Offline Enciphered PIN and Signature ....................... 67
3.1.50 RUPAY.DEV.P.050 - No CVM ..................................................................................... 68
3.1.51 RUPAY.DEV.P.051 - Response without Issuer authentication data ....................................... 69
3.1.52 RUPAY.DEV.P.052 - Purchase with SMS Card ................................................................ 70
3.1.53 RUPAY.DEV.P.053 - Cash on POS Transaction with SMS card ............................................. 71
3.1.54 RUPAY.DEV.P.054 - Purchase Cash Back Transaction with SMS Card .................................... 73
3.1.55 RUPAY.DEV.P.055 - Purchase with RuPay International Card ............................................. 74
3.1.56 RUPAY.DEV.P.056 - Cash at POS Transaction with RuPay International Card .......................... 75
3.1.57 RUPAY.DEV.P.057 - Purchase Cash Back Transaction with International Card ........................ 76
3.1.58 RUPAY.DEV.P.058 - Purchase fallback Transaction with International Card ........................... 77
3.1.59 RUPAY.DEV.P.059 - Cash Transaction with International Card ........................................... 78
3.1.60 RUPAY.DEV.P.060 - Purchase Only Card ...................................................................... 79
3.1.61 RUPAY.DEV.P.061 - Purchase Transaction with DMS Card with magnetic stripe only ................ 80
3.1.62 RUPAY.DEV.P.062 - Purchase Transaction with SMS Card with magnetic stripe only ................ 81
3.1.63 RUPAY.DEV.P.065 - International Card with CA Public Key Index '5D' ................................... 82
3.1.64 RUPAY.DEV.P.066 - Response without Issuer authentication data & declined by Issuer ............. 83
3.1.65 RUPAY.DEV.P.067 – RuPay Online PIN Card .................................................................. 84
3.1.66 RUPAY.DEV.P.068 – RuPay Offline PIN Card .................................................................. 86
3.1.67 RUPAY.DEV.P.069 - Fallback when chip fails ................................................................ 87
3.1.68 RUPAY.DEV.P.070 International Card with Online CVM, if transaction is in the application currency
and under X value ............................................................................................................ 88
3.1.69 RUPAY.DEV.P.071 Basic qSPARC Card ......................................................................... 90
3.1.70 JCB.DEV.P.001 – T=1 protocol .................................................................................. 91
3.1.71 JCB.DEV.P.002 – Fallback when AID mismatched ........................................................... 93
3.1.72 JCB.DEV.P.003 – Cardholder verification correctly according to CVM list .............................. 93
3.1.73 JCB.DEV.P.004 – ATR containing proprietary historical bytes ............................................ 95
3.1.74 UPI.DEV.P.001 – Debit card with Multiple Applications .................................................... 96
3.1.75 UPI.DEV.P.002 – Card without PSE ............................................................................. 98
3.1.76 UPI.DEV.P.003 – Issuer script processing and cardholder name absent in chip ....................... 100
3.1.77 UPI.DEV.P.004 – To validate 1st digit of service code ..................................................... 101
3.1.78 UPI.DEV.P.005 – Quasi credit card with Chinese character in AID ...................................... 102
3.1.79 UPI.DEV.P.006 – SDA successful card ......................................................................... 104
3.1.80 UPI.DEV.P.007 – SDA failed card .............................................................................. 105
3.1.81 UPI.DEV.P.008 - DDA Successful Card ........................................................................ 106
3.1.82 UPI.DEV.P.009 - DDA Failed Card ............................................................................. 108
3.1.83 UPI.DEV.P.010 - CDA Successful Card ........................................................................ 109
3.1.84 UPI.DEV.P.011 - CDA Failed Card ............................................................................. 110
3.1.85 UPI.DEV.P.012 - No Offline CAM supported ................................................................. 112
3.1.86 UPI.DEV.P.013 - Blocked Card ................................................................................. 113
3.1.87 UPI.DEV.P.014 - Application Blocked ........................................................................ 113

6/241 Confidential
uPay Device Validation Test Pla

3.1.88 UPI.DEV.P.015 - Expired Application ......................................................................... 114

3.1.89 UPI.DEV.P.016 – Application is not effective ............................................................... 115
3.1.90 UPI.DEV.P.017 – Different application version number ................................................... 116
3.1.91 UPI.DEV.P.018 - Unknown AID ................................................................................. 117
3.1.92 UPI.DEV.P.019 – Fallback when application selection failed ............................................ 118
3.1.93 UPI.DEV.P.020 - T= 1 Card ..................................................................................... 119
3.1.94 UPI.DEV.P.021 – PIN bypass .................................................................................... 120
3.1.95 UPI.DEV.P.022 – Dual asymmetric algorithm (RSA and SM) - Normal transaction .................... 121
3.1.96 UPI.DEV.P.023 - PIN of 12 digits .............................................................................. 122
3.1.97 UPI.DEV.P.024 - PIN of 4 digits ................................................................................ 123
3.1.98 UPI.DEV.P.025 - PIN Unblock .................................................................................. 124
3.1.99 UPI.DEV.P.026 - PIN Unblock/PIN Change script ........................................................... 126
3.1.100 UPI.DEV.P.027 – CVM Absent ............................................................................... 127
3.1.101 UPI.DEV.P.028 – Unknown CVM ............................................................................. 128
3.1.102 UPI.DEV.P.029 – AUC exceeds the region and service type restrictions ............................ 129
3.2 ATM and Micro ATM Certification Test Scenarios ................................................... 130
3.2.1 RUPAY.DEV.A.001 - Cash Withdrawal ........................................................................ 130
3.2.2 RUPAY.DEV.A.002 – T = 1 Card ................................................................................ 131
3.2.3 RUPAY.DEV.A.005 - PAN Maximum Length Card ........................................................... 132
3.2.4 RUPAY.DEV.A.006 - PAN SN Not Present ..................................................................... 133
3.2.5 RUPAY.DEV.A.007 - PAN SN Equal to 15 ..................................................................... 134
3.2.6 RUPAY.DEV.A.008 - Extended AID (1) ........................................................................ 135
3.2.7 RUPAY.DEV.A.009 - Extended AID (2) ........................................................................ 137
3.2.8 RUPAY.DEV.A.010 - Blocked Card ............................................................................. 138
3.2.9 RUPAY.DEV.A.012 - PIN of 6 digits............................................................................ 139
3.2.10 RUPAY.DEV.A.014 - Expired Application ..................................................................... 140
3.2.11 RUPAY.DEV.A.015 - Issuer Application Data of 32 Bytes .................................................. 141
3.2.12 RUPAY.DEV.A.016 - Application Blocked .................................................................... 142
3.2.13 RUPAY.DEV.A.017 - Single Application Blocked in multiple AID card .................................. 143
3.2.14 RUPAY.DEV.A.018 - PDOL ...................................................................................... 144
3.2.15 RUPAY.DEV.A.020 - Leap Year Expiration Date ............................................................ 146
3.2.16 RUPAY.DEV.A.021 - Script Processing (1) – Single script command ..................................... 147
3.2.17 RUPAY.DEV.A.022 - Script Processing (2) – Multiple script commands ................................. 148
3.2.18 RUPAY.DEV.A.025 - Issuer Authentication Data ............................................................ 150
3.2.19 RUPAY.DEV.A.027 – Balance inquiry Transaction .......................................................... 151
3.2.20 RUPAY.DEV.A.028 - Unknown AID ............................................................................. 152
3.2.21 RUPAY.DEV.A.029 - Fallback Not Allowed ................................................................... 153
3.2.22 RUPAY.DEV.A.034- Terminal failure Reversal .............................................................. 154
3.2.23 RUPAY.DEV.A.035 - Reversal with Issuer Script Results .................................................. 155
3.2.24 RUPAY.DEV.A.036 - Fallback when chip fails ............................................................... 157
3.2.25 RUPAY.DEV.A.039 - When Online PIN is not supported by the Card .................................... 157
3.2.26 RUPAY.DEV.A.040 - Response without Issuer authentication data ...................................... 159
3.2.27 RUPAY.DEV.A.041 - RuPay International Card with amount range in CVM list ........................ 160
3.2.28 RUPAY.DEV.A.042 - Purchase Only Card ..................................................................... 161
3.2.29 RUPAY.DEV.A.046 - Response without Issuer authentication data & declined by Issuer ............ 162
3.2.30 RUPAY.DEV.A.047 – PIN Change ............................................................................... 163
3.2.31 RUPAY.DEV.A.048 – Mini Statement .......................................................................... 164
3.2.32 RUPAY.DEV.A.050 – Mobile Banking Registration .......................................................... 166
3.2.33 RUPAY.DEV.A.051 – Mobile Banking Registration – incorrect mobile number ......................... 167
3.2.34 RUPAY.DEV.A.052 – Mobile Banking Registration (Issuer is not enabled for Mobile Banking
Registration) .................................................................................................................. 168
3.2.35 RUPAY.DEV.A.053 – Aadhaar Number Seeding .............................................................. 170

7/241 Confidential
uPay Device Validation Test Pla

3.2.36 RUPAY.DEV.A.054 – Aadhaar Number Seeding (Issuer is not enabled for Aadhaar Number Seeding)
171
3.2.37 RUPAY.DEV.A.055 – Cheque Book Request .................................................................. 173
3.2.38 RUPAY.DEV.A.056 – Cheque Book Request (Do not Honour) ............................................. 174
3.2.39 RUPAY.DEV.A.057 – Statement Request ..................................................................... 176
3.2.40 RUPAY.DEV.A.058 – Statement Request (Do not Honour) ................................................ 177
3.2.41 RUPAY.DEV.A.059 – Card to Card Fund Transfer ........................................................... 178
3.2.42 RUPAY.DEV.A.060 – Card to Card Fund Transfer – Beneficiary card number with Minimum length
180
3.2.43 RUPAY.DEV.A.061 – Card to Card Fund Transfer (Expired Card) ........................................ 181
3.2.44 RUPAY.DEV.A.062 – Inter-Operable Cash Deposit - Own Account ....................................... 183
3.2.45 RUPAY.DEV.A.063 – Inter-Operable Cash Deposit - Third Party Account (based on card number) 185
3.2.46 RUPAY.DEV.A.064 – Inter-Operable Cash Deposit (Beneficiary card expired) (based on card
number) 187
3.2.47 RUPAY.DEV.A.065 – Transaction with cardholder confirmation ......................................... 189
3.2.48 RUPAY.DEV.A.066 – Transaction with cardholder confirmation – time out ............................ 190
3.2.49 RUPAY.DEV.A.067 – Transaction with cardholder confirmation for one application ................ 191
3.2.50 RUPAY.DEV.A.068 – PIN Change without Issuer Scripting ................................................. 192
3.2.51 RUPAY.DEV.A.069 - Cash Withdrawal using a qSPARC Card .............................................. 194
3.3 ATM and Micro ATM Certification Test Scenarios - MRuPay ....................................... 195
3.3.1 RUPAY.DEV.A.M001 - Cash Withdrawal ...................................................................... 195
3.3.2 RUPAY.DEV.A.M002 – Balance Inquiry Transaction ........................................................ 197
3.3.3 RUPAY.DEV.A.M003 – PIN Change ............................................................................. 198
3.3.4 RUPAY.DEV.A.M004 – Mini Statement ........................................................................ 199
3.3.5 RUPAY.DEV.A.M005 – Mobile Banking Registration ........................................................ 201
3.3.6 RUPAY.DEV.A.M006 – Aadhaar Number Seeding ............................................................ 202
3.3.7 RUPAY.DEV.A.M007 – Cheque Book Request ................................................................ 204
3.3.8 RUPAY.DEV.A.M008 – Statement Request ................................................................... 205
3.3.9 RUPAY.DEV.A.M009 – Card to Card Fund Transfer ......................................................... 207
3.3.10 RUPAY.DEV.A.M011 – Inter-Operable Cash Deposit - Third Party Account (based on card number)
208
3.4 ATM and Micro ATM Certification Test Scenarios - VRuPay........................................ 211
3.4.1 RUPAY.DEV.A.V001 - Cash Withdrawal ...................................................................... 211
3.4.2 RUPAY.DEV.A.V002 – Balance Inquiry Transaction ......................................................... 212
3.4.3 RUPAY.DEV.A.V003 – PIN Change ............................................................................. 214
3.4.4 RUPAY.DEV.A.V004 – Mini Statement ........................................................................ 215
3.4.5 RUPAY.DEV.A.V005 – Mobile Banking Registration ......................................................... 217
3.4.6 RUPAY.DEV.A.V006 – Aadhaar Number Seeding ............................................................ 218
3.4.7 RUPAY.DEV.A.V007 – Cheque Book Request ................................................................ 220
3.4.8 RUPAY.DEV.A.V008 – Statement Request.................................................................... 221
3.4.9 RUPAY.DEV.A.V009 – Card to Card Fund Transfer ......................................................... 223
3.4.10 RUPAY.DEV.A.V011 – Inter-Operable Cash Deposit - Third Party Account (based on card number)
224
3.5 ATM Certification Test Scenarios - JCB .............................................................. 226
3.5.1 RUPAY.DEV.A.JCB001 – T=1 protocol ......................................................................... 226
3.5.2 RUPAY.DEV.A.JCB002 – ATR containing proprietary historical bytes ................................... 228
3.6 ATM Certification Test Scenarios – UPI ............................................................... 229
3.6.1 RUPAY.DEV.A.UPI001 – Card without PSE ................................................................... 229
3.6.2 RUPAY.DEV.A.UPI002 – Issuer script processing and cardholder name absent in chip .............. 231
3.6.3 RUPAY.DEV.A.UPI003 – To validate 1st digit of service code ............................................. 232
3.6.4 RUPAY.DEV.A.UPI004 – Quasi credit card with Chinese character in AID .............................. 234

8/241 Confidential
uPay Device Validation Test Pla

3.6.5 RUPAY.DEV.A.UPI005 – Application is not effective ....................................................... 235

3.6.6 RUPAY.DEV.A.UPI006 – Different application version number ........................................... 236
3.6.7 RUPAY.DEV.A.UPI007 – Fallback when application selection failed .................................... 237
3.6.8 RUPAY.DEV.A.UPI008 – Symmetric algorithm (SM) - Normal transaction .............................. 238
3.6.9 RUPAY.DEV.A.UPI009 – CVM Absent .......................................................................... 239
3.6.10 RUPAY.DEV.A.UPI010 – Unknown CVM ....................................................................... 240
3.6.11 RUPAY.DEV.A.UPI011 – AUC exceeds the region and service type restrictions ....................... 241

9/241 Confidential
 uPay Device Validation Test Pla

1 Introduction

1.1 Scope
This RuPay Device Validation Test Plan contains the test cases that may be executed by an Acquirer
or their authorized representative to validate that the Acquirer's infrastructure and terminals can
support RuPay chip card transactions in accordance with the RuPay chip specifications. RuPay chip
program is compliant with EMV™ specifications version 4.2.
For the purpose of certification testing, Acquirers must execute a subset of these test cases based
on the features indicated in Product Information Form (PIF).
EMV™ is a trademark owned by EMVCo LLC.

1.2 Audience
This document is intended to be used by
 Acquirers
 Member service providers
 RuPay CP
 RuPay test lab

1.3 Reference documents

# Documents Notation

1. RuPay - Online Switching Interface Specification v 1.7 [REF-1]

2. RuPay Chip Terminal Implementation Requirements Guide_v1.0 [REF-2]

3. EMV 4.2 Book 1 – ICC to Terminal Interface [REF-3]

4. EMV 4.2 Book 2 – Security and Key Management [REF-4]

5. EMV 4.2 Book 3 – Application Specification [REF-5]

6. EMV 4.2 Book 4 – Other Interfaces [REF-6]

1.4 Terminology
The following terminology applies:
“Shall” or "Must" - denotes a mandatory requirement
“Should” - denotes a recommendation
“May” - denotes an optional feature
Hexadecimal values are represented within ' '
Binary values are represented with a suffix “b”
The term complete transaction refers to a transaction started from a card insertion in the terminal
until the transaction outcome is arrived (after receiving the response from card in first GENERATE AC
/ second GENERATE AC). The possible transaction outcomes in RuPay DeV certification context are:
o Transaction approved
o Transaction declined

10/241 Confidential
 uPay Device Validation Test Pla

2 Device Validation Test

2.1 Purpose
The purpose of the RuPay Device Validation (DeV) tests is to ensure that Acquirer's card acceptance
device meets the following criteria:
 Ability to demonstrate that the deployed terminals meet the requirements of both the
Acquirer and NPCI
 Ability to demonstrate the terminals' acceptance of RuPay chip products
 Ability to send and receive authorization requests and responses between a terminal and
the Acquirer host and between the Acquirer host and the network
 Ability to demonstrate the capability of terminals to process chip-based functions including
support of PIN, fallback transactions, card verification methods (as supported by the
terminal), etc.
 Ability of the Acquirer-to-Network interfaces to complete full RuPay chip card transactions
as intended
 Ability of the terminal to manage magnetic stripe technology combined with chip card
technology according to RuPay requirements

For the purpose of executing the RuPay DeV tests, it is assumed that the Acquirer host interface has
already been certified by RuPay CP for magnetic stripe transactions, and RuPay chip transactions .

2.2 Test Environment

The RuPay test environment should be configured to reflect the Acquirer's production environment.

For the purposes of testing, it is assumed that:

 The test environment is configured to use a Point of Sale (PoS) device for purchase transactions
and a PoS/ATM for cash transactions.
 The test tools include an Issuer (and network) Host Simulator (IHS) to simulate a full RuPay
authorization and verify the data received from the test Acquirer. The System Under Test
(SUT), i.e., the Terminal, is connected to the Acquirer and the Acquirer is connected to the
Simulator via a TCP/IP link, using the NPCI RuPay protocol.

To undergo testing, a terminal shall be connected to a testing environment that simulates the acquirer
using a terminal/acquirer specific protocol. In that environment, it should be possible to verify
whether the value of the issuer authentication data and Application Cryptogram are correctly
transmitted to the acquirer.
A high-level example of a DeV test environment is provided in Figure 1.

11/241 Confidential
 uPay Device Validation Test Pla

Figure 1 RuPay DeV test environment

2.3 Test Case Structure

Test Cases are structured as follows:

RUPAY.X.YYY.ZZ - Revision M – Number of sub-cases: N

Where:

X = The category of the test. Set as DEV (for the device validation test).

YYY = The test number in sequence in the category. Starts from 001 and is
incremented by 001 for the successive test cases.
ZZ = The test number extension, used when a test needs to be added between
two existing tests. Starts from 00 and is incremented by 01 in case new
tests are to be added.
M = Version number of the respective test case. Starts from 0 and is
incremented by 1.
N = Number of sub-cases of the test cases. Zero, in case there are no sub-cases
in the related test.

12/241 Confidential
 uPay Device Validation Test Pla

3 Test Cases

3.1 PoS Certification Test Scenarios

3.1.1 RUPAY.DEV.P.001 - Basic RUPAY Card

RUPAY.DEV.P.001
Test No: RUPAY.DEV.P.001 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a basic RuPay card and is able to manage
Online PIN as CVM.

Reference: [REF-2]: Section 6 - REF Chip EMV transaction cycle @ Point of Sale

Applicability This test is applicable only if the terminal supports:

condition:
SDA
Online PIN

Test Card ID: RuPay Card Image 1 /DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.201.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 420300

The following fields shall be:

DE02 = 6074841230000023 /36070500001012

DE04 = 00 00 00 02 01 00

13/241 Confidential
uPay Device Validation Test Pla

DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F30 = 0620 /0201

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
PIN Verified OK shall be printed.
Signature panel shall not be printed
Application name shall be DINERS CLUB / RUPAY/RUPAY DEBIT
Card holder name shall be printed
Transaction type shall be SALE / PURCHASE
Card type shall be RUPAY / RUPAY DEBIT
MID shall be printed

Post Condition: NA

3.1.2 RUPAY.DEV.P.002 - T= 1 Card

RUPAY.DEV.P.002
Test No: RUPAY.DEV.P.002 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a RuPay card that supports T= 1 protocol.

Reference: [REF-2]: Annexure B - Terminal Configuration Recommendations

[REF-5]: Section 9: Transmission Protocols

14/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the Card supports:

condition:
T= 1 protocol

Test Card ID: RuPay Card Image 2 / DCI Card 02

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.202.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000031 / 36070500001020

DE04 = 00 00 00 02 02 00
DE52 is present
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.3 RUPAY.DEV.P.003 - DDA Successful Card

RUPAY.DEV.P.003
Test No: RUPAY.DEV.P.003 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a DDA card.

Reference: [REF-2]: Section 6.4.2.2 - Dynamic Data Authentication

[REF-5]: Section 10.3: Offline Data Authentication

15/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal:

condition:
Supports DDA
Supports Online PIN

Test Card ID: RuPay Card Image 3 / DCI Card 03

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.203.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 4 = 0 - Offline dynamic data authentication did not
fail
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 420300
AIP byte 1, bit 6 =1 - DDA supported

The following fields shall be:

DE02 = 6074841230000049 / 36070500001038

DE04 = 00 00 00 02 03 00
DE52 is present
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

INTERNAL AUTHENTICATE command is present and card returns SW '9000'

In first GENERATE AC command:

16/241 Confidential
uPay Device Validation Test Pla

Terminal requests ARQC

Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.4 RUPAY.DEV.P.004 - CDA Successful Card

RUPAY.DEV.P.004
Test No: RUPAY.DEV.P.004 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a CDA card.

Reference: [REF-2]: Section 6.4.2.3 - Combined DDA / AC Generation - CDA

[REF-5]: Section 10.3: Offline Data Authentication

Applicability This test is applicable only if the terminal supports:

condition:
CDA
Online PIN

Test Card ID: RuPay Card Image 4 / DCI Card 13

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.204.00 for POS / Rs.400.00 for ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 420302
AIP byte 1, bit 1 =1 - CDA supported

The following fields shall be:

DE02 = 6074841230000056 / 36070500001137

DE04 = 00 00 00 02 04 00 / 00 00 00 04 00 00

17/241 Confidential
uPay Device Validation Test Pla

DE22 = 051
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

If the terminal performs CDA in first GENERATE AC command:

In first GENERATE AC command:
Terminal requests ARQC with CDA
Card responds with ARQC (Tag 9F27 = '80') and SDAD in Tag 9F4B
TVR byte 1, bit 8 = 0 - Offline data authentication is performed

In second GENERATE AC command:

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
TVR byte 1, bit 3 = 0 - Combined dynamic data authentication did
not fail

If the terminal performs CDA in 2nd GENERATE AC command:

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
TVR byte 1, bit 8 = 1 - Offline data authentication not performed

In second GENERATE AC command:

Terminal requests TC with CDA
Card responds with TC (Tag 9F27 = '40') and SDAD in Tag 9F4B
TVR byte 1, bit 3 = 0 - Combined dynamic data authentication did
not fail

Post Condition: NA

3.1.5 RUPAY.DEV.P.005 - Domestic Only Card

RUPAY.DEV.P.005
Test No: RUPAY.DEV.P.005 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a domestic only card

18/241 Confidential
uPay Device Validation Test Pla

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 05

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.205.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001053

DE04 = 00 00 00 02 05 00
DE19 = 356
DE22 = 051
DE49 = 356
DE52 is present
DE55 - Tag 9F1A and Tag 5F2A = 0356
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F30 = 0620 / 0201

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.6 RUPAY.DEV.P.006 - PAN Maximum Length Card

RUPAY.DEV.P.006
Test No: RUPAY.DEV.P.006 - Revision 0 - Number of sub cases: 0

19/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal is able to manage a card with a PAN length of 19
digits.

Reference: [REF-2]: Annexure B - Terminal Configuration Recommendations

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 5 / DCI Card 06

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.206.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000000021 / 3607050000000000065

DE04 = 00 00 00 02 06 00
PAN in DE35 = PAN in DE02
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
The following criteria shall be verified in card log:

Tag 5A = '60 74 84 12 30 00 00 00 02 4F' / 36 07 05 00 00 00 00 00 06 5F

PAN in Tag 57 = PAN in Tag 5A
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.7 RUPAY.DEV.P.007 - PAN SN Not Present

RUPAY.DEV.P.007
Test No: RUPAY.DEV.P.007 - Revision 0 - Number of sub cases: 0

20/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal is able to manage a card without PAN Sequence
Number.

Reference: [REF-1]: Section 8.3.18 - Card sequence number

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 6 / DCI Card 07

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.207.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000064 / 36070500001079

DE04 = 00 00 00 02 07 00
DE23 = 000
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F34 is not present

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.8 RUPAY.DEV.P.008 - PAN SN Equal to 15

RUPAY.DEV.P.008
Test No: RUPAY.DEV.P.008 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the PAN SN is correctly transmitted in the Authorization request

21/241 Confidential
uPay Device Validation Test Pla

Reference: [REF-1]: Section 8.3.18 - Card sequence number

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 7 / DCI Card 08

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The entered amount is above the floor limit.
Enter transaction amount as: Rs.208.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000072 / 36070500001087

DE04 = 00 00 00 02 08 00
DE23 = 015
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F34 = '15'

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.9 RUPAY.DEV.P.009 - Extended AID (1)

RUPAY.DEV.P.009
Test No: RUPAY.DEV.P.009 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with an extended AID

Reference: [REF-2]: Section 6.1 - Application Selection

22/241 Confidential
uPay Device Validation Test Pla

[REF-4]: Section 11.3 - Application Selection

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 8 /DCI Card 09

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The terminal displays the names of two applications: RUPAY DEBIT1/ and RUPAY
DEBIT2, select the RUPAY DEBIT1 application.
The terminal displays the names of two applications: DINERS CLUB1/ and DINERS
CLUB 2, select the DINERS CLUB 1 application.
Enter transaction amount as: Rs.209.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

Terminal shall display two mutually supported applications in the following order:

RUPAY DEBIT1 / DINERS CLUB 1

RUPAY DEBIT2 / DINERS CLUB 2

RUPAY DEBIT1 / DINERS CLUB 1 application is selected.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000098 / 36070500001095

DE04 = 00 00 00 02 09 00
DE52 is present
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present
The following criteria shall be verified in card log:

Application Priority Indicator (Tag 87) for the AID ' A0 00 00 05 24 10 10

01' = '01'
Application Priority Indicator (Tag 87) for the AID ' A0 00 00 05 24 10 10
02' = '02'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
01’= 01'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
02’='02'

23/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Charge Slip
In charge slip the application name shall be “RUPAY DEBIT1 / DINERS CLUB 1”.

Post Condition: NA

3.1.10 RUPAY.DEV.P.010 - Extended AID (2)

RUPAY.DEV.P.010
Test No: RUPAY.DEV.P.010 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with an extended AID.

Reference: [REF-2]: Section 6.1 - Application Selection

[REF-2]: Section 6.1.2.2 - Final selection

Applicability This test is applicable to terminals with online processing capability and does not
condition: support Cardholder selection.

Test Card ID: RuPay Card Image 8 / DCI Card 09

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.210.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

Terminal shall select RUPAY DEBIT 1 / DINERS CLUB 1 application.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000098 /36070500001095

DE04 = 00 00 00 02 10 00
DE52 is present
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 is equal to 00

24/241 Confidential
uPay Device Validation Test Pla

DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Application Priority Indicator (Tag 87) for the AID A0 00 00 05 24 10 10

01' = '01'
Application Priority Indicator (Tag 87) for the AID ' A0 00 00 05 24 10 10
02' = '02'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
01’= 01'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
02’='02'
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.11 RUPAY.DEV.P.011 - Blocked Card

RUPAY.DEV.P.011
Test No: RUPAY.DEV.P.011 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal rejects the card, when the card is blocked and the
terminal does not allow processing of the transaction via magnetic stripe.

Reference: [REF-2]: Section 8 - Operating / Functional Requirements

Applicability The terminal is POS and ATM

condition:

Test Card ID: RuPay Card Image 9 / DCI Card 10

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

Pass Criteria: The terminal shall reject the card with a message “Transaction is not allowed,
Card is blocked”.
Terminal does not allow the card to perform a fallback transaction.

The following criteria shall be verified in card log:

The card returns SW '6A81' for SELECT command
The terminal shall display message “CARD BLOCKED”

25/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.1.12 RUPAY.DEV.P.012 - PIN Is Blocked

RUPAY.DEV.P.012
Test No: RUPAY.DEV.P.012 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal correctly processes a card when PIN Try Limit is
exceeded and the card is personalized to proceed with enciphered PIN
verification online when Offline PIN processing fails or is not supported by the
terminal.

Reference: [REF-2]: Section 6.6 - Cardholder Verification

Applicability This test is applicable only if the terminal:

condition:
Is POS

Test Card ID: RuPay Card Image 10 / DCI Card 11

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.212.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

If Offline Plain text PIN is supported:
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 6 = 1 - PIN Try Limit Exceeded

TVR byte 3, bit 8 = 1 - Cardholder Verification was not successful

The following fields shall be:

DE02 = 6074841230000114 / 36070500001111

DE04 = 00 00 00 00 212 00
CVR Byte 5 bit6 to 1 (PIN TRY limit is exceeded) when Offline PIN
processing fails
If Offline Plain text PIN is not supported ('Enciphered PIN verification online '
is selected as CVM option):
In the authorization request,
The following TVR bit shall be set:

26/241 Confidential
uPay Device Validation Test Pla

TVR byte 3, bit 8 = 0 - Cardholder Verification was successful

In the authorization response,

The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

No VERIFY command is sent to the card

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC

Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.13 RUPAY.DEV.P.013 - PIN of 6 digits

RUPAY.DEV.P.013
Test No: RUPAY.DEV.P.013 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a PIN with 6 digits and PIN bypass
is not allowed.

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN

Test Card ID: RuPay Card Image 11 / DCI Card 12

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 123456.
Enter transaction amount as: Rs.213.00 for POS

Pass Criteria: The terminal shall prompt the user to enter the PIN and display a message
“ENTER PIN”.
In the authorization request,

27/241 Confidential
uPay Device Validation Test Pla

The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

The following fields shall be:

DE02 = 6074841230000122 / 36070500001129
DE04 = 00 00 00 02 13 00
DE52 is absent
DE55.9F34 = 41 03 02
DE61.12 should be between 3 and 9 (recommended)
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

The terminal sends a VERIFY command to the card with plaintext PIN
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip
“PIN VERIFIED OK” shall be printed.
Signature panel shall not be printed

Post Condition: NA

3.1.14 RUPAY.DEV.P.014 - Partial PIN entry

RUPAY.DEV.P.014
Test No: RUPAY.DEV.P.014 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal does not allow partial PIN entry.

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN and Online PIN supported

Test Card ID: RuPay Card Image 11 / DCI Card 12

28/241 Confidential
uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The actual PIN value is 123456.
Enter the PIN as 1234.
Enter transaction amount as: Rs.214.00 for POS

Pass Criteria: The terminal shall decline the transaction.

The terminal shall prompt the user to enter the PIN
The terminal shall display the message “INCORRECT PIN”.
The following criteria shall be verified in card log:

Terminal sends a VERIFY command with Plaint text PIN (P2 = '80')
Card responds with SW '63CX' to VERIFY command, where X is from 2, 1, 0
Remove the card from the terminal, after the display of message “INCORRECT
PIN”

Post Condition: NA

3.1.15 RUPAY.DEV.P.015 - Offline Enciphered PIN

RUPAY.DEV.P.015
Test No: RUPAY.DEV.P.015 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage an Offline Enciphered PIN

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline enciphered PIN

Test Card ID: RuPay Card Image 12 / DCI Card 13

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234.
Enter transaction amount as: Rs.215.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

The terminal shall prompt the user to enter the PIN and display a message
“ENTER PIN”.

29/241 Confidential
uPay Device Validation Test Pla

In the authorization request,

The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

The following fields shall be:

DE02 = 6074841230000148 /36070500001137

DE04 = 00 00 00 02 15 00
DE52 is absent
DE55, Tag 9F34 = 44 03 02
CVR byte 2, bit 4 and 5 shall be 1
In the authorization response,
The following fields shall be:

DE39 = 00
DE55, Tag 91 is present

The following criteria shall be verified in card log:

Terminal send the VERIFY command with enciphered PIN (P2 = '88')
Card responds with SW '9000' to VERIFY command with enciphered PIN
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN,
PIN Verified OK shall be printed.
Signature panel shall not be printed

Post Condition: NA

3.1.16 RUPAY.DEV.P.016 - Offline Enciphered PIN – Wrong PIN entry

RUPAY.DEV.P.016
Test No: RUPAY.DEV.P.016 - Revision 0 - Number of sub cases: 0

30/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal does not allow wrong PIN entry

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline enciphered PIN

Test Card ID: RuPay Card Image 12 / DCI card 13

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The actual PIN value is 1234.
Enter the PIN as 5678.
Enter Actual PIN in 2nd attempt
Enter transaction amount as: Rs.216.00 for POS

Pass Criteria: The terminal shall prompt the user to enter the PIN.
The terminal sends a VERIFY command to the card with Enciphered PIN.

The terminal shall display the message “INCORRECT PIN”.

In the authorization request,

The following TVR bit shall be set:

TVR byte 3, bit 8 = 1 - Cardholder Verification is not successful

The following fields shall be:

DE02 = 6074841230000148 /36070500001137

DE04 = 00 00 00 02 16 00
DE52 is absent
DE55, Tag 9F34 = 44 03 01
CVR byte 2, bit 4 = 1
CVR byte 2, bit 5 =0
In the authorization response,
The following fields shall be:

DE39 = 00
DE55, Tag 91 is present (CSU = 031C)

The following criteria shall be verified in card log:

Terminal send the VERIFY command with enciphered PIN (P2 = '88')

31/241 Confidential
uPay Device Validation Test Pla

Card responds with SW '63CX' to VERIFY command with enciphered PIN,

where 'X' is from 2, 1, 0
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.17 RUPAY.DEV.P.017 - Expired Application

RUPAY.DEV.P.017
Test No: RUPAY.DEV.P.017 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage an expired card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 13 / DCI card 14

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The actual PIN value is 1234.
Enter transaction amount as: Rs.217.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

The following TVR bit shall be set:

TVR byte 2, bit 7 = 1 Expired application

In the authorization request,

The following fields shall be:

DE02 = 6074841230000155 / 36070500001145

DE04 = 00 00 00 02 17 00
In the authorization response,
The following fields shall be:

DE39 = 54

32/241 Confidential
uPay Device Validation Test Pla

DE55, Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F24 = '131231' / 081231

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

Terminal shall display “CARD EXPIRED” / “APP EXPIRED”.

Post Condition: NA

3.1.18 RUPAY.DEV.P.018 - Issuer Application Data of 32 Bytes

RUPAY.DEV.P.018
Test No: RUPAY.DEV.P.018 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with an Issuer Application
Data of 32 bytes and correctly populate the Authorization request

Reference: [REF-2]: Section 6.9 - First Card Action Analysis

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 14 / DCI Card 15

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.218.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000163 / 36070500001152

DE04 = 00 00 00 02 18 00
DE55 Tag 9F10 is 32 bytes data
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

33/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
The value of Tag 9F10 = Value of Tag 9F10 in DE55 if authorisation
request message (0100 / 0200)
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.19 RUPAY.DEV.P.019 - Application Blocked

RUPAY.DEV.P.019
Test No: RUPAY.DEV.P.019 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage the card, when the application of
the card is blocked and the terminal does not allow the processing of the
transaction via magnetic stripe

Reference: [REF-2]: Section 6.1 - Application Selection

[REF-2]: Section 6.1.2.2 - Final selection

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 15 / DCI card 016

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.219.00 for POS

Pass Criteria: The terminal shall display message “APPLICATION BLOCKED”

Terminal does not allow the card to perform a fallback transaction.

The following criterion shall be verified in card log:

The card returns SW '6283' for in response of select command for AID A0
00 00 05 24 10 10
The card returns SW '6283' for in response of select command for AID A0
00 00 01 52 30 10

Post Condition: NA

3.1.20 RUPAY.DEV.P.020 - Single Application Blocked in multiple AID card

RUPAY.DEV.P.020

34/241 Confidential
uPay Device Validation Test Pla

Test No: RUPAY.DEV.P.020 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage the card, when one of the
application is blocked in a multiple AID card

Reference: [REF-2]: Section 6.1 - Application Selection

[REF-2]: Section 6.1.2.2 - Final selection

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 33

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.220.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

The terminal shall display the message “RUPAY DEBIT1 BLOCKED, PERFORMED
TRANSACTION WITH RUPAY DEBIT2”.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000379
DE04 = 00 00 00 02 20 00
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

Card responds with SW '6283' for SELECT command with AID = ' A0 00 00 05
24 10 10 01'
Card responds with SW '9000' for SELECT command with AID = ' A0 00 00 05
24 10 10 02'
In first GENERATE AC command:
Terminal requests ARQC

35/241 Confidential
uPay Device Validation Test Pla

Card responds with ARQC (Tag 9F27 = '80')

In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip
In charge slip the application name shall be “RUPAY DEBIT2“

Post Condition: NA

3.1.21 RUPAY.DEV.P.021 - PDOL

RUPAY.DEV.P.021
Test No: RUPAY.DEV.P.021 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with a PDOL

Reference: [REF-2]: Section 6.2 - Initiate Application Processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 16 / DCI card 017

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.221.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In GET PROCESSING OPTIONS command, the terminal sends PDOL data as
requested by the card.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000189 /36070500001178

DE04 = 00 00 00 02 21 00
DE 18 shall be other than zero
DE55.9F1A = 0356
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

36/241 Confidential
uPay Device Validation Test Pla

The following criteria shall be verified in card log:

In Card's response to SELECT command with AID = ' A0 00 00 05 24 10 10'

contain Tag 9F38 = '9F 02 06 9F 03 06 9F 1A 02 5F 2A 02 9A 03 9F 35 01
9F 40 02 9F 15 02'
In Card's response to SELECT command with AID = ‘A0 00 00 01 52 30 10’
contain Tag 9F38 = '9F 02 06 9F 03 06 9F 1A 02 5F 2A 02 9A 03 9F 35 01
9F 40 02'
Terminal shall send GET PROCESSING OPTIONS command with PDOL data
with:
9F15 value shall be other than zero (If RuPay card is used)
9F1A value shall be 0356
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.22 RUPAY.DEV.P.022 - Offline Plaintext PIN

RUPAY.DEV.P.022
Test No: RUPAY.DEV.P.022 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage an Offline Plaintext PIN.

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN

Test Card ID: RuPay Card Image 17 / DCI Card 018

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234.
Enter transaction amount as: Rs.222.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

The terminal shall prompt the user to enter the PIN.
In the authorization request,

37/241 Confidential
uPay Device Validation Test Pla

The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - (Cardholder Verification was successful)

The following fields shall be:

DE02 = 6074841230000197 / 36070500001186
DE04 = 00 00 00 02 22 00
DE55, Tag 9F34 = 41 03 02
Card verification result, Byte 2, bit 5 = 1 (Offline PIN verification
performed)
Card verification result, Byte 2, bit 3 = 1 (Offline PIN verification
Successful)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

Terminal sends a VERIFY command with Plaint text PIN (P2 = '80')
Card responds with SW '9000' to VERIFY command
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.23 RUPAY.DEV.P.023 - Offline Plaintext PIN - Wrong PIN entry

RUPAY.DEV.P.023
Test No: RUPAY.DEV.P.023 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal does not allow wrong PIN entry

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN

Test Card ID: RuPay Card Image 17 / DCI Card 018

38/241 Confidential
uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The actual PIN value is 1234. But enter the PIN as 5678.
Enter transaction amount as: Rs.223.00 for POS

Pass Criteria: The terminal shall decline the transaction.

The terminal shall prompt the user to enter the PIN.

The terminal shall display the message “INCORRECT PIN” in 1st attempt

The following criteria shall be verified in card log:

Terminal sends a VERIFY command with Plaint text PIN (P2 = '80')
Card responds with SW '63CX' to VERIFY command with enciphered PIN,
where 'X' is from 2, 1, 0

Post Condition: NA

3.1.24 RUPAY.DEV.P.024 - Leap Year Expiration Date

RUPAY.DEV.P.024
Test No: RUPAY.DEV.P.024 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal correctly manages the expiration date in a leap year

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 18 / DCI Card 019

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.224.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 2, bit 7 = 0 (Application is not expired)

The following fields shall be:

DE02 = 6074841230000205 / 36070500001194

39/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 02 24 00
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F24 = '20 02 29'

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.25 RUPAY.DEV.P.025 - Script Processing (1) – Single script command

RUPAY.DEV.P.025
Test No: RUPAY.DEV.P.025 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to send one issuer script command received in
the authorization response

Reference: [REF-2]: Section 6.14 - Issuer to Card script processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.225.00 for POS / Rs.2500.00 for ATM

Pass Criteria: The terminal shall perform a complete transaction.

The host sends a PUT DATA command in the authorization response.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001202

40/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 02 25 00
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE55 Tag 72 is present with PUT DATA command

The following criteria shall be verified in card log:

The following TVR bit shall be set:

TVR, byte 5, bit 5 = 0 - (Script processing did not fail after final
Generate AC)
TSI, byte 1, bit 3 = 1 (Script processing was performed)

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Terminal shall send the following Issuer script command after second
GENERATE AC command:
PUT DATA command – 84 DA 00 CB 09 05 MAC(8 Bytes)

Post Condition: NA

3.1.26 RUPAY.DEV.P.026 - Script Processing (2) – Multiple script commands

RUPAY.DEV.P.026
Test No: RUPAY.DEV.P.026 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process several issuer script commands
received in the authorization response

Reference: [REF-2]: Section 6.14 - Issuer to Card script processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 020

Precondition: No specific condition required

41/241 Confidential
uPay Device Validation Test Pla

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.226.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001202

DE04 = 00 00 00 02 26 00
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE55 Tag 72 is present with PUT DATA commands for updating LCOL, LCOA
(new value), and LCOA (as personalised)

The following criteria shall be verified in card log:

TVR, byte 5, bit 5 = 0 - (Script processing did not fail after final
Generate AC)
TSI, byte 1, bit 3 = 1 (Script processing was performed)

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Terminal shall send the following Issuer script commands after second
GENERATE AC command
PUT DATA command – 84 DA 00 CB 09 07 MAC(8 Bytes)
PUT DATA command – 84 DA 00 C8 0E 00 00 00 00 00 00 MAC(8 Bytes)
PUT DATA command – 84 DA 00 C8 0E 00 00 00 01 00 00 MAC(8 Bytes)

Post Condition: NA

42/241 Confidential
uPay Device Validation Test Pla

3.1.27 RUPAY.DEV.P.027 - DDA (ICC Public Key Exponent 2^16+1)

RUPAY.DEV.P.027
Test No: RUPAY.DEV.P.027 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage DDA with an ICC Public Key
exponent of 2^16+1

Reference: [REF-2]: Section 6.4.2.2 - Dynamic Data Authentication

[REF-5], Section 10.3: Offline Data Authentication

Applicability This test is applicable only if the terminal:

condition:
Supports DDA
Supports Online PIN

Test Card ID: RuPay Card Image 21 / DCI Card 026

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.227.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 4 = 0 - Offline dynamic data authentication did not fail

The following fields shall be:

DE02 = 6074841230000239 / 36070500001269

DE04 = 00 00 00 02 27 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Terminal shall send INTERNAL AUTHENTICATE command

Card responds with SDAD and SW '9000'to INTERNAL AUTHENTICATE
command

43/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.28 RUPAY.DEV.P.028 - Offline Enciphered PIN (ICC Public Key Exponent 2^16+1)
RUPAY.DEV.P.028
Test No: RUPAY.DEV.P.028 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage Offline Enciphered PIN with an ICC
Public Key exponent of 2^16+1

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline enciphered PIN

Test Card ID: RuPay Card Image 22 / DCI Card 027

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Enter transaction amount as: Rs.228.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 (Cardholder Verification was successful)

The following fields shall be:

DE02 = 6074841230000247 / 36070500001277

DE04 = 00 00 00 02 28 00
DE52 is absent
In the authorization response,
The following fields shall be:

44/241 Confidential
uPay Device Validation Test Pla

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Terminal shall send GET CHALLENGE command

Terminal shall send VERIFY command with enciphered PIN command (P2 =
'88')
Card responds with SW '9000' for both GET CHALLENGE and VERIFY
commands
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.29 RUPAY.DEV.P.029 - Issuer Authentication Data

RUPAY.DEV.P.029
Test No: RUPAY.DEV.P.029 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage Issuer Authentication Data received
in the Authorization response.

Reference: [REF-2]: Section 6.10.2.1 - Issuer Authentication

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1/ DCI card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.229.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

45/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 02 29 00 In the authorization response,

The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC with the value of IAD = DE55 –Tag 91
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.30 RUPAY.DEV.P.030 - Inconsistent PAN between Chip and Magnetic stripe

RUPAY.DEV.P.030
Test No: RUPAY.DEV.P.030 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal rejects the card, when the value of PAN in Track 2
equivalent data (Tag 57) and PAN in magnetic stripe are different.

Reference: [REF-2] : Section 6.3 Step 3: Read Application Data

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 23 / DCI Card 030

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.230.00 for POS / Rs.3000.00 for ATM

Pass Criteria: The transaction must be declined.

The following criteria shall be verified in card log:

PAN in magnetic stripe is 6074841230001252
Tag 5A = 60 74 84 12 30 00 02 54
Tag 57 = 60 74 84 12 30 00 02 54 D3 31 26 20 45 60 00 00 00 0F
Tag 5A = 36 07 05 00 00 13 01
Tag 57 = 36 07 05 00 00 13 01 D1 71 22 01 12 01 00 05 62 00 00 0F

Post Condition: NA

46/241 Confidential
uPay Device Validation Test Pla

3.1.31 RUPAY.DEV.P.031 - Purchase with Cash Back Transaction

RUPAY.DEV.P.031
Test No: RUPAY.DEV.P.031 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Purchase with Cash back
transaction

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Purchase with Cashback

Test Card ID: RuPay Card Image 1 / DCI Card 031

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter the purchase amount of Rs.210.00 and cash back amount of Rs.100.00.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001319

DE04 = 00 00 00 03 10 00
DE55.9F03 shall be present and is equal to 000000010000
DE55.9F02 shall be present and is equal to 000000031000
DE54 last 12 digits should be equal to DE55.9F03
DE3 (first 2 digits) and DE55 Tag 9C is equal to 09
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC

47/241 Confidential
uPay Device Validation Test Pla

Card responds with TC (Tag 9F27 = '40')

Charge Slip
Transaction type shall be “Sale Cash back”

Post Condition: NA

3.1.32 RUPAY.DEV.P.032 - Unknown AID

RUPAY.DEV.P.032
Test No: RUPAY.DEV.P.032 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage an unknown AID and request to use
magnetic stripe

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 24 / DCI Card 033

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.232.00 for POS / Rs.3200.00 for ATM

Pass Criteria: The terminal shall prompt to swipe the card by displaying a message similar to
“PLEASE SWIPE CARD” or “USE MAGSTRIPE”.
In the authorization request,

The following fields shall be:

DE22= '801' (ICC card “Chip Fallback”)
DE55 is absent

In the authorization response,

The following fields shall be:

DE39 is equal to 00
DE55 is absent
The following criteria shall be verified in card log:

Card responds with SW '6A82' to SELECT command with AID = ' A0 00 00 05

24 10 10'
Card responds with SW '6A82' to SELECT command with AID = ‘A0 00 00 01
52 30 10’

Post Condition: NA

48/241 Confidential
uPay Device Validation Test Pla

3.1.33 RUPAY.DEV.P.033 - ATM Only Card

RUPAY.DEV.P.033
Test No: RUPAY.DEV.P.033 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal rejects an ATM only card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online capable

Test Card ID: RuPay Card Image 25 / DCI Card 035

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.233.00

Pass Criteria: The terminal shall reject the card and display an error message (such as “NOT
ACCEPTED”).
The terminal shall not require swiping the card or displaying a message “PLEASE
SWIPE CARD” or “USE MAGSTRIPE”.

The transaction must be declined.

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests AAC
TVR Byte 2 bit 5 = 1 - Requested services not allowed for the
card product
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.34 RUPAY.DEV.P.034 - Fallback Not Allowed

RUPAY.DEV.P.034
Test No: RUPAY.DEV.P.034 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal will not perform a fallback transaction when the
transaction is completed with a chip and declined by the host

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

49/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal:

condition:
Is POS
Does not support cash

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The entered amount is above the floor limit.
Enter PIN value as 1111
Enter transaction amount as: Rs.234.00 for POS

Pass Criteria: The transaction must be declined by the issuer because of incorrect PIN.
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 3 = 1 - Online PIN entered

The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 34 00
DE52 is present
In the authorization response,
The following shall be:

DE39 = 55
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')

The terminal displays the message: "INCORRECT PIN".

Post decline, the Terminal shall not require swiping the card or displaying the
message “PLEASE SWIPE CARD” or “USE MAGSTRIPE”

50/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.1.35 RUPAY.DEV.P.035 - PAN RuPay (SDA Successful card)

RUPAY.DEV.P.035
Test No: RUPAY.DEV.P.035 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a SDA card with a 16-digit PAN
length

Reference: [REF-2]: Section 6 - REF Chip EMV transaction cycle @ Point of Sale
[REF-2]: Section 6.4.2.1 - Static Data Authentication

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports SDA

Test Card ID: RuPay Card Image 1 / DCI card 045

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.235.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

If the terminal supports SDA,
In the authorization request,
The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication did not
fail

The following fields shall be:

DE02 = 6074841230000023 / 6499990000000452

DE04 = 00 00 00 02 35 00
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

51/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.36 RUPAY.DEV.P.036 - SDA Failed Card

RUPAY.DEV.P.036
Test No: RUPAY.DEV.P.036 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal sets the correct TVR bit in request when SDA is not
correct

Reference: [REF-2]: Section 6.4.2.1 - Static Data Authentication

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports SDA

Test Card ID: RuPay Card Image 27 / DCI Card 040

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.236.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 1 - Offline static data authentication failed

The following fields shall be:

DE02 = 6074841230000304 / 36070500001400

DE04 = 00 00 00 02 36 00
DE52 is present
In the authorization response,

52/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.37 RUPAY.DEV.P.037 - DDA Failed Card

RUPAY.DEV.P.037
Test No: RUPAY.DEV.P.037 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal sets the correct TVR bit in request when DDA is not
correct

Reference: [REF-2]: Section 6.4.2.2 - Dynamic Data Authentication

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports DDA

Test Card ID: RuPay Card Image 28 / DCI Card 041

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.237.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorisation request,
The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 4 = 1 - Offline dynamic data authentication failed

53/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE02 = 6074841230000312 / 36070500001418

DE04 = 00 00 00 02 37 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.38 RUPAY.DEV.P.038 - CDA Failed Card

RUPAY.DEV.P.038
Test No: RUPAY.DEV.P.038 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal sets the correct TVR bit in request when CDA is not
correct

Reference: [REF-2]: Section 6.4.2.3 - Combined DDA / AC Generation - CDA

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports CDA

Test Card ID: RuPay Card Image 29 / DCI Card 042

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.238.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

54/241 Confidential
uPay Device Validation Test Pla

In the authorization request,

The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 3 = 1 - Offline combined dynamic data
authentication is failed

The following fields shall be:

DE02 = 6074841230000338 / 36070500001426

DE04 = 00 00 00 02 38 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.39 RUPAY.DEV.P.039 - Purchase with Cash back Transaction with Purchase Only Card
RUPAY.DEV.P.039
Test No: RUPAY.DEV.P.039 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal rejects a purchase with Cashback transaction When
Cashback is not supported by the card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Purchase with Cashback

Test Card ID: RuPay Card Image 34 / DCI Card 01

Precondition: No specific condition required

55/241 Confidential
uPay Device Validation Test Pla

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Select the Transaction Type as “Purchase with CashBack”
Enter the PIN as 1234
Enter the transaction amount of Rs.239.00 and cash back amount of Rs.11.00

Pass Criteria: The terminal shall reject the transaction displaying “Transaction Not Allowed”.

The transaction must be declined.

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests AAC
TVR Byte 2 bit 5 = 1 - Requested services not allowed for the card
product
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.40 RUPAY.DEV.P.040 - Cash at POS Transaction

RUPAY.DEV.P.040
Test No: RUPAY.DEV.P.040 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process a Cash at POS transaction

Reference: [REF-1]: Section 8.3.2 - DE- 3 Processing Code

[REF-1]: Section 7.2.1.6 - Cash at POS

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports cash

Test Card ID: RuPay Card Image 1 / DCI Card 02

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Select Transaction Type as “Cash”
Enter the PIN as 1234
Enter transaction amount as: Rs.400.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

56/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE02 = 6074841230000023 / 36070500001020
DE04 = 00 00 00 04 00 00
DE4 should contain the cash amount and is same as DE55.9F02
DE55.9F03 = 00 00 00 00 00 00
DE03 (first 2 digits) and 9C must be equal to '01'
DE52 is present.
DE61.2= 2 and DE61.8= 2
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.41 RUPAY.DEV.P.041 - Terminal failure Reversal

RUPAY.DEV.P.041
Test No: RUPAY.DEV.P.041 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to generate a Reversal request when acquirer is
unable to complete a transaction due to the Terminal Failure

Reference: [REF-1] Section: 8.3.26 - DE– 39 Response Code

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.241.00 for POS

57/241 Confidential
uPay Device Validation Test Pla

Pass Criteria: In the authorization request,

The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 41 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

In the Reversal request,

The following fields shall be:

DE02 = PAN in authorization request

DE04 = Amount Authorized in authorization request
DE11, DE37 = STAN and RRN in authorization request
DE39 = 22

In the Reversal response,

The following fields shall be:

DE39 = 00

Post Condition: NA

3.1.42 RUPAY.DEV.P.042 - Reversal with Issuer Script Results

RUPAY.DEV.P.042
Test No: RUPAY.DEV.P.042 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to generate issuer script results and same is
forwarded in Reversal request when transaction is declined at the terminal during
final action analysis

Reference: [REF-2]: Section 8.1.1 - Chip Related Reversal

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

58/241 Confidential
uPay Device Validation Test Pla

Enter the PIN as 1234

Enter transaction amount as: Rs.242.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 42 00
DE52 is present
(The 0110 message must contain an invalid ARPC and a valid script.)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 = “Invalid”
DE55 Tag 72 is present

In the Reversal request,

The following fields shall be:

DE02 = PAN in authorization request

DE04 = Amount Authorized in authorization request
DE11, DE37 = STAN and RRN in authorization request
DE39 = E1
DE55 9F5B is present

In the Reversal response,

The following fields shall be:

DE39 = 00

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

59/241 Confidential
uPay Device Validation Test Pla

3.1.43 RUPAY.DEV.P.043 - Fallback when chip fails

RUPAY.DEV.P.043
Test No: RUPAY.DEV.P.043 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to perform fallback transaction when chip fails.

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.243.00 for POS

Pass Criteria: The terminal does not perform chip transaction.

The terminal prompts to swipe the card.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 43 00
DE22 (POS entry mode) is equal to 801
DE55 is absent
DE61.2 = 2 (PIN Entry)
DE61.7 = 2 (Magnetic Stripe read)
DE61.8 = 2 (PIN)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is absent

Post Condition: NA

3.1.44 RUPAY.DEV.P.044 - Void

RUPAY.DEV.P.044
Test No: RUPAY.DEV.P.044 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to generate void of an approved chip card
transaction

60/241 Confidential
uPay Device Validation Test Pla

Reference: [REF-1] Section: 7.3.1.9 Reversals

[REF-1] Section: 8.3.26 - DE– 39 Response Code

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.244.00 for POS
After the transaction is approved, initiate a void transaction

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 44 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

In the Reversal request,

The following fields shall be:

DE02 = PAN in authorization request

DE04 = Amount Authorized in authorization request
DE11, DE37 = STAN and RRN in authorization request
DE39 = 17

In the Reversal response,

The following fields shall be:

DE39 = 00

The following criteria shall be verified in card log:

61/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command (Authorisation request):

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command (Authorisation request):
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.45 RUPAY.DEV.P.045 - Void Reversal with Issuer Script Results

RUPAY.DEV.P.045
Test No: RUPAY.DEV.P.045 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to generate issuer script results and same is
forwarded in void Reversal request

Reference: [REF-1] Section: 7.3.1.9 Reversals

[REF-1] Section: 8.3.26 - DE– 39 Response Code

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.245.00 for POS
After the transaction is approved, initiate a void transaction.

Pass Criteria: The terminal shall perform a complete transaction.

Sends Issuer Authentication Data along with Issuer Script in the authorization
response.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 /36070500001012

DE04 = 00 00 00 02 45 00
In the authorization response,

62/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 Tag 91 is present
DE55 Tag 72 is present with a PUT DATA command

In the Reversal request,

The following fields shall be:

DE02 = PAN in authorization request

DE04 = Amount Authorized in authorization request
DE11, DE37 = STAN and RRN in authorization request
DE39 = 17
DE55.9F5B is present

The following criteria shall be verified in card log:

In first GENERATE AC command (Authorisation request):

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command (Authorisation request):
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.46 RUPAY.DEV.P.046 - Refund

RUPAY.DEV.P.046
Test No: RUPAY.DEV.P.046 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage refund transaction using chip card

Reference: [REF-2]: Section 8.5 - Refund transaction processing at terminal

Applicability Terminal is POS.

condition:

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.246.00
After the transaction is approved, Initiate a refund using Chip card with amount

63/241 Confidential
uPay Device Validation Test Pla

26.00.

Pass Criteria: The terminal can continue the transaction until completion or terminal abort the
transaction flow.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 46 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command (Authorisation request):

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command (Authorisation request):
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
“Refund successful” message is displayed on the terminal after Refund is
performed

Post Condition: NA

3.1.47 RUPAY.DEV.P.047 - Reversal when AAC/TC not received

RUPAY.DEV.P.047
Test No: RUPAY.DEV.P.047 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to initiate a reversal when AAC/TC is not
received from the card

Reference: [REF-1] Section: 7.3.1.9 Reversals

[REF-1] Section: 8.3.26 - DE– 39 Response Code

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable

Test Card ID: RuPay Card Image 1 / DCI Card 01

64/241 Confidential
uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Initiate a purchase transaction
Enter the PIN as 1234
Enter transaction amount as: Rs.247.00 for POS
When terminal goes online, remove the card

Pass Criteria: The Issuer host approves the transaction and sends Issuer Authentication Data
In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 02 47 00
DE52 is present

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

Terminal does not receive AAC/TC since the card is removed

In the reversal request,
The following fields shall be:

DE39 = E2

Post Condition: NA

3.1.48 RUPAY.DEV.P.048 - Combination CVM – Offline Plaintext PIN and Signature

RUPAY.DEV.P.048
Test No: RUPAY.DEV.P.048 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage both Offline Plaintext PIN and
Signature

Reference: [REF-2]: Section 6.6.2.2.4 - Combined Offline PIN and Signature

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN and Signature

65/241 Confidential
uPay Device Validation Test Pla

Test Card ID: RuPay Card Image 31

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN value as 1234
Enter transaction amount as: Rs.248.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

The terminal shall prompt the user to enter the PIN
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - (Cardholder Verification was successful)

The following fields shall be:

DE02 = 6074841230000353
DE04 = 00 00 00 02 48 00
DE52 is absent
DE61.12 should be between 3 and 9 (recommended).

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Terminal sends a VERIFY command with Plaint text PIN (P2 = '80')
Card responds with SW '9000' to VERIFY command
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC

Card responds with TC (Tag 9F27 = '40') The terminal shall require the cardholder
to sign the receipt displaying a message “SIGNATURE”.

Post Condition: NA

66/241 Confidential
uPay Device Validation Test Pla

3.1.49 RUPAY.DEV.P.049 - Combination CVM – Offline Enciphered PIN and Signature

RUPAY.DEV.P.049
Test No: RUPAY.DEV.P.049 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage both Offline Enciphered PIN and
Signature

Reference: [REF-2]: Section 6.6.2.2.4 - Combined Offline PIN and Signature

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Enciphered PIN and Signature

Test Card ID: RuPay Card Image 32

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234
Enter transaction amount as: Rs.249.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

The terminal shall prompt the user to enter the PIN and display a message “ENTER
PIN”.
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - (Cardholder Verification was successful)

The following fields shall be:

DE02 = 6074841230000361
DE04 = 00 00 00 02 49 00
DE52 is absent
DE61.12 should be between 3 and 9 (recommended)

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Terminal send the VERIFY command with enciphered PIN (P2 = '88')

67/241 Confidential
uPay Device Validation Test Pla

Card responds with SW '9000' to VERIFY command with enciphered PIN

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

The terminal shall require the cardholder to sign the receipt displaying a message
“SIGNATURE”.

Post Condition: NA

3.1.50 RUPAY.DEV.P.050 - No CVM

RUPAY.DEV.P.050
Test No: RUPAY.DEV.P.050 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a transaction with No CVM.

Reference: [REF-2] Section: 6.6.2.2.5 No CVM required

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports No CVM

Test Card ID: RuPay Card Image 26 / DCI Card 039

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.250.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 (Cardholder Verification was successful)

The following fields shall be:

DE02 = 6074841230000296 / 36070500001392

DE04 = 00 00 00 02 50 00
DE52 is absent
DE55 Tag 9F34 = 1F0002/3F0001
In the authorization response,

68/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

TSI byte 1, bit 7 = 1 (Cardholder Verification was performed)

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
PIN Verified OK shall not be printed.
Signature Panel Shall be printed

Post Condition: NA

3.1.51 RUPAY.DEV.P.051 - Response without Issuer authentication data

RUPAY.DEV.P.051
Test No: RUPAY.DEV.P.051 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process the transaction when Issuer
authentication is not required by the card

Reference: [REF-2] Fig 16: and Section 6.11 Step 11: Second Terminal Action Analysis

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable

Test Card ID: RuPay Card Image 19 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234

69/241 Confidential
uPay Device Validation Test Pla

Enter transaction amount as: Rs.251.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000213 / 36070500001202

DE04 = 00 00 00 02 51 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is absent

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC with IAD = '00 00 00 00 00 00 00 00 00 00'
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.52 RUPAY.DEV.P.052 - Purchase with SMS Card

RUPAY.DEV.P.052
Test No: RUPAY.DEV.P.052 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a basic RUPAY SMS card and is also able to
manage Online PIN As CVM

Reference: [REF-2]: Section 6.6.2.2.2 - Offline PIN – Plaintext and Enciphered

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable and Supports Online PIN

Test Card ID: RuPay Card Image 39

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

70/241 Confidential
uPay Device Validation Test Pla

The PIN value is 1234.

Enter transaction amount as: Rs.252.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
If the terminal supports SDA, the following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication did not fail
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder verification was successful
TVR byte 3, bit 3 = 1 - Online PIN entered

The following fields shall be:

DE02 = 6073841230000016
DE04 = 00 00 00 02 52 00
DE52 is present
DE22 (POS entry mode) = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.53 RUPAY.DEV.P.053 - Cash on POS Transaction with SMS card

RUPAY.DEV.P.053
Test No: RUPAY.DEV.P.053 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process a Cash on POS transaction with SMS
Card

71/241 Confidential
uPay Device Validation Test Pla

Reference: [REF-2]: Section 6.5 - Processing Restriction

[REF-1]: Section 7.2.1.6 - Cash at POS

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Cash

Test Card ID: RuPay Card Image 39

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Select the Transaction Type as “Cash”
Enter the PIN value as 1234
Enter transaction amount as: Rs.500.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6073841230000016
DE04 = 00 00 00 05 00 00
Amount in DE4 = amount DE55 Tag9F02
DE55 Tag 9F03 = 00 00 00 00 00 00
DE3 (first 2 digits) and 9C = 01
DE52 is present.
DE61.2= 2 (PIN Entry)
DE61.8= 2 (PIN)

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC

72/241 Confidential
uPay Device Validation Test Pla

Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.54 RUPAY.DEV.P.054 - Purchase Cash Back Transaction with SMS Card

RUPAY.DEV.P.054
Test No: RUPAY.DEV.P.054 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Purchase Cash back
transaction with SMS card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Cashback

Test Card ID: RuPay Card Image 39

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter the transaction amount of Rs.254.00 and cash back amount of Rs.14.00.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6073841230000016
DE04 = 00 00 00 02 54 00
DE55.9F03 = 000000001400
DE55.9F02 = 000000006800
DE54 last 12 digits = DE55.9F03
DE3 (first 2 digits) and 9C = 09

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

73/241 Confidential
uPay Device Validation Test Pla

Terminal requests ARQC

Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.55 RUPAY.DEV.P.055 - Purchase with RuPay International Card

RUPAY.DEV.P.055
Test No: RUPAY.DEV.P.055 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a RuPay International card with Service Code
226 and is also able to manage Online PIN As CVM

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable and Supports Online PIN

Test Card ID: RuPay Card Image 35 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN value is 1234.
Enter transaction amount as: Rs.255.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification was successful
TVR byte 3, bit 3 = 1 - Online PIN entered

The following fields shall be:

DE02 = 6522231230000017/ 36070500001012

DE04 = 00 00 00 02 55 00
DE52 is present

In the authorization response,

74/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F30 = '0226' /0201

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.56 RUPAY.DEV.P.056 - Cash at POS Transaction with RuPay International Card

RUPAY.DEV.P.056
Test No: RUPAY.DEV.P.056 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process a Cash at POS transaction with
RuPay International card with Service Code 226

Reference: [REF-2]: Section 6.5 - Processing Restriction

[REF-1]: Section 7.2.1.6 - Cash at POS

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Cash

Test Card ID: RuPay Card Image 35 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.600.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6522231230000017 / 36070500001012

75/241 Confidential
uPay Device Validation Test Pla

DE3 (first 2 digits) and 9C = 01

DE04 = 00 00 00 06 00 00
Amount in DE4 = amount DE55 Tag9F02
DE55 Tag 9F03 = 00 00 00 00 00 00
DE52 is present.
DE61.2= 2 (PIN Entry)
DE61.8= 2(PIN)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.57 RUPAY.DEV.P.057 - Purchase Cash Back Transaction with International Card

RUPAY.DEV.P.057
Test No: RUPAY.DEV.P.057 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Purchase Cash back
transaction with RuPay International card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Cashback

Test Card ID: RuPay Card Image 35 / DCI Card 31

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter the transaction amount of Rs.257.00 and cash back amount of Rs.17.00.

76/241 Confidential
uPay Device Validation Test Pla

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6522231230000017 / 36070500001319

DE04 = 00 00 00 02 57 00
DE55 Tag 9F03 = 000000001700
DE55Tag 9F02 = 000000007400
DE54 last 12 digits = DE55 Tag 9F03
DE3 (first 2 digits) and 9C = 09
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.58 RUPAY.DEV.P.058 - Purchase fallback Transaction with International Card

RUPAY.DEV.P.058
Test No: RUPAY.DEV.P.058 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Purchase fallback
transaction with RuPay International card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Fallback

Test Card ID: RuPay Card Image 35 / DCI Card 33

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the

77/241 Confidential
uPay Device Validation Test Pla

screen.
Enter the PIN as 1234
Enter the transaction amount of Rs.258.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

The following fields shall be:

DE02 = 6522231230000017 / 36070500001335
DE04 = 00 00 00 02 58 00
DE52 is Present
DE61.7=2 (Magnetic Stripe read)
In the authorization response,

The following fields shall be:

DE39 = 00
The transaction must be approved.

Post Condition: NA

3.1.59 RUPAY.DEV.P.059 - Cash Transaction with International Card

RUPAY.DEV.P.059
Test No: RUPAY.DEV.P.059 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage cash transaction with
RuPay International card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability Terminal is ATM

condition:

Test Card ID: RuPay Card Image 35 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN value is 1234.
Enter the transaction amount of Rs.5900.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

78/241 Confidential
uPay Device Validation Test Pla

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification was successful
TVR byte 3, bit 3 = 1 - Online PIN entered

The following fields shall be:

DE02 = 6522231230000017 / 36070500001012

DE04 = 00 00 00 59 00 00
DE52 is present

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.60 RUPAY.DEV.P.060 - Purchase Only Card

RUPAY.DEV.P.060
Test No: RUPAY.DEV.P.060 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal (ATM) rejects a Purchase only card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
Is ATM

Test Card ID: RuPay Card Image 34

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

79/241 Confidential
uPay Device Validation Test Pla

Enter the PIN value is 1234.

Enter the transaction amount of Rs.6000.00

Pass Criteria: The terminal shall reject the card and display an error message (such as “NOT
ACCEPTED”).
The terminal shall not require swiping the card or displaying a message “PLEASE
SWIPE CARD” or “USE MAGSTRIPE”.
The transaction must be declined.
The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests AAC
TVR Byte 2 bit 5 = 1 - Requested services not allowed for the card
product
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.61 RUPAY.DEV.P.061 - Purchase Transaction with DMS Card with magnetic stripe only
RUPAY.DEV.P.061
Test No: RUPAY.DEV.P.061 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Purchase transaction with
RuPay DMS magnetic stripe card

Reference: [REF-1]: Section 7.3.1.1 - Purchase

Applicability This test is applicable only if the terminal:

condition:
Is POS

Test Card ID: RuPay DMS PIN TEST CARD1

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 0015
Enter the transaction amount of Rs.261.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074840000000015

80/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 02 61 00
DE22 = 901
DE52 = Present
DE61.7 = 2 (Magnetic Stripe read)
DE55 = Absent
In the authorization response,

The following fields shall be:

DE39 = 00
DE55 = Absent

Post Condition: NA

3.1.62 RUPAY.DEV.P.062 - Purchase Transaction with SMS Card with magnetic stripe only
RUPAY.DEV.P.062
Test No: RUPAY.DEV.P.062 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Purchase transaction with
RuPay SMS magnetic stripe card

Reference: [EMV 4.2-3], Section 10.5.1: Offline PIN Processing

Applicability This test is applicable only if the terminal:

condition:
Is POS

Test Card ID: RuPay SMS TEST CARD1

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 0015
Enter the transaction amount of Rs.262.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6073840000000016
DE04 = 00 00 00 02 62 00
DE22 = 901
DE52 = Present
DE61.7=2 (Magnetic Stripe read)

81/241 Confidential
uPay Device Validation Test Pla

RUPAY.DEV.P.062
Test No: RUPAY.DEV.P.062 - Revision 0 - Number of sub cases: 0
DE55 = Absent
In the authorization response,

The following fields shall be:

DE39 = 00
DE55 = Absent

Post Condition: NA

3.1.63 RUPAY.DEV.P.065 - International Card with CA Public Key Index '5D'

RUPAY.DEV.P.065
Test No: RUPAY.DEV.P.065 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a RuPay International card with CA Public Key
Index '5D'

Reference: [REF-2]: Section 6.4.2 Technical Processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay Card Image 40

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN value is 1234.
Enter transaction amount as: Rs.265.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification was successful
TVR byte 3, bit 3 = 1 - Online PIN entered

The following fields shall be:

DE02 = 6522231230000058
DE04 = 00 00 00 02 65 00
DE52 is present

82/241 Confidential
uPay Device Validation Test Pla

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 8F = '5D'
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.64 RUPAY.DEV.P.066 - Response without Issuer authentication data & declined by Issuer
RUPAY.DEV.P.066
Test No: RUPAY.DEV.P.066 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process the transaction when Issuer
authentication is not required by the card

Reference: [REF-2] Fig 16: and Section 6.11 Step 11: Second Terminal Action Analysis

Applicability This test is applicable only if the terminal:

condition:
Is POS
Is Online Capable

Test Card ID: RuPay Card Image 19 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234
Enter transaction amount as: Rs.271.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

83/241 Confidential
uPay Device Validation Test Pla

DE02 = 6074841230000213 / 36070500001202

DE04 = 00 00 00 02 71 00
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 05
DE55 –Tag 91 is absent

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC with IAD = '00 00 00 00 00 00 00 00 00 00'
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.1.65 RUPAY.DEV.P.067 – RuPay Online PIN Card

RUPAY.DEV.P.067
Test No: RUPAY.DEV.P.067 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a basic RuPay card and is able to manage
Online PIN as CVM.

Reference: [REF-2]: Section 6 - REF Chip EMV transaction cycle @ Point of Sale

Applicability This test is applicable only if the terminal supports:

condition:
Online PIN

Test Card ID: RuPay online card with PAN 6074840123456789

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.110.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

84/241 Confidential
uPay Device Validation Test Pla

The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 020000

The following fields shall be:

DE02 = 6074840123456789
DE04 = 00 00 00 01 20 00
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F30 = 0620 /0201

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
PIN Verified OK shall be printed.
Signature panel shall not be printed

85/241 Confidential
uPay Device Validation Test Pla

Application name shall be DINERS CLUB / RUPAY/RUPAY DEBIT

Card holder name shall be printed
Transaction type shall be SALE / PURCHASE
Card type shall be RUPAY / RUPAY DEBIT
MID shall be printed

Post Condition: NA

3.1.66 RUPAY.DEV.P.068 – RuPay Offline PIN Card

RUPAY.DEV.P.068
Test No: RUPAY.DEV.P.068 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a basic RuPay card and is able to manage
Offline PIN as CVM.

Reference: [REF-2]: Section 6 - REF Chip EMV transaction cycle @ Point of Sale

Applicability This test is applicable only if the terminal supports:

condition:
Offline PIN

Test Card ID: RuPay online card with PAN 6074840123456789

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.120.00 for POS

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 410302

86/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE02 = 6074840123456789
DE04 = 00 00 00 01 10 00
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F30 = 0620 /0201

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
PIN Verified OK shall be printed.
Signature panel shall not be printed
Application name shall be DINERS CLUB / RUPAY/RUPAY DEBIT
Card holder name shall be printed
Transaction type shall be SALE / PURCHASE
Card type shall be RUPAY / RUPAY DEBIT
MID shall be printed

Post Condition: NA

3.1.67 RUPAY.DEV.P.069 - Fallback when chip fails

RUPAY.DEV.P.069
Test No: RUPAY.DEV.P.069 - Revision 0 - Number of sub cases: 0

87/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal accepts a basic RuPay card and is able to manage
fallback.

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: RuPay online card with PAN 6074840123456789

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.130

Pass Criteria: The terminal does not perform chip transaction.

The terminal prompts to swipe the card.
In the authorization request,
The following fields shall be:

DE02 = 6074840123456789
DE04 = 00 00 00 01 30 00
DE22 (POS entry mode) is equal to 801
DE55 is absent
DE61.2 = 2 (PIN Entry)
DE61.7 = 2 (Magnetic Stripe read)
DE61.8 = 2 (PIN)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is absent

Post Condition: NA

3.1.68 RUPAY.DEV.P.070 International Card with Online CVM, if transaction is in the

application currency and under X value
RUPAY.DEV.P.070
Test No: RUPAY.DEV.P.070 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a RuPay International card with Service Code
226 and is also able to manage Online PIN As CVM, If Transaction is in the
application currency and is under X value

88/241 Confidential
uPay Device Validation Test Pla

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal:

condition:
 Is POS
 Is Online Capable and supports online PIN

Test Card ID: RuPay Card Image 39 / Use card 3607050123456788

Precondition: AIP indicates Cardholder Verification is supported (AIP byte 1 bit 5 = ‘1’).
Enciphered PIN verification online if transaction is in the application currency and
is under X value (02 06). Transaction Amount is known before CVM Processing.
Transaction amount is less than X value. Transaction Currency Code equals
Application Currency Code.

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.255

Pass Criteria: The terminal does not perform chip transaction.

In the authorization request,
The following fields shall be:

TVR byte 2, bit 8 = 0 - ICC & Terminal have same application

versions
TVR byte 3, bit 3 = 1 - Online PIN entered
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

DE02 = 3607050123456788 / 6073841230000016

DE04 = 00 00 00 02 55 00
DE52 = Present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F30 = 0226

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

89/241 Confidential
uPay Device Validation Test Pla

In second GENERATE AC command:

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.69 RUPAY.DEV.P.071 Basic qSPARC Card

RUPAY.DEV.P.071
Test No: RUPAY.DEV.P.071 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a RuPay qSPARC card

Reference: [REF-2]: Section 6 - REF Chip EMV transaction cycle @ Point of Sale

Applicability This test is applicable only if the terminal:

condition:
 Is POS
 Is Online Capable and supports online PIN

Test Card ID: qSPARC Card with PAN = 6083260000000015

Precondition:

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.201

Pass Criteria: TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 3 = 0 - Offline static data authentication is not
failed
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered

The following fields shall be:

DE02 = 6083260000000015

DE04 = 000000020100
DE52 is present
DE22 = 051
DE 55.9F10 = Present, with 32 bytes of data

In the authorization response,

The following fields shall be:

90/241 Confidential
uPay Device Validation Test Pla

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.70 JCB.DEV.P.001 – T=1 protocol

JCB.DEV.P.001
Test No: JCB.DEV.P.001

Test Objective: To ensure POS terminal can:

Successfully completes J/Smart transaction.
Performs cardholder verification correctly according to CVM list.
Communicates using T=1 protocol.
Processes with payment system proprietary data.
Processes with 1408 bit length CA Public Key.
Processes with 1104 bit or longer ICC Public Key.
Performs Offline Enciphered PIN Verification with 1104 bit or longer ICC Public Key
or PIN Encipherment Public Key.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable when

condition:
Card supports: T= 1 protocol
Terminal Type: 11, 14, 21, 24

Test Card ID: Test Case 02 Test Card

Precondition: No specific condition required

Test Procedure: Perform a transaction with an amount below the terminal floor limit using test
card for Test Case 02.
If the terminal floor limit is zero, process a transaction with the smallest possible
transaction amount.

91/241 Confidential
uPay Device Validation Test Pla

Enter transaction amount as: Rs.099

Pass Criteria: Transaction is approved online for terminal type 11, 14, 21, 24
In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 3569990010082211
DE04 = 00 00 00 00 99 00
DE22 = 051
DE52 = Absent

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
PIN Verified OK shall be printed.
Signature panel shall not be printed
Card holder name shall be printed

92/241 Confidential
uPay Device Validation Test Pla

Transaction type shall be SALE / PURCHASE

MID shall be printed
Transaction Date & Time shall be printed

Post Condition: NA

3.1.71 JCB.DEV.P.002 – Fallback when AID mismatched

JCB.DEV.P.002
Test No: JCB.DEV.P.002

Test Objective: Confirm that Cirrus AID is not set in terminal.

Confirm that display indicates that the magnetic stripe should be read for MS
fallback transaction if AID does not match.

Confirm communicates using T=1 protocol.

Reference: RuPay Chip Terminal Implementation Requirements Guide

Applicability The terminal shall not have Cirrus AID

condition:
This test is applicable to terminals with online processing capability.

Test Card ID: Test Case 03 Test Card

Precondition: No specific condition required

Test Procedure: Perform a transaction using test card for Test Case 03.
Enter transaction amount as 101

Pass Criteria: Terminal shall display “Please swipe magstripe”

Post Condition: NA

3.1.72 JCB.DEV.P.003 – Cardholder verification correctly according to CVM list

JCB.DEV.P.003
Test No: JCB.DEV.P.003

Test Objective: To ensure that POS terminal -

Successfully completes J/Smart transaction.
Performs cardholder verification correctly according to CVM list.
Processes with 1408 bit length CA Public Key.
Processes keys correctly when:
Length of CA Public Key and Issuer Public Key differ by 36 bytes or more.
Length of Issuer Public Key and ICC Public Key differ by 42 bytes or more.
Processes keys correctly when:
Length of CA Public Key and Issuer Public Key differ by 36 bytes or more.
Length of Issuer Public Key and ICC PIN Encipherment Public Key

Reference: RuPay Chip Terminal Implementation Requirements Guide

93/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: Test Case 07 Test Card

Precondition: No specific condition required

Test Procedure: Perform a transaction with an amount below the terminal floor limit using test
card for Test Case 07.

If the terminal floor limit is zero, process a transaction with the smallest possible
transaction amount.

Enter transaction amount as: Rs.102

Pass Criteria: Transaction is approved online for terminal type 11, 14, 21, 24
In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 3569990010082211
DE04 = 00 00 00 01 02 00
DE22 = 051

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

94/241 Confidential
uPay Device Validation Test Pla

3.1.73 JCB.DEV.P.004 – ATR containing proprietary historical bytes

JCB.DEV.P.004
Test No: JCB.DEV.P.004

Test Objective: Confirm successfully complete J/Smart transaction with an ICC with ATR
containing proprietary historical bytes.
Confirm perform cardholder verification correctly according to CVM list.
Confirm processes with 1408 bit length CA Public Key.

Reference: RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: Test Case 08 Test Card

Precondition: No specific condition required

Test Procedure: Perform a transaction with an amount below the terminal floor limit using test
card for Test Case 08.
If the terminal floor limit is zero, process a transaction with the smallest possible
transaction amount.
Enter transaction amount as: Rs.103

Pass Criteria: Transaction is approved online for terminal type 11, 14, 21, 24
In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 =
DE04 = 00 00 00 01 02 00
DE22 = 051

In the authorization response, the following fields shall be:

95/241 Confidential
uPay Device Validation Test Pla

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.74 UPI.DEV.P.001 – Debit card with Multiple Applications

UPI.DEV.P.001
Test No: UPI.DEV.P.001

Test Objective: To validate POS is able to display multiple applications while inserting UPI card
and complete the debit transaction successfully when the Cardholder name(5F20)
contain Chinese Characters.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal supports:

condition:
Cardholder selection of application.
Online PIN transaction.

Test Card ID: FT01

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Debit'.
3. Enter "151.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

96/241 Confidential
uPay Device Validation Test Pla

TVR byte 1, bit 7 = 0 - Offline static data authentication is not

failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6210948000000029
DE04 = 00 00 00 01 51 00
DE22= 051
DE52 = Present

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

1st CVM in Tag 8E = 42 03

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Following criteria shall be verified in terminal:

The terminal displays three applications (UICC Credit, UICC Debit and UICC Quasi
Credit) while conducting the application selection;

Charge Slip:

The receipt contains AID

Approval Code
Total Amount
Masked PAN
TC value shall be printed
PIN Verified OK shall be printed

97/241 Confidential
uPay Device Validation Test Pla

Signature panel shall not be printed

Transaction type shall be SALE / PURCHASE
Transaction Date & Time shall be printed

Post Condition: NA

3.1.75 UPI.DEV.P.002 – Card without PSE

UPI.DEV.P.002
Test No: UPI.DEV.P.002

Test Objective: To validate POS is able to display multiple applications while inserting UPI card
without PSE and complete the credit transaction successfully when the Cardholder
name extended(9F0B) present and contain Chinese characters, and Cardholder
name(5F20) absent

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal supports:

condition:
Cardholder selection of application.
Online PIN transaction.

Test Card ID: FT02

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose ‘UICC Credit’.
3. Enter "152.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal shall perform a complete transaction.

The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

98/241 Confidential
uPay Device Validation Test Pla

IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC

In the authorization request,

DE02 = 6210948000000011
DE04 = 00 00 00 01 52 00
DE22= 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 9F08 = Present

Tag 5F20 = Absent
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Following criteria shall be verified in terminal:

The terminal displays three applications (UICC Credit, UICC Debit and UICC Quasi
Credit) while conducting the application selection;

Charge Slip

The receipt contains AID

Transaction Date and Time
Transaction Certificate shall be printed
Approval Code
Total Amount
Masked PAN
PIN Verified OK shall be printed
Signature panel shall printed
Transaction type shall be SALE / PURCHASE

99/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.1.76 UPI.DEV.P.003 – Issuer script processing and cardholder name absent in chip
UPI.DEV.P.003
Test No: UPI.DEV.P.003

Test Objective: To validate POS is able to perform the issuer script correctly and Track2
Equivalent Data (Tag57)on the chip is correctly sent to Issuer and the cardholder
name(5F20,9F0b) are absent

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT03

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Debit'.
3. Enter "153.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:

The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed.

TVR byte 1, bit 7 = 0 - Offline static data authentication is not failed.
TVR byte 2, bit 8 = 0 - ICC and terminal have same application versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful.
TVR byte 3, bit 3 = 1 - Online PIN is entered
TVR byte 5, bit 5 = 0 - Scripting processing not failed after final GEN AC
IAD byte 5, bit 5 = 0 & bit 6 = 1 ARQC

DE02 = 6210948000000037
DE04 = 00 00 00 01 53 00
DE22 = 051
DE35= Present
DE52- Present

100/241 Confidential
uPay Device Validation Test Pla

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE55 Tag 72 is present with PUT DATA command

The following criteria shall be verified in card log:

DE35 = Tag57
Tag 5F20 = Absent
Tab 9F0B = Absent
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Terminal shall send the following Issuer script command after second GENERATE
AC command:

Application Unblock command – 84 18 00 00 04

Post Condition: NA

3.1.77 UPI.DEV.P.004 – To validate 1st digit of service code

UPI.DEV.P.004
Test No: UPI.DEV.P.004

Test Objective: To validate POS is able to complete the credit transaction correctly and terminal
will only check the first digit of the service code. Terminal support the track 1
data contain Chinese characters

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT04

Precondition: No specific condition required

Test Procedure: 1. Please swipe a card first and the terminal shall prompt to use a chip card.
2. Please insert a card and select purchase function.

101/241 Confidential
uPay Device Validation Test Pla

3. Choose 'UICC Credit'.

4. Enter "154.00" as transaction amount.
5. Enter a correct online PIN as 1234 if required.
6. Processing completion

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 = 1 ARQC

The following fields shall be:

DE02 = 6210948000000045
DE04 = 00 00 00 01 54 00
DE22 = 051
DE35 = Present
In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.78 UPI.DEV.P.005 – Quasi credit card with Chinese character in AID

UPI.DEV.P.005

102/241 Confidential
uPay Device Validation Test Pla

Test No: UPI.DEV.P.005

Test Objective: To validate POS is able to complete the quasi credit transaction correctly when
the application Label(Tag:50) and Application Preferred Name(Tag:9F12) contain
Chinese Characters

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT05

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose “UICC Credit”.
3. Enter "155.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 7 = 0 - Offline static data authentication is not
failed
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC
DE02 = 6210948000000052
DE04 = 00 00 00 01 54 00
DE22 = 051
DE35 = Present

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

103/241 Confidential
uPay Device Validation Test Pla

In second GENERATE AC command:

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

The terminal shall perform a complete transaction:

The terminal displays three applications (UICC Credit, UICC Debit and UICC
Quasi Credit) while conducting the application selection.

Post Condition: NA

3.1.79 UPI.DEV.P.006 – SDA successful card

UPI.DEV.P.006
Test No: UPI.DEV.P.006

Test Objective: To validate POS is able to complete the credit transaction correctly when only SDA
is supported on the chip.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal supports:

condition:
SDA
Online PIN

Test Card ID: FT06

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "156.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set:

TVR byte 1, bit 2 = 1 -SDA selected

TVR byte 1, bit 7 = 0 - Offline static data authentication is not failed
AIP byte 1, bit 7 = 1 – SDA supported
DE02 = 6210948000000060

104/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 01 56 00

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.80 UPI.DEV.P.007 – SDA failed card

UPI.DEV.P.007
Test No: UPI.DEV.P.007

Test Objective: To validate POS is able to behave correctly during the credit transaction when SDA
is failed.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports SDA

Test Card ID: FT07

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose ‘UICC Credit’.
3. Enter "157.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,

105/241 Confidential
uPay Device Validation Test Pla

The following TVR bit shall be set:

TVR byte 1, bit 7 = 1 - Offline static data authentication failed

TVR byte 1, bit 2 = 1 – SDA selected card
AIP byte 1, bit 7 = 1 – SDA supported

The following fields shall be:

DE02 = 6210948000000078
DE04 = 00 00 00 01 57 00

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.81 UPI.DEV.P.008 - DDA Successful Card

UPI.DEV.P.008
Test No: UPI.DEV.P.008

Test Objective: To validate POS is able to complete the credit transaction correctly when only DDA
is supported on the chip and upload the card sequence number correctly.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Supports DDA
Supports Online PIN

Test Card ID: FT08

Precondition: No specific condition required

106/241 Confidential
uPay Device Validation Test Pla

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose ‘UICC Credit’.
3. Enter "158.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 4 = 0 - Offline dynamic data authentication is not failed
AIP byte 1, bit 6 = 1 - DDA supported

The following fields shall be:

DE02 = 6210948000000086
DE04 = 00 00 00 01 58 00
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

INTERNAL AUTHENTICATE command is present and card returns SW '9000'

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC

Card responds with TC (Tag 9F27 = '40')

Terminal shall send the following Issuer script command after second GENERATE
AC command:

Application Unblock command – 84 18 00 00 04

Post Condition: NA

107/241 Confidential
uPay Device Validation Test Pla

3.1.82 UPI.DEV.P.009 - DDA Failed Card

UPI.DEV.P.009
Test No: UPI.DEV.P.009

Test Objective: To validate POS is able to behave correctly during the credit transaction when DDA
is failed.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports DDA

Test Card ID: FT09

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "159.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorisation request,
The following TVR bit shall be set:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 4 = 1 - Offline dynamic data authentication is failed
AIP byte 1, bit 6 = 1 - DDA supported

The following fields shall be:

DE02 = 6210948000000094
DE04 = 00 00 00 01 59 00

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

108/241 Confidential
uPay Device Validation Test Pla

Terminal requests ARQC

Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.83 UPI.DEV.P.010 - CDA Successful Card

UPI.DEV.P.010
Test No: UPI.DEV.P.010

Test Objective: To validate POS is able to complete the credit transaction correctly when only CDA
is supported on the chip.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal supports:

condition:
CDA
Online PIN

Test Card ID: FT10

Precondition: If PoS supports CDA model 1, 2 and 4. Refer to Pass Criteria.

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "161.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 3 = 0 - Offline combined data authentication is not failed
TVR byte 3, bit 3 = 1 - Online PIN is entered
AIP byte 1, bit 1 = 1 - CDA supported

The following fields shall be:

DE02 = 6210948000000102

109/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 01 61 00
DE22 = 051
DE52 = Present

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

1st CVM in Tag 8E = 42 03

If POS support the "Offline Data Authentication" function and support CDA
model 1,2,4

If the terminal performs CDA in first GENERATE AC command:

In first GENERATE AC command:
Terminal requests ARQC with CDA
Card responds with ARQC (Tag 9F27 = '80') and SDAD in Tag 9F4B
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
If the terminal performs CDA in 2nd GENERATE AC command:
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC with CDA
Card responds with TC (Tag 9F27 = '40') and SDAD in Tag 9F4B

If POS doesn't support the "Offline Data Authentication" function or only

support CDA model 3:
1).Please provide the "Terminal EMV Level 2 Approve letter"
2). Please skip this test case.

Post Condition: NA

3.1.84 UPI.DEV.P.011 - CDA Failed Card

UPI.DEV.P.011
Test No: UPI.DEV.P.011

110/241 Confidential
uPay Device Validation Test Pla

Test Objective: To validate POS is able to behave correctly during the credit transaction when CDA
is failed.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports CDA

Test Card ID: FT11

Precondition: If PoS supports CDA model 1, 2 and 4. Refer to Pass Criteria.

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "162.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,

The following TVR bit shall be set as:

TVR byte 1, bit 8 = 0 - Offline data authentication is performed

TVR byte 1, bit 3 = 1 - Offline combined data authentication is failed
AIP byte 1, bit 1 = 1 - CDA supported

The following fields shall be:

DE02 = 6210948000000110
DE04 = 00 00 00 01 62 00
DE22 = 051

In the authorization response, the following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC

111/241 Confidential
uPay Device Validation Test Pla

Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.85 UPI.DEV.P.012 - No Offline CAM supported

UPI.DEV.P.012
Test No: UPI.DEV.P.012

Test Objective: To validate POS is able to complete the credit transaction when no offline CAM
(SDA/DDA/CDA) is supported on the chip.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability Applicable for ODA not supported card

condition:

Test Card ID: FT12

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "163.00" as transaction amount.
4. Enter a correct online PIN as 1234
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 1 - Offline data authentication not performed

TVR byte 3, bit 3 = 1 - Online PIN is entered

The following fields shall be:

DE02 = 6210948000000128
DE04 = 00 00 00 01 63 00
DE22 = 051
DE52 = Present

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

112/241 Confidential
uPay Device Validation Test Pla

1st CVM in Tag 8E = 42 03

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.86 UPI.DEV.P.013 - Blocked Card

UPI.DEV.P.013
Test No: UPI.DEV.P.013

Test Objective: To validate POS is able to behave correctly during the credit transaction when the
card is blocked.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability The terminal is POS

condition:

Test Card ID: FT13

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. The message is shown on the POS then the terminal stops the transaction.

Pass Criteria: The terminal shall reject the card with a message “Transaction is not allowed,
Card is blocked”.
Terminal does not allow the card to perform a fallback transaction.

The following criteria shall be verified in card log:

The card returns SW '6A81' for SELECT command
The terminal shall display message “CARD BLOCKED”

Post Condition: NA

3.1.87 UPI.DEV.P.014 - Application Blocked

UPI.DEV.P.014
Test No: UPI.DEV.P.014

Test Objective: To validate POS is able to behave correctly during the credit transaction when
UnionPay application is blocked.

113/241 Confidential
uPay Device Validation Test Pla

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT14

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. The message is shown on the POS then the terminal stops the transaction.

Pass Criteria: The terminal shall display message “APPLICATION BLOCKED”

Terminal does not allow the card to perform a fallback transaction.

The following criterion shall be verified in card log:

The card returns SW '6283' for in response of select command for AID
A000000333010102

Post Condition: NA

3.1.88 UPI.DEV.P.015 - Expired Application

UPI.DEV.P.015
Test No: UPI.DEV.P.015

Test Objective: To ensure that the terminal is able to manage an expired card

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT15

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "165.00" as transaction amount.
4. Enter a correct online PIN as '1234'
5. Processing completion.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 2, bit 7 = 1 Expired application

114/241 Confidential
uPay Device Validation Test Pla

DE02 = 6210948000000000152
DE04 = 00 00 00 02 17 00
DE52 = Present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55, Tag 91 is present

The following criteria shall be verified in card log:

1st CVM in Tag 8E = 42 03

Tag 5F24 = 101031
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

Terminal shall display “CARD EXPIRED” / “APP EXPIRED”.

Post Condition: NA

3.1.89 UPI.DEV.P.016 – Application is not effective

UPI.DEV.P.016
Test No: UPI.DEV.P.016

Test Objective: To validate POS is able to behave correctly during the credit transaction when
UnionPay application is not effective.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT16

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "166.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,

115/241 Confidential
uPay Device Validation Test Pla

The following TVR bit shall be set:

TVR byte 2, bit 6 = 1 - Application not yet effective

The following fields shall be:

DE02 = 6210948000000169
DE04 = 00 00 00 016600

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with TC (Tag 9F27 = '00')

Post Condition: NA

3.1.90 UPI.DEV.P.017 – Different application version number

UPI.DEV.P.017
Test No: UPI.DEV.P.017

Test Objective: To validate POS is able to behave correctly during the credit transaction
when the application version number is different.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT17

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "167.00" as transaction amount.
4. Enter a correct online PIN as 1234
5. Processing completion

Pass Criteria: The terminal goes online to complete the transaction;

The following TVR bit shall be set:

116/241 Confidential
uPay Device Validation Test Pla

TVR byte 2, bit 8 = 1 - Card and terminal have different application

versions

In the authorization request, the following fields shall be:

DE02 = 6210948000000177
DE04 = 00 00 00 00 167 00
DE22 = 051
DE52 = Present

The following criteria shall be verified in card log:

1st CVM in Tag 8E = 42 03

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with TC (Tag 9F27 = '00')

Post Condition: NA

3.1.91 UPI.DEV.P.018 - Unknown AID

UPI.DEV.P.018
Test No: UPI.DEV.P.018

Test Objective: To ensure that the terminal is able to manage an unknown AID and request to use
magnetic stripe

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT18

Precondition: No specific condition required

Test Procedure: Please insert a card and select purchase function.

2. Swipe a card after the message is displayed.

3. Enter "191" as transaction amount.

4. Enter a correct online PIN as '1234'.

5. Processing completion.
Pass Criteria: The terminal shall prompt to swipe the card by displaying a message similar to

117/241 Confidential
uPay Device Validation Test Pla

“PLEASE SWIPE CARD” or “USE MAGSTRIPE”.

In the authorization request, the following fields shall be:

DE02 = 6210948000000185
DE04 = 00 00 00 01 91 00
DE22= '801' (ICC card “Chip Fallback”)
DE23=absent
DE55 is absent
DE52 = present
DE61.SF7 = 2

In the authorization response,

The following fields shall be:

DE39 is equal to 00
DE55 is absent

Post Condition: NA

3.1.92 UPI.DEV.P.019 – Fallback when application selection failed

UPI.DEV.P.019
Test No: UPI.DEV.P.019

Test Objective: To validate POS is able to conduct fallback transaction correctly when application
selection is failed.
Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT19

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Swipe a card after the message is displayed.
3. Enter "169" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion.

Pass Criteria: Fallback is supported

Need to verify in Terminal:
The terminal shall prompt to swipe the card by displaying a message similar to
“PLEASE SWIPE CARD” or “USE MAGSTRIPE”.

118/241 Confidential
uPay Device Validation Test Pla

In the authorization request,

The following fields shall be:

DE02 = 6210848000000193
DE04 = 00 00 00 00 169 00
DE22 = 801
DE23 = Absent
DE52 = Present
DE55 = Absent
DE61.SF7 = 2

In the authorization response,

The following fields shall be:

DE39 is equal to 00
DE55 is absent

Post Condition: NA

3.1.93 UPI.DEV.P.020 - T= 1 Card

UPI.DEV.P.020
Test No: UPI.DEV.P.020

Test Objective: To validate POS is able to complete the credit transaction correctly when the chip
is T=1 card.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements

Applicability This test is applicable only if the Card supports:

condition:
T= 1 protocol

Test Card ID: FT20

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "193.00" as transaction amount.
4. Processing completion

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6210948000000201
DE04 = 00 00 00 01 93 00

119/241 Confidential
uPay Device Validation Test Pla

DE22 = 051
In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.94 UPI.DEV.P.021 – PIN bypass

UPI.DEV.P.021
Test No: UPI.DEV.P.021

Test Objective: To validate POS is able to behave correctly during the credit transaction
when PIN Bypass is performed.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability
condition:

Test Card ID: FT10

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Credit'.
3. Enter "170.00" as transaction amount.
4. Enter PIN Bypass if supported. If YES, Bypass PIN is successfully processed.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

Terminal shall prompts to enter online PIN.
The transaction is approved by issuer
Bypass PIN is successfully processed.
The following TVR bit shall be set as:

TVR byte 3, bit 4 = 1 - Pin Entry required, PIN pas present but PIN was not

120/241 Confidential
uPay Device Validation Test Pla

entered

In the authorization request,

DE02 = 6210948000000102
DE04 = 00 00 00 01 70 00
DE22 = 051
DE52 = Absent
In the authorization response, the following fields shall be:
DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip:
Signature panel shall printed

Post Condition: NA

3.1.95 UPI.DEV.P.022 – Dual asymmetric algorithm (RSA and SM) - Normal transaction
UPI.DEV.P.022
Test No: UPI.DEV.P.022

Test Objective: To validate POS is able to complete the Debit transaction correctly when the Union
pay IC card support dual asymmetric algorithm (RSA and SM)

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability
condition:

Test Card ID: FT21

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select purchase function.

2. Choose 'UICC Debit'.
3. Enter "171.00" as transaction amount.

121/241 Confidential
uPay Device Validation Test Pla

4. Enter a correct online PIN as 1234.

5. Processing to completion.

Pass Criteria: The terminal goes online to complete the transaction;

The following TVR bit shall be set as:

TVR byte 3, bit 3 – 1 - Online PIN entered

In the authorization request,

DE02 = 6210948000000219
DE04 = 00 00 00 01 71 00
DE22 = 051
DE52 = Present
In the authorization response, the following fields shall be:
DE39 = 00
DE55–Tag 91 is present

The following criteria shall be verified in card log:

1st CVM in Tag 8E = 02 03

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.96 UPI.DEV.P.023 - PIN of 12 digits

UPI.DEV.P.023
Test No: UPI.DEV.P.023

Test Objective: To Validate POS is able to perform correctly Offline Plaintext PIN with 12 digits.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN

Test Card ID: FT22

122/241 Confidential
uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: 1. Please insert a Card and select purchase function.

2. Choose UICC Credit
3. Enter 197.00‟as transaction amount.
4. Enter a correct offline PIN as '123456789012' if required.
5.Processing Completion

Pass Criteria: The terminal shall prompt the user to enter the PIN and display a message
“ENTER PIN”.
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

TVR byte 3, bit 6 = 0 - PIN Try limit not exceeded
The following fields shall be:
DE02 = 6210948000000227
DE04 = 00 00 00 01 97 00
DE61.12 should be between 9 (recommended)
In the authorization response, the following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.97 UPI.DEV.P.024 - PIN of 4 digits

UPI.DEV.P.024
Test No: UPI.DEV.P.024

Test Objective: To Validate POS is able to perform correctly Offline Plaintext PIN with 4 digits.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

123/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports Offline Plaintext PIN

Test Card ID: FT23

Precondition: No specific condition required

Test Procedure: 1. Please insert a Card and select purchase function.

2. Choose UICC Credit
3. Enter 199.00 as transaction amount.
4. Enter a correct offline PIN as '1234' if required.
5.Processing Completion

Pass Criteria: The terminal shall prompt the user to enter the PIN and display a message
“ENTER PIN”.
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

TVR byte 3, bit 6 = 0 - PIN Try limit not exceeded
The following fields shall be:
DE02 = 6210948000000235
DE04 = 00 00 00 01 99 00
DE22 = 051
In the authorization response, the following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.98 UPI.DEV.P.025 - PIN Unblock

UPI.DEV.P.025

124/241 Confidential
uPay Device Validation Test Pla

Test No: UPI.DEV.P.025

Test Objective: To Validate POS is able to behave correctly while entering incorrect PIN 3 times
and PIN Unblock/PIN Change script command is sent during the credit transaction.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT23

Precondition: No specific condition required

Test Procedure: 1. Please insert a Card and select purchase function.

2. Choose “UICC Credit”.
3. Enter “177.00” as transaction amount.
4. Enter incorrect offline PIN as '8888' 3 times if terminal required.
5.Processing Completion

Pass Criteria: The Terminal goes online to complete the transaction.

The following TVR bit shall be set:

TVR byte 3, bit 8 = 1 -Cardholder Verification was not successful

TVR byte 3, bit 6 = 1 –PIN Try Limit Exceeded
In the authorization response, the following fields shall be:
DE02 = 6210948000000235
DE04 = 00 00 00 01 77 00
DE22 = 051
DE52 = Absent

In the authorization response, the following fields shall be:

DE39 = 00
DE55, Tag 91 is present

The Response Message should include the issuer script.

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In 2nd GENERATE AC Command
TVR byte 5, bit 5 = 0 –Script processing is not failed after second GEN
AC

125/241 Confidential
uPay Device Validation Test Pla

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Terminal shall send the following Issuer script command after second GENERATE
AC command:
PIN UNBLOCK - 84 24 00 00 04

The following criteria shall be verified in terminal:

After two consecutive wrong PIN entries, the terminal displays prompts like
"one last attempt allowed to enter the PIN". And after inputting the wrong
PIN one more time, the transaction goes online.

Post Condition: NA

3.1.99 UPI.DEV.P.026 - PIN Unblock/PIN Change script

UPI.DEV.P.026
Test No: UPI.DEV.P.026

Test Objective: To Validate POS is able to behave correctly when PIN Unblock/PIN Change script
command have been successfully performed during last credit transaction.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: FT23

Precondition: Before performing this test case, UPI.DEV.P.025 must be completed.

Test Procedure: 1. Please insert a Card and select purchase function.

2. Choose “UICC Credit”.
3. Enter “178.00” as transaction amount.
4. Enter a correct offline PIN as '1234'.
5. Processing Completion.

Pass Criteria: If the POS support the Issuer script handle

The Terminal goes online to complete the transaction.
In authorization request :
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 -Cardholder Verification was successful

TVR byte 3, bit 6 = 0 –PIN Try Limit not Exceeded
, the following fields shall be:

126/241 Confidential
uPay Device Validation Test Pla

DE02 = 6210948000000235
DE04 = 00 00 00 01 78 00
DE22 = 051

In the authorization response, the following fields shall be:

DE39 = 00
DE55, Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
TVR byte 5, bit 5 = 0 –Script processing is not failed after second GEN
AC
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Terminal shall send the following Issuer script command after second GENERATE
AC command:
PIN CHANGE/UNBLOCK - 84 24 00 00 04

Post Condition: NA

3.1.100 UPI.DEV.P.027 – CVM Absent

UPI.DEV.P.027

Test No: UPI.DEV.P.027

Test Objective: To validate POS is able to behave correctly when the CVM list(Tag 8E) is absent

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports No CVM

Test Card ID: FT24

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Purchase function.

2. Choose 'UICC Credit'.
3. Enter "179.00" as transaction amount.

127/241 Confidential
uPay Device Validation Test Pla

4 Processing to completion.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 1, bit 6 = 1 -ICC Data missing

The following fields shall be:

DE02 = 6210948000000243 / 6210948000010242

DE04 = 00 00 00 01 79 00
DE52 is absent
In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.101 UPI.DEV.P.028 – Unknown CVM

UPI.DEV.P.028

Test No: UPI.DEV.P.028

Test Objective: To validate POS is able to behave correctly when the CVM list(Tag 8E) is unknown

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal:

condition:
Is POS
Supports No CVM

Test Card ID: FT24

Precondition: No specific condition required

128/241 Confidential
uPay Device Validation Test Pla

Test Procedure: 1. Please insert a card and select Purchase function.

2. Choose 'UICC Debit'.
3. Enter "180.00" as transaction amount.
4. Processing to completion.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 7 = 1 –Unrecognised CVM

The following fields shall be:

DE02 = 6210948000000243 / 6210948000010242

DE04 = 00 00 00 01 80 00
DE52 is absent
In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.1.102 UPI.DEV.P.029 – AUC exceeds the region and service type restrictions
UPI.DEV.P.029

Test No: UPI.DEV.P.029

Test Objective: To validate POS is able to behave correctly when the Application Usage Control
(AUC Tag: 9F07) exceeds the region and service type restrictions.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability
condition:

Test Card ID: FT25

129/241 Confidential
 uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Purchase function.

2. Choose 'UICC Credit'.
3. Enter "182.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing to completion

Pass Criteria: The terminal shall reject the transaction displaying “Transaction Not Allowed”.

The transaction must be declined.

The following criteria shall be verified in card log:

TVR byte 2, bit 5 = 1

Post Condition: NA

3.2 ATM and Micro ATM Certification Test Scenarios

3.2.1 RUPAY.DEV.A.001 - Cash Withdrawal

RUPAY.DEV.A.001
Test No: RUPAY.DEV.A.001 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a basic RuPay card and is able to manage
Online PIN as CVM for Cash Withdrawal.

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 1 /DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.3000.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

130/241 Confidential
uPay Device Validation Test Pla

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 30 00 00
DE52 is present
DE22 = 051
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

CVM results = 420100In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.2 RUPAY.DEV.A.002 – T = 1 Card

RUPAY.DEV.A.002
Test No: RUPAY.DEV.A.002 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a RuPay CARD that supports T= 1 protocol.

Reference: [REF-2]: Annexure B - Terminal Configuration Recommendations

[REF-5]: Section 9: Transmission Protocols

Applicability This test is applicable only if the Card supports:

condition:
T= 1 protocol

131/241 Confidential
uPay Device Validation Test Pla

And the terminal:

ATM
Micro ATM

Test Card ID: RuPay Card Image 2 / DCI Card 02

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.3100.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000031 / 36070500001020

DE04 = 00 00 00 31 00 00
DE52 is present
DE22 = 051
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.3 RUPAY.DEV.A.005 - PAN Maximum Length Card

RUPAY.DEV.A.005
Test No: RUPAY.DEV.A.005 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with a PAN length of 19
digits.

Reference: [REF-2]: Annexure B - Terminal Configuration Recommendations

132/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 5 / DCI Card 06

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.3500.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000000021 / 3607050000000000060

DE04 = 00 00 00 35 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
PAN in DE35 = PAN in DE02
DE35 = Tag 57 (without filler F)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
The following criteria shall be verified in card log:

Tag 5A = '60 74 84 12 30 00 00 00 02 1F' / 36 07 05 00 00 00 00 00 06 5F

PAN in Tag 57 = PAN in Tag 5A = 60 74 84 12 30 00 00 00 02 1F
Tag 57 = 60 74 84 12 30 00 00 00 02 1D 26 12 62 03 67 00 00 00 0F
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.4 RUPAY.DEV.A.006 - PAN SN Not Present

RUPAY.DEV.A.006
Test No: RUPAY.DEV.A.006 - Revision 0 - Number of sub cases: 0

133/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal is able to manage a card without PAN Sequence
Number.

Reference: [REF-1]: Section 8.3.18 - Card sequence number

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 6 / DCI Card 07

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.3600.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000064 / 36070500001079

DE04 = 00 00 00 36 00 00
DE23 = 000
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F34 is not present

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.5 RUPAY.DEV.A.007 - PAN SN Equal to 15

RUPAY.DEV.A.007

134/241 Confidential
uPay Device Validation Test Pla

Test No: RUPAY.DEV.A.007 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the PAN SN is correctly transmitted in the Authorization request

Reference: [REF-1]: Section 8.3.18 - Card sequence number

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 7 / DCI Card 08

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.3700.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000072 / 36070500001087

DE04 = 00 00 00 37 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE23 = 015
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F34 = '15'

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.6 RUPAY.DEV.A.008 - Extended AID (1)

RUPAY.DEV.A.008

135/241 Confidential
uPay Device Validation Test Pla

Test No: RUPAY.DEV.A.008 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with an extended AID

Reference: [REF-2]: Section 6.1 - Application Selection

[REF-4]: Section 11.3 - Application Selection

Applicability
condition: This test case is applicable if Terminal supports Cardholder selection
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 8 /DCI Card 09

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The terminal displays the names of two applications: RuPay Debit 1and RuPay
Debit 2, select the RuPay Debit 1 application.
The terminal displays the names of two applications: DINERS CLUB1 and DINERS
CLUB 2, select the DINERS CLUB 1 application.
Enter transaction amount as: Rs.3800.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

Terminal shall display two mutually supported applications in the following order:

RuPay Debit 1/ DINERS CLUB 1

RuPay Debit 2/ DINERS CLUB 2

RuPay Debit 1/ DINERS CLUB 1 application is selected.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000098 / 36070500001095

DE04 = 00 00 00 38 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

136/241 Confidential
uPay Device Validation Test Pla

The following criteria shall be verified in card log:

Application Priority Indicator (Tag 87) for the AID ' A0 00 00 05 24 10 10

01' = '01'
Application Priority Indicator (Tag 87) for the AID ' 'A0 00 00 05 24 10 10
02' = '02'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
01’= 01'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
02’='02'
In Final Selection “RuPay Debit 1” shall be selected
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.7 RUPAY.DEV.A.009 - Extended AID (2)

RUPAY.DEV.A.009
Test No: RUPAY.DEV.A.009 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with an extended AID.

Reference: [REF-2]: Section 6.1 - Application Selection

[REF-2]: Section 6.1.2.2 - Final selection

Applicability This test is applicable to terminals with online processing capability and does not
condition: support Cardholder selection
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 8 / DCI Card 09

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.3900.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

Terminal shall select RuPay Debit 1 / DINERS CLUB 1 application.

137/241 Confidential
uPay Device Validation Test Pla

In the authorization request,

The following fields shall be:

DE02 = 6074841230000098 /36070500001095

DE04 = 00 00 00 39 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
DE22 = 051
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Application Priority Indicator (Tag 87) for the AID ' A0 00 00 05 24 10 10

01' = '01'
Application Priority Indicator (Tag 87) for the AID ' A0 00 00 05 24 10 10
01' = '02'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
01’= 01'
Application Priority Indicator (Tag 87) for the AID ‘A0 00 00 01 52 30 10
02’='02'
In Final Selection “RuPay Debit 1” shall be selected.In first GENERATE AC
command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.8 RUPAY.DEV.A.010 - Blocked Card

RUPAY.DEV.A.010
Test No: RUPAY.DEV.A.010 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal rejects the card, when the card is blocked and the
terminal does not allow processing of the transaction via magnetic stripe.

Reference: [REF-2]: Section 8 - Operating / Functional Requirements

Applicability This test is applicable only if the terminal is:

condition:
ATM

138/241 Confidential
uPay Device Validation Test Pla

Micro ATM

Test Card ID: RuPay Card Image 9 / DCI Card 10

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

Pass Criteria: The terminal shall reject the card with a message “Transaction is not allowed,
Card is blocked”.
Terminal does not allow the card to perform a fallback transaction.

The following criteria shall be verified in card log:

The card returns SW '6A81' for SELECT command
The terminal shall display message “CARD BLOCKED”

Post Condition: NA

3.2.9 RUPAY.DEV.A.012 - PIN of 6 digits

RUPAY.DEV.A.012
Test No: RUPAY.DEV.A.012 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a PIN with 6 digits and PIN bypass
is not allowed.

Reference: RuPay Chip Terminal Implementation Requirements Guide_v1.0.pdf.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 1 /DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 123456.
Enter transaction amount as: Rs.4100.00 for ATM and Micro ATM

Pass Criteria: The terminal shall prompt the user to enter the PIN and display a message
“ENTER PIN”.
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

139/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE02 = 6074841230000023 / 36070500001012
DE04 = 00 00 00 41 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
DE61.12 should be between 3 and 9 (recommended)
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.10 RUPAY.DEV.A.014 - Expired Application

RUPAY.DEV.A.014
Test No: RUPAY.DEV.A.014 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage an expired card

Reference: [REF-2]: Section 6.5 Processing Restriction

Applicability This test is applicable to terminals with online processing capability

condition:
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 13 / DCI card 14

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The actual PIN value is 1234.
Enter transaction amount as: Rs.4500.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

140/241 Confidential
uPay Device Validation Test Pla

The following TVR bit shall be set:

TVR byte 2, bit 7 = 1 Expired application

In the authorization request,

The following fields shall be:

DE02 = 6074841230000155 / 36070500001145

DE04 = 00 00 00 45 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
In the authorization response,
The following fields shall be:

DE39 = 54
DE55, Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F24 = '131231' / ‘081231’

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command
Terminal requests AAC
Card responds with AAC (Tag 9F27 = 00)

Terminal shall display “CARD EXPIRED” / “APP EXPIRED”.

Post Condition: NA

3.2.11 RUPAY.DEV.A.015 - Issuer Application Data of 32 Bytes

RUPAY.DEV.A.015
Test No: RUPAY.DEV.A.015 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage a card with an Issuer Application
Data of 32 bytes and correctly populate the Authorization request

Reference: [REF-2]: Section 6.9 - First Card Action Analysis

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 14 / DCI Card 15

141/241 Confidential
uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.4600.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000163 / 36070500001152

DE04 = 00 00 00 46 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55 Tag 9F10 is 32 bytes data
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
The value of Tag 9F10 = Value of Tag 9F10 in DE55 if authorisation
request message (0100 / 0200)
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.12 RUPAY.DEV.A.016 - Application Blocked

RUPAY.DEV.A.016
Test No: RUPAY.DEV.A.016 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage the card, when the application of
the card is blocked and the terminal does not allow the processing of the
transaction via magnetic stripe

Reference: [REF-2]: Section 6.1 - Application Selection

142/241 Confidential
uPay Device Validation Test Pla

[REF-2]: Section 6.1.2.2 - Final selection

Applicability This test is applicable to terminals with online processing capability

condition:
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 15 / DCI card 016

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.4300.00 for ATM and Micro ATM

Pass Criteria: The terminal shall display message “APPLICATION BLOCKED”

Terminal does not allow the card to perform a fallback transaction.

The following criterion shall be verified in card log:

The card returns SW '6283' for in response of select command for AID A0
00 00 05 24 10 10 (If transaction performed using RuPay Card)
The card returns SW '6283' for in response of select command for AID A0
00 00 01 52 30 10 (If transaction performed using DCI Card)

Post Condition: NA

3.2.13 RUPAY.DEV.A.017 - Single Application Blocked in multiple AID card

RUPAY.DEV.A.017
Test No: RUPAY.DEV.A.017 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage the card, when one of the
application is blocked in a multiple AID card

Reference: [REF-2]: Section 6.1 - Application Selection

[REF-2]: Section 6.1.2.2 - Final selection

Applicability This test is applicable to terminals with online processing capability

condition:
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 33

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

143/241 Confidential
uPay Device Validation Test Pla

Enter the PIN as 1234

Enter transaction amount as: Rs.4800.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

The terminal shall display the message “RuPay Debit 1 BLOCKED, PERFORMED
TRANSACTION WITH RuPay Debit 2”.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000379
DE04 = 00 00 00 48 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

Card responds with SW '6283' for SELECT command with AID = 'A0 00 00 01
52 30 10 '
Card responds with SW '9000' for SELECT command with AID = 'A0 00 00 05
24 10 10'
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip
In charge slip the application name shall be “RuPay Debit 2 “

Post Condition: NA

3.2.14 RUPAY.DEV.A.018 - PDOL

RUPAY.DEV.A.018
Test No: RUPAY.DEV.A.018 - Revision 0 - Number of sub cases: 0

144/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal is able to manage a card with a PDOL

Reference: [REF-2]: Section 6.2 - Initiate Application Processing

Applicability This test is applicable to terminals with online processing capability

condition:
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 16 / DCI card 017

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.4900.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In GET PROCESSING OPTIONS command, the terminal sends PDOL data as
requested by the card.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000189 /36070500001178

DE04 = 00 00 00 49 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55.9F1A = 0356
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In Card's response to SELECT command with AID = 'A0 00 00 05 24 10 10'

contain Tag 9F38 = '9F 02 06 9F 03 06 9F 1A 02 5F 2A 02 9A 03 9F 35 01
9F 40 02 9F 15 02'
In Card's response to SELECT command with AID = ‘A0 00 00 01 52 30 10’
contain Tag 9F38 = '9F 02 06 9F 03 06 9F 1A 02 5F 2A 02 9A 03 9F 35 01
9F 40 02'
Terminal shall send GET PROCESSING OPTIONS command with PDOL data
of length 22/24 bytes with:
9F1A value shall be 0356

145/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.15 RUPAY.DEV.A.020 - Leap Year Expiration Date

RUPAY.DEV.A.020
Test No: RUPAY.DEV.A.020 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal correctly manages the expiration date in a leap year

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable to terminals with online processing capability.

condition:
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 18 / DCI Card 019

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.5200.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 2, bit 7 = 0 (Application is not expired)

The following fields shall be:

DE02 = 6074841230000205 / 36070500001194

DE04 = 00 00 00 52 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
In the authorization response,
The following fields shall be:

146/241 Confidential
uPay Device Validation Test Pla

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 5F24 = '28 02 29' (if RuPay card is used)

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.16 RUPAY.DEV.A.021 - Script Processing (1) – Single script command

RUPAY.DEV.A.021
Test No: RUPAY.DEV.A.021 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to send one issuer script command received in
the authorization response

Reference: [REF-2]: Section 6.14 - Issuer to Card script processing

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 1 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.5300 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

The host sends a PUT DATA command in the authorization response.
In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001202

DE04 = 00 00 00 53 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)

147/241 Confidential
uPay Device Validation Test Pla

DE22 = 051
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE55 Tag 72 is present with PUT DATA command

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Terminal shall send the following Issuer script command after second
GENERATE AC command:
PUT DATA command – 84 DA 00 CB 09 05 MAC(8 Bytes)

The following criteria shall be verified in Terminal trace log / Switch log
(Bank has to submit the logs)
TVR, byte 5, bit 5 = 0 - (Script processing did not fail after final
Generate AC)
TSI, byte 1, bit 3 = 1 (Script processing was performed)

Post Condition: NA

3.2.17 RUPAY.DEV.A.022 - Script Processing (2) – Multiple script commands

RUPAY.DEV.A.022
Test No: RUPAY.DEV.A.022 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process several issuer script commands
received in the authorization response

Reference: [REF-2]: Section 6.14 - Issuer to Card script processing

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

148/241 Confidential
uPay Device Validation Test Pla

Test Card ID: RuPay Card Image 1 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.5600.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001202

DE04 = 00 00 00 56 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE55 Tag 72 is present with PUT DATA commands for updating LCOL, LCOA
(new value), and LCOA (as personalised)

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Terminal shall send the following Issuer script commands after second
GENERATE AC command
PUT DATA command – 84 DA 00 CB 09 07 MAC(8 Bytes)
PUT DATA command – 84 DA 00 C8 0E 00 00 00 00 00 00 MAC(8 Bytes)
PUT DATA command – 84 DA 00 C8 0E 00 00 00 01 00 00 MAC(8 Bytes)
The following criteria shall be verified in Terminal trace log / Switch log
(Bank has to submit the logs):
TVR, byte 5, bit 5 = 0 - (Script processing did not fail after final
Generate AC)

149/241 Confidential
uPay Device Validation Test Pla

TSI, byte 1, bit 3 = 1 (Script processing was performed)

Post Condition: NA

3.2.18 RUPAY.DEV.A.025 - Issuer Authentication Data

RUPAY.DEV.A.025
Test No: RUPAY.DEV.A.025 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage Issuer Authentication Data received
in the Authorization response.

Reference: [REF-2]: Section 6.10.2.1 - Issuer Authentication

Applicability This test is applicable to terminals with online processing capability

condition:
And
ATM
Micro ATM

Test Card ID: RuPay Card Image 1/ DCI card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.5900.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 59 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
In the authorization response, the following fields shall be:

DE39 is equal to 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:

150/241 Confidential
uPay Device Validation Test Pla

Terminal requests TC with the value of IAD = DE55 –Tag 91

Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.19 RUPAY.DEV.A.027 – Balance inquiry Transaction

RUPAY.DEV.A.027
Test No: RUPAY.DEV.A.027 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Balance inquiry
transaction

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal is :

condition:
ATM
Micro ATM
Supports Balance inquiry

Test Card ID: RuPay Card Image 1 / DCI Card 031

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001319

DE04 = 00 00 00 00 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55.9F03 shall be present and is equal to 000000000000
DE55.9F02 shall be present and is equal to 000000000000
DE03 (first 2 digits) and DE55 Tag 9C is equal to 31
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE54 = Present

The following criteria shall be verified in card log:

151/241 Confidential
uPay Device Validation Test Pla

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.20 RUPAY.DEV.A.028 - Unknown AID

RUPAY.DEV.A.028
Test No: RUPAY.DEV.A.028 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage an unknown AID and request to use
magnetic stripe

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 24 / DCI Card 033

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as .6100.00 for ATM and Micro ATM

Pass Criteria: The terminal performs fall back (Magnetic stripe) transaction.
In the authorization request,

The following fields shall be:

DE22= '801' (ICC card “Chip Fallback”)
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55 is absent
In the authorization response,
The following fields shall be:

DE39 is equal to 00
DE55 is absent

152/241 Confidential
uPay Device Validation Test Pla

The following criteria shall be verified in card log:

Card responds with SW '6A82' to SELECT command with AID = 'A0 00 00 05

24 10 10'
Card responds with SW '6A82' to SELECT command with AID = ‘A0 00 00 01
52 30 10’

Post Condition: NA

3.2.21 RUPAY.DEV.A.029 - Fallback Not Allowed

RUPAY.DEV.A.029
Test No: RUPAY.DEV.A.029 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal will not perform a fallback transaction when the
transaction is completed with a chip and declined by the host

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN value as 1111
Enter transaction amount as: Rs.6200.00 for ATM and Micro ATM

Pass Criteria: The transaction must be declined by the issuer because of incorrect PIN.
In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 3 = 1 - Online PIN entered

The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 62 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
In the authorization response,
The following shall be:

153/241 Confidential
uPay Device Validation Test Pla

DE39 = 55
DE55 Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal displays the message: "INCORRECT PIN".

Post decline, the Terminal shall not perform fallback or Magnetic stripe
transaction.

Post Condition: NA

3.2.22 RUPAY.DEV.A.034- Terminal failure Reversal

RUPAY.DEV.A.034
Test No: RUPAY.DEV.A.034 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to generate a Reversal request when acquirer is
unable to complete a transaction due to the Terminal Failure

Reference: [REF-1] Section: 8.3.26 - DE– 39 Response Code

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.6700.00 for ATM and Micro ATM

Pass Criteria: In the authorization request,

The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 67 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)

154/241 Confidential
uPay Device Validation Test Pla

DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is present

In the Reversal request,

The following fields shall be:

DE02 = PAN in authorization request

DE04 = Amount Authorized in authorization request
DE11, DE37 = STAN and RRN in authorization request
DE39 = 21

In the Reversal response,

The following fields shall be:

DE39 = 00

Post Condition: NA

3.2.23 RUPAY.DEV.A.035 - Reversal with Issuer Script Results

RUPAY.DEV.A.035
Test No: RUPAY.DEV.A.035 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to generate issuer script results and same is
forwarded in Reversal request when transaction is declined at the terminal during
final action analysis

Reference: [REF-2]: Section 8.1.1 - Chip Related Reversal

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 1 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.6800.00 for ATM and Micro ATM

155/241 Confidential
uPay Device Validation Test Pla

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000023 / 36070500001012

DE04 = 00 00 00 68 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
(The 0210 message must contain an invalid ARPC and a valid script.)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 = “Invalid”
DE55 Tag 72 is present

In the Reversal request,

The following fields shall be:

DE02 = PAN in authorization request

DE04 = Amount Authorized in authorization request
DE11, DE37 = STAN and RRN in authorization request
DE39 = E1
DE55 9F5B = 2030303030 is present

In the Reversal response,

The following fields shall be:

DE39 = 00

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

156/241 Confidential
uPay Device Validation Test Pla

3.2.24 RUPAY.DEV.A.036 - Fallback when chip fails

RUPAY.DEV.A.036
Test No: RUPAY.DEV.A.036 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to perform fallback transaction when chip fails.

Reference: [REF-2]: Section 8.4 - Fall back to Magnetic Stripe Processing

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 37 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.6900.00 for ATM and Micro ATM

Pass Criteria: The terminal does not perform chip transaction.

The terminal performs fall back (Magnetic stripe) transaction.
In the authorization request,
The following fields shall be:

DE02 = 6522231230000033 / 36070500001012

DE04 = 00 00 00 69 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE22 (ATM entry mode) is equal to 801
DE55 is absent
DE61.2 = 2 (PIN Entry)
DE61.7 = 2 (Magnetic Stripe read)
DE61.8 = 2 (PIN)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 Tag 91 is absent

Post Condition: NA

3.2.25 RUPAY.DEV.A.039 - When Online PIN is not supported by the Card

RUPAY.DEV.A.039
Test No: RUPAY.DEV.A.039 - Revision 0 - Number of sub cases: 0

157/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that the terminal is able to manage a transaction when Online PIN is not
supported by the Card.

Reference:

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 26 / DCI Card 039

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter transaction amount as: Rs.7200.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 8 = 1 (Cardholder Verification was not successful)

The following fields shall be:

DE02 = 6074841230000296 / 36070500001392

DE04 = 00 00 00 72 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

TSI byte 1, bit 7 = 1 (Cardholder Verification was performed)

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

158/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.2.26 RUPAY.DEV.A.040 - Response without Issuer authentication data

RUPAY.DEV.A.040
Test No: RUPAY.DEV.A.040 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process the transaction when Issuer
authentication is not required by the card

Reference: [REF-2] Fig 16: and Section 6.11 Step 11: Second Terminal Action Analysis

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 19 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234
Enter transaction amount as: Rs.7300.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000213 / 36070500001202

DE04 = 00 00 00 73 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is absent

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC with IAD = '00 00 00 00 00 00 00 00 00 00'

159/241 Confidential
uPay Device Validation Test Pla

Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.27 RUPAY.DEV.A.041 - RuPay International Card with amount range in CVM list
RUPAY.DEV.A.041

Test No: RUPAY.DEV.A.041 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process a Cash at ATM transaction with
RuPay International card with Service Code 226

Reference: [REF-2]: Section 6.5 - Processing Restriction

[REF-1]: Section 7.2.1.6 - Cash at ATM

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 40 / DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Enter transaction amount as: Rs.7500.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6522231230000058 / 36070500001012

DE3 (first 2 digits) and 9C = 01
DE04 = 00 00 00 75 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
Amount in DE4 = amount DE55 Tag9F02
DE55 Tag 9F03 = 00 00 00 00 00 00
DE52 is present.
DE61.2= 2 (PIN Entry)
DE61.8= 2(PIN)
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

160/241 Confidential
uPay Device Validation Test Pla

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.28 RUPAY.DEV.A.042 - Purchase Only Card

RUPAY.DEV.A.042
Test No: RUPAY.DEV.A.042 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal (ATM) rejects a Purchase only card

Reference: [REF-2]: Section 6.5 - Processing Restriction

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 34

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN value is 1234.
Enter the transaction amount of Rs.500.00 for ATM and Micro ATM

Pass Criteria: The terminal shall reject the card and display an error message (such as “NOT
ACCEPTED”).
The terminal shall not require swiping the card or displaying a message “PLEASE
SWIPE CARD” or “USE MAGSTRIPE”.
The transaction must be declined.
The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests AAC
TVR Byte 2 bit 5 = 1 - Requested services not allowed for the card
product
Card responds with AAC (Tag 9F27 = '00')

161/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.2.29 RUPAY.DEV.A.046 - Response without Issuer authentication data & declined by Issuer
RUPAY.DEV.A.046
Test No: RUPAY.DEV.A.046 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to process the transaction when Issuer
authentication is not required by the card

Reference: [REF-2] Fig 16: and Section 6.11 Step 11: Second Terminal Action Analysis

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: RuPay Card Image 19 / DCI Card 020

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
The PIN value is 1234
Enter transaction amount as: Rs.7900.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6074841230000213 / 36070500001202

DE04 = 00 00 00 79 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
In the authorization response,
The following fields shall be:

DE39 = 05
DE55 –Tag 91 is absent

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:

162/241 Confidential
uPay Device Validation Test Pla

Terminal requests AAC with IAD = '00 00 00 00 00 00 00 00 00 00'

Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.2.30 RUPAY.DEV.A.047 – PIN Change

RUPAY.DEV.A.047
Test No: RUPAY.DEV.A.047 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage PIN change transaction

Reference:

Applicability This test is applicable only if the terminal is:

condition:
ATM

Test Card ID: RuPay Card Image 1 /DCI Card 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Select PIN Change
Enter new PIN: 4321

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000023 /36070500001012

DE03 Digit 1-2 = 90

DE04 = 00 00 00 00 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
DE22 = 051

163/241 Confidential
uPay Device Validation Test Pla

DE120 Tag 001 = 08

DE55.9C =90

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal sends the issuer script command to the card
The card responds to the issuer script command with SW=9000
The terminal shall display “PIN Change successful”

Post Condition: NA

3.2.31 RUPAY.DEV.A.048 – Mini Statement

RUPAY.DEV.A.048
Test No: RUPAY.DEV.A.048 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage mini statement

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM

Test Card ID: RuPay Card Image 3 /DCI Card 03

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234

164/241 Confidential
uPay Device Validation Test Pla

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000049 / 36070500001038

DE03 Digit 1-2 = 90

DE04 = 00 00 00 00 00 00
DE52 is present
DE22 = 051
DE55.9C =90
DE120.Tag 001 = 07
DE120.Tag 002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

165/241 Confidential
uPay Device Validation Test Pla

3.2.32 RUPAY.DEV.A.050 – Mobile Banking Registration

RUPAY.DEV.A.050
Test No: RUPAY.DEV.A.050 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the Mobile Banking Registration is successful

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Mobile Banking Registration

Test Card ID: RuPay Card Image 02

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Mobile Banking Registration
Enter the mobile number 915500112233 twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000031
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE 48.074 = 915500112233
DE52 is present
DE55.9C =90
DE120.001 = UR
DE120.002 = GDN

In the authorization response,

166/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = UR
DE120.002 = GDN

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “MOBILE BANKING REGISTRATION
SUCCESSFUL”.

Post Condition: NA

3.2.33 RUPAY.DEV.A.051 – Mobile Banking Registration – incorrect mobile number

RUPAY.DEV.A.051
Test No: RUPAY.DEV.A.051 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal responds correctly when incorrect mobile number
was entered during Mobile Banking Registration

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Mobile Banking Registration

Test Card ID: RuPay Card Image 03

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Mobile Banking Registration

167/241 Confidential
uPay Device Validation Test Pla

Enter the mobile number 915566778898 twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000049
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE 48.074 = 915566778898
DE52 is present
DE55.9C =90
DE120.001 = UR
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 69

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “INCORRECT MOBILE NUMBER”.

Post Condition: NA

3.2.34 RUPAY.DEV.A.052 – Mobile Banking Registration (Issuer is not enabled for Mobile
Banking Registration)
RUPAY.DEV.A.052
Test No: RUPAY.DEV.A.052 - Revision 0 - Number of sub cases: 0

168/241 Confidential
uPay Device Validation Test Pla

Test Objective: To ensure that Mobile Banking Registration failed since Issuer is not enabled for
Mobile Banking Registration

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Mobile Banking Registration

Test Card ID: RuPay Card Image 04

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Mobile Banking Registration
Enter the mobile number 915500112233 twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000056
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE 48.074 = 915500112233
DE52 is present
DE55.9C =90
DE120.001 = UR
DE120.002 = GDN

In the authorization response,

The following fields shall be:

169/241 Confidential
uPay Device Validation Test Pla

DE39 = 12

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “ISSUER IS NOT ENABLED FOR MOBILE BANKING
REGISTRATION”.

Post Condition: NA

3.2.35 RUPAY.DEV.A.053 – Aadhaar Number Seeding

RUPAY.DEV.A.053
Test No: RUPAY.DEV.A.053 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Aadhaar Number Seeding is successful

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Aadhaar Number Seeding

Test Card ID: RuPay Card Image 05

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Aadhaar Number Seeding
Enter the Aadhaar Number (100020003000) twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered

170/241 Confidential
uPay Device Validation Test Pla

IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000000021
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE48.066 = 100020003000DE52 is present
DE55.9C =90
DE120.001 = AN
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = AN
DE120.002 = GDN

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “AADHAAR NUMBER SEEDING SUCCESSFUL”.

Post Condition: NA

3.2.36 RUPAY.DEV.A.054 – Aadhaar Number Seeding (Issuer is not enabled for Aadhaar
Number Seeding)
RUPAY.DEV.A.054
Test No: RUPAY.DEV.A.054 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Aadhaar Number Seeding is failed since Issuer is not enabled for
Aadhaar Number Seeding.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

171/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Aadhaar Number Seeding

Test Card ID: RuPay Card Image 06

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Aadhaar Number Seeding
Enter the Aadhaar Number (100020003000) twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000064
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE48.066 = 100020003000
DE52 is present
DE55.9C =90
DE120.001 = AN
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 12

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC

172/241 Confidential
uPay Device Validation Test Pla

Card responds with ARQC (Tag 9F27 = '80')

In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “ISSUER IS NOT ENABLED FOR AADHAAR
NUMBER SEEDING”.

Post Condition: NA

3.2.37 RUPAY.DEV.A.055 – Cheque Book Request

RUPAY.DEV.A.055
Test No: RUPAY.DEV.A.055 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Cheque Book Request is successful

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Cheque Book Request

Test Card ID: RuPay Card Image 07

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cheque Book Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000072
DE03 = 90
DE04 = 00 00 00 00 00 00

173/241 Confidential
uPay Device Validation Test Pla

DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 36
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = 36
DE120.002 = GDN

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CHEQUE BOOK REQUEST SUCCESSFUL”.

Post Condition: NA

3.2.38 RUPAY.DEV.A.056 – Cheque Book Request (Do not Honour)

RUPAY.DEV.A.056
Test No: RUPAY.DEV.A.056 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that terminal shall reject the transaction when it receives the “Do not
Honour” message from issuer for Cheque Book Request.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM

Supports Cheque Book Request

Test Card ID: RuPay Card Image 08

174/241 Confidential
uPay Device Validation Test Pla

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cheque Book Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000098
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 36
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 05

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “CHEQUE BOOK REQUEST IS NOT
SUCCESSFUL”.

175/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.2.39 RUPAY.DEV.A.057 – Statement Request

RUPAY.DEV.A.057
Test No: RUPAY.DEV.A.057 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Statement Request is successful

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Statement Request

Test Card ID: RuPay Card Image 10

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Statement Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000114
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 37
DE120.002 = GDN

In the authorization response,

176/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = 37
DE120.002 = GDN

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “STATEMENT REQUEST SUCCESSFUL”.

Post Condition: NA

3.2.40 RUPAY.DEV.A.058 – Statement Request (Do not Honour)

RUPAY.DEV.A.058
Test No: RUPAY.DEV.A.058 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that terminal shall reject the transaction when it receives the “Do not
Honour” message from issuer for Statement Request.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Statement Request

Test Card ID: RuPay Card Image 11

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 123456
Choose Statement Request

Pass Criteria: The terminal shall perform a complete transaction.

177/241 Confidential
uPay Device Validation Test Pla

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000122
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 37
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 05

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “STATEMENT REQUEST IS NOT SUCCESSFUL”.

Post Condition: NA

3.2.41 RUPAY.DEV.A.059 – Card to Card Fund Transfer

RUPAY.DEV.A.059
Test No: RUPAY.DEV.A.059 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Card to Card Fund Transfer is successful.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

178/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Card to Card Fund transfer

Test Card ID: RuPay Card Image 12

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose ‘Card to Card Fund Transfer’
Enter beneficiary card number 6073841230000016 twice
Enter transfer amount Rs.5000.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000148
DE03 = 90
DE04 = 00 00 00 50 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE.103 = 6073841230000016
DE120.001 = FT
DE120.002 = SPT

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = FT

179/241 Confidential
uPay Device Validation Test Pla

DE120.002 = SPT

The following criteria shall be verified in card log:

CVM results = 420100

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CARD TO CARD FUND TRANSFER
SUCCESSFUL”.

Post Condition: NA

3.2.42 RUPAY.DEV.A.060 – Card to Card Fund Transfer – Beneficiary card number with
Minimum length
RUPAY.DEV.A.060
Test No: RUPAY.DEV.A.060 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Card to Card Fund Transfer is successful for RuPay card when
beneficiary card number has minimum length.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Card to Card Fund transfer

Test Card ID: RuPay Card Image 14

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Card to Card Fund Transfer
Enter beneficiary card number 607384123007 twice
Enter transfer amount Rs.5000.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

180/241 Confidential
uPay Device Validation Test Pla

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000163
DE03 = 90
DE04 = 00 00 00 50 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE.103 = 607384123007
DE120.001 = FT
DE120.002 = SPT

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = FT
DE120.002 = SPT

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CARD TO CARD FUND TRANSFER
SUCCESSFUL”.

Post Condition: NA

3.2.43 RUPAY.DEV.A.061 – Card to Card Fund Transfer (Expired Card)

RUPAY.DEV.A.061

181/241 Confidential
uPay Device Validation Test Pla

Test No: RUPAY.DEV.A.061 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that terminal can able to manage expired card during Card to Card
Fund Transfer.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Card to Card Fund Transfer

Test Card ID: RuPay Card Image 13

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose ‘Card to Card Fund Transfer’
Enter beneficiary card number 6073841230000024twice
Enter transfer amount Rs.5000.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000155
DE03 = 90
DE04 = 00 00 00 50 00 00
DE22 = 051
DE52 is present
DE55.9C = 90
DE.103 = 6073841230000024
DE120.001 = FT
DE120.002 = SPT

In the authorization response,

182/241 Confidential
uPay Device Validation Test Pla

The following fields shall be:

DE39 = 54

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “EXPIRED CARD”.

Post Condition: NA

3.2.44 RUPAY.DEV.A.062 – Inter-Operable Cash Deposit - Own Account

RUPAY.DEV.A.062
Test No: RUPAY.DEV.A.062 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal can able to manage Inter-Operable Cash Deposit to
card holder's account

Reference: NPCI - NFS_Interface_Specification_ VAS_Addendum_ Ver_ 6.0.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Inter-Operable Cash Deposit

Test Card ID: RuPay Card Image 15

Precondition: No specific condition required

Test Procedure: Step 1: Validation leg

Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cash deposit
Choose ‘Own account’
Step 2: Deposit leg
Deposit the following notes when terminal prompts for the same
Rs.2000 x No.1
Rs.500 x No.2

183/241 Confidential
uPay Device Validation Test Pla

Rs.100 x No.5
Rs.50 x No.10
Terminal displays the denomination and total amount of the deposited notes,
confirm the same.

Pass Criteria: Step 1: Validation leg

The terminal shall perform a complete transaction.
In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000171
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C = 90
DE103 = PAN in DE2
DE120.001 = IQ
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = IQ
DE120.002 = GDN
DE120.046 = ABCDEFGHIJKL Beneficiary Name
DE120. 080 is present Deposit ID
The following criteria shall be verified in card log:

CVM results = 420100In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:

184/241 Confidential
uPay Device Validation Test Pla

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “DEPOSIT CURRENCY”.
Step 2: Deposit leg

The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:

DE02 = 6074841230000171
DE03 = 90
DE04 = 00 00 00 40 00 00
DE103 = PAN in DE2DE120.001 = FD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120.080 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE120.001 = FD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120. 080 is present Deposit ID
The terminal shall display message “DEPOSIT SUCCESSFUL”.

Post Condition: NA

3.2.45 RUPAY.DEV.A.063 – Inter-Operable Cash Deposit - Third Party Account (based on card
number)
RUPAY.DEV.A.063
Test No: RUPAY.DEV.A.063 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal can able to manage Inter-Operable Cash Deposit to
Third Party Account

Reference: NPCI - NFS_Interface_Specification_ VAS_Addendum_ Ver_ 6.0.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Inter-Operable Cash Deposit

Test Card ID: RuPay Card Image 16

Precondition: No specific condition required

185/241 Confidential
uPay Device Validation Test Pla

Test Procedure: Step 1: Validation leg

Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cash deposit
Choose ‘Third Party Account’
Enter Beneficiary Card Number as 6073841230000016 twice
Step 2: Deposit leg
Deposit the following notes when terminal prompts for the same
Rs.2000 x No.1
Rs.500 x No.2
Rs.100 x No.5
Rs.50 x No.10
Terminal displays the denomination and total amount of the deposited notes,
confirm the same.

Pass Criteria: Step 1: Validation leg

The terminal shall perform a complete transaction.
In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same

application versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
The following fields shall be:

DE02 = 6074841230000189
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C = 90
DE103 = 6073841230000016
DE120.001 = CQ
DE120.002 = GDN
In the authorization response,
The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

186/241 Confidential
uPay Device Validation Test Pla

DE120.001 = CQ
DE120.002 = GDN
DE120.046 = ABCDEFGHIJKL Beneficiary Name
DE120. 080 is present Deposit ID
The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “DEPOSIT CURRENCY”.
Step 2: Deposit leg

The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:

DE02 = 6074841230000189
DE03 = 90
DE04 = 00 00 00 40 00 00
DE103 = 6073841230000016DE120.001 = CD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120.080 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE120.001 = CD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120. 080 is present Deposit ID
The terminal shall display message “DEPOSIT SUCCESSFUL”.

Post Condition: NA

3.2.46 RUPAY.DEV.A.064 – Inter-Operable Cash Deposit (Beneficiary card expired) (based on

card number)
RUPAY.DEV.A.064
Test No: RUPAY.DEV.A.064 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal can able to manage expired beneficiary card during
Inter-Operable Cash Deposit to Third Party Account

Reference: NPCI - NFS_Interface_Specification_ VAS_Addendum_ Ver_ 6.0.pdf

187/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Inter-Operable Cash Deposit

Test Card ID: RuPay Card Image 17

Precondition: No specific condition required

Test Procedure: Validation leg

Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cash deposit
Choose ‘Third Party Account’
Enter Beneficiary Card Number

Pass Criteria: Validation leg

The terminal shall perform a complete transaction.
In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000197
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C = 90
DE120.001 = CQ
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 54

The following criteria shall be verified in card log:

188/241 Confidential
 uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')
The terminal shall display message “BENEFICIARY CARD EXPIRED”.

Post Condition: NA

3.2.47 RUPAY.DEV.A.065 – Transaction with cardholder confirmation

RUPAY.DEV.A.065
Test No: RUPAY.DEV.A.065 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage card requires cardholder
confirmation

Reference:

Applicability This test case is applicable if Terminal supports Cardholder selection:

condition:
And
ATM

Test Card ID: RuPay Card Image 041

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Select the RuPay Debit 1 application
Enter the PIN as 1234.
Enter transaction amount as: Rs.6000.00 for ATM

Pass Criteria: Terminal shall prompt the “RuPay Debit 1” Application on the screen and
cardholder shall be able to select it. Terminal shall perform a complete
transaction.
In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered

189/241 Confidential
 uPay Device Validation Test Pla

IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000023

DE04 = 00 00 00 60 00 00
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.48 RUPAY.DEV.A.066 – Transaction with cardholder confirmation – time out

RUPAY.DEV.A.066
Test No: RUPAY.DEV.A.066 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage the transaction when the card
requires cardholder confirmation

Reference:

Applicability This test case is applicable if Terminal supports Cardholder selection:

condition:
And
ATM

Test Card ID: RuPay Card Image 041

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

190/241 Confidential
 uPay Device Validation Test Pla

Terminal shall display RuPay Debit

Do not select any application

Pass Criteria: Terminal shall not continue with the transaction

Terminal shall display “Transaction timed out” or similar message

In card log:
Terminal shall not send any other command after SELECT command response.

Post Condition: NA

3.2.49 RUPAY.DEV.A.067 – Transaction with cardholder confirmation for one application

RUPAY.DEV.A.067
Test No: RUPAY.DEV.A.067 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage the transaction when one of the
applications in the card requires cardholder confirmation

Reference:

Applicability This test is applicable only if the terminal is:

condition:
ATM

Test Card ID: RuPay Card Image 042

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

If Terminal supports Cardholder selection:

The terminal displays the names of two applications: “RuPay Debit 1” and “RuPay
Debit 2”, Select “RuPay Debit 2” application.

If Terminal supports Auto-selection:

Do not select any Application.

Enter the PIN as 1234.

Enter transaction amount as: Rs. 2600.00 for ATM

Pass Criteria: Terminal performs a complete transaction based on highest priority application.
In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions

191/241 Confidential
uPay Device Validation Test Pla

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6074841230000023

DE04 = 00 00 00 26 00 00
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In Final selection RuPay Debit 2 shall be selected

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.2.50 RUPAY.DEV.A.068 – PIN Change without Issuer Scripting

RUPAY.DEV.A.068
Test No: RUPAY.DEV.A.068 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage PIN change transaction without
issuer scripts

Reference:

Applicability This test is applicable only if the terminal is:

condition:
ATM

Test Card ID: RuPay Card Image 40 / DCI Card 01

Precondition: No specific condition required

192/241 Confidential
uPay Device Validation Test Pla

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Select PIN Change
Enter new PIN: 4321

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

The following fields shall be:

DE02 = 6522231230000058 /36070500001012

DE03 Digit 1-2 = 90

DE04 = 00 00 00 00 00 00
DE52 is present
DE22 = 051
DE120 Tag 001 = 08
DE55.9C =90

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

193/241 Confidential
uPay Device Validation Test Pla

The terminal shall display “PIN Change successful”

Post Condition: NA

3.2.51 RUPAY.DEV.A.069 - Cash Withdrawal using a qSPARC Card

RUPAY.DEV.A.069
Test No: RUPAY.DEV.A.069 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts a basic RuPay qSPARC card for Cash
Withdrawal.

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: qSPARC Card with PAN = 6083260000000015

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.100.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered

The following fields shall be:

DE02 = 6083260000000015
DE04 = 000000010000
DE52 is present
DE22 = 051
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55.9F10 = present, with 32 Bytes of data

In the authorization response,

194/241 Confidential
 uPay Device Validation Test Pla

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.3 ATM and Micro ATM Certification Test Scenarios - MRuPay

3.3.1 RUPAY.DEV.A.M001 - Cash Withdrawal

RUPAY.DEV.A.M001
Test No: RUPAY.DEV.A.M001 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts MRuPay card and is able to manage Online
PIN as CVM for Cash Withdrawal.

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.3000.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions

195/241 Confidential
uPay Device Validation Test Pla

TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE04 = 00 00 00 30 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present
DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In Read Record command:
PAN (Tag 5A) = 6083730089020019
AUC (Tag 9F07) Byte 1, bit 7 = 1

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
In 0100/0200 message, DE2 (PAN) = Tag 5A (PAN) from Read Record
In 0100/0200 message, DE4 (Transaction Amount) = Tag 9F02 (Amount) from
first GENERATE AC
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
Application name shall be MRuPay
Card holder name shall be printed

196/241 Confidential
uPay Device Validation Test Pla

Post Condition: NA

3.3.2 RUPAY.DEV.A.M002 – Balance Inquiry Transaction

RUPAY.DEV.A.M002
Test No: RUPAY.DEV.A.M002 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Balance inquiry
transaction for MRuPay card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM
Supports Balance inquiry

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6083730089020019
DE04 = 00 00 00 00 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55.9F03 shall be present and is equal to 000000000000
DE55.9F02 shall be present and is equal to 000000000000
DE3 (first 2 digits) and DE55 Tag 9C is equal to 31
In the authorization response,
The following fields shall be:

DE39 = 00
DE54 = Present
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

197/241 Confidential
uPay Device Validation Test Pla

In second GENERATE AC command:

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
In 0100/0200 message, DE02 (PAN) = Tag 5A (PAN) from Read Record
In 0100/0200 message, DE04 (Transaction Amount) = Tag 9F02 (Amount) from
first GENERATE AC
Charge Slip

Transaction type shall be “Balance inquiry”

Post Condition: NA

3.3.3 RUPAY.DEV.A.M003 – PIN Change

RUPAY.DEV.A.M003
Test No: RUPAY.DEV.A.M003 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage PIN change transaction for MRuPay
card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Supports PIN management

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Select PIN Change
Enter new PIN: 4321

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

198/241 Confidential
uPay Device Validation Test Pla

CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 Digit 1-2 = 90

DE04 = 00 00 00 00 00 00
DE52 is present
DE22 = 051
DE120 Tag 001 = 08
DE55.9C = 90

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

The terminal sends the issuer script command to the card
The card responds to the Issuer Script command with SW = 9000

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

The terminal shall display “PIN Change successful”

Post Condition: NA

3.3.4 RUPAY.DEV.A.M004 – Mini Statement

RUPAY.DEV.A.M004
Test No: RUPAY.DEV.A.M004 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage mini statement for MRuPay card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:

199/241 Confidential
uPay Device Validation Test Pla

ATM
Supports Mini Statement

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC
CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 Digit 1-2 = 90
DE04 = 00 00 00 00 00 00
DE52 is present
DE22 = 051
DE55.9C =90
DE120.Tag 001 = 07
DE120 Tag 002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC

200/241 Confidential
uPay Device Validation Test Pla

Card responds with ARQC (Tag 9F27 = '80')

In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
Application name shall be MRUPAY
Card holder name shall be printed

Post Condition: NA

3.3.5 RUPAY.DEV.A.M005 – Mobile Banking Registration

RUPAY.DEV.A.M005
Test No: RUPAY.DEV.A.M005 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the Mobile Banking Registration is successful for MRuPay card

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Mobile Banking Registration

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Mobile Banking Registration
Enter the mobile number 915500112233 twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

201/241 Confidential
uPay Device Validation Test Pla

TVR byte 3, bit 3 = 1 - Online PIN is entered

IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE 48.074 = 915500112233
DE52 is present
DE55.9C =90
DE120.001 = UR
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = UR
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “MOBILE BANKING REGISTRATION
SUCCESSFUL”.

Post Condition: NA

3.3.6 RUPAY.DEV.A.M006 – Aadhaar Number Seeding

RUPAY.DEV.A.M006
Test No: RUPAY.DEV.A.M006 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Aadhaar Number Seeding is successful for MRuPay card.

Reference:

202/241 Confidential
uPay Device Validation Test Pla

RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Aadhaar Number Seeding

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Aadhaar Number Seeding
Enter the Aadhaar Number (100020003000) twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE48.066 = 100020003000
DE55.9C =90
DE120.001 = AN
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

203/241 Confidential
uPay Device Validation Test Pla

DE120.001 = AN
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “AADHAAR NUMBER SEEDING SUCCESSFUL”.

Post Condition: NA

3.3.7 RUPAY.DEV.A.M007 – Cheque Book Request

RUPAY.DEV.A.M007
Test No: RUPAY.DEV.A.M007 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that cheque book request is successful for MRuPay card

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports cheque book request

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cheque Book Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered

204/241 Confidential
uPay Device Validation Test Pla

IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 36
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = 36
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CHEQUE BOOK REQUEST SUCCESSFUL”.

Post Condition: NA

3.3.8 RUPAY.DEV.A.M008 – Statement Request

RUPAY.DEV.A.M008
Test No: RUPAY.DEV.A.M008 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Statement Request is successful for MRuPay card

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:

205/241 Confidential
uPay Device Validation Test Pla

Is ATM
Supports Statement Request

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Statement Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 37
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = 37
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

206/241 Confidential
uPay Device Validation Test Pla

Terminal requests ARQC

Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “STATEMENT REQUEST SUCCESSFUL”.

Post Condition: NA

3.3.9 RUPAY.DEV.A.M009 – Card to Card Fund Transfer

RUPAY.DEV.A.M009
Test No: RUPAY.DEV.A.M009 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Card to Card Fund Transfer is successful for MRuPay card

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Card to Card Fund transfer

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Card to Card Fund Transfer
Enter beneficiary card number 6073841230000032 twice
Enter transfer amount Rs.5000.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

CVM results = 020000

The following fields shall be:

207/241 Confidential
uPay Device Validation Test Pla

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 50 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE.103 = 6073841230000032
DE120.001 = FT
DE120.002 = SPT

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = FT
DE120.002 = SPT

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CARD TO CARD FUND TRANSFER
SUCCESSFUL”.

Post Condition: NA

3.3.10 RUPAY.DEV.A.M011 – Inter-Operable Cash Deposit - Third Party Account (based on card
number)
RUPAY.DEV.A.M011
Test No: RUPAY.DEV.A.M011 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal can able to manage Inter-Operable Cash Deposit to
Third Party Account for MRuPay card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM

208/241 Confidential
uPay Device Validation Test Pla

Supports Inter-Operable Cash Deposit

Test Card ID: MRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Step 1: Validation leg

Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cash deposit
Choose ‘Third Party Account’
Enter Beneficiary Card Number
Step 2: Deposit leg
Deposit the following notes when terminal prompts for the same
Rs.2000 x No.1
Rs.500 x No.2
Rs.100 x No.5
Rs.50 x No.10
Terminal displays the denomination and total amount of the deposited notes,
confirm the same.

Pass Criteria: Step 1: Validation leg

The terminal shall perform a complete transaction.
In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 3, bit 5 = 0 & bit 6 =1 ARQC

CVM results = 020000

The following fields shall be:

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C = 90

209/241 Confidential
uPay Device Validation Test Pla

DE103 = 6073841230000016
DE120.001 = CQ
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = CQ
DE120.002 = GDN
DE120.046 = ABCDEFGHIJKL Beneficiary Name
DE120. 080 is present Deposit ID
The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “DEPOSIT CURRENCY”.
Step 2: Deposit leg

The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:

DE02 = 6083730089020019
DE03 = 90
DE04 = 00 00 00 40 00 00
DE103 = 6073841230000016DE120.001 = CD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120.080 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE120.001 = CD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010

210/241 Confidential
 uPay Device Validation Test Pla

DE120. 080 is present Deposit ID

The terminal shall display message “DEPOSIT SUCCESSFUL”.

Post Condition: NA

3.4 ATM and Micro ATM Certification Test Scenarios - VRuPay

3.4.1 RUPAY.DEV.A.V001 - Cash Withdrawal

RUPAY.DEV.A.V001
Test No: RUPAY.DEV.A.V001 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal accepts VRuPay card and is able to manage Online
PIN as CVM for Cash Withdrawal.

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Micro ATM

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Enter transaction amount as: Rs.3000.00 for ATM and Micro ATM

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)
CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE04 = 00 00 00 30 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE52 is present

211/241 Confidential
uPay Device Validation Test Pla

DE22 = 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In Read Record command:
PAN (Tag 5A) = 6083749001010114
AUC (Tag 9F07) Byte 1, bit 7 = 1

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
In 0100/0200 message, DE2 (PAN) = Tag 5A (PAN) from Read Record
In 0100/0200 message, DE4 (Transaction Amount) = Tag 9F02 (Amount) from
first GENERATE AC
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
Application name shall be VRuPay
Card holder name shall be printed

Post Condition: NA

3.4.2 RUPAY.DEV.A.V002 – Balance Inquiry Transaction

RUPAY.DEV.A.V002
Test No: RUPAY.DEV.A.V002 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to correctly manage Balance inquiry
transaction for VRuPay card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:

212/241 Confidential
uPay Device Validation Test Pla

ATM
Micro ATM
Supports Balance inquiry

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following fields shall be:

DE02 = 6083749001010114
DE04 = 00 00 00 00 00 00
DE18 = 6011 (for ATM) / 6012 (for Micro ATM)
DE55.9F03 shall be present and is equal to 000000000000
DE55.9F02 shall be present and is equal to 000000000000
DE03 (first 2 digits) and DE55 Tag 9C is equal to 31
In the authorization response,
The following fields shall be:

DE39 = 00
DE54 = Present
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
In 0100/0200 message, DE02 (PAN) = Tag 5A (PAN) from Read Record
In 0100/0200 message, DE04 (Transaction Amount) = Tag 9F02 (Amount) from
first GENERATE AC
Charge Slip

Transaction type shall be “Balance inquiry”

213/241 Confidential
uPay Device Validation Test Pla

Balance Amount

Post Condition: NA

3.4.3 RUPAY.DEV.A.V003 – PIN Change

RUPAY.DEV.A.V003
Test No: RUPAY.DEV.A.V003 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage PIN change transaction for VRuPay
card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Supports PIN management

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234
Select PIN Change
Enter new PIN: 4321

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)
CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 Digit 1-2 = 90
DE04 = 00 00 00 00 00 00
DE52 is present
DE22 = 051

214/241 Confidential
uPay Device Validation Test Pla

DE120 Tag 001 = 08

DE55.9C =90

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

The terminal sends the issuer script command to the card
The card responds to the Issuer Script command with SW=9000

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

The terminal shall display “PIN Change successful”

Post Condition: NA

3.4.4 RUPAY.DEV.A.V004 – Mini Statement

RUPAY.DEV.A.V004
Test No: RUPAY.DEV.A.V004 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal is able to manage Mini Statement for VRuPay card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal is:

condition:
ATM
Supports Mini Statement

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter PIN: 1234

215/241 Confidential
uPay Device Validation Test Pla

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set as:

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)
CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 Digit 1-2 = 90

DE04 = 00 00 00 00 00 00
DE52 is present
DE22 = 051
DE55.9C =90
DE120.Tag 001 = 07
DE120 Tag 002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120 = Present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code

216/241 Confidential
uPay Device Validation Test Pla

Total Amount
Masked PAN
Application name shall be VRuPay
Card holder name shall be printed

Post Condition: NA

3.4.5 RUPAY.DEV.A.V005 – Mobile Banking Registration

RUPAY.DEV.A.V005
Test No: RUPAY.DEV.A.V005 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the Mobile Banking Registration is successful for VRuPay card

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Mobile Banking Registration

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Mobile Banking Registration
Enter the mobile number 915500112233 twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)

CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 = 90

217/241 Confidential
uPay Device Validation Test Pla

DE04 = 00 00 00 00 00 00
DE22 = 051
DE 48.074 = 915500112233
DE52 is present
DE55.9C =90
DE120.001 = UR
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = UR
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “MOBILE BANKING REGISTRATION SUCCESSFUL”.

Post Condition: NA

3.4.6 RUPAY.DEV.A.V006 – Aadhaar Number Seeding

RUPAY.DEV.A.V006
Test No: RUPAY.DEV.A.V006 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Aadhaar Number Seeding is successful for VRuPay card.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Aadhaar Number Seeding

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

218/241 Confidential
uPay Device Validation Test Pla

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234.
Choose Aadhaar Number Seeding
Enter the Aadhaar Number (100020003000) twice

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)

CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE48.066 = 100020003000
DE52 is present
DE55.9C =90
DE120.001 = AN
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = AN
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:

219/241 Confidential
uPay Device Validation Test Pla

Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “AADHAAR NUMBER UPDATED SUCCESSFULLY”
or similar message.

Post Condition: NA

3.4.7 RUPAY.DEV.A.V007 – Cheque Book Request

RUPAY.DEV.A.V007
Test No: RUPAY.DEV.A.V007 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Cheque Book Request is successful for VRuPay card

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports cheque book request

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cheque Book Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)

CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051

220/241 Confidential
uPay Device Validation Test Pla

DE52 is present
DE55.9C =90
DE120.001 = 36
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = 36
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CHEQUE BOOK REQUEST SUCCESSFUL”.

Post Condition: NA

3.4.8 RUPAY.DEV.A.V008 – Statement Request

RUPAY.DEV.A.V008
Test No: RUPAY.DEV.A.V008 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Statement Request is successful for VRuPay

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Statement Request

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.

221/241 Confidential
uPay Device Validation Test Pla

Enter the PIN as 1234

Choose Statement Request

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)

CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE120.001 = 37
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = 37
DE120.002 = GDN

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “STATEMENT REQUEST SUCCESSFUL”.

Post Condition: NA

222/241 Confidential
uPay Device Validation Test Pla

3.4.9 RUPAY.DEV.A.V009 – Card to Card Fund Transfer

RUPAY.DEV.A.V009
Test No: RUPAY.DEV.A.V009 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that Card to Card Fund Transfer is successful for VRuPay card.

Reference:
RuPay Interface Specification VAS Addendum Ver_1.2.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Card to Card Fund transfer

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Card to Card Fund Transfer
Enter beneficiary card number 6073841230000040 twice
Enter transfer amount Rs.5000.00

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:

DE02 = 6083749001010114
DE03 = 90
DE04 = 00 00 00 50 00 00
DE22 = 051
DE52 is present
DE55.9C =90
DE.103 = 6073841230000040
DE120.001 = FT
DE120.002 = SPT

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = FT

223/241 Confidential
uPay Device Validation Test Pla

DE120.002 = SPT

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “CARD TO CARD FUND TRANSFER
SUCCESSFUL”.

Post Condition: NA

3.4.10 RUPAY.DEV.A.V011 – Inter-Operable Cash Deposit - Third Party Account (based on card
number)
RUPAY.DEV.A.V011
Test No: RUPAY.DEV.A.V011 - Revision 0 - Number of sub cases: 0

Test Objective: To ensure that the terminal can able to manage Inter-Operable Cash Deposit to
Third Party Account for VRuPay card

Reference: RuPay - Online Switching Interface Specification_V1.7.3.pdf

Applicability This test is applicable only if the terminal:

condition:
Is ATM
Supports Inter-Operable Cash Deposit

Test Card ID: VRuPay Card Image 01

Precondition: No specific condition required

Test Procedure: Step 1: Validation leg

Insert the card in the chip reader and follow the instructions displayed on the
screen.
Enter the PIN as 1234
Choose Cash deposit
Choose ‘Third Party Account’
Enter Beneficiary Card Number
Step 2: Deposit leg
Deposit the following notes when terminal prompts for the same
Rs.2000 x No.1

224/241 Confidential
uPay Device Validation Test Pla

Rs.500 x No.2
Rs.100 x No.5
Rs.50 x No.10
Terminal displays the denomination and total amount of the deposited notes,
confirm the same.

Pass Criteria: Step 1: Validation leg

The terminal shall perform a complete transaction.
In the authorization request,

TVR byte 2, bit 8 = 0 - ICC and terminal have same application

versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
TVR byte 3, bit 3 = 1 - Online PIN is entered
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)

CVM results = 020000

The following fields shall be:

DE02 = 6083749001010114
DE03 = 90
DE04 = 00 00 00 00 00 00
DE22 = 051
DE52 is present
DE55.9C = 90
DE103 = 6073841230000016DE120.001 = CQ
DE120.002 = GDN

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE120.001 = CQ
DE120.002 = GDN
DE120.046 = “ABCDEFGHIJKL” Beneficiary Name
DE120. 080 is present Deposit ID
The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC

225/241 Confidential
 uPay Device Validation Test Pla

Card responds with ARQC (Tag 9F27 = '80')

In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall display message “DEPOSIT CURRENCY”.

Step 2: Deposit leg

The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:

DE02 = 6083749001010114
DE03 = 90
DE04 = 00 00 00 40 00 00
DE103 = 6073841230000016
DE120.001 = CD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120.080 is present
In the authorization response,
The following fields shall be:

DE39 = 00
DE120.001 = CD
DE120.002 = GDN
DE120.063 = 2000001050000201000050050010
DE120. 080 is present Deposit ID

Post Condition: NA

3.5 ATM Certification Test Scenarios - JCB

3.5.1 RUPAY.DEV.A.JCB001 – T=1 protocol

RUPAY.DEV.A.JCB001
Test No: RUPAY.DEV.A.JCB001

Test Objective: To ensure ATM can:

Successfully completes J/Smart transaction.
Performs cardholder verification correctly according to CVM list.
Communicates using T=1 protocol.
Processes with payment system proprietary data.

226/241 Confidential
uPay Device Validation Test Pla

Processes with 1408 bit length CA Public Key.

Processes with 1104 bit or longer ICC Public Key.
Performs Offline Enciphered PIN Verification with 1104 bit or longer ICC Public Key
or PIN Encipherment Public Key.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable when

condition:
Card supports: T= 1 protocol
Terminal Type: 11, 14, 21, 24

Test Card ID: JCB card image 01

Precondition: No specific condition required

Test Procedure: Perform a transaction with an amount mentioned below using test card for Test
Case 02.
Enter transaction amount as: Rs.500

Pass Criteria: Transaction is approved online for terminal type 11, 14, 21, 24
In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)The following fields shall
be:

DE02 = 3569990010082211
DE04 = 00 00 00 05 00 00
DE22 = 051
DE52 = Present

CVM results = 020000In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

227/241 Confidential
uPay Device Validation Test Pla

Terminal requests ARQC

Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Charge Slip

The receipt contains AID

Approval Code
Total Amount
Masked PAN
Signature panel shall not be printed
Card holder name shall be printed
Transaction type shall be Cash Withdrawal
MID shall be printed
Transaction Date & Time shall be printed

Post Condition: NA

3.5.2 RUPAY.DEV.A.JCB002 – ATR containing proprietary historical bytes

RUPAY.DEV.A.JCB002
Test No: RUPAY.DEV.A.JCB002
Test Objective: Confirm successfully complete J/Smart transaction with an ICC with ATR
containing proprietary historical bytes.
Confirm perform cardholder verification correctly according to CVM list.
Confirm processes with 1408 bit length CA Public Key.

Reference: RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability (Online only
condition: terminals).

Test Card ID: JCB card image 02

Precondition: No specific condition required

Test Procedure: Perform a transaction with an amount below the terminal floor limit using test
card for Test Case 08.
Enter transaction amount as: Rs.400

Pass Criteria: Transaction is approved online for terminal type 11, 14, 21, 24
In the authorization request,
The following TVR bit shall be set as:

228/241 Confidential
 uPay Device Validation Test Pla

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)

The following fields shall be:

DE02 = 3569990010082211
DE04 = 00 00 00 04 00 00
DE22 = 051
CVM Results = 420300

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.6 ATM Certification Test Scenarios – UPI

3.6.1 RUPAY.DEV.A.UPI001 – Card without PSE

RUPAY.DEV.A.UPI001
Test No: RUPAY.DEV.A.UPI001
Test Objective: To validate ATM is able to display multiple applications while inserting UPI card
without PSE and complete the credit transaction successfully when the Cardholder
name extended (9F0B) present and contain Chinese characters, and Cardholder
name(5F20) absent

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable only if the terminal supports:

condition:

229/241 Confidential
uPay Device Validation Test Pla

Cardholder selection of application.

Online PIN transaction.

Test Card ID: UPI card image 02

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose ‘UICC Credit’.
3. Enter "200.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal shall perform a complete transaction.

The following TVR bit shall be set as:

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

In the authorization request,

DE02 = 6210948000000029
DE04 = 00 00 00 02 00 00
DE22= 051

In the authorization response,

The following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

Tag 9F08 = Present

Tag 5F20 = Absent
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

230/241 Confidential
uPay Device Validation Test Pla

Following criteria shall be verified in terminal:

The terminal displays three applications (UICC Credit, UICC Debit and UICC Quasi
Credit) while conducting the application selection;

Charge Slip

The receipt contains AID

Transaction Date and Time
Transaction Certificate shall be printed
Approval Code
Total Amount
Masked PAN
Signature panel shall not be printed
Transaction type shall be Cash / Cash Withdrawal

Post Condition: NA

3.6.2 RUPAY.DEV.A.UPI002 – Issuer script processing and cardholder name absent in chip
RUPAY.DEV.A.UPI002
Test No: RUPAY.DEV.A.UPI002
Test Objective: To validate ATM is able to perform the issuer script correctly and Track2
Equivalent Data (Tag57) on the chip is correctly sent to Issuer and the cardholder
name(5F20,9F0b) are absent

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 03

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Debit'.
3. Enter "300.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion.

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request, the following fields shall be:
The following TVR bit shall be set:

TVR byte 1, bit 8 = 1 - Offline data authentication is not performed.

231/241 Confidential
uPay Device Validation Test Pla

TVR byte 2, bit 8 = 0 - ICC and terminal have same application versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful.
TVR byte 3, bit 3 = 1 - Online PIN is entered
TVR byte 5, bit 5 = 0 - Scripting processing not failed after final GEN AC

DE02 = 6210948000000037
DE04 = 00 00 00 03 00 00
DE22 = 051
DE35= Present
DE52- Present

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
DE55 Tag 72 is present with PUT DATA command
The following criteria shall be verified in card log:
DE35 = Tag57
Tag 5F20 = Absent
Tab 9F0B = Absent
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
Terminal shall send the following Issuer script command after second GENERATE
AC command:

Application Unblock command – 84 18 00 00 04 MAC

Post Condition: NA

3.6.3 RUPAY.DEV.A.UPI003 – To validate 1st digit of service code

RUPAY.DEV.A.UPI003
Test No: RUPAY.DEV.A.UPI003
Test Objective: To validate ATM is able to complete the credit transaction correctly and terminal
will only check the first digit of the service code. Terminal support the track 1
data contain Chinese characters

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

232/241 Confidential
uPay Device Validation Test Pla

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 04

Precondition: No specific condition required

Test Procedure: 1. Please swipe a card first and the terminal shall prompt to use a chip card.
2. Please insert a card and select purchase function.
3. Choose 'UICC Credit'.
4. Enter "400.00" as transaction amount.
5. Enter a correct online PIN as 1234.
6. Processing completion

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 2, bit 8 = 0 - ICC and terminal have same application
versions
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful

The following fields shall be:

DE02 = 6210948000000045
DE04 = 00 00 00 04 00 00
DE22 = 051
DE35 = Present
In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
The following criteria shall be verified in card log:
In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

233/241 Confidential
uPay Device Validation Test Pla

3.6.4 RUPAY.DEV.A.UPI004 – Quasi credit card with Chinese character in AID

RUPAY.DEV.A.UPI004
Test No: RUPAY.DEV.A.UPI004

Test Objective: To validate ATM is able to complete the quasi credit transaction correctly when
the application Label(Tag:50) and Application Preferred Name(Tag:9F12) contain
Chinese Characters

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 05

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose “UICC Credit”.
3. Enter "500.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set as:

TVR byte 1, bit 8 = 1 - Offline data authentication is not

performed
TVR byte 3, bit 8 = 0 - Cardholder Verification is successful
IAD byte 5, bit 5 = 0 & bit 6 =1 ARQC (9F10.B5 = A0)
DE02 = 6210948000000052
DE04 = 00 00 00 05 00 00
DE22 = 051
DE35 = Present

In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present
The following criteria shall be verified in card log:
In first GENERATE AC command:
Terminal requests ARQC

234/241 Confidential
uPay Device Validation Test Pla

Card responds with ARQC (Tag 9F27 = '80')

In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')
The terminal shall perform a complete transaction:

The terminal displays three applications (UICC Credit, UICC Debit and UICC
Quasi Credit) while conducting the application selection.

Post Condition: NA

3.6.5 RUPAY.DEV.A.UPI005 – Application is not effective

RUPAY.DEV.A.UPI005
Test No: RUPAY.DEV.A.UPI005
Test Objective: To validate ATM is able to behave correctly during the credit transaction when
UnionPay application is not effective.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 06

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Credit'.
3. Enter "700.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing completion.

Pass Criteria: The terminal goes online to complete the transaction;

In the authorization request,
The following TVR bit shall be set:

TVR byte 2, bit 6 = 1 - Application not yet effective

The following fields shall be:

DE02 = 6210948000000169
DE04 = 00 00 00 07 00 00
The following criteria shall be verified in card log:

235/241 Confidential
uPay Device Validation Test Pla

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.6.6 RUPAY.DEV.A.UPI006 – Different application version number

RUPAY.DEV.A.UPI006
Test No: RUPAY.DEV.A.UPI006
Test Objective: To validate ATM is able to behave correctly during the credit transaction
when the application version number is different.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 07

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Credit'.
3. Enter "800.00" as transaction amount.
4. Enter a correct online PIN as 1234
5. Processing completion

Pass Criteria: The terminal goes online to complete the transaction;

The following TVR bit shall be set:

TVR byte 2, bit 8 = 1 - Card and terminal have different application

versions

In the authorization request, the following fields shall be:

DE02 = 6210948000000177
DE04 = 00 00 00 08 00 00
DE22 = 051
DE52 = Present

236/241 Confidential
uPay Device Validation Test Pla

The following criteria shall be verified in card log:

Terminal shall not send a VERIFY command

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests AAC
Card responds with AAC (Tag 9F27 = '00')

Post Condition: NA

3.6.7 RUPAY.DEV.A.UPI007 – Fallback when application selection failed

RUPAY.DEV.A.UPI007
Test No: RUPAY.DEV.A.UPI012

Test Objective: To validate ATM is able to conduct fallback transaction correctly when
application selection is failed.
Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 08

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Swipe a card after the message is displayed.
3. Enter "1000.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing completion.

Pass Criteria: Fallback is supported

Need to verify in Terminal:
The terminal shall prompt to swipe the card by displaying a message similar to
“PLEASE SWIPE CARD” or “USE MAGSTRIPE”.
In the authorization request,
The following fields shall be:

DE02 = 6210948000000193
DE04 = 00 00 00 10 00 00
DE22 = 801
DE23 = Absent
DE52 = Present

237/241 Confidential
uPay Device Validation Test Pla

DE55 = Absent
DE61.SF7 = 2

In the authorization response,

The following fields shall be:

DE39 is equal to 00
DE55 is absent

Post Condition: NA

3.6.8 RUPAY.DEV.A.UPI008 – Symmetric algorithm (SM) - Normal transaction

RUPAY.DEV.A.UPI008
Test No: RUPAY.DEV.A.UPI008
Test Objective: To validate ATM is able to complete the Debit transaction correctly when the
Union pay IC card support Symmetric algorithm (SM)

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 09

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Debit'.
3. Enter "1300.00" as transaction amount.
4. Enter a correct online PIN as 1234.
5. Processing to completion.

Pass Criteria: The terminal goes online to complete the transaction;

The following TVR bit shall be set as:

TVR byte 3, bit 3 – 1 - Online PIN entered

In the authorization request,

DE02 = 6210948000000219
DE04 = 00 00 00 13 00 00
DE22 = 051
DE52 = Present
In the authorization response, the following fields shall be:
DE39 = 00

238/241 Confidential
uPay Device Validation Test Pla

DE55–Tag 91 is present

The following criteria shall be verified in card log:

1st CVM in Tag 8E = 42 03

In first GENERATE AC command:
Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')
In second GENERATE AC command:
Terminal requests TC
Card responds with TC (Tag 9F27 = '40')

Post Condition: NA

3.6.9 RUPAY.DEV.A.UPI009 – CVM Absent

RUPAY.DEV.A.UPI009

Test No: RUPAY.DEV.A.UPI009

Test Objective: To validate ATM is able to behave correctly when the CVM list(Tag 8E) is absent

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 13

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Credit'.
3. Enter "1800.00" as transaction amount.
4. Terminal shall not continue the transaction

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 1, bit 6 = 1 -ICC Data missing

The following fields shall be:

DE02 = 6210948000000243
DE04 = 00 00 00 18 00 00
DE52 is present
In the authorization response, the following fields shall be:

239/241 Confidential
uPay Device Validation Test Pla

DE39 = 00
DE55 –Tag 91 is present

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

Post Condition: NA

3.6.10 RUPAY.DEV.A.UPI010 – Unknown CVM

RUPAY.DEV.A.UPI010

Test No: RUPAY.DEV.A.UPI010

Test Objective: To validate ATM is able to behave correctly when the CVM list(Tag 8E) is unknown

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 10

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Debit'.
3. Enter "1900.00" as transaction amount.
4. Terminal shall not continue the transaction

Pass Criteria: The terminal shall perform a complete transaction.

In the authorization request,
The following TVR bit shall be set:

TVR byte 3, bit 7 = 7 -Unrecognized CVM

The following fields shall be:

DE02 = 6210948000010242
DE04 = 00 00 00 19 00 00
DE52 is present
In the authorization response, the following fields shall be:

DE39 = 00
DE55 –Tag 91 is present

240/241 Confidential
uPay Device Validation Test Pla

The following criteria shall be verified in card log:

In first GENERATE AC command:

Terminal requests ARQC
Card responds with ARQC (Tag 9F27 = '80')

Post Condition: NA

3.6.11 RUPAY.DEV.A.UPI011 – AUC exceeds the region and service type restrictions
RUPAY.DEV.A.UPI011

Test No: RUPAY.DEV.A.UPI011

Test Objective: To validate ATM is able to behave correctly when the Application Usage Control
(AUC Tag: 9F07) exceeds the region and service type restrictions.

Reference: [REF] : RuPay Chip Terminal Implementation Requirements Guide

Applicability This test is applicable to terminals with online processing capability.

condition:

Test Card ID: UPI card image 11

Precondition: No specific condition required

Test Procedure: 1. Please insert a card and select Cash Withdrawal function.
2. Choose 'UICC Credit'.
3. Enter "2000.00" as transaction amount.
4. Enter a correct online PIN as 1234 if required.
5. Processing to completion

Pass Criteria: The terminal shall reject the transaction displaying “Transaction Not Allowed”.

The transaction must be declined.

The following criteria shall be verified in card log:

TVR byte 2, bit 5 = 1

Post Condition: NA
~ End of Document ~

241/241 Confidential