paypass userguide

8/19/2019 PayPass UserGuide

1/252

PayPass M-TIP TestCase User Guide

November 2013


2/252

Copyright The information contained in this manual is proprietary andconfidential to MasterCard International Incorporated (MasterCard)and its members.

This material may not be duplicated, published, or disclosed, inwhole or in part, without the prior written permission ofMasterCard.

Media This document is available in both electronic and printed format.

MasterCard Worldwide - CCoEChaussée de Tervuren, 198AB-1410 WaterlooBelgium

Fax: +32 2 352 5353


3/252

Table of Contents

© 2013 MasterCardPayPass M-TIP Test Case User Guide • November 2013 i

1 Using this Manual ...............................................................................................................................................1

1.1 Scope ............................................................................................................................................................1

1.2 Audience ................................................................ ................................................................. ......................1

1.3 Terminology .................................................................................................................................................1

1.4 Document structure ........................................................... ................................................................. ..........2

1.5 Related Publications .......................................................................................... ..........................................2

1.6 Abbreviations ..................................................................................................... ..........................................3

1.7 Notations ............................................................... ................................................................. ......................4

1.8 History ........................................................ ................................................................... ...............................4

2 Introduction .........................................................................................................................................................5

2.1 Terminal Integration Testing Process ..........................................................................................................5

2.2 Introduction to the M-TIP Cards ............................................................ ......................................................6 2.3 Testing configuration requirements .............................................................................................................7

3 Test Cases ............................................................................................................................................................8

3.1 Test Case Template Description ............................................................. ......................................................8

3.2 Common PayPass M/Chip Test Cases ............................................................... ........................................ 10 TC001 - Regression – card does not support any ODA ......................................................... ............................. 10 TC002 - Regression – CDA ................................................................. ............................................................... 11 TC003 - Regression – different CA key lengths ......................................................... ........................................ 11 TC004 - Regression – exponent 2^16+1 ............................................. ............................................................... 12 TC005 - Regression – Offline-only & ARQC ............................................................................................ ........ 12 TC006 - Integration/capabilities – No SDA .......................................................................... ............................. 13 TC011 - Interoperability – various uncommon data/length ............................................................... ................. 13 TC012 - Interoperability – CDOL1 includes tags forbidden in DE 55 ............................................................... 14 TC021 - Integration/capabilities – OfflinePIN not supported in PayPass .......................................................... 14 TC024 - Integration/capabilities – cardholder receipt .................................................................... .................... 15 TC025 - Integration/capabilities – refund ................................................................... ........................................ 15 TC026 - Integration/capabilities – Data Storage ................................. ............................................................... 16 TC028 - Integration/capabilities – ATM display ................................................................. ............................... 16 TC031 - Integration/CVM – only NoCVM below the CVM limit ..................................................................... 17 TC034 - Integration/CVM – ATM ..................... ................................................................... ............................. 17 TC035 - Integration/CVM – noCVM above the CVM Required limit ............................................................... 18 TC037 - Integration/Mobile – Non-[ PayPass3.0 ] terminal vs Mobile device .................................................... 18 TC038 - Integration/Mobile – On-Device cardholder verification requested ..................................................... 19 TC041 - Integration/online message – Gratuities / ‘Tips’ ................... ............................................................... 19 TC042 - Integration/online message – Issuer response: successful ................................................ .................... 20 TC043 - Integration/online message – Issuer response: unsuccessful ............................................ .................... 20 TC045 - Integration/online message – Issuer response contains script .............................................................. 21 TC046 - Integration/online message – Network mandatory data not in CDOL1 ............................................... 21 TC047 - Integration/online message – PAN sequence number from chip .......................................................... 22 TC048 - Integration/online message – PAN sequence number not returned ...................................................... 22 TC049 - Integration/online message – Full Grade ................................................................ .............................. 23 TC050 - Integration/online message – PayPass Values in Existing Authorization Fields ................................. 24 TC051 - Integration/online message – Online PIN ................................................................ ............................. 24 TC052 - Integration/online message – Issuer response: wrong Online PIN ....................................................... 25 TC053 – Integration/online message – Track 2 Equivalent Data must be used in the authorization request ..... 25 TC054 - Integration/online message – CVM Results in authorization message ................................................. 26 TC055 - Integration/online message – Device Type data element in the authorization request ......................... 26 TC061 - Integration/configuration – Contactless Transaction Limit .................................................................. 27


4/252

Table of Contents

ii© 2013 MasterCard

PayPass M-TIP Test Case User Guide • November 2013

TC062 - Integration/configuration – Terminal application version number for PayPass - M/Chip is ′0002′ ..... 28 TC063 – Integration/configuration – Manual Cash Advance ............................................................................. 28 TC065 - Integration – PIX extension .............................................................. .................................................... 29 TC066 - Integration – service code indicates a chip is present on card .............................................................. 29 TC067 - Integration – service code indicates Online PIN .................................................................................. 30

TC068 - Integration – Transaction declined (not ATM)................................................................. .................... 30 TC068b - Integration – Transaction declined (ATM) .......................... .............................................................. 31 TC070 - Integration – Application Selection without cardholder assistance ...................................................... 32 TC072 - Integration – PIN entry canceled .................................................................. ........................................ 32

3.3 MasterCard PayPass M/Chip Test Cases .......................................................................................... ........ 33 TC201 - Regression – SDA ................................................................................................. ............................... 33 TC221 - Integration/CVM – attended terminal ................................... ............................................................... 33 TC222 - Integration/CVM – CAT1 ............................... ................................................................. .................... 34 TC223 - Integration/CVM – CAT2 and CAT3............................................... .................................................... 35 TC260 - Integration/configuration – Purchase with Cash Back ................................. ........................................ 36

3.4 Maestro PayPass M/Chip Test Cases..................................................... .................................................... 37 TC401 - Integration/capabilities – No PayPass Mag Stripe .............................................................. ................. 37 TC410 - Integration/CVM – Online PIN above the CVM Required Limit ........................................................ 37

3.5 PayPass Mag Stripe Test Cases ............................................................. .................................................... 38 TC601 - Interoperability – various uncommon data/length ............................................................... ................. 38 TC610 - Integration – Building the discretionary data ................................................................... .................... 38 TC611 - Integration – Service Code checking ............................................................ ........................................ 39 TC612 - Integration – ATC in discretionary data ................................................................ ............................... 39 TC613 - Integration – Issuer response: unsuccessful ..................................... .................................................... 40 TC614 - Integration – Traditional Mag Stripe ............................................................ ........................................ 40 TC615 - Integration – Track 1 and Track 2 data are processed independently .......................................... ........ 40 TC616 - Integration – Track1 data not fully populated ...................................................................................... 41 TC681 - Integration/Mobile – Non-[ PayPass3.0 ] terminal vs Mobile device (Mag-Stripe) .............................. 41 TC682 - Integration/Mobile – On-Device cardholder verification not requested ............................................... 42

TC683 - Integration/Mobile – On-Device cardholder verification requested ..................................................... 43

TC684 - Integration/Mobile – PIN verification successful ................................................................................. 44

4 Test Scenarios for M-TIP Subset 8 .............................................................. .................................................... 45

4.1 M-TIP Subset 8 card details ................................................................... .................................................... 45

4.2 Using the Test Cards .............................................................................. .................................................... 47

4.3 Test Scenario Template Description ........................................... ............................................................... 47

4.4 Test Scenarios for MasterCard PayPass M/Chip .......................................................... ............................. 50

4.5 Test Scenarios for Maestro PayPass M/Chip ........................................................................................... 146

5 Test Scenarios for M-TIP Subset 6 .............................................................. .................................................. 222

5.1 M-TIP Subset 6 card details ................................................................... .................................................. 222

5.2 Using the Test Cards .............................................................................. .................................................. 223

5.3 Test Scenario Template Description ........................................... ............................................................. 223

5.4 Test Scenarios for PayPass Mag Stripe ................................................. .................................................. 224

6 Annexes ................................................................................................ ............................................................ 245

6.1 RSA Keys used ....................................................... .................................................................... ............... 245

6.2 DES Keys used .............................................................................................................. ........................... 247

6.3 DES Key Used for PVV and CVC.............................................................................................. ............... 248


5/252

Using this Manual

© 2013 MasterCardPayPass M-TIP Test Case User Guide • November 2013 1

1 Using this ManualThis chapter contains information that helps you understand and use this document.

1.1 ScopeThis document lists the PayPass Mag Stripe and PayPass M/Chip test cases and testscenarios used for the PayPass M-TIP.

1.2 Audience

This document is intended for use by terminal vendors and Acquirers who want toobtain approval for their PayPass implementation.

1.3 Terminology'Terminal' vs. 'reader'

In many cases the PayPass reader is separate from the POS terminal. However, whendealing with M-TIP it makes more sense to consider both the separate “reader” andthe POS terminal as a single device. Therefore this document will use the term“terminal” or “ PayPass terminal” in order to refer to:

the device providing the contactless interface used by the PayPass card and

the device supporting the PayPass application and

the device sending the authorization/clearing messages online.

'Card'

This document uses the term "card" or "M-TIP card" but the test tool could also be acard simulator or a probe.

'Contactless Transaction Limit'

This document uses the term "Contactless Transaction Limit" in order to refer to:

the "Terminal Contactless Transaction Limit" (used in [ PayPass2.x ] and[ PPReq2013 ])

the "Reader Contactless Transaction Limit (No On-device CVM)" (used in[ PayPass3.0 ])


6/252

Using this Manual

2© 2013 MasterCard


1.4 Document structureThis document includes 4 sections:

Introduction: this section gives some details about the test cards and the testingconfiguration requirements.

Test cases: this section lists the high level test cases that are linked to individualrequirements extracted from the specifications. Most of the high level test casesare split into several test scenarios in order to test all terminal types. The highlevel test cases first row is in blue.

TC011 - Interoperability – various uncommon data/length

Test scenarios: this section lists the test scenarios that will be used during thetesting session. The test scenarios first row is in black.In the second row, the objective contains a reference to the related high level test

case in square brackets.PPC MCD 02 Test 02 Scenario 01

ObjectiveTo ensure the terminal correctly behaves when it receivesuncommon data value or length from the card. [TC011]

Annexes: this section lists some test cards cryptography details.

1.5 Related PublicationsThe following publications contain information related to the contents of this manual.

PPReq201 3 PayPass - M/Chip Requirements, 3 July 201 3

ATM2013 MasterCard Contactless ATM Implementation Requirements

12 June 2013

MChip201 3 M/Chip Requirements – 20 September 201 3

CustomerIntfce Customer Interface Specification – 21 May 2013

PayPass3.0 PayPass – M/Chip Reader Card Application Interface SpecificationV3.0. 2 – May 2013

EMV Contactless Book C-2 - Kernel 2 v2.3 – February 2013

PayPass2.1 PayPass – M/Chip Reader Card Application Interface Specification(V2.1) + PayPass M/Chip ApplicationNote#18 (April 12, 2010)

PayPass2.0 PayPass – M/Chip Reader Card Application Interface Specification(V2.0) + PayPass M/Chip ApplicationNote#15 (April 2, 2009)

PayPass2.x [PayPass2.1] or [PayPass2.0]

MTIPguide M-TIP Process Guide – 15 May 2013

QualifiedTools M/Chip Qualified Test Tools


7/252

Using this Manual


1.6 AbbreviationsThe following abbreviations are used in this manual:

Abbreviation Description

AAC Application Authentication Cryptogram

AFL Application File Locator

AID Application Identifier

AIP Application Interchange Profile

ARQC Authorization Request Cryptogram

ATC Application Transaction Counter

CA Public Key Certification Authority Public Key

CDA Combined DDA/AC generation

CDOL Card Risk Management Data Object List

CVM Cardholder Verification Method

EMV Europay MasterCard Visa

IAC Issuer Action Code

ICC Integrated Circuit Card

M/Chip MasterCard Chip

PAN Primary Account Number

PDOL Processing Data Object List

PIN Personal Identification Number

POS Point of Sale

PPSE PayPass Payment System Environment

RFU Reserved for Future Use

RID Registered Application Provider Identifier

SDA Static Data Authentication

SE Subelement

TAC Terminal Authentication Code

TC Transaction Certificate

TVR Terminal Verification Results


8/252

Using this Manual

4© 2013 MasterCard


1.7 NotationsThe following notations apply:Notation Description

‘0’ to ‘9’ and ‘A’ to ‘F’ 16 hexadecimal digits. Values expressed in hexadecimal form areenclosed in single quotes (i.e. ‘_’).

1001b Binary notation. Values expressed in binary form are followed by alower case ‘b’.

‘abcd’ an or ans string.

[…] Optional part.

xx Any value.

1.8 HistoryThe following lists the main changes:Version Changes

September 2012 New version aligned with [ PPReq2011 ]

December 2012 Various updates

February 2013 Various updates

April 2013 Various updates

August 2013 Various updates

November 2013 Aligned with [ PPReq2013 ] and [ ATM2013 ]. The main changes arehighlighted in the document.


9/252

Introduction


2 IntroductionThis chapter contains an introduction to the M-TIP testing processes and the M-TIPcards.

2.1 Terminal Integration Testing ProcessThe M-TIP process defined in [ MTIPprocess ] is applicable for PayPass terminalssupporting [ PayPass2.x ] or [ PayPass3.0 ].

Acquirers must complete the M-TIP process before deploying and using a terminal ina live environment.

The objective of the M-TIP process is to ensure the terminal meets the MasterCardrequirements described in [ PPReq2013 ].

The current document describes:

the M-TIP test cases that are defined to ensure the correct implementation ofthe MasterCard requirements.

the test scenarios that must be executed in M-TIP. The test scenarios refer toone or several test cases. Each test scenario involves an M-TIP card.

A Test Scenario is a short test procedure permitting to check one or severalspecification requirements identified in the Test Cases. This is outlined in the figure

below:

Test Case # 1 Objective+

Test Case # 2 Objective+

Test Case # 3 Objective

Card xx

Specifications(requirements)

Test Cases

Test Scenario

TIPcards


10/252

Introduction

6© 2013 MasterCard


2.2 Introduction to the M-TIP Cards

About M-TIP Cards

MasterCard has designed sets of test cards, to allow the acquirer to test that the hostand terminal payment applications are compliant with MasterCard requirements. TheM-TIP cards are grouped into different “subsets” in order to allow targeted testing.For the M-TIP process, the following PayPass subsets are used.

For PayPass – M/Chip terminals, the Subset 6 ensures that the PayPass – M/Chipterminals correctly work with PayPass – Mag Stripe cards.

Note that the Subset 6 is also used during Network Interface Validation (NIV) tests of PayPass Mag Stripe terminals. However the current document is M-TIP-focused sothe Subset 6 will sometimes be referred to as "M-TIP Subset 6".

The Subset 8 ensures that the PayPass – M/Chip terminals correctly work with PayPass – M/Chip cards.

Number of Cards

The following table summarizes the content of the PayPass M-TIP Subsets.

Note that the tests defined in this document do not use all the cards above. The fewunused cards may be removed in the next future.

Subset Type Number of cards

Subset 6 PayPass Mag Stripe cards 1 2

PayPass M/Chip cards 1

Subset 8

MasterCard PayPass M/Chip cards 20

Maestro PayPass M/Chip cards 20

Combo cards (both MasterCard and MaestroPayPass M/Chip)

2

Total Number of cards 5 5


11/252

Introduction


2.3 Testing configuration requirementsDuring the M-TIP testing session, the terminal configuration must be as close as

possible as it will be in the live environment. In particular, the terminal must be

configured as follows. The list of Application Identifiers (AID) supported by the terminal must be

the ones intended for live deployment.

Application Version Number PayPass Mag Stripe: Terminal Applicationversion number shall be set to ‘0001’ for PayPass – Mag Stripe.

Application Version Number PayPass M/Chip: Terminal Application versionnumber shall be set to ‘0002’ for PayPass – M/Chip.

The Terminal Contactless Transaction Limit shall have the same value as inthe field for MasterCard and Maestro applications.

The Terminal Contactless Transaction Limit (On-Device CVM), whenapplicable, shall have the same value as in the field for MasterCard andMaestro applications.

The Terminal Contactless Floor Limit shall have the same value as in thefield for MasterCard and Maestro applications

The Terminal CVM Required Limit shall have the same value as in the fieldfor MasterCard and Maestro applications.

However the Certification Authority Public Keys shall be the test keys definedfurther in the section "RSA Keys used ".

Note that the test keys must be removed from the terminal before any deployment.


12/252

Test Cases

8© 2013 MasterCard


3 Test CasesThis chapter lists the high level PayPass M/Chip M-TIP Test Cases.

3.1 Test Case Template DescriptionOverview

Below is an example of Test Case. This template is described here after.

TC002 - Regression – CDA

Objective To ensure that the PayPass terminal performs CDA correctly.

Applicability Terminal supports CDA

Reference [ PPReq2013 ]: Section “ 2.4.5 Offline Data Authentication Requirements ” p2 -11

Test ConditionsThe transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that CDA is supported.Data returned by card is such as the transaction can be approved offline*.

Pass CriteriaThe terminal shall send request a TC with CDA (‘50’) in the Generate AC.Transaction shall be approved offline.

Note *: most of the PayPass terminals will bypass the CDA if the transaction is declined or sentonline, see the transaction flow in technical specifications.

Test Case nameTC002 - Regression – CDA

The Test Case is as follows: TCxyy - [Test category] - [Test title].

TCxyy uniquely identifies the Test Case. It follows the below rules:

TC0yy: Common PayPass M/Chip Test Cases

TC2yy: MasterCard PayPass M/Chip Test Cases

TC4yy: Maestro PayPass M/Chip Test Cases

TC6yy: PayPass Mag Stripe Test Cases

[Test category] can be the following:

"Regression": major Level2 tests that are re-performed during M-TIP to ensure noregression occurs when integrating the product in the live environment.

"Interoperability": these tests are basic tests that are re-performed during M-TIP becausethey often led to interoperability issues.

"Integration": those tests ensure the PayPass terminal complies with the MasterCard

requirements defined in [ PPReq2013 ].


13/252

Test Cases


ObjectiveObjective To ensure that the PayPass terminal performs CDA correctly.

This is a short description of the objective of the test.

ApplicabilityApplicability Terminal supports CDA

This gives the conditions for the test to be applicable.

ReferenceReference [ PPReq2013 ]: Section “ 2.4.5 Offline Data Authentication Requirements ” p2 -11

This makes a reference to the related requirement in the specifications.

Test Conditions

Test ConditionsThe transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that CDA is supported.Data returned by card is such as the transaction can be approved offline*.

This lists all the conditions required for testing the objective.

Note: the test conditions often assume that the reader supports the "Contactless TransactionLimit". If not, it is obvious that the related condition shall be disregarded.

Pass CriteriaPass Criteria

The terminal shall send request a TC with CDA (‘50’) in the Generate AC.Transaction shall be approved offline.

This lists the conditions required in order to pass the test.

NoteNote *: most of the PayPass terminals will bypass the CDA if the transaction is declined or sentonline, see the transaction flow in technical specifications.

Some Test Cases include a note in order to clarify some test details.


14/252

Test Cases

10© 2013 MasterCard


3.2 Common PayPass M/Chip Test CasesThe test cases described in this section apply to terminals that accept either MasterCard PayPass or Maestro PayPass .

TC001 - Regression – card does not support any ODA

ObjectiveTo ensure the PayPass terminal correctly behaves when the card does not support anyoffline data authentication method.

Applicability As per below sub-cases

Reference Regression test – no specific reference

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that SDA, DDA and CDA are NOT supported.Tests are run for MasterCard and Maestro applications, when applicable:Case 1a: [if CVM Required Limit is not zero] amount is below the Floor Limit (andterminal is online capable)*Case 1b: [if CVM Required Limit is zero] amount is below the Floor Limit (and terminal isonline capable)Case 2: amount is above the Floor LimitCase 3: terminal is offline-only

Pass Criteria

The terminal will set the TVR byte 1 bit 8 (offline data authentication not performed).Cases 1 & 2: Online capable terminals shall request an ARQC as per TAC settings, even ifthe amount is below the Floor Limit.Case 3: Offline-only terminals will decline the transaction offline as per TAC settings.

Note *: if the CVM Required Limit is lower than the Floor Limit and if both the card and theterminal support Online PIN, the amount should be below the CVM Required Limit inorder to not set the TVR byte 3 bit 3 (“OnlinePIN entered”).


15/252

Test Cases


TC002 - Regression – CDA

Objective To ensure that the PayPass terminal performs CDA correctly.


Reference [ PPReq2013 ]: Section “ Offline Card Authentication ” p4-13

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that CDA is supported.Tests are run for MasterCard and Maestro applications, when applicable.Case 1: the amount is below the Floor Limit. Data returned by card is such that thetransaction can be approved offline*.Case 2 (terminal supports [PayPass3.0] ): the amount is above the Floor Limit

Pass Criteria

TVR byte 1 bit 8 is not set (offline data authentication was performed).TVR byte 1 bit 7 is not set (SDA did not fail).TVR byte 1 bit 4 is not set (DDA did not fail).TVR byte 1 bit 3 is not set (CDA did not fail).Case 1: The terminal shall request a TC with CDA (‘50’) in the Generate AC.The transaction shall be approved offline.Case 2: The terminal shall request an ARQC with CDA (‘ 90’) in the Generate AC. Thetransaction shall be approved online.

Note *: PayPass terminals supporting [PayPass2.x ] will bypass the CDA if the transaction isdeclined or sent online, see the transaction flow in technical specifications.

TC003 - Regression – different CA key lengths

ObjectiveTo ensure the PayPass terminal correctly supports different certification authority publickey lengths.

Applicability Terminal supports SDA or CDA


Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that SDA or/and CDA is supported.If the terminal supports [PayPass2.x ], data returned by card is such as the transaction can

be approved offline*.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: CA key length is 1152/144Case 2: CA key length is 1408/176Case 3: CA key length is 1984/248

Pass CriteriaThe TVR shall indicate that the ODA was performed: TVR byte 1 bit 8 = 0.Transaction shall be approved.



16/252

Test Cases



TC004 - Regression – exponent 2^16+1

Objective To ensure the PayPass terminal correctly supports the exponent 2^16+1.



Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that CDA is supported.ICC public key exponent is 2^16+1.If the terminal supports [PayPass2.x ], data returned by card is such as the transaction can

be approved offline*.Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaThe TVR shall indicate that the ODA was performed: TVR byte 1 bit 8 = 0.Transaction shall be approved.


TC005 - Regression – Offline-only & ARQC

ObjectiveTo ensure that offline-only PayPass terminal correctly behaves when the card erroneouslysends an ARQC.

Applicability Terminal is offline-only


Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 indicates that CDA is supported.The card is such as it always returns an ARQC.Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaThe offline-only PayPass terminal shall terminate the transaction upon reception of theARQC

Note


17/252

Test Cases


TC006 - Integration/capabilities – No SDA

Objective To ensure the PayPass terminal does not support SDA, when applicable.

Applicability Terminal does not support SDA

Reference [ PPReq2013 ]: Section “ Offline Card Authentication ” p 4-13

Test Conditions The card indicates in the AIP that it does support SDA but not CDA.

Pass Criteria

The terminal shall set the TVR byte 1 bit 8 "ODA was not performed".The terminal shall NOT set the TVR byte 1 bit 7 "SDA did not fail".The terminal shall NOT set the TVR byte 1 bit 3 "CDA did not fail".If the terminal is offline-only it will decline with an AAC as per the TACs.If the terminal is online capable then it will send an ARQC as per the TACs.

Note


ObjectiveTo ensure the PayPass terminal correctly behaves when it receives uncommon data valueor length from the card.

Applicability Always applicable

Reference Interoperability test – no specific reference

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.

The card returns the data defined below.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: Unknown tags (e.g. : ‘88’) in PPSE response Case 2: Service Code inconsistency between track2 (‘57’) and specific tag (‘5F30’) Case 3: Discretionary Data inconsistency between track2 (‘57’) and specific tag (‘9F20’) Case 4: Track1 discretionary data (tag ‘9F1F’) with maximum length (48 bytes) Case 5: Track2 (‘57’) with maximum acceptable length (37 digits)Case 6: Unrecognized CVM returned in the CVM listCase 7: IAD (‘9F10’) with maximum lengthCase 8: the signed record is padded up to 254 bytes with '00's. Card supports SDA only.Case 9: the signed record is padded up to 254 bytes with '00's. Card supports CDA.

Case 10: PayPass Third Party data (‘9F6E’) with length 5.Case 11: PayPass Third Party data (‘9F6E’) with length 32. Case 12: Application Capabilities Information data ('9F5D')Case 13: Terminal Risk Management data ('9F1D')

Pass Criteria

In all cases the terminal shall approve the transaction. Case 12: The terminal must not display or print any balance information.Case 13: Terminals implementing [ PayPass3.0 ] must return a correct value for the tag'9F1D'. Terminals implementing [ PayPass2.x ] must return zero for the tag '9F1D'.

Note


18/252

Test Cases



TC012 - Interoperability – CDOL1 includes tags forbidden in DE 55

ObjectiveTo ensure the PayPass terminal correctly behaves when the CDOL1 includes tags beingforbidden in the DE 55.

ApplicabilityTerminal is online capable.


Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The card requests ‘9F21’ (Transaction Time) and ‘9F40’ (Additional TerminalCapabilities) in CDOL1. Those data items are forbidden in DE 55.The network simulator validates the authorization message and returns the response '00'(Approved).Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaThe Terminal shall not send the tags ‘9F21’ and ‘9F40’ to the network. The Terminal shall approve the transaction.

Note

TC021 - Integration/capabilities – OfflinePIN not supported in PayPass

Objective To ensure the PayPass terminal does not support offlinePIN.


Reference [ PPReq2013 ]: “Cardholder Verification ” page 4-15

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The AIP byte 1 bit 5 indicates “Cardholder Verification supported”. The first CVM in the card CVM list is OfflinePIN.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: amount is below the CVM Required LimitCase 2: amount is above the CVM Required Limit

Pass CriteriaThe terminal does not send any VerifyPIN command.The CVM results byte 1 is different from '41'.The PayPass transaction completes successfully.

Note


19/252

Test Cases


TC024 - Integration/capabilities – cardholder receipt

Objective To ensure that the PayPass terminal is able to print a cardholder receipt.

Applicability Terminal supports receipt printing

Reference [ PPReq2013 ]: Section “ Receipts ” page 4-18

Test ConditionsTests are run for MasterCard and Maestro applications, when applicable.Case 1: amount is below the CVM Required LimitCase 2: amount is above the CVM Required Limit

Pass Criteria

The terminal shall approve the PayPass transaction.Case 1:The PayPass terminal shall be able to print a cardholder receipt in case thecardholder requests it.Case 2: The PayPass terminal must print a cardholder receipt.

Note

TC025 - Integration/capabilities – refund

Objective To ensure the PayPass terminal correctly performs refund.

Applicability Terminal supports refund

Reference [ PPReq2013 ]: Section “Refunds” page 4 -6

Test Conditions

- First step is to perform the purchase:The transaction amount must be below the Contactless Transaction Limit.- Second step is to perform the refund:If requested, the refund amount must be the same as the purchase amount.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: [terminal supports [PayPass2.0] ] PayPass M/Chip transaction to be refundedCase 2: [terminal supports [PayPass2.1] or [PayPass3.0] ] PayPass M/Chip transaction to

be refundedCase 3: PayPass Mag Stripe MasterCard transaction

Pass Criteria

Case 1:The first transaction is approved.In the second transaction, the end of the transaction is out of scope. At the end of therefund process, the terminal displays a message to inform the cardholder that refundhas been done successfully.

Case 2:The first transaction is approved.In the second transaction, the PayPass terminal requests an AAC. At the end of therefund process, the terminal displays a message to inform the cardholder that refundhas been done successfully.

Case 3:The first transaction is approved.At the end of the refund process, the terminal displays a message to inform thecardholder that refund has been done successfully.

Note


20/252

Test Cases



TC026 - Integration/capabilities – Data Storage

ObjectiveTo ensure the terminal correctly completes the payment transaction when the card supportsData Storage.


Reference No specific reference

Test Conditions

The card requests the tags '9F5C' and '9F40' in the PDOL.The card returns the Application Capabilities Information '01 05 00' (DS version 1, fieldoff request, CDA over AAC, Undefined SDS configuration**).The card returns the DS ID.AIP byte 1 bit 2 is set ("On-device cardholder verification supported").AIP byte 2 bit 8 is set ("EMV supported").The card returns the DSDOL.The network simulator returns the response ‘00’ (successful). Tests are run for MasterCard and Maestro applications, when applicable:

Case 1 [if the terminal does not support IDS]: the card only returns AIP and AFL in theGetPO response

Case 2 [if the terminal supports IDS]: whatever the DS Requested Operator ID provided inthe GetPO command, the card returns AIP, AFL and '9F5F 01 00' ("no slot available") inthe GetPO response

Case 3 [if the terminal supports IDS]: whatever the DS Requested Operator ID provided inthe GetPO command, the card returns AIP, AFL, '9F5F 01 40' (volatile slot), '9F7F' (DSUnpredictable Number), '9F7D 08 00…00' (DS Summary 1). When the GenAC commandincludes the DSDOL data then Summary2 and Summary3 are included in the SDAD.

Summary2=Summary1. Summary3Summary2.

Pass Criteria The terminal shall approve the transaction.

Note

TC028 - Integration/capabilities – ATM display

ObjectiveTo ensure all user instructions are displayed on the existing screen of the ATM.To ensure the contactless reader does not provide any instructions directly to the ATMuser.

Applicability The terminal is an ATM

Reference [ ATM2013 ]: Section “ Reader Display ” page 3-1

Test Conditions Visual check

Pass CriteriaThe ATM must display all user instructions on the existing screen.The reader must not provide any instructions directly to the ATM user.

Note


21/252

Test Cases


TC031 - Integration/CVM – only NoCVM below the CVM limit

ObjectiveTo ensure the PayPass terminal only supports ‘No CVM’ as the CVM method for

PayPass transactions below or equal to the defined limit.

Applicability The CVM Required limit is greater than zero

Reference [ PPReq2013 ]: Section “Terminal CVM Required Limit” page 4-9

Test ConditionsThe transaction amount must be below the CVM limit.The card CVM list includes other CVM methods before the ‘noCVM’ one. Tests are run for MasterCard and Maestro applications, unless not applicable.

Pass Criteria

The terminal shall approve the PayPass transaction.The terminal shall not prompt for PIN or print a signature receipt. The cardholderverification shall be successful:- TVR byte 3 bit 8 = 0

- CVM result shall be ‘1F 03 00’ or '1F 03 02'Note

TC034 - Integration/CVM – ATM

Objective To ensure the ATM correctly performs Cardholder Verification.

Applicability Terminal is an ATM.

Reference [ ATM2013 ]: Section “ CVM Requirements ”, page 3-3

Test Conditions

The transaction amount must be the smallest possible amount.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: card supports Signature and No CVM (‘5E03 1F03’). Case 2: card supports Online PIN, Signature and No CVM (’4203 5E03 1F03’).

Pass Criteria

Case 1: The cardholder verification shall fail: TVR byte 3 bit 8 = 1 CVM Result shall be ‘3F 00 01’

The ATM shall neither prompt for PIN nor request a signature. The ATM shall decline the transaction as per the TACs.

Case 2: The ATM shall request an ARQC. The terminal shall prompt for PIN.

TVR byte 3 bit 3 = 1 (Online PIN entered) CVM result shall be ‘42 03 00’ The ATM approves the transaction.

Note


22/252

Test Cases



TC035 - Integration/CVM – noCVM above the CVM Required limit

Objective To ensure the PayPass terminal does not support noCVM above the CVM Required Limit.

Applicability The CVM Required limit is lower than then Contactless Transaction limit

Reference [ PPReq2013 ]: Section “ Terminal CVM Required Limit ” p 4-9

Test ConditionsThe transaction amount must be above the CVM Required Limit.Tests are run for MasterCard and Maestro applications, when applicable:The card supports noCVM only (‘1F 03’).

Pass Criteria

The cardholder verification shall fail:- TVR byte 3 bit 8 = 1- CVM result shall be ‘3F 00 01’ - The terminal shall neither prompt for PIN nor request a signature.The outcome of the transaction is out of scope.

Note

TC037 - Integration/Mobile – Non-[ PayPass3.0 ] terminal vs Mobile device

ObjectiveTo ensure the terminal not supporting "On-device cardholder verification" correctlycompletes the transaction with a Mobile.

ApplicabilityTerminal does not support [ PayPass3.0] or the "Kernel Configuration" indicates "On-device cardholder verification NOT supported"

Reference Integration test – no specific reference

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.

AIP byte 1 bit 2 is set ("On-device cardholder verification supported").AIP byte 2 bit 8 is not set ("EMV NOT supported").The network simulator returns the response ‘00’ (successful). Tests are run for MasterCard and Maestro applications, when applicable:


Note


23/252

Test Cases


TC038 - Integration/Mobile – On-Device cardholder verification requested

Objective To ensure the terminal correctly completes the transaction with a Mobile.

Applicability Terminal supports [PayPass3.0] and On-Device cardholder verification


Test Conditions

AIP byte 1 bit 2 is set ("On-device cardholder verification supported").AIP byte 2 bit 8 is set ("EMV supported").The network simulator returns the response ‘00’ (successful). Tests are run for MasterCard and Maestro applications, when applicable:

- A first transaction is performed where the Mobile indicates that the Mobile PIN wassuccessfully verifiedCase 1: amount is below the CVM Required Limit.Case 2: amount is above the CVM Required Limit.- A second transaction is performed where the Mobile indicates "PIN verificationsuccessful"

Pass Criteria

In first transaction, the terminal shall display "Please see phone" (or equivalent).In second transaction, the terminal shall approve the transaction.Case 1: CVM results value must be '3F 00 02'Case 2: CVM results value must be '01 00 02'

Note

TC041 - Integration/online message – Gratuities / ‘Tips’

Objective To ensure the PayPass terminal correctly manages the gratuities, when supported.

Applicability Terminal supports gratuities

Reference [ PPReq2013 ]: “Gratuities” page 4-7

Test Conditions

The cardholder must enter a gratuity amount. The transaction amount plus the gratuityamount must be below the Contactless Transaction Limit.The network simulator validates the authorization message and returns a successfulresponse.

Tests are run for MasterCard and Maestro applications, when applicable.

Pass Criteria

The online authorization request must contain the sum of initial amount and gratuity in the'Amount authorized' field (DE 55 SE 9F02) and in DE 4.The 'Amount, other' field (DE 55 SE 9F03) must contain zeroes or be absent.The transaction shall be approved.

Note


24/252

Test Cases



TC042 - Integration/online message – Issuer response: successful

Objective To ensure the PayPass terminal correctly manages the Issuer response ‘00’ (successful).

Applicability Terminal is online capable

Reference [CustomerIntfce ] Section “Authorization Request Response ” page 4-83

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The card returns an ARQC.The network simulator validates the authorization message and returns the responses ‘00’(successful).Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaDE 55 SE 9F27 value in the network log shall be the same as returned by the card to thefirst GENERATE AC.The terminal shall approve the transaction upon reception of the network response.

Note

TC043 - Integration/online message – Issuer response: unsuccessful

ObjectiveTo ensure the PayPass terminal correctly manages the Issuer responses ‘51’ (insufficientfunds) and ‘57’ (Transaction not permitted).


Reference [CustomerIntfce ] Section “Authorization Request Response ” page 4-83

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The network simulator validates the authorization message and returns the responses

below.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: network simulator response is ‘51’ (insufficient funds) Case 2: network simulator response is ‘57’ (Transaction not permitted)

Pass Criteria The terminal shall decline the transaction upon reception of the network response.

Note


25/252

Test Cases


TC045 - Integration/online message – Issuer response contains script

ObjectiveTo ensure the PayPass terminal does not process the ICC response data erroneouslyreturned by the issuer.


Reference [ PPReq2013 ]: Section “A cquirer Network Requirements ” page 4 -21

Test Conditions

The transaction amount must be above the Floor Limit and below the ContactlessTransaction Limit.Card is let on the terminal until the transaction is completed or the ticket is printed.The network simulator validates the authorization message and returns the followingresponse:

- DE 39 (Response code) = '00' (Approved)- DE 55 SE 91 (Issuer Authentication Data) is present

- DE 55 SE 72 (Issuer Script Template 2) with one script identifier and 6 PINUnblock commands followed by a PIN Change Unblock.Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaThe terminal must not send any command to the card beyond the 1st Generate AC.The transaction must successfully complete.

Note

TC046 - Integration/online message – Network mandatory data not in CDOL1

ObjectiveTo ensure the PayPass terminal transmits transaction mandatory data to the network evenif it is not requested by the card in the CDOL1.



Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The card does not request Terminal Country Code (tag ‘9F1A’) , Transaction Date (tag‘9A’), Transaction Type (tag ‘9C’) nor Transaction Currency Code (tag ‘5F2A’) in theCDOL1.The network simulator validates the authorization message (not the ARQC) and returns theresponse '00' (Approved).Tests are run for MasterCard and Maestro applications, when applicable.

Pass Criteria

The Terminal shall send to the network: Terminal Country Code (tag ‘9F1A’) Transaction Date (tag ‘9A’) Transaction Type (tag ‘9C’) Transaction Currency Code (tag ‘5F2A’)

The Terminal shall approve the transaction.

Note


26/252

Test Cases



TC047 - Integration/online message – PAN sequence number from chip

ObjectiveTo ensure the PayPass terminal transmits the PAN sequence number coming from the chipand not from the Track2 equivalent data item.

ApplicabilityTerminal is online capable


Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The PAN sequence number value from the tag ‘5F34’ is different from the one in theTrack2 equivalent data item.The network simulator validates the authorization message and returns the response '00'(Approved).Tests are run for MasterCard and Maestro applications, when applicable.

Pass Criteria

The Terminal shall send the PAN sequence number value from the tag ‘5F34’ to thenetwork.The simulator must successfully validate the provided ARQC.The Terminal shall approve the transaction.

Note

TC048 - Integration/online message – PAN sequence number not returned

ObjectiveTo ensure the PayPass terminal does not transmit the PAN sequence number when it is notreturned by the card.



Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The PAN sequence number is not returned by the card.The network simulator validates the authorization message and returns the response '00'(Approved).Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaThe Terminal shall not send the PAN sequence number (DE 23) to the network.The Terminal shall approve the transaction.

Note


27/252

Test Cases


TC049 - Integration/online message – Full Grade

Objective To ensure that the PayPass terminal supports the Full Grade network messages.


Reference [ PPReq2013 ]: Section “ Authorization Requirements ” p4-23

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The network simulator validates the authorization message and returns the response '00'(Approved).Tests are run for MasterCard and Maestro applications, when applicable.Case 1: terminal is not an ATMCase 2: terminal is an ATM

Pass Criteria

The terminal shall approve the transaction.The terminal shall send a DE 55 message to the network.DE 55 SE 9F03 (Amount, Other) contains zeroes or is absent.

Case 1:DE 3 subfield 1 (transaction type code) value is '00' (purchase).

Case 2:DE 3 subfield 1 (transaction type code) value is '01' (withdrawal).DE 48 byte 1 value is 'Z'.

Note


28/252

Test Cases



TC050 - Integration/online message – PayPass Values in Existing Authorization Fields

ObjectiveTo ensure the PayPass terminal correctly manages the PayPass values in the existingauthorization fields.

ApplicabilityTerminal is online capable

Reference [ PPReq2013 ]: Section “ Authorization Requirements ” page 4 -22

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The network simulator validates the authorization message and returns the response ‘00’(successful).Tests are run for MasterCard and Maestro applications as well as card and mobile devicetypes, when applicable:Case 1: PayPass Mag Stripe transaction (MasterCard application only)Case 2: PayPass M/Chip transaction, tag ‘5F34’ is returned by card*

Pass Criteria

Case 1: the network simulator shall receive the following:

DE 22 subfield 1 = ‘91’ DE 61 subfield 11 = ‘3’ Case 2: the network simulator shall receive the following:

DE 22 subfield 1 = ‘07’ DE 23 = ‘01’ DE 55 shall be presentDE 61 subfield 11 = ‘3’

The terminal shall approve the transaction.

Note *: another specific test [TC048] exists where the card does not return the tag ‘5F34’.

TC051 - Integration/online message – Online PIN

ObjectiveTo ensure the PayPass terminal correctly manages the Online PIN verification, whensupported.

Applicability Terminal supports Online PIN


Test Conditions

The transaction amount must be above the CVM Required Limit and below the ContactlessTransaction Limit.The AIP indicates that CVM is supported.Data returned by card is such as Online PIN is to be performed.

The network simulator validates the authorization message (including PIN) and returns asuccessful response.Several tests are performed. In all cases the Online PIN entered is correct:Case 1: Online PIN is 4 digits longCase 2: Online PIN is 5 digits longCase 3: Online PIN is 6 digits long.

Pass Criteria

The TVR byte 3 bit 3 must be set (Online PIN entered).The network simulator displays the correct PIN value: “PIN Validation, PIN = xxxx”where xxxx is the card PIN.The terminal shall approve the transaction.

Note


29/252

Test Cases


TC052 - Integration/online message – Issuer response: wrong Online PIN

Objective To ensure the PayPass terminal correctly manages the Issuer responses ‘55’ (wrong PIN)and ‘75’ (Allowable number of PIN tries exceeded).

Applicability Terminal supports Online PINReference [ PPReq2013 ] Section “Cardholder Verification” page 4 -15

Test Conditions

The transaction amount must be above the CVM Required Limit and below the ContactlessTransaction Limit.The network simulator validates the authorization and returns the responses below.Tests are run for MasterCard application:Case 1: network response i s ‘55’ (wrong PIN) Case 2: network response is ‘75’ (Allowable number of PIN tries exceeded)

Pass Criteria

The TVR byte 3 bit 3 must be set (Online PIN entered).Case 1: the terminal must indicate the cardholder that the PIN is incorrect. The end of the

transaction is out of scope.*Case 2: the terminal shall decline the transaction upon reception of the network response.

Note

*: one could expect the terminal to prompt the cardholder to enter the PIN again and thenresend the authorization message with the second PIN. However some issuers will declineif they receive a second authorization with the same transaction counter value, even if the

second PIN is correct. Therefore some terminals could rather decline the transaction inorder to avoid such issues in the field.

TC053 – Integration/online message – Track 2 Equivalent Data must be used in the authorization request

Objective

To ensure that a terminal transmits the Track2 Equivalent Data for a PayPass – M/Chip

transaction.


Reference [ PPReq2013 ]: Section “ Track Data Consistency ”, page 4 -11

Test Conditions

The transaction amount must be above the CVM Required limit (if existing) and below theContactless Transaction Limit.Tests are run for MasterCard and Maestro applications, when applicable.Case 1: purchase with a cardCase 2: purchase with a mobileCase 3: purchase with Cash Back Case 4: manual Cash Advance

Pass Criteria The 0100 (or 0200) message shall contain a DE 35 populated with the content of the cardTrack2 Equivalent Data (both’D’ and ‘=’ are acceptable separators).

Note


30/252

Test Cases



TC054 - Integration/online message – CVM Results in authorization message

ObjectiveTo ensure the PayPass terminal correctly transmits the CVM Results in the authorizationmessage containing DE 55 (effective 1 April 2017).

ApplicabilityThe terminal is online capable

Reference [ MChip2013 ]: "Contents of DE 55", [RA117.11], page 3-34

Test Conditions

Tests are run for MasterCard and Maestro applications, when applicable:Case 1: the CDOL requests the CVM Results. Card device type.Case 2: the CDOL requests the CVM Results. Mobile device type.Case 3: the CDOL does not request the CVM Results

Pass CriteriaThe PayPass terminal must transmit the CVM Results (DE 55 SE 9F34) in theauthorization message (effective 1 April 2017).

Note

TC055 - Integration/online message – Device Type data element in the authorization request

ObjectiveTo ensure the terminal correctly transmits the Device Type data element in theauthorization message, if supported.

Applicability Always

Reference [ PPReq2013 ]: Section “ Authorization Messages ”, page 4 -23

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.Tests are run for MasterCard and Maestro applications, PayPass M/Chip and PayPass MagStripe, when applicable.Case 1: the card returns a Third Party Data indicating a device type 'card'Case 2: [terminal does not support on-device cardholder verification] the card returns aThird Party Data indicating a device type 'mobile'Case 3: [terminal supports on-device cardholder verification] the card returns a Third PartyData indicating a device type 'mobile'Case 4: the card returns a Third Party Data indicating a device type 'tag'

Pass Criteria

The 0100 (or 0200) message shall contain a DE 48 SE 23 (effective 19 April 2013 in USregion and 17 October 2014 in Canada for newly deployed devices) populated with thecorrect device type value:Case 1: '00' (card)Cases 2 & 3: '01' (mobile)Case 4: '04' (tag)

Note


31/252

Test Cases


TC061 - Integration/configuration – Contactless Transaction Limit

Objective To ensure the PayPass terminal correctly implements the Contactless Transaction Limit.


Reference [ PPReq2013 ]: Section “ Terminal Contactless Transaction Limit ” p4-7

Test Conditions

The card returns only one AID in the PPSE.Tests are run for MasterCard and Maestro applications, when applicable:Case 1a: [if the terminal allows the user to enter amounts equal to the ContactlessTransaction Limit] amount is equal to the Contactless Transaction Limit (e.g. : 25.00€) Case 1b: [if the terminal supports On Device Cardholder Verification and allows the user toenter amounts equal to the Contactless Transaction Limit (On Device CVM)] amount isequal to the Contactless Transaction Limit (On Device CVM) (e.g.: 25.00€) Case 2: [if the terminal supports [PayPass2.x] and allows to enter amounts greater than theContactless Transaction Limit], the amount is one minor unit above the ContactlessTransaction Limit (e.g. : 25.01€) Case 3a: [if the terminal supports [PayPass3.0] and allows to enter amounts greater thanthe Contactless Transaction Limit], the amount is one minor unit above the ContactlessTransaction Limit (e.g.: 25.01€) Case 3b: [if the terminal supports On Device Cardholder Verification and allows to enteramounts greater than the Contactless Transaction Limit (On Device CVM)] the amount isone minor unit above the Contactless Transaction Limit (On Device CVM) (e.g.: 25.01€)

Pass Criteria

Cases 1a & 1b: the terminal shall approve the transaction.Case 2: the terminal shall not perform the transaction above the Contactless TransactionLimit. The terminal will either abort after the PPSE response or will not activate the

PayPass reader*.Cases 3a & 3b: the terminal shall not perform the transaction above the ContactlessTransaction Limit. The terminal will either abort after the last ReadRecord response or willnot activate the PayPass reader*.

Note

Case of amount below the Contactless Transaction Limit is implicitly tested in most of the scenarios.

*: The terminals may not activate the reader if none of the supported applications acceptamounts greater than the Contactless Transaction Limit being tested.


32/252

Test Cases



TC062 - Integration/configuration – Terminal application version number for PayPass - M/Chip is ′0002′

ObjectiveTo ensure that a terminal has its application version number for PayPass - M/Chip set to′0002′.

ApplicabilityAlways applicable

Reference [ PPReq2013 ]: Section “ Terminal Risk Management ”, page 4 -17

Test ConditionsThe transaction amount must be below the Contactless Transaction Limit.Test is run for MasterCard and Maestro applications, when applicableThe card Application Version Number is set to ‘0002’ (‘9F08 02 0002’)

Pass CriteriaThe terminal shall approve the transaction online or offline.TVR byte 2 bit 8 = 0 (ICC & terminal have same application versions)

Note

TC063 – Integration/configuration – Manual Cash Advance

ObjectiveTo ensure the terminal always performs cardholder verification for cash advancetransactions.

Applicability Terminal supports Cash Advance

Reference [ PPReq2013 ]: Section “Manual Cash Advance”, page 4 -6

Test Conditions

The transaction amount must be the smallest possible amount.The card supports Online PIN, Signature and No CVM.Test is run for MasterCard and Maestro applications, when applicable.

The network simulator returns the responses ‘00’ (successful).

Pass Criteria

- The TVR shall indicate that the CVM was successful: TVR byte 3 bit 8 = 0.- The CVM result shall be either ’42 03 xx’ or ‘1E 03 xx’. The network simulator shall receive a 0100 (or 0200) message.- DE 3 (Processing code) - subfield 1 = '17'- DE 4 must be the cash advance amount- DE 55 SE 9C (Transaction type) = '12'- DE 55 SE 9F02 (Amount, Authorized) contains the same amount as DE 4


Note


33/252

Test Cases


TC065 - Integration – PIX extension

Objective To ensure that the PayPass terminal correctly manages the extended AIDs.


Reference [ PPReq2013 ]: Section “ Application Selection ” page 4-12

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The network simulator validates the authorization message and returns the response '00'(Approved).Tests are run for MasterCard and Maestro applications, when applicable:Case 1: AID is extended with the following: ‘D056 0 1’ Case 2: AID is extended with the following: ‘C123456789’

Pass Criteria The terminal shall select the extended AID and correctly continue the transaction.

Note

TC066 - Integration – service code indicates a chip is present on card

ObjectiveTo ensure that the PayPass terminal does not prompt for a contact transaction when theservice code indicates a chip is present on the card.


Reference [ PPReq2013 ]: Section “ Service Codes ” page 4-11

Test ConditionsThe transaction amount must be below the Contactless Transaction Limit.The service code included in the Track2 indicates that a chip is present on the card.Tests are run for MasterCard and Maestro applications, when applicable.

Pass CriteriaThe terminal shall approve the PayPass transaction. The terminal shall not prompt for acontact transaction.

Note


34/252

Test Cases



TC067 - Integration – service code indicates Online PIN

ObjectiveTo ensure that the PayPass terminal does not use the service code in order to require onlineauthorization or Online PIN.

ApplicabilityAlways applicable

Reference [ PPReq2013 ]: Section “ Service Codes ” page 4-11

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.Tests are run for MasterCard and Maestro applications, when applicable:CVM list does not include Online PIN.Case 1: Service Code contained in Track2 is ‘206’ (Normal Authorization, PIN if pinpad

present). Amount is below the CVM Required Limit.Case 2: Service Code contained in Track2 is ‘206’ (Normal Authorization, PIN if pinpad

present). Amount is above the CVM Required Limit.Case 3: Service Code in Track2 is ‘220’ (Issuer Authorizat ion, PIN if pinpad present)Case 4: Service Code contained in Track2 is ‘226’ (Issuer Authorization, PIN required)

Pass Criteria

The terminal shall not prompt for PIN.The TVR byte 3 bits 5,4,3 must be unset (Online PIN not required / not entered).Cases 1: the terminal shall approve the PayPass transaction.Cases 2 & 3 & 4: the terminal shall approve the PayPass transaction offline.

Note

TC068 - Integration – Transaction declined (not ATM)

ObjectiveTo ensure the PayPass terminal prompts the cardholder to perform a contact transaction,

if supported, when the card, the terminal or the issuer declines.Applicability The terminal supports contact and is not an ATM

Reference [ PPReq2013 ]: Section “ Subsequent Contact Transactions ” p 4-19

Test Conditions

The transaction amount must be below the Contactless transaction limit.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: the card declines the transactionCase 2: the terminal declines the transactionCase 3: the issuer (simulator) declines the transaction

Pass Criteria The terminal shall prompt the cardholder to perform a contact transaction.

Note


35/252

Test Cases


TC068b - Integration – Transaction declined (ATM)

Objective

To ensure the PayPass ATM allows a repeat attempt of a failed contactless transactionusing any acceptance technology supported by the ATM, including trying contactlessagain.To ensure the ATM does not force fallback from contactless acceptance to any otherform of acceptance technology before a second transaction is attempted.

Applicability The terminal is an ATM

Reference [ ATM2013 ]: Section “ Acceptance Technology Fallback ” p 3-2

Test Conditions

The transaction amount must be below the Contactless transaction limit.Tests are run for MasterCard and Maestro applications, when applicable:Case 1: the card declines the transactionCase 2: the terminal declines the transaction

Case 3: the issuer (simulator) declines the transactionPass Criteria

The ATM shall allow a repeat attempt of the failed transaction using the contactlesstechnology. The ATM does not force fallback to a contact technology.

Note


36/252

Test Cases



TC070 - Integration – Application Selection without cardholder assistance

ObjectiveTo ensure the terminal always selects the highest priority application without cardholderassistance.

ApplicabilityAs per below sub-cases

Reference[ PPReq2013 ]: Section “ Application Selection ”, page 4 -12[ ATM2013 ]: Section “ Cardholder Selection ”, page 3-9

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.Card 1 : The card exposes a PPSE returning the following 2 applications in this specificorder:

Maestro with priority 03 (tag '87' with value '03') MasterCard with priority 02 (tag '87' with value '02')

Card 2 : The card exposes a PPSE returning the following 2 applications in this specificorder:

MasterCard with priority 15 (tag '87' with value '0F') Maestro with priority 06 (tag '87' with value '06')

Case 1: The terminal supports MasterCard and the cardholder uses card 1.Case 2: The terminal supports Maestro and the cardholder uses card 2.Case 3: The terminal supports MasterCard only and the cardholder uses card 2.Case 4: The terminal supports Maestro only and the cardholder uses card 1.

Pass Criteria

In all cases below the terminal must automatically select the application mentioned andsuccessfully complete the transaction.Case 1: The terminal selects the MasterCard application.Case 2: The terminal selects the Maestro application.Case 3: The terminal selects the MasterCard application.Case 4: The terminal selects the Maestro application.

Note

TC072 - Integration – PIN entry canceled

ObjectiveTo ensure the transaction terminates when the PIN entry is canceled by the cardholder ormerchant or if the terminal times out.

Applicability Terminal supports Online PIN

Reference [ PPReq2013 ]: Section “ Cardholder Verification ” page 4-16

Test ConditionsThe transaction amount must be above the CVM Required limit and below the ContactlessTransaction Limit.PIN entry is canceled by the cardholder or merchant

Pass CriteriaThe terminal shall prompt for PIN.The terminal must terminate the transaction since the PIN entry did not complete.The network simulator does not receive any authorization request for this transaction.

Note


37/252

Test Cases


3.3 MasterCard PayPass M/Chip Test CasesThe test cases described in this section apply to terminals that accept MasterCard PayPass .

TC201 - Regression – SDA

Objective To ensure the PayPass terminal correctly performs SDA , when applicable .

Applicability Terminal supports SDA and supports MasterCard


Test ConditionsThe transaction amount must be below the Floor Limit.The AIP byte 1 bit 7 indicates that SDA is supported.Data returned by card is such as the transaction is approved offline*.

Pass CriteriaTVR byte 1 bit 8 is not set (offline data authentication was performed).The terminal shall send request a TC without CDA (‘40’) in the Generate AC.Transaction shall be approved offline.

Note *: the PayPass terminals may bypass the SDA if the transaction is declined or sent online.

TC221 - Integration/CVM – attended terminal

ObjectiveTo ensure the attended PayPass terminal correctly manages the cardholder verificationabove the CVM Required Limit.

Applicability Terminal is attended and supports MasterCard

Reference [ PPReq2013 ]: Section “ Cardholder Verification ” p 4-15

Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The network simulator validates the authorization message and returns ‘00’ (successful). Several tests are run, when applicable:Case 1: the card supports offlinePIN then Signature (‘5E 03’) then noCVM. Thetransaction amount must be the lowest value above the CVM Required Limit (e.g.:25.01€). Case 2: Terminal supports gratuity. The card supports offlinePIN then Signature (‘5E 03’)then noCVM. The sum of transaction and gratuity amounts must be the lowest value above

the CVM Required Limit (e.g.: 25.01€). Case 3: card supports Online PIN (‘02 03’) then noCVM. Terminal supports Online PIN.The transaction amount must be the lowest value above the CVM Required Limit (e.g.:25.01€).

Pass Criteria

The terminal shall approve the transaction.The cardholder verification shall be successful (except case 5): TVR byte 3 bit 8 = 0Case 1 & 2: The terminal shall request signature for cardholder verification.- CVM result shall be ‘5E 03 00’ Case 3: The terminal shall request an ARQC. The terminal shall prompt for PIN.- TVR byte 3 bit 3 = 1 (Online PIN entered)- CVM result shall be ‘02 03 00’

Note N/A


38/252

Test Cases



TC222 - Integration/CVM – CAT1

ObjectiveTo ensure the CAT1 PayPass terminal correctly manages the cardholder verification abovethe CVM Required Limit.

ApplicabilityTerminal supports MasterCard and is a CAT1 or a CAT1/2


Test Conditions

The transaction amount must be above the CVM Required Limit and below the ContactlessTransaction Limit.The network simulator validates the authorization message and returns the responses ‘00’(successful).Several tests are run, when applicable:Case 1: the card supports offlinePIN then Signature then noCVM.Case 2: the card supports Online PIN then noCVM.

Pass Criteria


Case 1: the cardholder verification shall fail:- TVR byte 3 bit 8 = 1- CVM r esult shall be ‘3F 00 01’ The terminal shall neither prompt for PIN nor request a signature.Case 2: the cardholder verification shall be successful:- TVR byte 3 bit 8 = 0- TVR byte 3 bit 3 = 1 (Online PIN entered)- CVM result shall be ‘02 03 00’ The terminal shall request an ARQC.The terminal shall prompt for PIN.Case 3: the cardholder verification shall fail:

- TVR byte 3 bit 8 = 1- CVM result shall be ‘3F 00 01’ The terminal shall neither prompt for PIN nor request a signature.

Note


39/252

Test Cases


TC223 - Integration/CVM – CAT2 and CAT3

Objective To ensure the CAT2 and CAT3 PayPass terminals correctly manage the cardholderverification above the CVM Required Limit.

ApplicabilityTerminal supports MasterCard and is a CAT2 or a CAT3 and has a CVM Required Limitlower than the Contactless Transaction Limit.


Test Conditions

The transaction amount must be above the CVM Required Limit and below the ContactlessTransaction Limit.The network simulator validates the authorization message and returns the responses ‘00’(successful).Several tests are run, when applicable:Case 1: the card supports offlinePIN then Signature then noCVMCase 2: the card supports Online PIN then noCVMCase 3: the card supports noCVM only

Pass Criteria

The terminal shall approve the transaction.Case 1: the cardholder verification shall be successful:- TVR byte 3 bit 8 = 0- CVM result shall be ‘ 1F 03 00’ or '1F 03 02'The terminal shall neither prompt for PIN nor request a signature.Case 2: the cardholder verification shall be successful:- TVR byte 3 bit 8 = 0- CVM result shall be ‘1F 03 00’ or '1F 03 02'The terminal shall neither prompt for PIN nor request a signature.Case 3: the cardholder verification shall be successful:- TVR byte 3 bit 8 = 0- CVM result shall be ‘1F 0 3 00’ or '1F 03 02'The terminal shall neither prompt for PIN nor request a signature.

Note


40/252

Test Cases



TC260 - Integration/configuration – Purchase with Cash Back

ObjectiveTo ensure the terminal always performs cardholder verification and online authorization incase of Purchase with Cash Back.

Applicability Terminal supports Cash Back

Reference [ PPReq2013 ]: Section “ Purchase with Cash Back ”, page 4 -5

Test ConditionsThe total transaction amount (including Cash Back) must be the smallest possible amount.The card supports Online PIN, Signature and No CVM.The network simulator returns the responses ‘00’ (successful).

Pass Criteria

The terminal must request an ARQC.- The TVR shall indicate that the CVM was successful: TVR byte 3 bit 8 = 0.- The CVM result shall be either ’42 03 xx’ or ‘1E 03 xx’. The network simulator shall receive a 0100 (or 0200) message.- DE 3 (Processing code) - subfield 1 = '09'.- DE 4 must be the sum of the purchase and cash back amounts.

- DE 54 (Additional Amount) contains the cash back amount.- DE 55 SE 9C (Transaction type) = '09'.- DE 55 SE 9F02 (Amount, Authorized) contains the same amount as DE 4.- DE 55 SE 9F03 (Amount, Other) contains the Cash Back amount.


Note


41/252

Test Cases


3.4 Maestro PayPass M/Chip Test CasesThe test cases described in this section apply to terminals that accept Maestro PayPass .

TC401 - Integration/capabilities – No PayPass Mag Stripe

ObjectiveTo ensure that the terminal terminates the transaction if the PayPass Maestro card indicatesthat it does not support PayPass – M/Chip.

Applicability Terminal supports Maestro PayPass

Reference [ PPReq2013 ]: Section “ PayPass Acceptance ” page 4-1

Test ConditionsTransaction amount is below the Contactless Transaction Limit.The card indicates in the AIP that it does not support PayPass – M/Chip.

Pass Criteria The terminal shall terminate the transaction.

Note

TC410 - Integration/CVM – Online PIN above the CVM Required Limit

Objective To ensure the terminal correctly performs Online PIN above the CVM Required Limit.

Applicability Terminal supports Maestro and Online PIN .

Reference [ PPReq2013 ]: Section “ Cardholder Verification ” p 4-15

Test Conditions

Transaction amount is above the CVM Required Limit and below the ContactlessTransaction Limit.The network simulator validates the authorization message and returns ‘00’ (successful). The card CVM list indicates Online PIN.

Pass Criteria

The cardholder verification shall be successful:- TVR byte 3 bit 8 = 0 (Cardholder verification was successful)- TVR byte 3 bit 3 = 1 (Online PIN entered)- CVM result shall be ‘42 03 00’ The terminal shall request an ARQC.The terminal shall prompt for PIN.The terminal shall approve the transaction.

Note


42/252

Test Cases



3.5 PayPass Mag Stripe Test CasesThe test cases described in this section apply to terminals that accept MasterCard PayPass MagStripe.


Objective To ensure the PayPass terminal correctly behaves when it receives uncommon data valueor length from the card.

Applicability Terminal supports MasterCard PayPass


Test Conditions

The transaction amount must be below the Contactless Transaction Limit.The network simulator returns the responses ‘00’ (successful). The card returns the data defined below.Case 1: Track1 (tag ‘56’) with maximum length (48 bytes)Case 2: Track2 (‘9F6B’) with maximum length (37 digits) Case 3: Track1 discretionary data (tag ‘56’) with minimum length (3 bytes) Case 4: Track2 discretionary data (tag ‘9F6B’) with minimum length (3 digits)

Pass Criteria In all cases the terminal shall approve the transaction.

Note

TC610 - Integration – Building the discretionary data

Objective To ensure that the PayPass Mag Stripe terminal correctly builds the discretionary data.



Test ConditionsThe transaction amount is below the Contactless Transaction Limit.The card indicates in the AIP that it does not support PayPass – M/Chip.The network simulator returns the responses ‘00’ (successful).

Pass Criteria The terminal must correctly build the discretionary data.

Note


43/252

Test Cases


TC611 - Integration – Service Code checking

ObjectiveTo ensure that the terminal correctly completes the PayPass Mag Stripe transactionwhatever the Service Code value encoded in the card.


Reference [ PPReq2013 ]: Section “Service Code s” page 4-11

Test Conditions

The transaction amount is below the Contactless Transaction Limit.The card indicates in the AIP that it does not support PayPass – M/Chip.The network simulator returns the responses ‘00’ (successful). Case 1: card returns a service code ‘101’ Case 2: card returns a service code ‘205’ Case 3: card retur ns a service code ‘502’ Case 4: card returns a service code ‘817’


Note

TC612 - Integration – ATC in discretionary data

ObjectiveTo ensure that the terminal correctly copies the ATC in the PayPass Track 1 and/or Track2 and pass the values to the network.


Reference Integration/

paypass userguide

Documents