PayPass M-TIP Test Case User Guide · PayPass M-TIP Test Case User Guide • July 2014 i ......

PayPass M-TIP

Test Case User Guide

July 2014

Copyright The information contained in this manual is proprietary and

confidential to MasterCard International Incorporated (MasterCard)

and its members.

This material may not be duplicated, published, or disclosed, in

whole or in part, without the prior written permission of

MasterCard.

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

MasterCard Worldwide - CCoE

Chaussée de Tervuren, 198A

B-1410 Waterloo

Belgium

Fax: +32 2 352 5353

Table of Contents

© 2014 MasterCard

PayPass M-TIP Test Case User Guide • July 2014 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 ............................................................................................. 25 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 ..... 26 TC054 - Integration/online message – CVM Results in authorization message ................................................. 26 TC055 - Integration/online message – Device Type data element in the authorization request ......................... 27 TC061 - Integration/configuration – Contactless Transaction Limit .................................................................. 28

Table of Contents

ii

© 2014 MasterCard

PayPass M-TIP Test Case User Guide • July 2014

TC062 - Integration/configuration – Terminal application version number for PayPass - M/Chip is ′0002′ ..... 29 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 .................................................................................................. 34 TC222 - Integration/CVM – CAT1 .................................................................................................................... 35 TC223 - Integration/CVM – CAT2 and CAT3................................................................................................... 36 TC260 - Integration/configuration – Purchase with Cash Back ......................................................................... 37

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

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

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

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

4.2 Using the Test Cards .................................................................................................................................. 48

4.3 Test Scenario Template Description .......................................................................................................... 48

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

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

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

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

5.2 Using the Test Cards ................................................................................................................................ 238

5.3 Test Scenario Template Description ........................................................................................................ 238

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

6 Annexes ............................................................................................................................................................ 261

6.1 RSA Keys used .......................................................................................................................................... 261

6.2 DES Keys used ......................................................................................................................................... 263

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

Using this Manual

© 2014 MasterCard

PayPass M-TIP Test Case User Guide • July 2014 1

1 Using this Manual

This chapter contains information that helps you understand and use this document.

1.1 Scope

This document lists the PayPass Mag Stripe and PayPass M/Chip test cases and test

scenarios used for the PayPass M-TIP.

1.2 Audience

This document is intended for use by terminal vendors and Acquirers who want to

obtain approval for their PayPass implementation.

1.3 Terminology

'Terminal' vs. 'reader'

In many cases the PayPass reader is separate from the POS terminal. However, when

dealing with M-TIP it makes more sense to consider both the separate “reader” and

the 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 a

card 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

[PPReq2014])

the "Reader Contactless Transaction Limit (No On-device CVM)" (used in

[PayPass3.0])

Using this Manual

2

© 2014 MasterCard


1.4 Document structure

This document includes 4 sections:

Introduction: this section gives some details about the test cards and the testing

configuration requirements.

Test cases: this section lists the high level test cases that are linked to individual

requirements extracted from the specifications. Most of the high level test cases

are split into several test scenarios in order to test all terminal types. The high

level 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 the

testing 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

Objective To ensure the terminal correctly behaves when it receives

uncommon data value or length from the card. [TC011]

Annexes: this section lists some test cards cryptography details.

1.5 Related Publications

The following publications contain information related to the contents of this manual.

PPReq2014 PayPass - M/Chip Requirements, 10 April 2014

ATM2013 MasterCard Contactless ATM Implementation Requirements

12 June 2013

MChip2013 M/Chip Requirements – 20 September 2013

CustomerIntfce Customer Interface Specification – 15 January 2014

SingleMsg Single Message System Specifications - 25 October 2013

PayPass3.0 PayPass – M/Chip Reader Card Application Interface Specification

V3.0.2 – May 2013

EMV Contactless Book C-2 - Kernel 2 v2.4 – February 2014


(V2.1) + PayPass M/Chip ApplicationNote#18 (April 12, 2010)


(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

Using this Manual

© 2014 MasterCard


1.6 Abbreviations

The 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

Using this Manual

4

© 2014 MasterCard


1.7 Notations

The following notations apply:

Notation Description

‘0’ to ‘9’ and ‘A’ to ‘F’ 16 hexadecimal digits. Values expressed in hexadecimal form are

enclosed in single quotes (i.e. ‘_’).

1001b Binary notation. Values expressed in binary form are followed by a

lower case ‘b’.

‘abcd’ an or ans string.

[…] Optional part.

xx Any value.

1.8 History

The 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 are

highlighted in the document.

January 2014 - TC049 updated and TC063 removed: reviewed tests related to cash

advance

- TC050: DE61 value 4 now acceptable

- TC055: case 5 added (device type 'mobile phone case or sleeve')

April 2014 - TC011 sub-case 14 added to test the tag '9F2A'

July 2014 Aligned with [PPReq2014]

- TC068 updated

- updated some pass criteria checking the CVM Results

Introduction

© 2014 MasterCard


2 Introduction

This chapter contains an introduction to the M-TIP testing processes and the M-TIP

cards.

2.1 Terminal Integration Testing Process

The M-TIP process defined in [MTIPprocess] is applicable for PayPass terminals

supporting [PayPass2.x] or [PayPass3.0].

Acquirers must complete the M-TIP process before deploying and using a terminal in

a live environment.

The objective of the M-TIP process is to ensure the terminal meets the MasterCard

requirements described in [PPReq2014].

The current document describes:

the M-TIP test cases that are defined to ensure the correct implementation of

the MasterCard requirements.

the test scenarios that must be executed in M-TIP. The test scenarios refer to

one 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 several

specification requirements identified in the Test Cases. This is outlined in the figure

below:

Test Case # 1 Objective

+


+


Card xx

Specifications

(requirements)

Test Cases

Test Scenario

TIP

cards

Introduction

6

© 2014 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 host

and terminal payment applications are compliant with MasterCard requirements. The

M-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/Chip

terminals 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 so

the 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 few

unused cards may be removed in the next future.

Subset Type Number of cards

Subset 6

PayPass Mag Stripe cards 12

PayPass M/Chip cards 1

Subset 8

MasterCard PayPass M/Chip cards 20

Maestro PayPass M/Chip cards 20

Combo cards (both MasterCard and Maestro

PayPass M/Chip) 2

Total Number of cards 55

Introduction

© 2014 MasterCard


2.3 Testing configuration requirements

During 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 Application

version number shall be set to ‘0001’ for PayPass – Mag Stripe.

Application Version Number PayPass M/Chip: Terminal Application version

number shall be set to ‘0002’ for PayPass – M/Chip.

The Terminal Contactless Transaction Limit shall have the same value as in

the field for MasterCard and Maestro applications.

The Terminal Contactless Transaction Limit (On-Device CVM), when

applicable, shall have the same value as in the field for MasterCard and

Maestro applications.

The Terminal Contactless Floor Limit shall have the same value as in the

field for MasterCard and Maestro applications

The Terminal CVM Required Limit shall have the same value as in the field

for MasterCard and Maestro applications.

However the Certification Authority Public Keys shall be the test keys defined

further in the section "RSA Keys used".

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

Test Cases

8

© 2014 MasterCard


3 Test Cases

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

3.1 Test Case Template Description

Overview

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 [PPReq2014]: Section “2.4.5 Offline Data Authentication Requirements” p2-11

Test Conditions

The 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 Criteria The 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 sent online, see the transaction flow in technical specifications.

Test Case name


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 no regression occurs when integrating the product in the live

environment.

"Interoperability": these tests are basic tests that are re-performed during M-

TIP because they often led to interoperability issues.

Test Cases

© 2014 MasterCard


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

MasterCard requirements defined in [PPReq2014].

Objective


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

Applicability


This gives the conditions for the test to be applicable.

Reference

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

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

Test Conditions

Test Conditions



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

Transaction Limit". If not, it is obvious that the related condition shall be

disregarded.

Pass Criteria

Pass Criteria The terminal shall send request a TC with CDA (‘50’) in the Generate AC.


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

Note

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

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

Test Cases

10

© 2014 MasterCard


3.2 Common PayPass M/Chip Test Cases

The 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

Objective To ensure the PayPass terminal correctly behaves when the card does not support any

offline data authentication method.

Applicability As per below sub-cases

Reference Regression test – no specific reference

Test Conditions


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 (and

terminal is online capable)*

Case 1b: [if CVM Required Limit is zero] amount is below the Floor Limit (and terminal is

online capable)

Case 2: amount is above the Floor Limit

Case 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 if

the 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 the

terminal support Online PIN, the amount should be below the CVM Required Limit in order to not set the TVR byte 3 bit 3 (“OnlinePIN entered”).

Test Cases

© 2014 MasterCard





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

Test Conditions



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 the

transaction 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. The

transaction shall be approved online.

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

TC003 - Regression – different CA key lengths

Objective To ensure the PayPass terminal correctly supports different certification authority public

key lengths.

Applicability Terminal supports SDA or CDA


Test Conditions


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*.


Case 1: CA key length is 1152/144



Pass Criteria The TVR shall indicate that the ODA was performed: TVR byte 1 bit 8 = 0.

Transaction shall be approved.

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

Test Cases

12

© 2014 MasterCard


TC004 - Regression – exponent 2^16+1

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



Test Conditions



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*.


Pass Criteria The TVR shall indicate that the ODA was performed: TVR byte 1 bit 8 = 0.

Transaction shall be approved.

Note *: PayPass terminals supporting [PayPass2.x ] will bypass the CDA if the transaction is

declined or sent online, see the transaction flow in technical specifications.

TC005 - Regression – Offline-only & ARQC

Objective To ensure that offline-only PayPass terminal correctly behaves when the card erroneously

sends an ARQC.

Applicability Terminal is offline-only


Test Conditions



The card is such as it always returns an ARQC.


Pass Criteria The offline-only PayPass terminal shall terminate the transaction upon reception of the

ARQC

Note

Test Cases

© 2014 MasterCard


TC006 - Integration/capabilities – No SDA

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

Applicability Terminal does not support SDA

Reference [PPReq2014]: 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


Objective To ensure the PayPass terminal correctly behaves when it receives uncommon data value

or length from the card.

Applicability Always applicable

Reference Interoperability test – no specific reference

Test Conditions


The card returns the data defined below.


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 list

Case 7: IAD (‘9F10’) with maximum length

Case 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')

Case 14: Kernel Identifier ('9F2A') returned in PPSE

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

Test Cases

14

© 2014 MasterCard


TC012 - Interoperability – CDOL1 includes tags forbidden in DE 55

Objective To ensure the PayPass terminal correctly behaves when the CDOL1 includes tags being

forbidden in the DE 55.

Applicability Terminal is online capable.


Test Conditions


The card requests ‘9F21’ (Transaction Time) and ‘9F40’ (Additional Terminal

Capabilities) in CDOL1. Those data items are forbidden in DE 55.

The network simulator validates the authorization message and returns the response '00'

(Approved).


Pass Criteria The 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 [PPReq2014]: “Cardholder Verification” page 4-15

Test Conditions


The AIP byte 1 bit 5 indicates “Cardholder Verification supported”.

The first CVM in the card CVM list is OfflinePIN.


Case 1: amount is below the CVM Required Limit

Case 2: amount is above the CVM Required Limit

Pass Criteria

The terminal does not send any VerifyPIN command.

The CVM results byte 1 is different from '41'.

The PayPass transaction completes successfully.

Note

Test Cases

© 2014 MasterCard


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 [PPReq2014]: Section “Receipts” page 4-18

Test Conditions


Case 1: amount is below the CVM Required Limit

Case 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 the

cardholder 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 [PPReq2014]: Section “Refunds” page 4-6

Test Conditions

- First step is to perform the purchase:


- Second step is to perform the refund:

If requested, the refund amount must be the same as the purchase amount.


Case 1: [terminal supports [PayPass2.0]] PayPass M/Chip transaction to be refunded

Case 2: [terminal supports [PayPass2.1] or [PayPass3.0]] PayPass M/Chip transaction to

be refunded

Case 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 the

refund process, the terminal displays a message to inform the cardholder that refund

has been done successfully.

Case 2:


In the second transaction, the PayPass terminal requests an AAC. At the end of the

refund process, the terminal displays a message to inform the cardholder that refund

has been done successfully.

Case 3:


At the end of the refund process, the terminal displays a message to inform the

cardholder that refund has been done successfully.

Note

Test Cases

16

© 2014 MasterCard


TC026 - Integration/capabilities – Data Storage

Objective To ensure the terminal correctly completes the payment transaction when the card supports

Data 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, field

off 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).


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

GetPO response

Case 2 [if the terminal supports IDS]: whatever the DS Requested Operator ID provided in

the GetPO command, the card returns AIP, AFL and '9F5F 01 00' ("no slot available") in

the GetPO response

Case 3 [if the terminal supports IDS]: whatever the DS Requested Operator ID provided in

the GetPO command, the card returns AIP, AFL, '9F5F 01 40' (volatile slot), '9F7F' (DS

Unpredictable Number), '9F7D 08 00…00' (DS Summary 1). When the GenAC command

includes the DSDOL data then Summary2 and Summary3 are included in the SDAD.

Summary2=Summary1. Summary3<>Summary2.

Pass Criteria The terminal shall approve the transaction.

Note

TC028 - Integration/capabilities – ATM display

Objective

To 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 ATM

user.

Applicability The terminal is an ATM

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

Test Conditions Visual check

Pass Criteria The ATM must display all user instructions on the existing screen.

The reader must not provide any instructions directly to the ATM user.

Note

Test Cases

© 2014 MasterCard


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

Objective To 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 [PPReq2014]: Section “Terminal CVM Required Limit” page 4-9

Test Conditions

The 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 cardholder

verification 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.


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

Test Cases

18

© 2014 MasterCard


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 [PPReq2014]: Section “Terminal CVM Required Limit” p 4-9

Test Conditions

The transaction amount must be above the CVM Required Limit.


The card supports noCVM only (‘1F 03’).

Pass Criteria

The cardholder verification shall fail:


- 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

Objective To ensure the terminal not supporting "On-device cardholder verification" correctly

completes the transaction with a Mobile.

Applicability Terminal does not support [PayPass3.0] or the "Kernel Configuration" indicates "On-

device cardholder verification NOT supported"

Reference Integration test – no specific reference

Test Conditions



AIP byte 2 bit 8 is not set ("EMV NOT supported").




Note

Test Cases

© 2014 MasterCard


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





- A first transaction is performed where the Mobile indicates that the Mobile PIN was

successfully verified

Case 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 verification

successful"

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 [PPReq2014]: “Gratuities” page 4-7

Test Conditions

The cardholder must enter a gratuity amount. The transaction amount plus the gratuity

amount must be below the Contactless Transaction Limit.

The network simulator validates the authorization message and returns a successful

response.


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

Test Cases

20

© 2014 MasterCard


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

[SingleMsg] Section “DE 39 - Response Code” page 4-103

Test Conditions


The card returns an ARQC.

The network simulator validates the authorization message and returns the response ‘00’

(successful).


Pass Criteria

DE 55 SE 9F27 value in the network log shall be the same as returned by the card to the

first GENERATE AC.

The terminal shall approve the transaction upon reception of the network response.

Note

TC043 - Integration/online message – Issuer response: unsuccessful

Objective To ensure the PayPass terminal correctly manages the Issuer responses ‘51’ (insufficient

funds) and ‘57’ (Transaction not permitted).




Test Conditions


The network simulator validates the authorization message and returns the response below.


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

Test Cases

© 2014 MasterCard


TC045 - Integration/online message – Issuer response contains script

Objective To ensure the PayPass terminal does not process the ICC response data erroneously

returned by the issuer.


Reference [PPReq2014]: Section “Acquirer Network Requirements” page 4-21

Test Conditions

The transaction amount must be above the Floor Limit and below the Contactless

Transaction 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 following

response:

- 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 PIN

Unblock commands followed by a PIN Change Unblock.


Pass Criteria The 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

Objective To ensure the PayPass terminal transmits transaction mandatory data to the network even

if it is not requested by the card in the CDOL1.



Test Conditions


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 the

CDOL1.

The network simulator validates the authorization message (not the ARQC) and returns the

response '00' (Approved).


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’)


Note

Test Cases

22

© 2014 MasterCard


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

Objective To ensure the PayPass terminal transmits the PAN sequence number coming from the chip

and not from the Track2 equivalent data item.



Test Conditions


The PAN sequence number value from the tag ‘5F34’ is different from the one in the

Track2 equivalent data item.


(Approved).


Pass Criteria

The Terminal shall send the PAN sequence number value from the tag ‘5F34’ to the

network.

The simulator must successfully validate the provided ARQC.


Note

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

Objective To ensure the PayPass terminal does not transmit the PAN sequence number when it is not

returned by the card.



Test Conditions


The PAN sequence number is not returned by the card.


(Approved).


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


Note

Test Cases

© 2014 MasterCard


TC049 - Integration/online message – Full Grade

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


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

Test Conditions



(Approved).


Case 1: terminal is not an ATM or a Bank Branch

Case 2: terminal is an ATM

Case 3: terminal is a Bank Branch

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'

Case 3:

- DE 3 subfield 1 (transaction type code) = '17' (cash disbursement).

- DE 4 must be the cash advance amount

- DE 55 SE 9C (Transaction type) = '17'

- DE 55 SE 9F02 (Amount, Authorized) contains the same amount as DE 4

Note

Test Cases

24

© 2014 MasterCard


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

Objective To ensure the PayPass terminal correctly manages the PayPass values in the existing

authorization fields.


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

Test Conditions



(successful).

Tests are run for MasterCard and Maestro applications as well as card and mobile device

types, 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’ or '4'

Case 2: the network simulator shall receive the following:


DE 23 = ‘01’

DE 55 shall be present



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

Test Cases

© 2014 MasterCard


TC051 - Integration/online message – Online PIN

Objective To ensure the PayPass terminal correctly manages the Online PIN verification, when

supported.

Applicability Terminal supports Online PIN


Test Conditions

The transaction amount must be above the CVM Required Limit and below the Contactless

Transaction 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 a

successful response.

Several tests are performed. In all cases the Online PIN entered is correct:

Case 1: Online PIN is 4 digits long

Case 2: Online PIN is 5 digits long

Case 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.


Note

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).


Reference [PPReq2014] Section “Cardholder Verification” page 4-15

Test Conditions


Transaction Limit.

The network simulator validates the authorization and returns the response below.

Tests are run for MasterCard application:

Case 1: network response is ‘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 then resend the authorization message with the second PIN. However some issuers will decline

if 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 in

order to avoid such issues in the field.

Test Cases

26

© 2014 MasterCard


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 [PPReq2014]: Section “Track Data Consistency”, page 4-11

Test Conditions

The transaction amount must be above the CVM Required limit (if existing) and below the

Contactless Transaction Limit.


Case 1: purchase with a card

Case 2: purchase with a mobile

Case 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 card

Track2 Equivalent Data (both’D’ and ‘=’ are acceptable separators).

Note

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

Objective To ensure the PayPass terminal correctly transmits the CVM Results in the authorization

message containing DE 55 (effective 1 April 2017).

Applicability The terminal is online capable

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

Test Conditions


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 Criteria The PayPass terminal must transmit the CVM Results (DE 55 SE 9F34) in the

authorization message (effective 1 April 2017).

Note

Test Cases

© 2014 MasterCard


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

Objective To ensure the terminal correctly transmits the Device Type data element in the

authorization message, if supported.

Applicability Always

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

Test Conditions


Tests are run for MasterCard and Maestro applications, PayPass M/Chip and PayPass Mag

Stripe, 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 a

Third Party Data indicating a device type 'mobile'

Case 3: [terminal supports on-device cardholder verification] the card returns a Third Party

Data indicating a device type 'mobile'

Case 4: the card returns a Third Party Data indicating a device type 'tag'

Case 5: the card returns a Third Party Data indicating a device type 'mobile phone case or

sleeve'.

Pass Criteria

The 0100 (or 0200) message shall contain a DE 48 SE 23 (effective 19 April 2013 in US

region and 17 October 2014 in Canada for newly deployed devices) populated with the

correct device type value:

Case 1: '00' (card)

Cases 2 & 3: '01' (mobile)

Case 4: '04' (tag)

Case 5: '06' (mobile phone case or sleeve)

Note

Test Cases

28

© 2014 MasterCard


TC061 - Integration/configuration – Contactless Transaction Limit

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


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

Test Conditions

The card returns only one AID in the PPSE.


Case 1a: [if the terminal allows the user to enter amounts equal to the Contactless

Transaction 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 to

enter amounts equal to the Contactless Transaction Limit (On Device CVM)] amount is

equal 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 the

Contactless Transaction Limit], the amount is one minor unit above the Contactless

Transaction Limit (e.g.: 25.01€)

Case 3a: [if the terminal supports [PayPass3.0] and allows to enter amounts greater than

the Contactless Transaction Limit], the amount is one minor unit above the Contactless

Transaction Limit (e.g.: 25.01€)

Case 3b: [if the terminal supports On Device Cardholder Verification and allows to enter

amounts greater than the Contactless Transaction Limit (On Device CVM)] the amount is

one 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 Transaction

Limit. 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 Contactless

Transaction Limit. The terminal will either abort after the last ReadRecord response or will

not 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 accept amounts greater than the Contactless Transaction Limit being tested.

Test Cases

© 2014 MasterCard


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

Objective To ensure that a terminal has its application version number for PayPass - M/Chip set to

′0002′.


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

Test Conditions


Test is run for MasterCard and Maestro applications, when applicable

The card Application Version Number is set to ‘0002’ (‘9F08 02 0002’)

Pass Criteria The terminal shall approve the transaction online or offline.

TVR byte 2 bit 8 = 0 (ICC & terminal have same application versions)

Note

TC065 - Integration – PIX extension

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


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

Test Conditions



(Approved).


Case 1: AID is extended with the following: ‘D056 01’

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

Objective To ensure that the PayPass terminal does not prompt for a contact transaction when the

service code indicates a chip is present on the card.


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

Test Conditions


The service code included in the Track2 indicates that a chip is present on the card.


Pass Criteria The terminal shall approve the PayPass transaction. The terminal shall not prompt for a

contact transaction.

Note

Test Cases

30

© 2014 MasterCard


TC067 - Integration – service code indicates Online PIN

Objective To ensure that the PayPass terminal does not use the service code in order to require online

authorization or Online PIN.



Test Conditions



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 Authorization, 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)

Objective To 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 [PPReq2014]: Section “Subsequent Contact Transactions” p 4-19

Test Conditions

The Device Type (if present) indicates that the cardholder device has a contact interface.

The transaction is not a refund.

The transaction amount must be below the Contactless transaction limit.


Case 1: the card declines the transaction

Case 2: the terminal declines the transaction

Case 3: the issuer (simulator) declines the transaction using an authorization response

code '65' (exceeds withdrawal count limit)

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

Note

Test Cases

© 2014 MasterCard


TC068b - Integration – Transaction declined (ATM)

Objective

To ensure the PayPass ATM allows a repeat attempt of a failed contactless transaction

using any acceptance technology supported by the ATM, including trying contactless

again.

To ensure the ATM does not force fallback from contactless acceptance to any other

form 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.


Case 1: the card declines the transaction

Case 2: the terminal declines the transaction

Case 3: the issuer (simulator) declines the transaction

Pass Criteria The ATM shall allow a repeat attempt of the failed transaction using the contactless

technology. The ATM does not force fallback to a contact technology.

Note

Test Cases

32

© 2014 MasterCard


TC070 - Integration – Application Selection without cardholder assistance

Objective To ensure the terminal always selects the highest priority application without cardholder

assistance.


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

[ATM2013]: Section “Cardholder Selection”, page 3-9

Test Conditions


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

order:

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 specific

order:

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 and

successfully 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

Objective To ensure the transaction terminates when the PIN entry is canceled by the cardholder or

merchant or if the terminal times out.


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

Test Conditions

The transaction amount must be above the CVM Required limit and below the Contactless

Transaction Limit.

PIN entry is canceled by the cardholder or merchant

Pass Criteria

The 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

Test Cases

© 2014 MasterCard


3.3 MasterCard PayPass M/Chip Test Cases

The 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 Conditions

The 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 Criteria

TVR 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.


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

Test Cases

34

© 2014 MasterCard


TC221 - Integration/CVM – attended terminal

Objective To ensure the attended PayPass terminal correctly manages the cardholder verification

above the CVM Required Limit.

Applicability Terminal is attended* and supports MasterCard

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

Test Conditions


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. The

transaction 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 cardholder verification shall be successful (except case 5): TVR byte 3 bit 8 = 0

Case 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 *: could be a Bank Branch

Test Cases

© 2014 MasterCard


TC222 - Integration/CVM – CAT1

Objective To ensure the CAT1 PayPass terminal correctly manages the cardholder verification above

the CVM Required Limit.

Applicability Terminal supports MasterCard and is a CAT1 or a CAT1/2


Test Conditions


Transaction Limit.


(successful).


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:



The terminal shall neither prompt for PIN nor request a signature.

Case 2: the cardholder verification shall be successful:




The terminal shall request an ARQC.


Case 3: the cardholder verification shall fail:




Note

Test Cases

36

© 2014 MasterCard


TC223 - Integration/CVM – CAT2 and CAT3

Objective To ensure the CAT2 and CAT3 PayPass terminals correctly manage the cardholder

verification above the CVM Required Limit.

Applicability Terminal supports MasterCard and is a CAT2 or a CAT3 and has a CVM Required Limit

lower than the Contactless Transaction Limit.


Test Conditions


Transaction Limit.


(successful).


Case 1: the card supports offlinePIN then Signature then noCVM

Case 2: the card supports Online PIN then noCVM

Case 3: the card supports noCVM only

Pass Criteria














Note

Test Cases

© 2014 MasterCard


TC260 - Integration/configuration – Purchase with Cash Back

Objective To ensure the terminal always performs cardholder verification and online authorization in

case of Purchase with Cash Back.

Applicability Terminal supports Cash Back

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

Test Conditions

The total transaction amount (including Cash Back) must be the smallest possible amount.

The card supports Online PIN, Signature and No CVM.


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 ‘5E 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

Test Cases

38

© 2014 MasterCard


3.4 Maestro PayPass M/Chip Test Cases

The test cases described in this section apply to terminals that accept Maestro

PayPass.

TC401 - Integration/capabilities – No PayPass Mag Stripe

Objective To ensure that the terminal terminates the transaction if the PayPass Maestro card indicates

that it does not support PayPass – M/Chip.

Applicability Terminal supports Maestro PayPass

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

Test Conditions Transaction 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 [PPReq2014]: Section “Cardholder Verification” p 4-15

Test Conditions

Transaction amount is above the CVM Required Limit and below the Contactless

Transaction 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)



The terminal shall request an ARQC.



Note

Test Cases

© 2014 MasterCard


3.5 PayPass Mag Stripe Test Cases

The test cases described in this section apply to terminals that accept MasterCard

PayPass Mag Stripe.



or length from the card.

Applicability Terminal supports MasterCard PayPass


Test Conditions



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 Conditions

The transaction amount is below the Contactless Transaction Limit.



Pass Criteria The terminal must correctly build the discretionary data.

Note

Test Cases

40

© 2014 MasterCard


TC611 - Integration – Service Code checking

Objective To ensure that the terminal correctly completes the PayPass Mag Stripe transaction

whatever the Service Code value encoded in the card.



Test Conditions




Case 1: card returns a service code ‘101’





Note

TC612 - Integration – ATC in discretionary data

Objective To ensure that the terminal correctly copies the ATC in the PayPass Track 1 and/or Track

2 and pass the values to the network.


Reference Integration/regression test – no specific reference

Test Conditions


The card indicates in the AIP that it does not support PayPass – M/Chip.

The card is tapped several times on the reader so several ATC values are tested.


Pass Criteria The terminal shall approve all transactions and pass the correct PayPass Track 1 and/or

Track 2 values to the network correctly.

Note

Test Cases

© 2014 MasterCard


TC613 - Integration – Issuer response: unsuccessful

Objective To ensure the PayPass terminal correctly manages the Issuer response ‘51’ (Insufficient

funds/over credit limit).




Test Conditions The transaction amount must be below the Contactless Transaction Limit.

The network simulator returns ‘51’ (Insufficient funds/over credit limit).

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

Note

TC614 - Integration – Traditional Mag Stripe

Objective To ensure the terminal still performs correctly a traditional Mag Stripe transaction when it

contains or is connected to a PayPass reader.



Test Conditions


The card is swiped in the terminal


Pass Criteria

The network simulator shall receive the following:

DE 22 subfield 1 = ‘90’ (POS entry mode: traditional Mag stripe)

DE 61 subfield 11 = ‘2’ or ‘3’ or ‘5’ or ‘7’ or ‘8’ (card data terminal

input capability: traditional Mag stripe)


Note

Test Cases

42

© 2014 MasterCard


TC615 - Integration – Track 1 and Track 2 data are processed independently

Objective To ensure that a terminal processes Track 1 Data as Track 1 and Track 2 Data as Track 2

during PayPass - Mag Stripe transactions.


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

Test Conditions


The card indicates in the AIP that it does not support PayPass – M/Chip.

The card data is such that the Track1 discretionary data and the Track2 discretionary data

generated by the terminal are different.

Pass Criteria The terminal shall approve the transaction and pass the correct PayPass Track 1 and/or

Track 2 values to the network correctly.

Note

TC616 - Integration – Track1 data not fully populated

Objective To ensure the PayPass terminal correctly behaves when the cardholder name is not fully

populated in the Track 1.


Reference [PPReq2014]: Section “Cardholder Name”, page 4-11

Test Conditions The transaction amount must be below the Contactless Transaction Limit.

The Cardholder Name value returned in the Track1 data object is " /".

Pass Criteria The Terminal shall approve the transaction.

Note

TC681 - Integration/Mobile – Non-[PayPass3.0] terminal vs Mobile device (Mag-Stripe)

Objective To ensure the terminal not supporting [PayPass3.0] correctly completes the Mag-Stripe

transaction with a Mobile.

Applicability Terminal supports MasterCard PayPass and does not support [PayPass3.0]


Test Conditions




The device returns the UDOL requesting the MSI tag in addition of the Unpredictable

Number.



Note

Test Cases

© 2014 MasterCard


TC682 - Integration/Mobile – On-Device cardholder verification not requested

Objective To ensure the [PayPass3.0] terminal correctly completes the Mag-Stripe transaction with a

Mobile not requesting On-Device cardholder verification.

Applicability Terminal supports MasterCard PayPass and [PayPass3.0].


Test Conditions


The device does not request On-Device cardholder verification.


Case 1:


The terminal configuration is such that the CVM Required Limit is greater than zero.

The transaction amount must be below the CVM Required Limit.

Case 2:


The terminal configuration is such that the CVM Required Limit is lower than the

Contactless Transaction Limit (On-device CVM).

The terminal configuration is such that Kernel Configuration indicates 'On-Device Cardholder Verification not supported'.


Transaction Limit (On-device CVM).

Case 3:

AIP byte 1 bit 2 is not set ("On-device cardholder verification NOT supported").

The transaction amount must be below the Contactless Transaction Limit (On-device

CVM).


Note

Test Cases

44

© 2014 MasterCard


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

Objective To ensure the terminal correctly completes the Mag-Stripe transaction with a Mobile

requesting On-Device cardholder verification.



Test Conditions


The device requests On-Device cardholder verification.

Case 1:




The terminal configuration is such that the Kernel Configuration indicates 'On-Device Cardholder Verification supported'.



Case 2:




Case 3:


The terminal configuration is such that the CVM Required Limit is zero.

Pass Criteria The terminal shall display "Please see phone" (or equivalent).

Note

Test Cases

© 2014 MasterCard


TC684 - Integration/Mobile – PIN verification successful


indicating 'PIN verification successful'.



Test Conditions


The device must indicate a successful PIN verification.


Case 1:






Case 2:




Case 3:




Note

Test Scenarios for M-TIP Subset 8

46

© 2014 MasterCard


4 Test Scenarios for M-TIP Subset 8

This chapter lists the PayPass M/Chip M-TIP Test Scenarios.

4.1 M-TIP Subset 8 card details

The card versions mentioned below are given for information. The qualified test tools

are listed in [QualifiedTools] located on MasterCardConnect.com.

PINs

Below are the M-TIP Subset 8 MasterCard card details:

Card Name Card version PIN

PPC MCD 01 v2.0 or v2.1 or v2.2 4315

PPC MCD 02 v2.2 4315

PPC MCD 03 v2.0 or v2.1 or v2.2 4315

PPC MCD 04 v2.0 or v2.2 4315

PPC MCD 06 v2.0 or v2.1 or v2.2 4315

PPC MCD 07 v2.0 or v2.1 or v2.2 4315

PPC MCD 09 v2.0 or v2.1 or v2.2 4315

PPC MCD 10 v2.0 or v2.1 or v2.2 4315

PPC MCD 11 v2.2 4315

PPC MCD 12 v2.3 4315

PPC MCD 4A v1.0 4315

PPC MCD 4B v1.0 4315

PPC MCD 50 v1.0 4315

PPC MAP 01 v2.0 or v2.1 or v2.2 4315

PPC MAP 03 v2.0 or v2.1 or v2.2 4315

PPC MAP 04 v2.0 or v2.1 or v2.2 4315

PPC MAP 06 v2.0 or v2.1 or v2.2 431555

PPC MAP 07 v2.0 or v2.1 or v2.2 43155

PPC MAP 08 v2.0 or v2.1 or v2.2 4315

PPC MAP 10 v2.0 or v2.1 or v2.2 4315


© 2014 MasterCard


Below are the M-TIP Subset 8 Maestro card details:


MP01 v2.2 4315

MP11 v2.2 4315

MP12 v2.2 4315

MP13 v2.2 4315

MP14 v2.2 4315

MP15 v2.2 4315

MP16 v2.2 4315

MP17 v2.3 4315

MP18 v2.3 4315

MP19 v2.2 4315

MP20 v2.2 4315

MP4A v1.1 4315

MP4B v1.1 4315

MP50 v1.1 4315

MP71 v2.2 4315

MP72 v2.3 4315

MP91 v2.3 4315

MP92 v2.2 4315

MP93 v2.2 4315

MP94 v2.2 4315

Below are the M-TIP Subset 8 combo card details:


Combo01 v1.1 4315

Combo11 v1.1 4315

Keys

The RSA and DES keys generated for these test cards are MasterCard test keys.

There are three lengths and one exponent value for RSA keys in this set, in

accordance with MasterCard policy for debit/credit products.


48

© 2014 MasterCard


4.2 Using the Test Cards

Card log feature

All M-TIP Subset 8 cards have the ability to store the command and response

exchanges between the terminal and the card. The stored exchanges can then be

extracted from the card with the appropriate software.

Card version

The card version is returned in Select response as the value of Application Label tag:

Application Label................ (50 09) [MP01 v2 1]

4.3 Test Scenario Template Description

Overview

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


Objective

To ensure the PayPass terminal correctly behaves when it receives uncommon data value

or length from the card. Cases of Discretionary Data inconsistency and IAD (‘9F10’) with

maximum length. [TC011-3 and 7]

Applicability Terminal supports MasterCard

Card details

The Discretionary Data value in the track2 (‘57’) is different from the value returned in the

specific tag (‘9F20’).

The IAD (‘9F10’) returned by the card has the maximum length.

User Action

Please use the following test card: M-TIP Subset 8 – PPC MCD 02 v2.2.

Amount must be equal to the Contactless Transaction Limit*.

Tap card on the PayPass reader and follow the instructions.

If needed, PIN value is 4315.

Simulator In case of online transaction, the network simulator validates the authorization message

and returns ‘00’ (accepted).

Pass Criteria

- Application Label indicates “PPC MCD 02 v2 2" - OK/NOK

- AIP byte 2 bit 8 indicates “PayPass M/Chip transaction” - OK/NOK

- Amount is equal to the MasterCard Contactless Transaction Limit - OK/NOK

- The terminal approves the transaction - OK/NOK

Note

*: if the terminal supports [PayPass2.x] you must consider the limit mentioned in the M-TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are indeed different in [PayPass2.x] terminals.


© 2014 MasterCard


Test Scenario Identification


"PPC MCD xx" identifies the card to be used.

"Test yy" and "Scenario zz" identify the Test Scenario number.

Objective

Objective



maximum length. [TC011-3 and 7]

To ensure that the PayPass terminal correctly implements the Contactless Transaction

Limit. Case of amount equal to the limit. [TC061-2]

This cell lists all the Test Cases objectives tested in the current Test Scenario. The

Test Case reference is given "[TC061-2]".

Applicability

Applicability Terminal supports MasterCard

This gives the conditions for the Test Scenario to be applicable.

Card details

Card details




This lists the M-TIP card configuration, if any, used in the test.

User Action

User Action





This lists the actions to be done by the user in order to perform the test.

Simulator

Simulator In case of online transaction, the network simulator validates the authorization message and

returns ‘00’ (accepted).

This gives the network simulator configuration required for the test.


50

© 2014 MasterCard


Pass Criteria

Pass Criteria

- Application Label indicates “PPC MCD 02 v2 2" - OK/NOK




This lists the conditions required in order to pass the test. During a M-TIP session,

the user shall select "OK" or "NOK" in the test report before returning it to the

service provider.

Note

Note

*: if the terminal supports [PayPass2.x] you must consider the limit mentioned in the M-

TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are

indeed different in [PayPass2.x] terminals.

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


© 2014 MasterCard


4.4 Test Scenarios for MasterCard PayPass M/Chip


52

© 2014 MasterCard



Objective

To ensure that the PayPass terminal supports the Full Grade network messages. [TC049-1]

To ensure the PayPass terminal correctly manages the PayPass values in the authorization

fields. Case of M/Chip transaction. [TC050-2]

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

transaction. Purchase with a card. [TC053-1]

To ensure the PayPass terminal correctly transmits the CVM Results in the authorization

message containing DE 55. [TC054-1]

Applicability Terminal supports MasterCard and is online capable and is not an ATM or a Bank Branch.

Card details This card has no specific feature.

User Action

Please use the following test card: M-TIP Subset 8 – PPC MCD 01 v2.0 or v2.1 or v2.2.

Enter amount below the Contactless Transaction Limit. Possible amount values are:

- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’

- or any other rounded value.



Simulator The network simulator validates the authorization message and returns ‘00’ (accepted).

Pass Criteria

Visual checks:

- The terminal approves the online transaction - OK/NOK

Card log checks:

- Application Label indicates "PPC MCD 01 v2 2" (or v2 1 or v2 0) - OK/NOK


- Amount is below (and not equal to) the Contactless Transaction Limit - OK/NOK

Network simulator checks:

- DE 3 subfield 1 (transaction type code) = '00' (purchase) - OK/NOK

- DE 22 subfield 1 = ‘07’ (POS entry mode: contactless M/Chip) - OK/NOK

- DE 23 = ‘001’ (card sequence number) - OK/NOK

- DE 35 contains ‘5413330089600010D14122010123409172’ or

‘5413330089600010D25122010123409172’ (both ‘D’ and ‘=’ are acceptable separators) –

OK/NOK

- DE 55 SE 9F03 ('amount other') contains '000000000000' or is not present - OK/NOK

- DE 55 SE 9F34 (CVM Result) is present (effective 1 April 2017)* - Present/Not

present/Not required

- DE 61 subfield 11 = ‘3’ (card data terminal input capability: contactless M/Chip) -

OK/NOK

- ARQC is successfully validated by the simulator - OK/NOK

- Issuer simulator ARC = 00 (accepted) - OK/NOK

Note *: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages

containing DE 55 effective 1 April 2017.


© 2014 MasterCard


PPC MCD 01 Test 01b Scenario 01

Objective

To 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 ATM user. [TC028]








Applicability Terminal supports MasterCard and is an ATM


User Action



- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’


If needed select the MasterCard PayPass product.





54

© 2014 MasterCard


Pass Criteria

Visual checks:

- The ATM must display all user instructions on the existing screen. The reader must not

provide any instructions directly to the ATM user – OK/NOK


Card log checks:





- DE 3 subfield 1 (transaction type code) = '01' (withdrawal) - OK/NOK



- DE 35 contains ‘5413330089600010D14122010123409172’ or


OK/NOK

- DE 48 byte 1 (TCC) = 'Z' ('ATM Cash Disbursement') - OK/NOK




OK/NOK



Note *: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages containing DE 55 effective 1 April 2017.


© 2014 MasterCard


PPC MCD 01 Test 01c Scenario 01

Objective








Applicability Terminal supports MasterCard and is a Bank Branch.


User Action



- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’





Pass Criteria

Visual checks:


Card log checks:





- DE 3 subfield 1 (transaction type code) = '17' (cash disbursement) - OK/NOK

- DE 4 must be the cash advance amount - OK/NOK



- DE 35 contains ‘5413330089600010D14122010123409172’ or


OK/NOK

- DE 55 SE 9C (Transaction type) = '17' - OK/NOK

- DE 55 SE 9F02 (Amount, Authorized) contains the same amount as DE 4 - OK/NOK




- DE 61 subfield 11 = ‘3’ (contactless M/Chip) - OK/NOK




56

© 2014 MasterCard




Objective To ensure the PayPass terminal correctly manages the Issuer response ‘51’ (insufficient

funds). [TC043-1]

Applicability Terminal supports MasterCard and is online capable.


User Action



- ‘4.51’ or ‘4 510 000’

- ’10.51’ or ’10 510 000’

- ‘40.51’ or ’40 510 000’

- ‘100.51’ or ’100 510 000’

- or any value like *51*



Simulator The network simulator validates the authorization message and returns the response ‘51’

(insufficient funds).

Pass Criteria

Visual checks:

- The terminal declines the online transaction - OK/NOK

Card log checks:




- Simulator response is ‘51’ (insufficient funds) - OK/NOK

Note N/A


© 2014 MasterCard


PPC MCD 01 Test 02b Scenario 01

Objective To ensure the PayPass terminal prompts the cardholder to perform a contact transaction, if

supported, when the card, the terminal or the issuer declines. [TC068-3]

Applicability Terminal supports MasterCard and is online capable and supports contact transactions.

It is not an ATM.


User Action



- ‘6.65’ or ‘6 650 000’

- ’66.50’ or ’66 500 000’

- ‘665.00’ or ’665 000 000’





(exceeds withdrawal count limit).

Pass Criteria

Visual checks:


- The terminal prompts the cardholder to perform a contact transaction – OK/NOK

Card log checks:




- Simulator response is ‘65’ (exceeds withdrawal count limit) - OK/NOK

Note N/A


58

© 2014 MasterCard


PPC MCD 01 Test 02c Scenario 01

Objective



again. To ensure the ATM does not force fallback from contactless acceptance to any other

form of acceptance technology before a second transaction is attempted. [TC068b-3]

Applicability Terminal supports MasterCard and is an ATM.


User Action



- ‘6.65’ or ‘6 650 000’

- ’66.50’ or ’66 500 000’

- ‘665.00’ or ’665 000 000’






Pass Criteria

Visual checks:

- The ATM declines the online transaction - OK/NOK

- The ATM allows a repeat attempt of the failed transaction using the contactless

technology; it does not force fallback to a contact technology – OK/NOK

Card log checks:





Note N/A


© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer response ‘57’ (Transaction

not permitted). [TC043-2]



User Action



- ‘4.57’ or ‘4 570 000’

- ’10.57’ or ’10 570 000’

- ‘40.57’ or ’40 570 000’

- ‘100.57’ or ‘100 570 000’





(Transaction not permitted).

Pass Criteria

Visual checks:


Card log checks:




- Simulator response is ‘57’ (Transaction not permitted) - OK/NOK

Note N/A


60

© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer responses ‘55’ (wrong PIN).

[TC052-1]

Applicability Terminal supports MasterCard and Online PIN and has a CVM Required Limit lower than

the Contactless Transaction Limit.


User Action


Enter amount above the CVM Required Limit and below the Contactless Transaction

Limit. Possible amount values are:

- ‘5.55’ or ‘5 550 000’

- ’10.55’ or ’10 550 000’

- ‘40.55’ or ’40 550 000’

- ‘100.55’ or ‘100 550 000’



The correct PIN value is 4315. (You do not need to enter an incorrect PIN to trigger the

simulator response ‘55’ (wrong PIN)).


(wrong PIN).

Pass Criteria

Visual checks:

- The terminal must indicate the cardholder that the PIN is incorrect - OK/NOK

Card log checks:



- Amount is above the CVM Required Limit - OK/NOK

- TVR byte 3 bit 3 = 1 (Online PIN entered) - OK/NOK


- Simulator response is ‘55’ (wrong PIN) - OK/NOK

Note N/A


© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer responses ‘75’ (Allowable

number of PIN tries exceeded). [TC052-2]

Applicability Terminal supports MasterCard and Online PIN and has a CVM Required Limit lower than



User Action




- ‘4.75’ or ‘4 750 000’

- ’10.75’ or ’10 750 000’

- ‘40.75’ or ’40 750 000’

- ‘100.75’ or ‘100 750 000’




simulator response ‘75’ (Allowable number of PIN tries exceeded)).


(Allowable number of PIN tries exceeded).

Pass Criteria

Visual checks:


Card log checks:






- Simulator response is ‘75’ (Allowable number of PIN tries exceeded) - OK/NOK

Note N/A


62

© 2014 MasterCard




returned by the issuer. [TC045]



User Action



- ‘5.99’ or ‘5 990 000’

- ’10.99’ or ’10 990 000’

- ‘40.99’ or ’40 990 000’

- ‘100.99’ or ‘100 990 000’





Simulator


response:


- DE 55 SE 91 (Issuer Authentication Data) is present

- DE 55 SE 72 (Issuer Script Template 2) with one script identifier and 6 PIN


Pass Criteria

Visual checks:

- The transaction must successfully complete – OK/NOK

Card log checks:



- The terminal must not send any command to the card beyond the 1st Generate AC –

OK/NOK


- Simulator response contains DE 55 SE 91 and SE 72 - OK/NOK

Note N/A


© 2014 MasterCard



Objective To ensure that the PayPass terminal correctly implements the Contactless Transaction

Limit. Case of amount just above the limit. Terminal supports [PayPass2.x]. [TC061-2]

Applicability Terminal supports MasterCard and [PayPass2.x].

Terminal allows the user to enter amounts greater than the Contactless Transaction Limit.


User Action


- First step is to initialize the card log:

Please run a successful transaction with any amount below the Contactless Transaction

Limit and then ensure the transaction was correctly stored in the card log.

- Second step is the test itself:

Amount must be one minor unit above the MasterCard Contactless Transaction Limit*

(e.g.: 25.01€)

Tap card on the PayPass reader even if it looks deactivated.

Simulator N/A

Pass Criteria

Visual checks:

- What amount did you enter in the first step transaction?

- What amount did you enter in the second step transaction?

Card log checks:

- The card log for the second transaction is either empty or contains the log of the

transaction performed at the first step (that is, the amount in the GenerateAC command is

the amount used at the first step)** - OK/NOK

Note

*: You must consider the limit mentioned in the M-TIP Questionnaire, NOT the one

personalized in the PayPass reader. Both values are indeed different in [PayPass2.x] terminals.

**: When the test tool stores a new log for each single transaction, the log will be empty since the terminal must either not activate the PayPass reader or abort after the PPSE

response (and the PPSE is not stored in the log).

When the test tool manages a unique log file, the log will be the one from the previous

transaction since a log is not created until the SelectADF is sent, which is never the case here.


64

© 2014 MasterCard




Limit. Case of amount above the limit. Terminal supports [PayPass3.0]. [TC061-3a]

Applicability Terminal supports MasterCard and [PayPass3.0] and allows to enter amounts greater than



User Action






Amount must be one minor unit above the MasterCard Contactless Transaction Limit (e.g.:

25.01€).


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:



the amount used at the first step)* or contains a transaction that aborts after the last Read

Record response - OK/NOK

Note

*: In case the terminal does not activate the PayPass reader when the entered amount is above all the application Contactless Transaction Limits, the log will be:

- empty, when the test tool stores a new log for each single transaction

- the one from the previous transaction, when the test tool manages a unique log file.


© 2014 MasterCard



Objective

To ensure the terminal always performs cardholder verification and online authorization in

case of Purchase with Cash Back [TC260]


transaction. Purchase with Cash Back. [TC053-3]

Applicability Terminal supports Cash Back

Card details This card has no specific feature (Domestic and International Cash Back bits not set in the

AUC)

User Action


Enter any amount below the Contactless Transaction Limit.



Pass Criteria

Visual checks:

- The terminal shall approve the transaction – OK/NOK

Card log checks:



- The terminal must request an ARQC - OK/NOK

- The TVR shall indicate that the CVM was successful: TVR byte 3 bit 8 = 0 - OK/NOK

- The CVM result shall be either ’42 03 xx’ or ‘5E 03 xx’ - OK/NOK


The network simulator shall receive a 0100 (or 0200) message with the following:

- DE 3 subfield 1 (transaction type code) = '09' - OK/NOK

- DE 4 must be the sum of the purchase and cash back amounts - OK/NOK

- DE 35 contains ‘5413330089600010D14122010123409172’ or


OK/NOK

- DE 54 (Additional Amount) contains the cash back amount - OK/NOK



- DE 55 SE 9F03 (Amount, Other) contains the Cash Back amount - OK/NOK

Note Since the Domestic and International Cash Back bits are not set in the AUC, the bit ‘Requested service not allowed for card product’will be set in the TVR.


66

© 2014 MasterCard




merchant or if the terminal times out. [TC072]

Applicability Terminal supports MasterCard and Online PIN

Card details This card has no specific feature

User Action


Enter amount above the CVM Required limit and below the Contactless Transaction Limit.


Please press the cancel button when the terminal prompts for the PIN.

Simulator N/A

Pass Criteria

Visual checks:

- The terminal must prompt for PIN – OK/NOK

- The terminal must terminate the transaction when the PIN entry is cancelled – OK/NOK

Card log checks:




- The network simulator does not receive any authorization request for this transaction -

OK/NOK

Note N/A


© 2014 MasterCard



Objective



maximum length and '9F1D'. [TC011-3 and 7 and 13]


Limit. Case of amount equal to the limit. [TC061-1a]

Applicability Terminal supports MasterCard and [PayPass2.x]

The terminal allows the user to enter amounts equal to the Contactless Transaction Limit.

Card details




User Action







Pass Criteria

Visual checks:


Card log checks:

- Application Label indicates "PPC MCD 02 v2 2" - OK/NOK


- In GetPO command, the '9F1D' tag value is all zeroes – OK/NOK


Note

*: if the terminal supports [PayPass2.x] you must consider the limit mentioned in the M-TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are indeed different in [PayPass2.x] terminals.


68

© 2014 MasterCard



Objective





Limit. Case of amount equal to the limit. [TC061-1a]

Applicability Terminal supports MasterCard and [PayPass3.0]


Card details




User Action







Pass Criteria

Visual checks:


Card log checks:



- In GetPO command, the '9F1D' tag value is correct: byte 1 bit 7 is set if the terminal

supports Online PIN, byte 1 bit 3 is set if the terminal supports on-device CVM, byte 3 is

'00' – OK/NOK


Note N/A


© 2014 MasterCard



Objective




Applicability

Terminal supports MasterCard and [PayPass2.x].

The terminal does not allow the user to enter amounts equal to the Contactless Transaction

Limit.

Card details




User Action







Pass Criteria

Visual checks:


Card log checks:




Note N/A


70

© 2014 MasterCard



Objective




Applicability

Terminal supports MasterCard and [PayPass3.0].


Limit.

Card details




User Action







Pass Criteria

Visual checks:


Card log checks:





'00' – OK/NOK

Note N/A


© 2014 MasterCard



Objective

To ensure the PayPass terminal does not support offlinePIN. Case of amount below the

CVM Required Limit. [TC021-1]

To ensure that the PayPass terminal does not use the service code in order to require online

authorization or Online PIN. Service Code is ‘206’ and amount is below the limit. [TC067-

1]

Applicability

Terminal supports MasterCard and has a CVM Required Limit greater than zero for the

MasterCard application.

Terminal does not support refund.

Card details

The first CVM method in the CVM list is “OfflinePIN”.

The CVM list does not include Online PIN and Service Code contained in Track2 is ‘206’

(Normal Authorization, PIN if pinpad present).

User Action


Enter any amount below the CVM Required Limit.




Pass Criteria

Visual checks:

- The terminal does not prompt for any PIN to be entered - OK/NOK


Card log checks:



- The amount is below the CVM Required Limit - OK/NOK

- The terminal does not send any VerifyPIN command - OK/NOK

- TVR byte 3 bit 5 = 0 (Online PIN not required) - OK/NOK


- TVR byte 3 bit 3 = 0 (Online PIN not entered) - OK/NOK

- The CVM results byte 1 is different from '41' - OK/NOK

Note N/A


72

© 2014 MasterCard



Objective



To ensure the PayPass terminal does not use the service code to require Online PIN or

online authorization. Service Code is ‘206’ and amount is below the limit. [TC067-1]

To ensure the PayPass terminal correctly performs refund. Case [PayPass2.0]. [TC025-1]

Applicability Terminal supports MasterCard and has a CVM Required Limit greater than zero.

Terminal supports refund and [PayPass2.0].

Card details




User Action





Please store the card log since it will be required after the subsequent refund transaction.







Pass Criteria

Visual checks - first step (purchase):



Card log checks - first step (purchase):









Visual checks - second step (refund):

- The end of the transaction is out of scope.

- At the end of the refund process, the terminal displays a message to inform the cardholder

that refund has been done successfully - OK/NOK

Card log checks - second step (refund):



Note N/A


74

© 2014 MasterCard



Objective



To ensure the terminal does not use the service code to require online authorization or

Online PIN. Service Code is ‘206’ and amount is below the limit. [TC067-1]

To ensure the PayPass terminal correctly performs refund. Case of [PayPass2.1] or

[PayPass3.0]. [TC025-2]

Applicability Terminal supports MasterCard and refund and ([PayPass2.1] or [PayPass3.0]).

The CVM Required Limit equals the Contactless Transaction Limit.

Card details




User Action












Pass Criteria

Visual checks - first step (purchase):



Card log checks - first step (purchase):









Visual checks – second step (refund):



Card log checks – second step (refund):



- The terminal requests an AAC - OK/NOK


© 2014 MasterCard


Note N/A


Objective

To ensure the PayPass terminal does not support offlinePIN. Case of amount above the



authorization or Online PIN. Service Code is ‘206’. [TC067-2]

To ensure the attended PayPass terminal correctly manages the cardholder verification.

Case of Signature. [TC221-1]

Applicability Terminal supports MasterCard and is attended. It does not support refund.

The CVM Required Limit is lower than the Contactless Transaction Limit.

Card details


The CVM list includes Signature.



User Action


Amount must be the lowest value above the CVM Required Limit* (e.g.: 25.01€).




Pass Criteria

Visual checks:


- The terminal requests signature for cardholder verification - OK/NOK


Card log checks:



- Amount is the lowest value above the CVM Required Limit - OK/NOK


- TVR byte 3 bit 8 = 0 (Cardholder verification was successful) - OK/NOK




- CVM result is ‘5E 03 00’ - OK/NOK

Note

*: if the terminal supports [PayPass2.x] you must consider the limit mentioned in the M-TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are



76

© 2014 MasterCard



Objective





To ensure the PayPass terminal correctly performs refund. Case of [PayPass2.0]. [TC025-

1]



Applicability Terminal supports MasterCard and is attended. It supports refund and [PayPass2.0].

The CVM Required Limit is lower than the Contactless Transaction Limit

Card details





User Action













© 2014 MasterCard


Pass Criteria

Visual checks – first step (purchase):




Card log checks – first step (purchase):

















Note




78

© 2014 MasterCard



Objective

To ensure the PayPass terminal does not support offlinePIN. [TC021-2]



To ensure the PayPass terminal correctly performs refund. Case of [PayPass2.1] or

[PayPass3.0]. [TC025-2]



Applicability

Terminal supports MasterCard and is attended. It supports refund and ([PayPass2.1] or

[PayPass3.0]).


Card details





User Action













© 2014 MasterCard


Pass Criteria






















Note




80

© 2014 MasterCard



Objective




To ensure the CAT1 terminal correctly manages the cardholder verification. Case of card

supporting Signature. [TC222-1]

Applicability Terminal supports MasterCard and is a CAT1 or a CAT1/2.

Card details





User Action


Enter any amount above the CVM Required Limit and below the Contactless Transaction

Limit.



Pass Criteria

Visual checks:


- The terminal does not request signature for cardholder verification - OK/NOK


Card log checks:




- TVR byte 3 bit 8 = 1 (Cardholder verification was NOT successful) - OK/NOK




- CVM result is ‘3F 00 01’ - OK/NOK


- DE 55 SE 9F34 (CVM Results)* = ‘3F 00 01’ - OK/NOK/Not present


Note *: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages containing DE 55 effective 1 April 2017


© 2014 MasterCard



Objective




To ensure the CAT2 and CAT3 terminals correctly manage the cardholder verification.

Case of card supporting Signature. [TC223-1]

Applicability Terminal supports MasterCard and is a CAT2 or a CAT3.


Card details





User Action



Limit.




Pass Criteria

Visual checks:


- The terminal does not request signature for cardholder verification - OK/NOK


Card log checks:









- CVM result is ‘1F 03 00’ or '1F 03 02' - OK/NOK

Note N/A


82

© 2014 MasterCard



Objective To ensure the attended PayPass terminal correctly manages the cardholder verification.

Case of Signature with gratuity. [TC221-2]

Applicability Terminal supports MasterCard and is attended and supports gratuity.


Card details The first CVM method in the CVM list is “OfflinePIN”.


User Action


The sum of transaction and gratuity amounts must be the lowest value above the CVM

Required Limit* (e.g.: 25.01€).




Pass Criteria

Visual checks:

- What transaction amount did you enter?

- What gratuity amount did you enter?




Card log checks:



- The sum of transaction and gratuity amounts is the lowest value above the CVM

Required Limit - OK/NOK



Note


TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are indeed different in [PayPass2.x] terminals.


© 2014 MasterCard



Objective





Card details




User Action




Simulator N/A

Pass Criteria

Visual checks:


- The terminal declines the transaction - OK/NOK

Card log checks:









- CVM result is ‘3F 00 01’ - OK/NOK

Note N/A


84

© 2014 MasterCard



Objective

To ensure that the PayPass terminal performs CDA correctly. [TC002-1]

To ensure the PayPass terminal correctly supports different certification authority public

key lengths. CA key length is 1984/248. [TC003-3]

To ensure the PayPass terminal correctly supports the exponent 2^16+1. [TC004]

Applicability Terminal supports MasterCard and is offline capable and has a CVM Required Limit

greater than zero for the MasterCard application.

Card details The returned AIP indicates that the card supports CDA.


User Action

Please use the following test card: M-TIP Subset 8 – PPC MCD 04 v2.0 or v2.2.

Enter any amount below the Floor Limit and the CVM Required Limit.


Simulator N/A

Pass Criteria

Visual checks:

- The terminal approves the offline transaction - OK/NOK

Card log checks:

- Application Label indicates "PPC MCD 04 v2 2" (or v2 0) - OK/NOK


- Amount is below the Floor Limit and the CVM Required Limit - OK/NOK

- TVR byte 1 bit 8 = 0 (ODA was performed) - OK/NOK

- The terminal requests a TC with CDA (‘50’) in the Generate AC - OK/NOK

Note N/A


© 2014 MasterCard



Objective





Applicability Terminal supports MasterCard and is offline capable and has a CVM Required Limit equal

to zero and is not a CAT 1.



User Action


Enter any amount below the Floor Limit.


Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



- Amount is below the Floor Limit - OK/NOK



Note N/A


86

© 2014 MasterCard



Objective




Applicability Terminal supports MasterCard and CDA and [PayPass3.0].

It is online-only or is a CAT 1. It is not an ATM.



User Action




Simulator The network simulator validates the authorization message (not the ARQC) and returns

‘00’ (accepted).

Pass Criteria

Visual checks:


Card log checks:




- The terminal requests an ARQC with CDA (‘90’) in the Generate AC - OK/NOK

Note N/A


© 2014 MasterCard



Objective


key lengths. Case of 1408/176. [TC003-2]


or length from the card. Case of SDA signed record having maximum length. [TC011-8]



To ensure that the PayPass terminal performs SDA correctly. [TC201]

Applicability Terminal supports MasterCard and is offline capable.

Terminal supports SDA.

Card details

The card returns a record with the maximum length (254 bytes).

Card supports SDA only.

CA key length is 1408/176.

The Service Code contained in Track2 is ‘226’ (Issuer Authorization, PIN if pinpad

present).


User Action


Enter an amount below the Floor Limit.


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:



- Amount is below the Floor Limit - OK/NOK


- TVR byte 1 bit 7 = 0 (SDA was successful) - OK/NOK




- The terminal requests a TC without CDA ‘40’ - OK/NOK

Note N/A


88

© 2014 MasterCard



Objective To ensure that the PayPass terminal does not use the service code in order to require online


Applicability Terminal supports MasterCard and is online-only and supports SDA. It is not an ATM.

Card details


present).


User Action


Enter an amount below the Contactless Transaction Limit.



Pass Criteria

Visual checks:



Card log checks:




- TVR byte 1 bit 7 = 0 (SDA was successful) - OK/NOK




Note N/A


© 2014 MasterCard



Objective

To ensure the PayPass terminal does not support SDA, when applicable. [TC006]



Applicability Terminal supports MasterCard and is online capable and does not support SDA.

It is not an ATM

Card details

AIP indicates that the card supports SDA but not CDA.


present).


User Action





Pass Criteria

Visual checks:



Card log checks:



- TVR byte 1 bit 8 = 1 (ODA was not performed) - OK/NOK

- TVR byte 1 bit 7 = 0 (SDA did not fail) - OK/NOK

- TVR byte 1 bit 3 = 0 (CDA did not fail) - OK/NOK




- The terminal requests an ARQC - OK/NOK

Note N/A


90

© 2014 MasterCard



Objective




Applicability Terminal supports MasterCard and is offline-only and does not support SDA.

Card details

AIP indicates that the card supports SDA but not CDA.


present).


User Action




Simulator N/A

Pass Criteria

Visual checks:



Card log checks:










Note N/A


© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the extended AIDs. Case of AID

extended with ‘D056 01’. [TC065-1]

Applicability

Terminal supports MasterCard.

Terminal does not support receipt printing or the CVM Required Limit equals the


Card details The card has an extended AID ‘A0 00 00 00 04 10 10 D056 01’.

User Action

Please, use the following test card: M-TIP Subset 8 – PPC MCD 07 v2.0 or v2.1 or v2.2.






Pass Criteria

Visual checks:


Card log checks:

- The terminal selects the AID ‘A0 00 00 00 04 10 10 D056 01’ - OK/NOK



Note N/A


92

© 2014 MasterCard



Objective

To ensure the PayPass terminal correctly manages the extended AIDs. Case of AID


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

CVM required Limit [TC024-2]

Applicability

Terminal supports MasterCard.

Terminal supports receipt printing and the CVM Required Limit is lower than the


Card details The card has an extended AID ‘A0 00 00 00 04 10 10 D056 01’.

User Action

Please, use the following test card: M-TIP Subset 8 – PPC MCD 07 v2.0 or v2.1 or v2.2.


Limit.





Pass Criteria

Visual checks:


- The terminal prints a cardholder receipt without requesting it - OK/NOK

Card log checks:




Note N/A


© 2014 MasterCard




extended with ‘C123456789’. [TC065-2]


Card details The card has an extended AID ‘A0 00 00 00 04 10 10 C123456789’.

Note: the cards always returns an ARQC.

User Action






Pass Criteria

Visual checks:


Card log checks:

- The terminal selects the AID ‘A0 00 00 00 04 10 10 C123456789’ - OK/NOK





Note N/A


94

© 2014 MasterCard



Objective

To ensure the offline-only PayPass terminal correctly behaves when the card erroneously

sends an ARQC. [TC005]


extended with ‘C123456789’. [TC065-2]

Applicability Terminal supports MasterCard and is offline-only.

Card details The card has an extended AID ‘A0 00 00 00 04 10 10 C123456789’.

The cards always returns an ARQC.

User Action




Simulator N/A

Pass Criteria

Visual checks:

- The terminal terminates the transaction - OK/NOK

Card log checks:

- The terminal selects the AID ‘A0 00 00 00 04 10 10 C123456789’ - OK/NOK



- the card returns an ARQC - OK/NOK

Note N/A


© 2014 MasterCard



Objective


or length from the card. Case of Unrecognized CVM. [TC011-6]


or length from the card. Case of tag ‘9F6E’. [TC011-11]

To ensure that a terminal has its application version number for PayPass - M/Chip set to

′0002′. [TC062]

Applicability Terminal supports MasterCard.

Card details

The card returns an unrecognized CVM in the CVM list.

The card returns the tag ‘9F6E’ in a Read Record (PayPass Third Party data).

The card Application Version Number is set to ‘0002’.

User Action







Pass Criteria

Visual checks:


Card log checks:



- TVR byte 2 bit 8 = 0 (ICC & terminal have same application versions) - OK/NOK

- TVR byte 3 bit 7 = 1 (Unrecognized CVM) - OK/NOK

Note N/A


96

© 2014 MasterCard



Objective

To ensure the PayPass terminal correctly behaves when the card does not support any

offline data authentication method. Amount below the Floor Limit and the CVM Required

Limit. [TC001-1a]

To ensure the PayPass terminal transmits transaction mandatory data to the network even

if it is not requested by the card in the CDOL1. [TC046]


message containing DE 55 [TC054-3]

To ensure the terminal correctly transmits the Device Type data element in the

authorization message, if supported. [TC055-1]

Applicability Terminal supports MasterCard and is offline and online capable and has a CVM Required

Limit greater than zero for the MasterCard application.

Card details

The returned AIP indicates that SDA and CDA are not supported.


‘9A’), Transaction Type (tag ‘9C’) Transaction Currency Code (tag ‘5F2A’) and CVM

Results (tag '9F34') in the CDOL1.

The card returns a Third Party Data indicating a device type 'card'.

User Action


Enter any amount below the Floor Limit and the CVM Required Limit.




Pass Criteria

Visual checks:


Card log checks:



- Amount must be below the Floor Limit and the CVM Required Limit.- OK/NOK




- DE 48 SE 23 value is '00' (effective 19 April 2013 in US region and 17 October 2014 in

Canada for newly deployed devices)* - OK/NOK/Not required

- DE 55 SE 5F2A (Transaction Currency Code) is present and value is correct - OK/NOK

- DE 55 SE 9A (Transaction Date) is present and value is correct - OK/NOK

- DE 55 SE 9C (Transaction Type) value is '00' (goods and services) - OK/NOK

- DE 55 SE 9F1A (Terminal Country Code) is present and value is correct - OK/NOK

- DE 55 SE 9F34 (CVM Result) is present (effective 1 April 2017)** - Present/Not


Note

*: U.S. region acquirers (effective 19 April 2013) and Canada acquirers (effective 17 October 2014 for newly deployed devices) must transmit the device type indicator value (DE 48 SE 23), if present on the card or non-card form factor.

**: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages



© 2014 MasterCard



Objective


offline data authentication method. Amount below the Floor Limit. [TC001-1b]







Applicability Terminal supports MasterCard and is offline and online capable and has a CVM Required

Limit equal to zero for the MasterCard application.

Card details



‘9A’), Transaction Type (tag ‘9C’), Transaction Currency Code (tag ‘5F2A’) and CVM



User Action


Enter any amount below the Floor Limit.





Pass Criteria

Visual checks:


Card log checks:



- Amount must be below the Floor Limit - OK/NOK












Note

*: U.S. region acquirers (effective 19 April 2013) and Canada acquirers (effective 17 October 2014 for newly deployed devices) must transmit the device type indicator value

(DE 48 SE 23), if present on the card or non-card form factor.




98

© 2014 MasterCard



Objective


offline data authentication method. Amount above the Floor Limit. [TC001-2]








The Floor Limit is lower than the Contactless Transaction Limit.

Card details



‘9A’), Transaction Type (tag ‘9C’), Transaction Currency Code (tag ‘5F2A’) and CVM



User Action


Enter any amount above the Floor Limit and below the Contactless Transaction Limit.





Pass Criteria

Visual checks:


Card log checks:



- Amount is above the Floor Limit - OK/NOK







- DE 55 SE 9C (Transaction Type) value is '00' (goods and services) or '01' (cash ATM) or

'17' (funds withdrawal) - OK/NOK




Note






© 2014 MasterCard




offline data authentication method. Case of offline-only terminal. [TC001-3]

Applicability Terminal supports MasterCard and is offline-only and does not support contact

transactions.

Card details The returned AIP indicates that SDA and CDA are not supported.

User Action




Simulator N/A

Pass Criteria

Card log checks:





Note N/A


Objective



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


Applicability Terminal supports MasterCard and is offline-only and supports contact transactions.


User Action




Simulator N/A

Pass Criteria

Visual checks:

- the terminal declines the transaction – OK/NOK

- the terminal prompts the cardholder to perform a contact transaction since the contactless

transaction declined - OK/NOK

Card log checks:





Note N/A


100

© 2014 MasterCard




or length from the card. Cases of Service Code discrepancy and '9F2A'. [TC011-2 and 14]

Applicability Terminal supports MasterCard. It is attended not supporting Online PIN.


Card details

The card returns the tag '9F2A' (Kernel Identifier) in the PPSE.

The Service Code returned in the track2 (‘57’) is different from the one in the specific tag

(‘5F30’).

The card supports Online PIN then noCVM (‘1F 03’).

User Action



Limit.




Pass Criteria

Visual checks:


Card log checks:




Note N/A


© 2014 MasterCard



Objective



To ensure the PayPass terminal correctly manages the Online PIN verification, when

supported. Case of 4 digits PIN. [TC051-1]


Case of Online PIN supported. [TC221-3]

Applicability Terminal supports MasterCard and is attended supporting Online PIN.


Card details



(‘5F30’).

The card supports Online PIN (’42 03’) then noCVM.

User Action




PIN value is 4315.


Pass Criteria

Visual checks:

- The terminal prompts for PIN - OK/NOK


Card log checks:







- CVM result must be ‘42 03 00’ - OK/NOK


- DE 52 is present - OK/NOK

- The network simulator displays the correct PIN value: “PIN Validation, PIN = xxxx”

where xxxx is the PIN entered – OK/NOK

- DE 55 SE 9F34 (CVM Results)** = ‘42 03 00’ - OK/NOK/Not present


Note


TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are indeed different in [PayPass2.x] terminals.

**: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages containing DE 55 effective 1 April 2017


102

© 2014 MasterCard



Objective






Card details



(‘5F30’).


User Action




PIN value is 4315.


Pass Criteria

Visual checks:



Card log checks:











- DE 55 SE 9F34 (CVM Results)* = ‘42 03 00’ - OK/NOK/Not present




© 2014 MasterCard



Objective





To ensure the CAT1 PayPass terminal correctly manages the cardholder verification above

the CVM Required Limit. Case of Online PIN supported. [TC222-2]


Card details



(‘5F30’).


User Action



Limit.


PIN value is 4315.


Pass Criteria

Visual checks:



Card log checks:















104

© 2014 MasterCard



Objective



To ensure the CAT2 and CAT3 PayPass terminals correctly manage the cardholder

verification. Case of card supporting Online PIN. [TC223-2]

Applicability Terminal supports MasterCard and is a CAT2 or a CAT3.

The CVM Required limit is lower than the Contactless Transaction Limit.

Card details



(‘5F30’).

The card supports Online PIN then noCVM (‘1F 03’).

User Action


Enter any amount above the CVM Required limit and below the Contactless Transaction

Limit.




Pass Criteria

Visual checks:

- The terminal does neither prompt for PIN nor request signature - OK/NOK


Card log checks:





- CVM result must be ‘1F 03 00’ or '1F 03 02' - OK/NOK

Note N/A


© 2014 MasterCard





Applicability Terminal supports MasterCard.


Card details The Service Code returned in the track2 (‘57’) is different from the one in the specific tag

(‘5F30’).

User Action







Pass Criteria

Visual checks:


Card log checks:



Note N/A


106

© 2014 MasterCard


PPC MCD 4A Test 01 Scenario 01

Objective

To ensure the terminal correctly completes the transaction with a Mobile. Amount below

the CVM Required Limit. [TC038-1]

To ensure the PayPass terminal correctly manages the PayPass values in the existing

authorization fields. [TC050-2]


transaction. Purchase with a mobile. [TC053-2]


message containing DE 55 (effective 1 April 2017).[TC054-2]



Applicability

Terminal supports [PayPass3.0] and MasterCard and is online capable.


The terminal configuration is such that the Kernel Configuration indicates 'On-Device

Cardholder Verification supported' and the Contactless Transaction Limit (On-device

CVM) is not zero.

Card details AIP byte 1 bit 2 is set ("On-device cardholder verification supported").


User Action

- A first transaction is performed where the card requests On-Device cardholder

verification:

Please use the following test card: M-TIP Subset 8 – PPC MCD 4A v1.0.

Enter any amount below the CVM Required Limit and below the Contactless Transaction

Limit (On-device CVM).


- A second transaction is performed where the Mobile indicates that the Mobile PIN was

successfully verified:

Please use the following test card: M-TIP Subset 8 – PPC MCD 4B v1.0.

If needed, the transaction amount must be the same as in the previous transaction.




© 2014 MasterCard


Pass Criteria

Visual checks – first transaction:

- The terminal displays "Please see phone" (or equivalent) - OK/NOK

Card log checks – first transaction:

- Application Label indicates "PPC MCD 4A v1 0" - OK/NOK


Visual checks – second transaction:


Card log checks – second transaction:

- Application Label indicates "PPC MCD 4B v1 0" - OK/NOK


- In GenAC command, the CVM results value must be '3F 00 02' - OK/NOK

Network simulator checks – second transaction:

The following data must be observed on the 0100 or 0200 message:



- DE 35 contains ‘5413330089600408D25122010123409172’ (both ‘D’ and ‘=’ are

acceptable separators) – OK/NOK



- DE 55 SE 9F03 ('amount other') either contains '000000000000' or is not present -

OK/NOK

- DE 55 SE 9F34 (CVM Results)** = '3F 00 02' - OK/NOK/Not present


OK/NOK



Note




containing DE 55 effective 1 April 2017


108

© 2014 MasterCard



Objective

To ensure the terminal correctly completes the transaction with a Mobile. Amount above







message containing DE 55 (effective 1 April 2017).[TC054-2]



Applicability





Cardholder Verification supported'.



User Action


verification:












© 2014 MasterCard


Pass Criteria











- In GenAC command, the CVM results value must be '01 00 02' - OK/NOK










OK/NOK

- DE 55 SE 9F34 (CVM Results)** = '01 00 02' – OK/NOK/Not present


OK/NOK



Note






110

© 2014 MasterCard



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


Applicability

Terminal supports [PayPass3.0] and MasterCard and is offline-only.


The terminal configuration is such that the Kernel Configuration indicates 'On-Device Cardholder Verification supported' and the Contactless Transaction Limit (On-device

CVM) is not zero.



User Action


verification:










Simulator N/A

Pass Criteria












Note N/A


© 2014 MasterCard



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


Applicability

Terminal supports [PayPass3.0] and MasterCard and is offline-only.







User Action


verification:










Simulator N/A

Pass Criteria












Note N/A


112

© 2014 MasterCard


PPC MCD 4B Test 01 Scenario 01

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

[TC061-1b]

Applicability


The terminal configuration is such that it allows to enter amounts equal to the Contactless






User Action


Amount is equal to the Contactless Transaction Limit (On-device CVM).



Pass Criteria

Visual checks:


Card log checks:



- Amount equals the Contactless Transaction Limit (On-device CVM) - OK/NOK

Note


© 2014 MasterCard




[TC061-1b]

Applicability

Terminal supports [PayPass3.0] and MasterCard and is offline only.







User Action




Simulator N/A

Pass Criteria

Visual checks:


Card log checks:




Note


114

© 2014 MasterCard




[TC061-3b]

Applicability

Terminal supports [PayPass3.0] and MasterCard and On Device Cardholder Verification

and allows to enter amounts greater than the Contactless Transaction Limit (On Device

CVM).



User Action




Limit (On-device CVM) and then ensure the transaction was correctly stored in the card

log.


Amount is equal to one minor unit above the Contactless Transaction Limit (On-device

CVM) (e.g.:25.01€).


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:





Note

*: In case the terminal does not activate the PayPass reader when the entered amount is

above all the application Contactless Transaction Limits, the log will be:




© 2014 MasterCard



Objective

To ensure the terminal not supporting "On-device cardholder verification" correctly

completes the transaction with a Mobile. [TC037]



Applicability Terminal supports MasterCard and is online capable and does not support [PayPass3.0] or

the "Kernel Configuration" indicates "On-device cardholder verification NOT supported"



User Action


Amount must be below the Contactless Transaction Limit.




Pass Criteria

Visual checks:


Card log checks:






Note



116

© 2014 MasterCard





Applicability Terminal supports MasterCard and is offline only and does not support [PayPass3.0] or the

"Kernel Configuration" indicates "On-device cardholder verification NOT supported"



User Action


Amount must be below the Contactless Transaction Limit.


Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



Note


© 2014 MasterCard



Objective


or length from the card.[TC011-12]

To ensure the terminal correctly completes the payment transaction when the card supports

Data Storage.[TC026-1]

Applicability Terminal supports MasterCard and not IDS.

Card details


The card returns the Application Capabilities Information '01 05 00' (DS version 1, field off

request, CDA over AAC, Undefined SDS configuration**).




User Action






Pass Criteria

Visual checks:

- The terminal does not display or print any balance information – OK/NOK


Card log checks:



Note N/A


118

© 2014 MasterCard



Objective




Data Storage. Case of volatile slot. [TC026-3]

Applicability Terminal supports MasterCard and IDS.

Card details


The card returns the Application Capabilities Information '01 05 00' (DS version 1, field off

request, CDA over AAC, Undefined SDS configuration**).




Whatever the DS Requested Operator ID provided in the GetPO command, the card returns

AIP, AFL, '9F5F 01 40' (volatile slot), '9F7F' (DS Unpredictable Number), '9F7D 08

00…00' (DS Summary 1).

When the GenAC command includes the DSDOL data then Summary2 and Summary3 are

included in the SDAD. Summary2=Summary1. Summary3<>Summary2.

User Action






Pass Criteria

Visual checks:



Card log checks:



- In the GetPO response, the card returns AIP, AFL, '9F5F 01 40' (volatile slot), '9F7F' (DS

Unpredictable Number), '9F7D 08 00…00' (DS Summary 1) - OK/NOK

Note N/A


© 2014 MasterCard


PPC MAP 01 Test 01 Scenario 01

Objective




or length from the card. Case of CDA record having maximum length. [TC011-9]

To ensure that the PayPass terminal does not prompt for a contact transaction when the

service code indicates a chip is present on the card. Service Code is ‘220’. [TC066]



Applicability

Terminal supports MasterCard and is offline capable and is not a CAT 1.

It may be a CAT1/2 if the Floor Limit is below (or equal to) the CVM Required limit.

The Floor Limit is below the Contactless Transaction limit.

The terminal allows to enter an amount equal to the Floor limit.

Card details


Card supports CDA.

The Service Code contained in Track2 is ‘220’(Issuer Authorization, PIN required)



User Action

Please use the following test card: M-TIP Subset 8 – PPC MAP 01 v2.0 or v2.1 or v2.2.

Enter any amount equal to the Floor Limit.


Simulator N/A

Pass Criteria

Visual checks:

- The terminal must not prompt for a contact transaction - OK/NOK



Card log checks:

- Application Label indicates "PPC MAP 01 v2 2" (or v2 1 or v2 0) - OK/NOK


- Amount must be equal to the Floor Limit - OK/NOK


- TVR byte 1 bit 3 = 0 (CDA was successful) - OK/NOK




Note N/A


120

© 2014 MasterCard


PPC MAP 01 Test 01b Scenario 01

Objective









Applicability

Terminal supports MasterCard and is offline capable and is not a CAT1.

The Floor Limit is above the Contactless Transaction limit,

or it is a CAT1/2 with the Floor Limit greater than the CVM Required limit,

or the terminal does not allow to enter an amount equal to the Floor limit.

Card details


Card supports CDA.




User Action


Enter any amount below the CVM Required limit.


Simulator N/A

Pass Criteria

Visual checks:




Card log checks:



- Amount is below the CVM Required limit - OK/NOK






Note N/A


© 2014 MasterCard



Objective







Applicability Terminal supports MasterCard and is online-only and is not an ATM or is a CAT 1.

It does not support [PayPass3.0] or does not support CDA

Card details




User Action





Pass Criteria

Visual checks:




Card log checks:








Note N/A


122

© 2014 MasterCard



Objective



To ensure the ATM correctly performs Cardholder Verification. [TC034-1]

To ensure the PayPass terminal does not use the service code in order to require online







Card details




User Action


Enter the smallest possible amount below the Contactless Transaction Limit.


Simulator N/A

Pass Criteria

Visual checks:

- The ATM does neither prompt for PIN nor request signature - OK/NOK

- The ATM declines the transaction - OK/NOK


technology, it does not force fallback to a contact technology – OK/NOK

Card log checks:



- TVR byte 3 bit 8 = 1 (Cardholder verification failed) - OK/NOK




- CVM Result shall be ‘3F 00 01’- OK/NOK

- ATM requests an AAC – OK/NOK

Note N/A


© 2014 MasterCard



Objective









Applicability Terminal supports MasterCard and [PayPass3.0] and CDA and is online-only and is not an

ATM or is a CAT 1.

Card details




User Action





Pass Criteria

Visual checks:




Card log checks:










Note N/A


124

© 2014 MasterCard




supported, when the card declines. [TC068-1]

Applicability Terminal supports MasterCard and contact and is not an ATM

Card details The card always returns an AAC.

User Action




Simulator N/A

Pass Criteria

Visual checks:

- the terminal declines the transaction – OK/NOK

- the terminal shall prompt the cardholder to perform a contact transaction - OK/NOK

Card log checks:



- terminal requests a TC or an ARQC – OK/NOK

- the card returns an AAC – OK/NOK

Note N/A


© 2014 MasterCard



Objective





Applicability Terminal supports MasterCard and is an ATM


User Action




Simulator N/A

Pass Criteria

Visual checks:

- the ATM declines the transaction – OK/NOK

- the ATM allows a repeat attempt of the failed transaction using the contactless

technology, it does not force fallback to a contact technology - OK/NOK

Card log checks:





Note N/A


126

© 2014 MasterCard



Objective

To ensure the PayPass terminal transmits the PAN sequence number coming from the chip

and not from the Track2 equivalent data item. [TC047]


verification above the CVM Required Limit. Case of card supporting noCVM only.

[TC223-3]

Applicability Terminal supports MasterCard and is a CAT2 online capable.


Card details




User Action



Limit.



Pass Criteria

Visual checks:



Card log checks:





- CVM result shall be ‘1F 03 00’ or '1F 03 02' - OK/NOK


- DE 23 (card sequence number) = '049' - OK/NOK

- DE 55 SE 9F34 (CVM Results)* = ‘1F 03 00’ or '1F 03 02' - OK/NOK/Not present




© 2014 MasterCard



Objective



[TC223-3]

Applicability Terminal supports MasterCard and is a CAT2 offline-only.


Card details The card supports noCVM only (‘1F 03’).

User Action



Limit.


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:






Note N/A


128

© 2014 MasterCard



Objective



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

[TC035]


Card details




User Action



Limit.



Pass Criteria

Visual checks:



Card log checks:




- CVM result shall be ‘3F 00 01’ - OK/NOK







© 2014 MasterCard



Objective



[TC223-3]

Applicability Terminal supports MasterCard and is a CAT3.



User Action



Limit.


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:






Note N/A


130

© 2014 MasterCard



Objective To ensure the PayPass terminal transmits the PAN sequence number coming from the chip


Applicability Terminal supports MasterCard and is attended and online capable.


Card details The PAN sequence number value from the tag ‘5F34’ is different from the one in the


User Action

Please use the following test card: M-TIP Subset 8 - PPC MAP 04 v2.0 or v2.1 or v2.2.




Pass Criteria

Visual checks:


Card log checks:






Note N/A


© 2014 MasterCard



Objective


[TC035]



Applicability Terminal supports MasterCard and is attended and online capable.


Card details




User Action



Limit.



Pass Criteria

Visual checks:



Card log checks:












132

© 2014 MasterCard




[TC035]

Applicability Terminal supports MasterCard and is attended and offline-only.



User Action



Limit.


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:






Note N/A



or length from the card. Case of maximum Track2 length. [TC011-5]


Card details The Track2 data (tag ‘57’) has the maximum length (37 digits).

User Action




Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



Note N/A


© 2014 MasterCard



Objective



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

[TC042]


It does not support Online PIN.


User Action





Pass Criteria

Visual checks:


Card log checks:




- DE 35 contains '5413330089601067D14122020123409172999’ or

'5413330089601067D25122020123409172999’ (both ‘D’ and ‘=’ are acceptable

separators) - OK/NOK

- DE 55 SE 9F27 value is '80' – OK/NOK


Note N/A


134

© 2014 MasterCard



Objective




[TC042]



Applicability Terminal supports MasterCard and Online PIN and is not an ATM.



The card has a 6 digits PIN (431555).

User Action



Limit.


PIN value is 431555.


Pass Criteria

Visual checks:



Card log checks:



- Amount above the CVM Required Limit - OK/NOK



- DE 35 contains '5413330089601067D14122020123409172999’ or







Note N/A


© 2014 MasterCard



Objective





[TC042]






User Action




PIN value is 431555.


Pass Criteria

Visual checks:



Card log checks:



- The terminal requests an ARQC- OK/NOK


- CVM result is ‘42 03 00’ - OK/NOK


- DE 35 contains '5413330089601067D14122020123409172999’ or










136

© 2014 MasterCard



Objective


or length from the card. Case of Track1 maximum length. [TC011-4]

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

CVM Required Limit.[TC024-1]

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

PayPass transactions below or equal to the defined limit. [TC031]

Applicability Terminal supports MasterCard and receipt printing.

It has a CVM Required Limit greater than zero for the MasterCard application.

Card details The Track1 discretionary data (tag ‘9F1F’) has the maximum length (48 bytes).

The card contains (‘4203 5E03 1F03’) in the CVM list.

User Action






Pass Criteria

Visual checks:


- The terminal is able to print a cardholder receipt below the CVM Required Limit in case

the cardholder requests it - OK/NOK

- The terminal does neither prompt for PIN nor print a signature receipt - OK/NOK

Card log checks:



- Amount is below the CVM Required Limit - OK/NOK


- CVM Result must indicate ‘1F0300’ or ‘1F0302’ - OK/NOK

Note N/A


© 2014 MasterCard





Applicability

Terminal supports MasterCard and not Online PIN and has a CVM Required Limit equal to

zero.

Terminal does not support [PayPass3.0] or does not support CDA or is offline-only or the

floor limit is above the Contactless Transaction Limit.


User Action







Pass Criteria

Visual checks:


Card log checks:



Note N/A


138

© 2014 MasterCard



Objective



key lengths. [TC003-2]



Applicability

Terminal supports MasterCard and not Online PIN and has a CVM Required Limit equal to

zero.

Terminal supports [PayPass3.0] and CDA and has a floor limit lower than the Contactless

Transaction Limit.


User Action


Enter any amount above the floor limit and below the Contactless Transaction Limit.




Pass Criteria

Visual checks:


Card log checks:



- The terminal shall request an ARQC with CDA (‘90’) - OK/NOK

- TVR byte 1 = '00' (CDA successful) - OK/NOK

Note N/A


© 2014 MasterCard



Objective




Applicability

Terminal supports MasterCard and not Online PIN and has a CVM Required Limit greater

than zero.

Terminal supports [PayPass3.0] and CDA and has a floor limit lower than the Contactless

Transaction Limit.

Card details The card supports CDA.

User Action


Enter any amount above the floor limit and below the Contactless Transaction Limit.




Pass Criteria

Visual checks:


Card log checks:





Note N/A


140

© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Online PIN verification, when


Applicability

Terminal supports MasterCard and Online PIN and has a CVM Required Limit greater

than zero for the MasterCard application.

Terminal does not support [PayPass3.0] or does not support CDA.

Card details The card has a 5 digits PIN (43155).

User Action



Limit.


PIN value is 43155.


Pass Criteria

Visual checks:



Card log checks:









Note N/A


© 2014 MasterCard



Objective






Applicability

Terminal supports MasterCard and Online PIN and has a CVM Required Limit greater

than zero for the MasterCard application.

Terminal supports [PayPass3.0] and CDA.

Card details The card has a 5 digits PIN (43155).

User Action



Limit.


PIN value is 43155.


Pass Criteria

Visual checks:



Card log checks:











Note N/A


142

© 2014 MasterCard



Objective





Applicability

Terminal supports MasterCard and Online PIN and has a CVM Required Limit equal to

zero for the MasterCard application.

Terminal does not support [PayPass3.0] or does not support CDA.



User Action




PIN value is 43155.


Pass Criteria

Visual checks:



Card log checks:



- TVR byte 3 bit 3 = 1(Online PIN entered) - OK/NOK





Note N/A


© 2014 MasterCard



Objective








Applicability

Terminal supports MasterCard and Online PIN and has a CVM Required Limit equal to

zero for the MasterCard application.

Terminal supports [PayPass3.0] and CDA.



User Action




PIN value is 43155.


Pass Criteria

Visual checks:



Card log checks:










Note N/A


144

© 2014 MasterCard




[TC041]

Applicability Terminal supports MasterCard and is online capable and supports gratuity.

Card details

User Action


Enter any amount and a gratuity amount. The transaction amount plus the gratuity amount

must be below the Contactless Contactless Transaction Limit.




Pass Criteria

Visual checks:




Card log checks:




- DE 4 contains the sum of initial amount and gratuity - OK/NOK

- DE 55 SE 9F02 ('Amount authorized') contains the sum of initial amount and gratuity -

OK/NOK

- DE 55 SE 9F03 ('Amount, other') contains zeroes or is absent - OK/NOK


Note N/A


© 2014 MasterCard



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

Applicability Terminal supports MasterCard and is offline-only and supports gratuity.

Card details

User Action



must be below the Contactless Transaction Limit.


Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



Note N/A


146

© 2014 MasterCard



Objective





Applicability Terminal supports MasterCard and has a CVM Required Limit greater than zero.

Terminal does not support receipt printing.


The card contains (‘4203 5E03 1F03’) in the CVM list.

User Action




Please print a receipt.



Pass Criteria

Visual checks:



Card log checks:






Note N/A


© 2014 MasterCard



Objective


or length from the card. Case of tag ‘88’. [TC011-1]

To ensure the PayPass terminal correctly behaves when the CDOL1 includes tags being

forbidden in the DE 55. [TC012]

To ensure the PayPass terminal does not transmit the PAN sequence number when it is not

returned by the card. [TC048]


Card details

The card returns the unknown tag ‘88’ in PPSE response.


Capabilities) in CDOL1. This data is forbidden in DE 55.

The card does not return any PAN sequence number.

User Action






Pass Criteria

Visual checks:


Card log checks:




- The Terminal does not send the tags ‘9F21’ and ‘9F40’ to the network - OK/NOK

- The Terminal does not send the PAN sequence number (DE 23) to the network -

OK/NOK


Note N/A


148

© 2014 MasterCard






Card details The card returns the unknown tag ‘88’ in PPSE response.

User Action




Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



Note N/A


© 2014 MasterCard


Combo01 Test 01 Scenario 01

Objective


or length from the card. Case of Third Party data with length 5. [TC011-10]

To ensure the terminal always selects the highest priority application without cardholder

assistance. [TC070-1]

Applicability Terminal supports MasterCard and not IDS

Card details

Card returns the PayPass Third Party data (‘9F6E’) with length 5.

Card contains 2 applications returned in the following order:

Maestro, priority 03

MasterCard, priority 02

User Action

Please use the following test card: M-TIP Subset 8 – Combo01 v1.1.

Enter any amount below the MasterCard Contactless Transaction Limit.





Pass Criteria

Visual checks:


Card log checks:

- The terminal automatically selects the MasterCard application - OK/NOK

- Application Label indicates "Combo01 v1 1" - OK/NOK


Note N/A


150

© 2014 MasterCard



Objective


or length from the card. Case of Third Party data with length 5. [TC011-10]


Data Storage. Case of slot not available. [TC026-2]



Applicability Terminal supports MasterCard and IDS

Card details

Card returns the PayPass Third Party data (‘9F6E’) with length 5.




Whatever the DS Requested Operator ID (different from zero) provided in the GetPO

command, the card returns AIP, AFL, '9F5F 01 00' ("no slot available").

User Action







Pass Criteria

Visual checks:


Card log checks:




- The card returns '9F5F 01 00' ("no slot available") in the GetPO response - OK/NOK

Note N/A


© 2014 MasterCard





Applicability Terminal supports MasterCard and not Maestro.

Card details




User Action







Pass Criteria

Visual checks:


Card log checks:




Note N/A


152

© 2014 MasterCard


4.5 Test Scenarios for Maestro PayPass M/Chip

MP01 Test 01 Scenario 01

Objective

To ensure the terminal correctly manages the Issuer response ‘00’ (successful). [TC042]

To ensure the PayPass terminal supports the Full Grade network messages. [TC049-1]

To ensure the PayPass terminal correctly manages PayPass values in the existing

authorization fields. Case of M/Chip transaction. [TC050-2]


transaction. [TC053-1]



Applicability Terminal supports Maestro and is online capable and the CVM Required Limit is greater

than zero. It is not an ATM or a Bank Branch.


User Action

Please use the following test card: M-TIP Subset 8 – MP01 v2.2.

Enter amount below the CVM Required Limit. Possible amount values are:

- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’




Pass Criteria

Visual checks:


Card log checks:

- Application Label indicates "MP01 v2 2" - OK/NOK


- Amount is below (and not equal to) the CVM Required Limit - OK/NOK









- DE 55 SE 9F34 ('CVM Result') is present (effective 1 April 2017)* - Present/Not



OK/NOK





154

© 2014 MasterCard


MP01 Test 01b Scenario 01

Objective

To 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 ATM user. [TC028]


[TC042]








Applicability Terminal supports Maestro and is an ATM.


User Action


Enter an amount below the Contactless Transaction Limit. Possible amount values are:

- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’





© 2014 MasterCard


Pass Criteria

Visual checks:

- The ATM must display all user instructions on the existing screen. The reader must not

provide any instructions directly to the ATM user – OK/NOK


Card log checks:




- DE 3 subfield 1 (transaction type code) = '01' (withdrawal) - OK/NOK





- DE 48 byte 1 (TCC) = 'Z' ('ATM Cash Disbursement') - OK/NOK


OK/NOK


- DE 55 SE 9F34 (CVM Result') is present in the authorization message (effective 1 April

2017)* - Present/Not present/Not required


OK/NOK





156

© 2014 MasterCard


MP01 Test 01c Scenario 01

Objective


[TC042]








Applicability Terminal supports Maestro and is online capable and the CVM Required Limit is zero.

It is not an ATM or a Bank Branch.


User Action



- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’




Pass Criteria

Visual checks:


Card log checks:














OK/NOK





158

© 2014 MasterCard


MP01 Test 01d Scenario 01

Objective


[TC042]








Applicability Terminal supports Maestro and is a Bank Branch.


User Action



- ‘5.00’ or ‘5 000 000’

- ’10.00’ or ’10 000 000’

- ‘40.00’ or ’40 000 000’

- ‘100.00’ or ’100 000 000’




Pass Criteria

Visual checks:


Card log checks:




- DE 3 subfield 1 (transaction type code) = '17' (cash disbursement) - OK/NOK

- DE 4 must be the cash advance amount - OK/NOK











- DE 61 subfield 11 = ‘3’ (contactless M/Chip) - OK/NOK




© 2014 MasterCard




Objective To ensure the PayPass terminal correctly manages the Issuer response ‘51’ (insufficient

funds). [TC043-1]

Applicability Terminal supports Maestro and is online capable.


User Action


Enter amount below the CVM Required Limit (if not zero). Possible amount values are:

- ‘5.51’ or ‘5 510 000’

- ’10.51’ or ’10 510 000’

- ‘40.51’ or ’40 510 000’

- ‘100.51’ or ’100 510 000’

- or any value like *51*.



(insufficient funds).

Pass Criteria

Visual checks:


Card log checks:





Note N/A


160

© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer response ‘57’ (Transaction

not permitted). [TC043-2]



User Action



- ‘5.57’ or ‘5 570 000’

- ’10.57’ or ’10 570 000’

- ‘40.57’ or ’40 570 000’

- ‘100.57’ or ‘100 570 000’




(Transaction not permitted).

Pass Criteria

Visual checks:


Card log checks:




- Simulator response is ‘57’ (Transaction not permitted) - OK/NOK

Note N/A


© 2014 MasterCard





Applicability Terminal supports Maestro and is online capable and supports contact transactions.

It is not an ATM.


User Action



- ‘6.65’ or ‘6 650 000’

- ’66.50’ or ’66 500 000’

- ‘665.00’ or ’665 000 000’





Pass Criteria

Visual checks:



Card log checks:





Note N/A


162

© 2014 MasterCard


MP01 Test 03c Scenario 01

Objective







User Action



- ‘6.65’ or ‘6 650 000’

- ’66.50’ or ’66 500 000’

- ‘665.00’ or ’665 000 000’





Pass Criteria

Visual checks:



technology, it does not force fallback to a contact technology. – OK/NOK

Card log checks:





Note N/A


© 2014 MasterCard




returned by the issuer. [TC045]



User Action



- ‘5.99’ or ‘5 990 000’

- ’10.99’ or ’10 990 000’

- ‘40.99’ or ’40 990 000’

- ‘100.99’ or ‘100 990 000’




Simulator


response:


- DE 55 - PDS 91 (Issuer Authentication Data) is present

- DE 55 - PDS 72 (Issuer Script Template 2) with one script identifier and 6 PIN


Pass Criteria

Visual checks:

- The transaction must successfully complete - OK/NOK

Card log checks:



- The terminal must not send any command to the card beyond the 1st Generate AC-

OK/NOK


- Simulator response contains DE 55 SE 91 and SE 72 - OK/NOK

Note N/A


164

© 2014 MasterCard




Limit. Case of amount just above the limit. Terminal supports [PayPass2.x]. [TC061-2]

Applicability Terminal supports Maestro and [PayPass2.x].



User Action






Amount must be one minor unit above the Maestro Contactless Transaction Limit* (e.g.:

25.01€)


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:


transaction performed at the first step( that is, the amount in the GenerateAC command is

the amount used at the first step)** - OK/NOK

Note

*: You must consider the limit mentioned in the M-TIP Questionnaire, NOT the one

personalized in the PayPass reader. Both values are indeed different in [PayPass2.x] terminals.

**: When the test tool stores a new log for each single transaction, the log will be empty since the terminal must either not activate the PayPass reader or abort after the PPSE

response (and the PPSE is not stored in the log).

When the test tool manages a unique log file, the log will be the one from the previous

transaction since a log is not created until the SelectADF is sent, which is never the case here.


© 2014 MasterCard




Limit. Case of amount above the limit. Terminal supports [PayPass3.0]. [TC061-3a]

Applicability Terminal supports Maestro and [PayPass3.0].



User Action






Amount must be one minor unit above the Maestro Contactless Transaction Limit* (e.g.:

25.01€).


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:





Note





166

© 2014 MasterCard




merchant or if the terminal times out. [TC072]

Applicability Terminal supports Maestro and not MasterCard and Online PIN

Card details This card has no specific feature

User Action




Please press the cancel button when the terminal prompts for the PIN.

Simulator N/A

Pass Criteria

Visual checks:

- The terminal must prompt for PIN – OK/NOK

- The terminal shall terminate the transaction – OK/NOK

Card log checks:




- The network simulator does not receive any authorization request for this transaction -

OK/NOK

Note N/A


© 2014 MasterCard



Objective




PayPass transactions below or equal to the defined limit.[TC031]

Applicability Terminal supports Maestro and not refund and the CVM Required Limit is greater than

zero.

Card details Card CVM list indicates 1) Offline PIN 2) Offline Encrypted PIN 3) Signature 4) Online

PIN 5) noCVM.

User Action







Pass Criteria

Visual checks:



Card log checks:







Note N/A


168

© 2014 MasterCard



Objective



To ensure the PayPass terminal correctly performs refund. [TC025-1]



Applicability Terminal supports Maestro and refund and [PayPass2.0].

The CVM Required Limit is greater than zero.


PIN 5) noCVM.

User Action



Enter an amount equal to the CVM Required Limit**.










Pass Criteria







- Amount is equal to the CVM Required Limit - OK/NOK











Note

**: if the terminal supports [PayPass2.x] you must consider the limit mentioned in the M-TIP Questionnaire, NOT the one personalized in the PayPass reader. Both values are



170

© 2014 MasterCard



Objective






Applicability Terminal supports Maestro and refund and ([PayPass2.1] or [PayPass3.0]).



PIN 5) noCVM.

User Action



Enter an amount equal to the CVM Required Limit**.










Pass Criteria







- Amount is equal to the CVM Required Limit - OK/NOK











Note

**: if the terminal supports [PayPass2.x] or [PayPass3.0] you must consider the limit mentioned in the M-TIP Questionnaire, NOT the one personalized in the PayPass reader.

Both values are indeed different in [PayPass2.x] or [PayPass3.0] terminals.


© 2014 MasterCard



Objective To ensure the PayPass terminal does not support offlinePIN. Case of amount above the


Applicability

Terminal supports Maestro and the CVM Required Limit is lower than the Contactless

Transaction Limit.

It does not support refund or the CVM Required Limit is greater than zero.


PIN 5) noCVM.

User Action



Limit.




Pass Criteria

Visual checks:


Card log checks:





- CVM results is ‘42 03 00' – OK/NOK

Note N/A


172

© 2014 MasterCard



Objective




Applicability Terminal supports Maestro and refund and [PayPass2.0].

The CVM Required Limit is zero.


PIN 5) noCVM.

User Action



Enter an amount below the Contactless Transaction limit.









Pass Criteria







- CVM result byte 1 is different from ‘41’ - OK/NOK









Note N/A


© 2014 MasterCard



Objective




Applicability Terminal supports Maestro and refund and ([PayPass2.1] or [PayPass3.0]).



PIN 5) noCVM.

User Action



Enter an amount below the Contactless Transaction limit.









Pass Criteria







- CVM result byte 1 is different from ‘41’ - OK/NOK









Note N/A


174

© 2014 MasterCard



Objective






authorization or Online PIN. Service Code is ‘206’ and amount is below the limit. [TC067-

1]

Applicability Terminal supports Maestro and the CVM Required Limit is greater than zero.

Card details

The Track2 data (tag ‘57’) has the maximum length (37 digits).

The card returns the tag ‘9F6E’ (PayPass Third Party data).

Service Code contained in Track2 is ‘206’ (Normal Authorization, PIN if pinpad present).

User Action


Enter amount below the CVM Required Limit.




Pass Criteria

Visual checks:



Card log checks:






Note N/A


© 2014 MasterCard



Objective





Applicability Terminal supports Maestro and the CVM Required Limit is zero.

It does not support CDA or supports [PayPass2.x].



User Action


Enter amount below the Contactless Transaction Limit.



Pass Criteria

Visual checks:


Card log checks:



Note N/A


176

© 2014 MasterCard



Objective







Applicability Terminal supports Maestro and CDA and [PayPass3.0] and the CVM Required Limit is

zero.

Card details

The returned AIP indicates that the card supports CDA.


The Track2 data (tag ‘57’) has the maximum length (37 digits).


User Action





Pass Criteria

Visual checks:


Card log checks:





Note N/A


© 2014 MasterCard



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

Applicability Terminal supports Maestro and is online capable and supports gratuity.

Card details

User Action



must be below the CVM Required Limit (if not zero).



Pass Criteria

Visual checks:




Card log checks:




- DE 4 contains the sum of initial amount and gratuity - OK/NOK

- DE 55 SE 9F02 ('Amount authorized') contains the sum of initial amount and gratuity -

OK/NOK

- DE 55 SE 9F03 ('Amount, other') contains zeroes or is absent - OK/NOK


Note N/A


178

© 2014 MasterCard




[TC041]

Applicability Terminal supports Maestro and is offline-only and supports gratuity.

Card details

User Action

Please, use the following test card: M-TIP Subset 8 – MP12 v2.2.

Enter any amount and a gratuity amount. The transaction amount plus the gratuity

amount must be below the CVM Required Limit.


Simulator N/A

Pass Criteria

Visual checks:

- The terminal offers to enter the gratuity amount before tapping - OK/NOK


Card log checks:



Note N/A


© 2014 MasterCard



Objective








Applicability Terminal supports Maestro and is offline capable and the CVM Required Limit is greater

than zero.

Card details


Card supports CDA.



User Action


Enter amount below the contactless Floor Limit and below the CVM Required Limit.


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:









Note N/A


180

© 2014 MasterCard



Objective






Applicability Terminal supports Maestro and is online-only or the CVM Required Limit is zero.

It supports CDA and [PayPass3.0].

Card details


Card supports CDA.



User Action





Pass Criteria

Visual checks:


Card log checks:






Note N/A


© 2014 MasterCard



Objective





Applicability

Terminal supports Maestro.

It is online-only and the CVM Required Limit is greater than zero.

It does not support CDA or supports [PayPass2.x]

Card details The card returns a record with the maximum length (254 bytes).


User Action





Pass Criteria

Visual checks:



Card log checks:








Note N/A


182

© 2014 MasterCard





Applicability Terminal supports Maestro and has a CVM Required Limit equal to zero.

It does not support CDA or supports [PayPass2.x]

Card details The card returns a record with the maximum length (254 bytes).

User Action





Pass Criteria

Visual checks:


Card log checks:





Note N/A


© 2014 MasterCard



Objective







than zero.

Card details



present).



User Action


Enter any amount below the floor limit and below CVM Required Limit.


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:



- Amount must be below the CVM Required Limit - OK/NOK







Note N/A


184

© 2014 MasterCard



Objective






Applicability

Terminal supports Maestro and CDA and [PayPass3.0].


The Floor Limit is lower than the CVM Required Limit.

Card details




User Action


Enter any amount above the Floor Limit and below the CVM Required Limit.



Pass Criteria

Visual checks:



Card log checks:



- Amount must be below the CVM Required Limit - OK/NOK







Note N/A


© 2014 MasterCard



Objective




Applicability Terminal supports Maestro and [PayPass3.0] and CDA.


Card details




User Action





Pass Criteria

Visual checks:


Card log checks:






Note N/A


186

© 2014 MasterCard



Objective


or length from the card. Case of IAD (‘9F10’) with maximum length. [TC011-7]




Card details




User Action


Enter amount below the CVM Required Limit (if not zero).



Pass Criteria

Visual checks:


Card log checks:





Note N/A


© 2014 MasterCard




or length from the card. Case of IAD (‘9F10’) with maximum length. [TC011-7]

Applicability Terminal supports Maestro and is offline-only.

Card details The IAD (‘9F10’) returned by the card has the maximum length.

User Action




Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



Note N/A


188

© 2014 MasterCard



Objective


or length from the card. Case of Discretionary Data inconsistency. [TC011-3]

To ensure that the PayPass terminal correctly implements the Contactless Contactless

Transaction Limit. Case of amount equal to the limit. [TC061-1a]

Applicability Terminal supports Maestro.


Card details The Discretionary Data value in the track2 (‘57’) is different from the value returned in the


User Action







Pass Criteria

Visual checks:


Card log checks:



- Amount is equal to the Maestro Contactless Transaction Limit - OK/NOK

Note




© 2014 MasterCard



Objective





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

[TC410]

Applicability Terminal supports Maestro and not receipt printing.


Card details




User Action

Please use the following test card: M-TIP Subset 8 - MP16 v2.2.


Limit and different from *55* and *75*.


PIN value is 4315.


Pass Criteria

Visual checks:

- Terminal asks to enter PIN – OK/NOK


Card log checks:



- Amount is above the CVM Required Limit – OK/NOK


- TVR byte 3 bit 8 = 0 (Cardholder verification was successful) – OK/NOK

- TVR byte 3 bit 3 = 1 (Online PIN entered) – OK/NOK





where xxxx is the card PIN - OK/NOK





190

© 2014 MasterCard



Objective



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




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

[TC410]

Applicability Terminal supports Maestro and receipt printing.


Card details




User Action



Limit and different from *55* and *75*.


PIN value is 4315.


Pass Criteria

Visual checks:



- The terminal prints a cardholder receipt - OK/NOK

Card log checks:



- Amount is above the CVM Required Limit – OK/NOK








where xxxx is the card PIN - OK/NOK





© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer response ‘55’ (wrong PIN).

[TC052-1]



Card details The card supports Online PIN (’42 03’) then noCVM.

User Action




- ‘5.55’ or ‘5 550 000’

- ’10.55’ or ’10 550 000’

- ‘40.55’ or ’40 550 000’

- ‘100.55’ or ‘100 550 000’




simulator response ‘55’ (wrong PIN)).


(wrong PIN).

Pass Criteria

Visual checks:

- The terminal must indicate the cardholder that the PIN is incorrect - OK/NOK

Card log checks:






- Simulator response is ‘55’ (wrong PIN) - OK/NOK

Note N/A


192

© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer responses ‘75’ (Allowable

number of PIN tries exceeded). [TC052-2]



Card details The card supports Online PIN (’42 03’) then noCVM.

User Action




- ‘4.75’ or ‘4 750 000’

- ’10.75’ or ’10 750 000’

- ‘40.75’ or ’40 750 000’

- ‘100.75’ or ‘100 750 000’




simulator response ‘75’ (Allowable number of PIN tries exceeded)).


(Allowable number of PIN tries exceeded).

Pass Criteria

Visual checks:


Card log checks:






- Simulator response is ‘75’ (Allowable number of PIN tries exceeded) - OK/NOK

Note N/A


© 2014 MasterCard





Applicability

Terminal supports Maestro.


Limit.

The CVM Required Limit equals the Contactless Transaction Limit

Card details The Discretionary Data value in the track2 (‘57’) is different from the value returned in the


User Action


Amount must be below the Contactless Transaction Limit and different from *55* and

*75*.




Pass Criteria

Visual checks:


Card log checks:



Note N/A


194

© 2014 MasterCard



Objective

To ensure the PayPass terminal correctly behaves when it receives unexpected data

value or length from the card. Case of ServiceCode discrepancy, unrecognized CVM and

'9F1D' tag. [TC011-2 and 6 and 13]

Applicability Terminal supports Maestro and is not an ATM and supports [PayPass2.x].

Card details


The Service Code returned in the track2 (‘57’) is different from the one in the specific

tag (‘5F30’).

User Action


Enter amount below the CVM Required limit (if not zero).




Pass Criteria

Visual checks:


Card log checks:






- CVM result must be '42 03 00' or ‘1F 03 00’ or '1F 03 02' - OK/NOK

Note N/A


© 2014 MasterCard


MP17 Test 01 Scenario 01b

Objective



'9F1D' tag. [TC011-2 and 6 and 13]

Applicability Terminal supports Maestro and is not an ATM and supports [PayPass3.0].

Card details



tag (‘5F30’).

User Action


Enter amount below the CVM Required limit (if not zero).




Pass Criteria

Visual checks:


Card log checks:





'80' – OK/NOK



- CVM result must be '42 03 00' or ‘1F 03 00’ or '1F 03 02' - OK/NOK

Note N/A


196

© 2014 MasterCard



Objective



'9F1D' tag. [TC011-2 and 6 and 13]

Applicability Terminal supports Maestro and is an ATM and supports [PayPass2.x].

Card details

The CVM list includes an unrecognized CVM.


tag (‘5F30’).

User Action


Enter amount below the Contactless Transaction limit.



Pass Criteria

Visual checks:


Card log checks:






Note N/A


© 2014 MasterCard


MP17 Test 01 Scenario 02b

Objective



'9F1D' tag. [TC011-2 and 6 and 13]

Applicability Terminal supports Maestro and is an ATM and supports [PayPass3.0].

Card details

The CVM list includes an unrecognized CVM.


tag (‘5F30’).

User Action


Enter amount below the Contactless Transaction limit.



Pass Criteria

Visual checks:


Card log checks:



- In GetPO command, the '9F1D' tag value is correct: byte 1 is '40' and byte 3 is '80' –

OK/NOK



Note N/A


198

© 2014 MasterCard



Objective To ensure the PayPass terminal correctly supports different certification authority public



than zero.


CA key length is 1984/248

User Action


Enter any amount below the CVM Required Limit and below the floor limit.


Simulator N/A

Pass Criteria

Visual checks:


Card log checks:





Note N/A


© 2014 MasterCard



Objective

To ensure that the PayPass terminal performs CDA correctly. Amount above the Floor

Limit. [TC002-2]



Applicability Terminal supports Maestro and [PayPass3.0] and CDA.

The CVM Required Limit or the Floor Limit are below the Contactless Transaction Limit.


CA key length is 1984/248

User Action


Enter any amount above the floor limit or above the CVM Required Limit.


Simulator The network simulator returns the response ‘00’ (accepted).

Pass Criteria

Visual checks:


Card log checks:





Note N/A


200

© 2014 MasterCard



Objective

To ensure the PayPass terminal correctly behaves when the CDOL1 includes tags being

forbidden in the DE 55. [TC012]

To ensure the PayPass terminal does not transmit the PAN sequence number when it is not

returned by the card. [TC048]




Card details


Capabilities) in CDOL1. This data is forbidden in DE 55.

The card does not return any PAN sequence number.

The service code included in the Track2 (‘220’) indicates that a chip is present on the card.

User Action





Pass Criteria

Visual checks:



Card log checks:




- The Terminal does not send the tags ‘9F21’ and ‘9F40’ to the network - OK/NOK

- The Terminal does not send the PAN sequence number (DE 23) to the network -

OK/NOK


Note N/A


© 2014 MasterCard



Objective To ensure that the PayPass terminal does not prompt for a contact transaction when the



Card details The service code included in the Track2 (‘220’) indicates that a chip is present on the card.

User Action




Simulator N/A

Pass Criteria

Visual checks:



Card log checks:



Note N/A


202

© 2014 MasterCard



Objective




or length from the card. Case of Track1 maximum. [TC011-4]


′0002′. [TC062]

Applicability Terminal supports Maestro and the CVM Required Limit equals zero.

Card details


The Track1 discretionary data (tag ‘9F1F’) has the maximum length (48 bytes).


User Action






Pass Criteria

Visual checks:


Card log checks:




Note N/A


© 2014 MasterCard



Objective





To ensure that the PayPass terminal is able to print a cardholder receipt. [TC024-1]


′0002′. [TC062]

Applicability Terminal supports Maestro and receipt printing and the CVM Required Limit is greater

than zero.

Card details




User Action






Pass Criteria

Visual checks:


- The terminal is able to print a cardholder receipt below the CVM Required Limit in case

the cardholder requests it - OK/NOK

Card log checks:




Note N/A


204

© 2014 MasterCard



Objective






′0002′. [TC062]

Applicability Terminal supports Maestro and not receipt printing and the CVM Required Limit is greater

than zero.

Card details




User Action






Pass Criteria

Visual checks:


Card log checks:




Note N/A


© 2014 MasterCard


MP4A Test 01 Scenario 01

Objective

To ensure the terminal correctly completes the transaction with a Mobile. Amount below







message containing DE 55 (effective 1 April 2017).[TC054-2]To ensure the terminal

correctly transmits the Device Type data element in the authorization message, if

supported. [TC055-3]

Applicability

Terminal supports [PayPass3.0] and Maestro and is online capable.



Cardholder Verification supported' and the Contactless Transaction Limit (On-device

CVM) is not zero.



User Action


verification:

Please use the following test card: M-TIP Subset 8 – MP4A v1.1.






Please use the following test card: M-TIP Subset 8 – MP4B v1.1.





206

© 2014 MasterCard


Pass Criteria




- Application Label indicates "MP4A v1 1" - OK/NOK





- Application Label indicates "MP4B v1 1" - OK/NOK












OK/NOK

- DE 55 SE 9F34 (CVM Results)** = '3F 00 02' – OK/NOK/Not present


OK/NOK



Note






© 2014 MasterCard



Objective

To ensure the terminal correctly completes the transaction with a Mobile. Amount above







message containing DE 55 (effective 1 April 2017).[TC054-2]To ensure the terminal

correctly transmits the Device Type data element in the authorization message, if

supported. [TC055-3]

Applicability




The terminal configuration is such that the Kernel Configuration indicates 'On-Device Cardholder Verification supported'.



User Action


verification:












208

© 2014 MasterCard


Pass Criteria





















OK/NOK

- DE 55 SE 9F34 (CVM Results)** = '01 00 02' – OK/NOK/Not present


OK/NOK



Note






© 2014 MasterCard



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


Applicability

Terminal supports [PayPass3.0] and Maestro and is offline-only.


The terminal configuration is such that the Kernel Configuration indicates 'On-Device Cardholder Verification supported' and the Contactless Transaction Limit (On-device

CVM) is not zero.



User Action


verification:










Simulator N/A

Pass Criteria












Note N/A


210

© 2014 MasterCard



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


Applicability

Terminal supports [PayPass3.0] and Maestro and is offline-only.







User Action


verification:










Simulator N/A

Pass Criteria












Note N/A


© 2014 MasterCard


MP4B Test 01 Scenario 01


[TC061-1b]

Applicability








User Action





Pass Criteria

Visual checks:


Card log checks:




Note


212

© 2014 MasterCard




[TC061-1b]

Applicability

Terminal supports [PayPass3.0] and Maestro and is offline only.







User Action




Simulator N/A

Pass Criteria

Visual checks:


Card log checks:




Note


© 2014 MasterCard




[TC061-3b]

Applicability

Terminal supports [PayPass3.0] and Maestro.

Terminal allows to enter amounts greater than the Contactless Transaction Limit (On

Device CVM) and is unattended.





User Action




Limit (On-device CVM) and then ensure the transaction was correctly stored in the card

log.


Amount is equal to one minor unit above the Contactless Transaction Limit (On-device

CVM) (e.g.:25.01€).


Simulator N/A

Pass Criteria

Visual checks:



Card log checks:





Note





214

© 2014 MasterCard



Objective

To ensure the terminal not supporting "On-device cardholder verification" correctly




Applicability Terminal supports Maestro and is online capable and does not support [PayPass3.0] or the




User Action


Amount must be below the CVM Required Limit (if not zero).



Pass Criteria

Visual checks:


Card log checks:






Note




© 2014 MasterCard





Applicability Terminal supports Maestro and is offline only and does not support [PayPass3.0] or the




User Action


Amount must be below the CVM Required Limit.


Simulator N/A

Pass Criteria

Visual checks:


Card log checks:



Note


216

© 2014 MasterCard



Objective





Applicability Terminal supports Maestro and not IDS.

Card details







User Action


Enter any amount below the CVM Required Limit (if not zero).




Pass Criteria

Visual checks:



Card log checks:



Note N/A


© 2014 MasterCard



Objective





Applicability Terminal supports Maestro and IDS.

Card details







Whatever the DS Requested Operator ID provided in the GetPO command, the card returns

AIP, AFL, '9F5F 01 40' (volatile slot), '9F7F' (DS Unpredictable Number), '9F7D 08

00…00' (DS Summary 1).

When the GenAC command includes the DSDOL data then Summary2 and Summary3 are

included in the SDAD. Summary2=Summary1. Summary3<>Summary2.

User Action






Pass Criteria

Visual checks:



Card log checks:



- In the GetPO response, the card returns AIP, AFL, '9F5F 01 40' (volatile slot), '9F7F' (DS

Unpredictable Number), '9F7D 08 00…00' (DS Summary 1) - OK/NOK

Note N/A


218

© 2014 MasterCard






Card details The Maestro application has an extended AID ‘A0 00 00 00 04 30 60 D056 02’.

User Action






Pass Criteria

Visual checks:


Card log checks:




Note N/A


© 2014 MasterCard



Objective


or length from the card. Case of '9F2A'. [TC011-14]


extended with ‘C12345 6789’. [TC065-2]

Applicability Terminal supports Maestro and supports SDA.

Card details


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

The Maestro application has an extended AID ‘A0 00 00 00 04 30 60 C12345 6789’.

User Action






Pass Criteria

Visual checks:

- The terminal approves the offline or online transaction - OK/NOK

Card log checks:

- The terminal selects the AID ‘A0 00 00 00 04 30 60 C12345 6789’ - OK/NOK






Note N/A


220

© 2014 MasterCard



Objective






Applicability Terminal supports Maestro and is offline-only and does not support SDA.

Card details



The card has an extended AID ‘A0 00 00 00 04 30 60 C12345 6789’.

User Action




Simulator N/A

Pass Criteria

Visual checks:


Card log checks:








Note N/A


© 2014 MasterCard



Objective






Applicability Terminal supports Maestro and is online capable and does not support SDA.

Card details



The Maestro application has an extended AID ‘A0 00 00 00 04 30 60 C12345 6789’.

User Action






Pass Criteria

Visual checks:


Card log checks:








Note N/A


222

© 2014 MasterCard



Objective


offline data authentication method. Amount below the Floor Limit and the CVM Required

Limit. [TC001-1a]


or length from the card. [TC011-11]



Applicability Terminal supports Maestro and is offline and online capable and the CVM Required Limit

is greater than zero.

Card details


The card returns the PayPass Third Party data (‘9F6E’) with length 32.

The card returns a Third Party Data indicating a device type 'mobile phone case or sleeve'.

User Action


Enter any amount below the Floor Limit and below the CVM Required Limit.




Pass Criteria

Visual checks:


Card log checks:

- Application Label indicates “MP91 v2 3” - OK/NOK


- Amount must be below the Floor Limit - OK/NOK


- TVR byte 1 bit 8 = 1 (ODA not performed) - OK/NOK




Note

*: U.S. region acquirers (effective 19 April 2013) and Canada acquirers (effective 17

October 2014 for newly deployed devices) must transmit the device type indicator value (DE 48 SE 23), if present on the card or non-card form factor.


© 2014 MasterCard



Objective











Applicability

Terminal supports Maestro and is online capable.

The Floor Limit is lower than the Contactless Transaction Limit.


Card details



CDOL1 does not request Terminal Country Code (tag ‘9F1A’), Transaction Date (‘9A’),

Transaction Type (‘9C’), Transaction Currency Code (‘5F2A’) and CVM Results ('9F34').


User Action


Enter any amount above the Floor Limit and below the Contactless Transaction Limit.





Pass Criteria

Visual checks:


Card log checks:



- Amount is above the Floor Limit - OK/NOK









- DE 55 SE 9F34 (CVM Result) is present in the authorization message (effective 1 April

2017)** - Present/Not present/Not required

Note


(DE 48 SE 23), if present on the card or non-card form factor

**: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages containing DE 55 effective 1 April 2017.


© 2014 MasterCard



Objective











Applicability Terminal supports Maestro and is online capable and the CVM Required Limit is lower

than the Contactless Transaction Limit.

Card details



CDOL1 does not request Terminal Country Code (tag ‘9F1A’), Transaction Date (‘9A’),

Transaction Type (‘9C’), Transaction Currency Code (‘5F2A’) and CVM Results ('9F34').


User Action


Amount must be above the CVM Required Limit and below the Contactless Transaction

Limit*.


PIN value is 4315.



Pass Criteria

Visual checks:



Card log checks:









Canada for newly deployed devices)** - OK/NOK/Not required



- DE 55 SE 9C (Transaction Type) value is '00' (goods and services) or '01' (cash ATM) -

OK/NOK


- DE 55 SE 9F34 (CVM Result) is present in the authorization message (effective 1 April

2017)*** - Present/Not present/Not required


226

© 2014 MasterCard


Note



**: U.S. region acquirers (effective 19 April 2013) and Canada acquirers (effective 17 October 2014 for newly deployed devices) must transmit the device type indicator value


***: Acquirers must include the CVM Results (tag ‘9F34’) in all authorization messages





Applicability Terminal supports Maestro and is offline-only and does not support contact transactions.


User Action




Simulator N/A

Pass Criteria

Card log checks:





Note N/A


© 2014 MasterCard



Objective





Applicability Terminal supports Maestro and is offline-only and supports contact transactions.


User Action




Simulator N/A

Pass Criteria

Visual checks:

- The terminal prompts the cardholder to perform a contact transaction since the contactless


Card log checks:





Note N/A


Objective To ensure that the terminal terminates the transaction if the PayPass Maestro card indicates

that it does not support PayPass – M/Chip. [TC401]


Card details The card indicates in the AIP that it does not support PayPass –M/Chip.

User Action




Simulator N/A

Pass Criteria

Card log checks:


- The terminal terminates the transaction upon reception of the GetPO response - OK/NOK

Note N/A


228

© 2014 MasterCard




supported, when the card declines. [TC068-1]

Applicability Terminal supports Maestro and contact and is not an ATM


User Action




Simulator N/A

Pass Criteria

Visual checks:

- The terminal shall prompt the cardholder to perform a contact transaction - OK/NOK

Card log checks:



- terminal requests a TC or an ARQC – OK/NOK


Note N/A


© 2014 MasterCard



Objective





Applicability Terminal supports Maestro and is an ATM


User Action




Simulator N/A

Pass Criteria

Visual checks:

- The ATM declines the transaction – OK/NOK


technology, it does not force fallback to a contact technology. - OK/NOK

Card log checks:



- terminal requests an ARQC – OK/NOK


Note N/A


230

© 2014 MasterCard



Objective To ensure the offline-only PayPass terminal correctly behaves when the card erroneously

sends an ARQC. [TC005]


Card details The cards always returns an ARQC.

User Action




Simulator N/A

Pass Criteria

Visual checks:

- The terminal terminates the transaction - OK/NOK

Card log checks:



- The card returns an ARQC - OK/NOK

Note N/A


© 2014 MasterCard




[TC035]

Applicability Terminal supports Maestro and the CVM Required Limit is lower than the Contactless

Transaction Limit. It does not support contact transactions.

Card details CVM list is noCVM only.

Note: the test card MP94 may generate an ARQC when the terminal requests an AAC.

User Action


Amount must be above the Maestro CVM Required Limit and below the Contactless

Transaction Limit.


Simulator N/A

Pass Criteria

Visual checks:

- Terminal does not ask to enter PIN – OK/NOK

Card log checks:




- TVR byte 3 bit 8 = 1 (Cardholder verification failed) – OK/NOK

- TVR byte 3 bit 3 = 0 (Online PIN not entered) – OK/NOK

- CVM results is ‘3F 00 01' – OK/NOK

- Terminal requests an AAC as per the TACs – OK/NOK

Note N/A


232

© 2014 MasterCard



Objective


[TC035]



Applicability Terminal supports Maestro and the CVM Required Limit is lower than the Contactless

Transaction Limit. It supports contact transactions. It is not an ATM.



User Action


Amount must be above the Maestro CVM Required Limit and below the Contactless

Transaction Limit.


Simulator N/A

Pass Criteria

Visual checks:


- The terminal prompts the cardholder to perform a contact transaction since the contactless


Card log checks:







- Terminal requests an AAC as per the TACs – OK/NOK

Note N/A


© 2014 MasterCard



Objective









User Action


Enter the smallest possible amount below the Contactless Transaction Limit.


Simulator N/A

Pass Criteria

Visual checks:


- The ATM declines the transaction - OK/NOK


technology, it does not force fallback to a contact technology – OK/NOK

Card log checks:







Note N/A


234

© 2014 MasterCard





Applicability Terminal supports Maestro and not MasterCard.

Card details




User Action


Enter any amount below the Maestro CVM Required Limit (if not zero).




Pass Criteria

Visual checks:


Card log checks:

- The terminal automatically selects the Maestro application - OK/NOK



Note N/A


© 2014 MasterCard





Applicability Terminal supports Maestro and not IDS

Card details




User Action






Pass Criteria

Visual checks:


Card log checks:




Note N/A


236

© 2014 MasterCard



Objective


Data Storage. Case of slot not available. [TC026-2]



Applicability Terminal supports Maestro and IDS

Card details




Whatever the DS Requested Operator ID (different from zero) provided in the GetPO

command, the card returns AIP, AFL, '9F5F 01 00' ("no slot available").

User Action






Pass Criteria

Visual checks:


Card log checks:




- The card returns '9F5F 01 00' ("no slot available") in the GetPO response - OK/NOK

Note N/A


© 2014 MasterCard


5 Test Scenarios for M-TIP Subset 6

This chapter lists the PayPass Mag Stripe M-TIP Test Scenarios.

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 so

the Subset 6 will sometimes be referred to as "M-TIP Subset 6".

5.1 M-TIP Subset 6 card details

The card versions mentioned below are given for information. The qualified test tools

are listed in [QualifiedTools] located on MasterCardConnect.com.

PINs

Below are the M-TIP Subset 6 card details:


MCC 351 v1.2 5001

MCC 352 v1.2 7584

MCC 353 v1.3 6614

MCC 354 v1.2 8024

MCC 355 v1.2 7815

MCC 356 v1.2 1045

MCC 357 v1.0

MCC 371A v1.1 3718

MCC 371B v1.1 3718

MCC 372 v1.1

MCC 373 v1.1

MCC 374 v1.1

MCC 406 v1.3 8045


238

© 2014 MasterCard


5.2 Using the Test Cards

Card MCC 356

This card ensures that the terminal correctly includes the ATC value in the

calculation of the PayPass Track1 and Track2.

Three ATC values are possible on this card. Each ATC value is linked to a read-

record and a CVC3 value.

Tool providers may implement 3 different cards to meet this objective.

Other tool providers may implement a single card supporting only 3 ATC values. If

so the ATC values would increment according to the round-robin principle. Therefore

the fourth transaction will be the same as the first one.

Figure 1: Card MCC 356 increments according to round-robin principle

5.3 Test Scenario Template Description

Please see "Test Scenarios for M-TIP Subset 6" above.

Transaction #1 (ATC#1, record#1, CVC3#1)




© 2014 MasterCard


5.4 Test Scenarios for PayPass Mag Stripe

MCC 351 Test 01 Scenario 01

Objective

To ensure the PayPass terminal correctly performs refund. Case of PayPass Mag Stripe.

[TC025-3]


authorization fields. Case of PayPass Mag Stripe. [TC050-1]

To ensure the PayPass terminal correctly builds the discretionary data. [TC610]

To ensure that the terminal correctly completes the PayPass Mag Stripe transaction

whatever the Service Code value encoded in the card. Case of ‘101’. [TC611-1]

Applicability Terminal supports PayPass MasterCard and supports refund.

Card details Service Code: '101' (international, MagStripe-only, no restrictions).

User Action


Please use the following test card: M-TIP Subset 6 – MCC 351 v1.2.



If needed, PIN value is ‘5001’.






Pass Criteria



Card log checks:

- Application Label indicates "MCC 351 v1 2" - OK/NOK

Network simulator checks – first step (purchase):


- DE 22 subfield 1 = ‘91’ (POS entry mode: contactless Mag stripe) - OK/NOK

- DE 61 subfield 11 = ‘3’ or '4' - OK/NOK

- DE 35 (Track2) or DE 45 (Track1) must be present and have the expected value:

- Track 1: B5413330056003511^CUST IMP MC 351/^2512101067750500 –

OK/NOK/Not Applicable

- Track 2: 5413330056003511D2512101067750500 (both ‘D’ and ‘=’ are acceptable

separators) – OK/NOK/ Not Applicable




Note N/A


240

© 2014 MasterCard



Objective






Applicability Terminal supports PayPass MasterCard and does not support refund.


User Action






Pass Criteria

Visual checks:


Card log checks:






- DE 35 (Track2) or DE 45 (Track1) must be present and have the expected value as shown

below:





Note N/A


© 2014 MasterCard



Objective To ensure the terminal still performs correctly a traditional Mag Stripe transaction when it

contains or is connected to a PayPass reader. [TC614]

Applicability Terminal supports MasterCard and traditional Mag Stripe.


User Action



Swipe card in the terminal and follow the instructions.



Pass Criteria

Visual checks:




- DE 22 subfield 1 = ‘90’ (POS entry mode: traditional Mag stripe) - OK/NOK

- DE 61 subfield 11 = ‘2’ or '3' or '4' or ‘5’ or ‘7’ or ‘8’ - OK/NOK


below:





Note N/A


242

© 2014 MasterCard



Objective




or length from the card. Case of Track1 and Track2 having maximum length. [TC601-1

and 2]




To ensure that a terminal processes Track 1 Data as Track 1 and Track 2 Data as Track 2

during PayPass - Mag Stripe transactions. [TC615]

Applicability Terminal supports PayPass MasterCard.

Card details Service Code: '205' (international, chip, PIN required).

User Action


Amount must be equal to 000000000100 or 000000010000.




Pass Criteria

Visual checks:


Card log checks:







below:

- Track 1: B5413330056003529^CUST IMP MC

352/^25122059900909900000099909909969929990400 – OK/NOK/Not Applicable



Note N/A


© 2014 MasterCard



Objective To ensure the PayPass terminal correctly manages the Issuer response ‘51’ (Insufficient

funds/over credit limit). [TC613]

Applicability Terminal supports PayPass MasterCard and is not an ATM.


User Action





Simulator The network simulator returns the response ‘51’ (Insufficient funds/over credit limit).

Pass Criteria

Visual checks:


Card log checks:




Note N/A


244

© 2014 MasterCard


MCC 352 Test 02b Scenario 01



Applicability Terminal supports PayPass MasterCard and contact and is not an ATM.


User Action


Possible amount values are:

- ‘6.65’ or ‘6 650 000’

- ’66.50’ or ’66 500 000’




Simulator The network simulator returns the response ‘65’ (exceeds withdrawal count limit).

Pass Criteria

Visual checks:



Card log checks:




Note N/A


© 2014 MasterCard



Objective





To ensure the PayPass terminal correctly manages the Issuer response ‘51’ (Insufficient

funds/over credit limit). [TC613]

Applicability Terminal supports PayPass MasterCard and is an ATM.


User Action





Simulator The network simulator returns the response ‘51’ (Insufficient funds/over credit limit).

Pass Criteria

Visual checks:

- The ATM declines the online transaction - OK/NOK


technology. It does not force fallback to a contact technology – OK/NOK

Card log checks:




Note N/A


246

© 2014 MasterCard



Objective






or length from the card. Case of Track1 and Track2 having minimum discretionary data

length. [TC601-3 and 4]




To ensure the PayPass terminal correctly behaves when the cardholder name is not fully

populated in the Track 1. [TC616]

Applicability Terminal supports PayPass MasterCard and the CVM Required limit is greater than zero.

Card details

Service Code: '502' (domestic, MagStripe-only, goods & services only).

Track1 and Track2 have minimum discretionary data length.


The Third Party Data item bytes 5 and 6 indicate a device type 'tag'.

User Action


Enter amount below the CVM Required limit.


If needed, PIN value is '6614'.


Pass Criteria

Visual checks:


Card log checks:






Canada for newly deployed devices)* - OK/NOK /Not required



below:

- Track 1: B5413330056003537^ /^2512502980 – OK/NOK/Not Applicable

- Track 2: 5413330056003537D2512502050 (both ‘D’ and ‘=’ are acceptable separators) –

OK/NOK/ Not Applicable

Note



© 2014 MasterCard



Objective






or length from the card. Case of Track1 and Track2 having minimum discretionary data

length. [TC601-3 and 4]




To ensure the PayPass terminal correctly behaves when the cardholder name is not fully

populated in the Track 1. [TC616]

Applicability Terminal supports PayPass MasterCard and the CVM Required limit is lower than the


Card details

Service Code: '502' (domestic, MagStripe-only, goods & services only).

Track1 and Track2 have minimum discretionary data length.


The Third Party Data item bytes 5 and 6 indicate a device type 'tag'.

User Action




If needed, PIN value is '6614'.


Pass Criteria

Visual checks:


Card log checks:






Canada for newly deployed devices)* - OK/NOK /Not required



below:

- Track 1: B5413330056003537^ /^2512502980 – OK/NOK/Not Applicable

- Track 2: 5413330056003537D2512502050 (both ‘D’ and ‘=’ are acceptable separators) –

OK/NOK/ Not Applicable

Note



248

© 2014 MasterCard



Objective




or length from the card. Case of Track1 and Track2 having maximum length. [TC601-1

and 2]





Card details Service Code: '817' (unknown).

User Action




If needed, PIN value is ‘7815.


Pass Criteria

Visual checks:


Card log checks:







below:

- Track 1: B5413330056003552^CUST IMP MC

355/^25128179099969999999999999999959927899990 – OK/NOK/Not Applicable



Note N/A


© 2014 MasterCard



Objective


To ensure that the terminal correctly copies the ATC in the PayPass Track 1 and/or Track

2 and pass the values to the network. [TC612]


Card details

The card ATC increments following the round-robin principle: ‘0001’, ‘0002’, ‘0003’,

‘0001’, ‘0002’ etc…

You can observe the ATC value in the 'cardholder name' subfield of Track 1 data: “CUST

IMP MC 356/ [ATC value]”.

User Action





This transaction will be performed three times.


Pass Criteria

Visual checks:

- The terminal approves the 3 online transactions - OK/NOK

Card log checks:



The network simulator shall receive three sets of Track 1 and/or Track 2 data, not

necessarily in the order shown below.

For one of the transactions, the values shall be:

- Track 1: B5413330056003560^CUST IMP MC 356/

1^251210100000170099909919769790 – OK/NOK/Not Applicable


separators) – OK/NOK/Not Applicable











Note N/A


250

© 2014 MasterCard



Objective To ensure the PayPass terminal correctly builds the discretionary data. [TC610]


Card details The card supports dynamic CVC3

User Action




If needed, PIN value is ‘4315.


Pass Criteria

Visual checks:


Card log checks:



- CVC3 validation is successful – OK/NOK


- DE 35 (Track2) or DE 45 (Track1) must be present and have the discretionary data last

digit equal to '2' – OK/NOK

Note N/A


© 2014 MasterCard


MCC 371A Test 01 Scenario 01

Objective




To ensure the terminal not supporting [PayPass3.0] correctly completes the Mag-Stripe

transaction with a Mobile. [TC681]

Applicability Terminal supports MasterCard PayPass and does not support [PayPass3.0]

Card details




Number.

User Action

Please use the following test card: M-TIP Subset 6 – MCC 371A v1.1.





Pass Criteria

Visual checks:


Card log checks:

- Application Label indicates "MCC 371A v1 1" - OK/NOK





- Track 1: B5413330056003719^CUST IMP MC 371A/^2512106067750680 –




Note




252

© 2014 MasterCard



Objective


To ensure the [PayPass3.0] terminal correctly completes the Mag-Stripe transaction with a

Mobile not requesting On-Device cardholder verification below the CVM Required Limit.

[TC682-1]



Card details




Number.

User Action





Pass Criteria

Visual checks:


Card log checks:








Note N/A


© 2014 MasterCard



Objective


To ensure the terminal correctly completes the Mag-Stripe transaction with a Mobile

requesting On-Device cardholder verification. [TC683-1]


indicating 'PIN verification successful'. [TC684-1]

Applicability

Terminal supports MasterCard PayPass and [PayPass3.0].







User Action


verification:





- A second transaction is performed where the card indicates that the Mobile PIN was


Please use the following test card: M-TIP Subset 6 – MCC 371B v1.1.




Pass Criteria








- Application Label indicates "MCC 371B v1 1" - OK/NOK



- Track 1: B5413330056003719^CUST IMP MC 371B/^2512106067750935 –




Note N/A


254

© 2014 MasterCard



Objective



Mobile not requesting On-Device cardholder verification. [TC682-2]

Applicability




The terminal configuration is such that Kernel Configuration indicates 'On-Device Cardholder Verification NOT supported'.



User Action



Limit.



Pass Criteria

Visual checks:


Card log checks:








Note N/A


© 2014 MasterCard


MCC 371B Test 01 Scenario 01

Objective




Applicability




The terminal configuration is such that Kernel Configuration indicates 'On-Device

Cardholder Verification NOT supported'.



User Action



Limit.



Pass Criteria

Visual checks:


Card log checks:








Note N/A


256

© 2014 MasterCard


MCC 371B Test 02 Scenario 01

Objective




Applicability


The terminal configuration is such that the CVM Required Limit equals the Contactless

Transaction Limit (On-device CVM). Both limits are greater than zero.



User Action


Enter any amount below the Contactless Transaction Limit (On-device CVM).



Pass Criteria

Visual checks:


Card log checks:








Note N/A


© 2014 MasterCard



Objective





Mobile not requesting On-Device cardholder verification. [TC682-3]


Card details AIP byte 1 bit 2 is NOT set ("On-device cardholder verification NOT supported").


User Action





Pass Criteria

Visual checks:


Card log checks:










Note




258

© 2014 MasterCard









User Action




When the terminal displays "Please see phone" (or equivalent) the test is completed so you

can stop/cancel the transaction.

Simulator N/A

Pass Criteria

Visual checks:


Card log checks:


Note N/A








User Action




When the terminal displays "Please see phone" (or equivalent) the test is completed so you

can stop/cancel the transaction.

Simulator N/A

Pass Criteria

Visual checks:


Card log checks:


Note N/A


© 2014 MasterCard



Objective








User Action





Pass Criteria

Visual checks:


Card log checks:








Note N/A


260

© 2014 MasterCard



Objective








User Action





Pass Criteria

Visual checks:


Card log checks:








Note N/A

Annexes

© 2014 MasterCard


6 Annexes

6.1 RSA Keys used

The Public Keys and modulus to be loaded into the terminal for offline CAM

Verification are given hereafter. The hash value is calculated on the concatenation of

all parts using SHA-1.

RID A0 00 00 00 04

Certification Authority Public Key Index FA

CA Public Key Modulus (1152 bits / 144 bytes) A9 0F CD 55 AA 2D 5D 99 63 E3 5E D0 F4 40 17 76 99 83

2F 49 C6 BA B1 5C DA E5 79 4B E9 3F 93 4D 44 62 D5 D1

27 62 E4 8C 38 BA 83 D8 44 5D EA A7 41 95 A3 01 A1 02

B2 F1 14 EA DA 0D 18 0E E5 E7 A5 C7 3E 0C 4E 11 F6 7A

43 DD AB 5D 55 68 3B 14 74 CC 06 27 F4 4B 8D 30 88 A4

92 FF AA DA D4 F4 24 22 D0 E7 01 35 36 C3 C4 9A D3 D0

FA E9 64 59 B0 F6 B1 B6 05 65 38 A3 D6 D4 46 40 F9 44

67 B1 08 86 7D EC 40 FA AE CD 74 0C 00 E2 B7 A8 85 2D

Public Key Exponent 03

Hash (20 bytes using SHA-1) 5B ED 40 68 D9 6E A1 6D 2D 77 E0 3D 60 36 FC 7A 16 0E

A9 9C

RID A0 00 00 00 04

Certification Authority Public Key Index F1

CA Public Key Modulus (1408 bits / 176 bytes) A0 DC F4 BD E1 9C 35 46 B4 B6 F0 41 4D 17 4D DE 29

4A AB BB 82 8C 5A 83 4D 73 AA E2 7C 99 B0 B0 53 A9

02 78 00 72 39 B6 45 9F F0 BB CD 7B 4B 9C 6C 50 AC 02

CE 91 36 8D A1 BD 21 AA EA DB C6 53 47 33 7D 89 B6

8F 5C 99 A0 9D 05 BE 02 DD 1F 8C 5B A2 0E 2F 13 FB 2A

27 C4 1D 3F 85 CA D5 CF 66 68 E7 58 51 EC 66 ED BF 98

85 1F D4 E4 2C 44 C1 D5 9F 59 84 70 3B 27 D5 B9 F2 1B

8F A0 D9 32 79 FB BF 69 E0 90 64 29 09 C9 EA 27 F8 98

95 95 41 AA 67 57 F5 F6 24 10 4F 6E 1D 3A 95 32 F2 A6

E5 15 15 AE AD 1B 43 B3 D7 83 50 88 A2 FA FA 7B E7


Hash (20 bytes using SHA-1) D8 E6 8D A1 67 AB 5A 85 D8 C3 D5 5E CB 9B 05 17 A1

A5 B4 BB

Annexes

262

© 2014 MasterCard


RID A0 00 00 00 04

Certification Authority Public Key Index EF

CA Public Key Modulus (1984 bits / 248 bytes) A1 91 CB 87 47 3F 29 34 9B 5D 60 A8 8B 3E AE E0 97 3A

A6 F1 A0 82 F3 58 D8 49 FD DF F9 C0 91 F8 99 ED A9 79

2C AF 09 EF 28 F5 D2 24 04 B8 8A 22 93 EE BB C1 94 9C

43 BE A4 D6 0C FD 87 9A 15 39 54 4E 09 E0 F0 9F 60 F0

65 B2 BF 2A 13 EC C7 05 F3 D4 68 B9 D3 3A E7 7A D9

D3 F1 9C A4 0F 23 DC F5 EB 7C 04 DC 8F 69 EB A5 65

B1 EB CB 46 86 CD 27 47 85 53 0F F6 F6 E9 EE 43 AA 43

FD B0 2C E0 0D AE C1 5C 7B 8F D6 A9 B3 94 BA BA 41

9D 3F 6D C8 5E 16 56 9B E8 E7 69 89 68 8E FE A2 DF 22

FF 7D 35 C0 43 33 8D EA A9 82 A0 2B 86 6D E5 32 85 19

EB BC D6 F0 3C DD 68 66 73 84 7F 84 DB 65 1A B8 6C 28

CF 14 62 56 2C 57 7B 85 35 64 A2 90 C8 55 6D 81 85 31 26

8D 25 CC 98 A4 CC 6A 0B DF FF DA 2D CC A3 A9 4C 99

85 59 E3 07 FD DF 91 50 06 D9 A9 87 B0 7D DA EB 3B


Hash (20 bytes using SHA-1) 21 76 6E BB 0E E1 22 AF B6 5D 78 45 B7 3D B4 6B AB 65

42 7A

Annexes

© 2014 MasterCard


6.2 DES Keys used

The Issuer Master Key (IMK) to be programmed in the Network Simulator for

Online Cryptograms (ARQC) verification is:

IMKARQC (IMK for ARQC)

9E 15 20 43 13 F7 31 8A CB 79 B9 0B D9 86 AD 29

The other keys (IMK for TC, AAC, Secure Messaging for Confidentiality and/or

Integrity) are the following.

IMKTC (IMK for TC, same as IMKARQC)

9E 15 20 43 13 F7 31 8A CB 79 B9 0B D9 86 AD 29

IMKAAC (IMK for AAC, same as IMKARQC)

9E 15 20 43 13 F7 31 8A CB 79 B9 0B D9 86 AD 29

IMKSMI (IMK for Secure Messaging for Integrity)

46 64 94 2F E6 15 FB 02 E5 D5 7F 29 2A A2 B3 B6

IMKSMC (IMK for Secure Messaging for Confidentiality)

CE 29 3B 8C C1 2A 97 73 79 EF 25 6D 76 10 94 92

Note: The above DES test keys is already put within your simulator

Annexes

264

© 2014 MasterCard


6.3 DES Key Used for PVV and CVC

Introduction

The PVV calculation uses the MasterCard algorithm.

Below shows how to program the DES key for PVV verification.

Issuer PVK

Issuer PVK:

D1 0C 52 A4 D9 38 13 CF 3F F6 2E 21 C2 27 FF 58

Issuer PVKI: 1

Below shows how to program the DES key for CVC verification is:

Issuer CVK:

D1 0C 52 A4 D9 38 13 CF 3F F6 2E 21 C2 27 FF 58

Note: The above DES test keys are already put within your MCI simulator.

*** END OF DOCUMENT ***

PayPass M-TIP Test Case User Guide · PayPass M-TIP Test Case User Guide • July 2014 i ......

Documents

Transcript of PayPass M-TIP Test Case User Guide · PayPass M-TIP Test Case User Guide • July 2014 i ......