Download - PP MTIP UserGuide Dec2011

5/21/2018 PP MTIP UserGuide Dec2011

1/201

PayPassUserGuide for TIP

SubsetsDecember 2011


2/201

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

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

whole or in part, without the prior written permission ofMasterCard.

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

MasterCard Worldwide - CCoEChausse de Tervuren, 198AB-1410 Waterloo

Belgium

Fax: +32 2 352 5353


3/201

Table of Contents

2011 MasterCard

PayPassUser Guide for TIP Subsets December 2011 i

1 Using this Manual ........................................................................................................................................... 1-11.1

Scope ........................................................................................................................................................ 1-1

1.2 Audience ................................................................ ................................................................. .................. 1-11.3 Terminology ............................................................................................................................................. 1-11.4 Language Use ........................................................ .................................................................... ............... 1-21.5 Related Publications .......................................................................................... ...................................... 1-21.6 Abbreviations ..................................................................................................... ...................................... 1-31.7 Notations ............................................................... ................................................................. .................. 1-41.8 History ........................................................ ................................................................... ........................... 1-4

2 Introduction .................................................................. ................................................................. .................. 2-12.1 Terminal Integration Testing Process ....................................................................................... ............... 2-12.2 Introduction to the TIP Cards ................................................................ .................................................. 2-22.3 Testing configuration requirements ......................................................................................................... 2-2

3 Test Cases ........................................................................................................................................................ 3-13.1 Test Case Template Description ............................................................. .................................................. 3-13.2 Common PayPass M/Chip Test Cases ..................................................................................................... 3-3

TC001 - Regressioncard does not support any ODA ......................................................... ........................... 3-3TC002 -RegressionCDA ................................................................. ............................................................. 3-4TC003 - Regressiondifferent CA key lengths ......................................................... ...................................... 3-4TC004 - Regressionexponent 2^16+1 .......................................................................................................... 3-5TC005 - RegressionOffline-only & ARQC ............................................................ ...................................... 3-5TC011 - Interoperabilityvarious unexpected data/length ............................................................... ............... 3-6TC012 -InteroperabilityCDOL1 includes tags forbidden in DE055 ............................................................ 3-6TC021 - Integration/capabilitiesOfflinePIN not supported inPayPass........................................................ 3-6TC022 - Integration/capabilitiesNo accumulated transaction amount .......................................................... 3-7TC023 -Integration/capabilitiesNo Velocity Checking .................................................... ........................... 3-8TC024 - Integration/capabilitiescardholder receipt below CVM limit ......................................................... 3-8TC031 - Integration/CVMonly NoCVM below the CVM limit ................................................................... 3-9TC032 - Integration/CVMonly NoCVM below the CVM limitonline transaction ................................... 3-9TC041 - Integration/online messageGratuities / Tips.............................................................................. 3-10TC042 - Integration/online messageIssuer response: successful ............................................................ .... 3-10TC043 - Integration/online messageIssuer response: unsuccessful ........................................................ .... 3-11TC045 - Integration/online messageIssuer response contains script ................................ .......................... 3-11TC046 - Integration/online messageTerminal Country Code not in CDOL1 ............................................. 3-11TC047 -Integration/online messagePAN sequence number from chip ...................................................... 3-12TC048 -Integration/online messagePAN sequence number not returned .................................................. 3-13TC049 -Integration/online messageFull Grade ................................................................ .......................... 3-13TC050 - Integration/online messageNew Values in Existing Authorization Fields ................................... 3-14TC051 - Integration/online messageOnline PIN ................................................................ ......................... 3-15TC052 - Integration/online messageIssuer response: wrong online PIN .................................................... 3-16TC061 - Integration/configurationContactless Transaction Limit .......................................................... .... 3-17TC063 -IntegrationAmount known before ................................................................................................ 3-17TC065 -IntegrationPIX extension .............................................................. ................................................ 3-18TC065b -IntegrationPIX extension not supported ............................................................ ......................... 3-18TC066 -Integrationservice code indicates a chip is present on card .......................................................... 3-19TC067 -Integrationservice code indicates OnlinePIN ........................................... .................................... 3-19TC068 -IntegrationFollowing a card decline ......................................................... .................................... 3-20


4/201

Table of Contents

ii 2011 MasterCard

PayPassUser Guide for TIP Subsets December 2011

TC069 - Integration/capabilitiesrefund (v2.x) ........... ................................................................. ................ 3-21TC069b - Integration/capabilitiesrefund (v1.3) ..................... ................................................................. .... 3-22

3.3 MasterCard PayPass M/Chip Test Cases ........................................................... .................................... 3-23TC201 - RegressionSDA ............................................................................................................................ 3-23TC221 - Integration/CVMattended terminal ........................................................... .................................... 3-24

TC222 - Integration/CVMCAT1....................................................... .......................................................... 3-25TC223 - Integration/CVMCAT2 and CAT3 ........................................................... .................................... 3-26

3.4 Maestro PayPass M/Chip Test Cases ................................................................. .................................... 3-27TC401 - Integration/capabilitiesNoPayPassMag Stripe ........................................................................... 3-27TC402 - Integration/capabilitiesNo SDA ................................................................ .................................... 3-27TC410 - Integration/CVMOnlinePIN above the CVM limit (in Maestro OnlinePIN Market) ................... 3-28TC411 - Integration/CVMnoCVM above the CVM limit (in Maestro OnlinePIN Market) ....................... 3-28TC412 - Integration/CVMHard limit market .......................................................... .................................... 3-29

3.5 PayPass Mag Stripe Test Cases ............................................................. ................................................ 3-30TC601 - Interoperabilityvarious unexpected data/length ............................................................... ............. 3-30TC611 - IntegrationService Code checking ................................................................................................ 3-30TC612 - IntegrationATC in discretionary data ........................................................................................... 3-31

TC613 -IntegrationIssuer response: unsuccessful ...................................................................................... 3-31TC614 - IntegrationTraditional Mag Stripe ................................................ ................................................ 3-32

4 Test Scenarios for TIP Subset 8 ................................................................................................... ................ 4-334.1 TIP Subset 8 card details .................................................................................................................... .... 4-334.2 Using the Test Cards ......................................................... ................................................................. .... 4-354.3 Test Scenario Template Description ................................................................... .................................... 4-354.4 Test Scenarios for MasterCard PayPass M/Chip ................................................................................... 4-384.5 Test Scenarios for Maestro PayPass M/Chip ......................................................................... .............. 4-123

5 Test Scenarios for TIP Subset 6 .................................. ................................................................. .............. 5-1765.1 TIP Subset 6 card details .................................................................................................................... .. 5-1765.2 Using the Test Cards ......................................................... ................................................................. .. 5-1775.3 Test Scenario Template Description ................................................................... .................................. 5-1775.4 Test Scenarios for PayPass Mag Stripe .............................................................. .................................. 5-178

6 Annexes ........................................................................................................................................................ 6-1866.1 RSA Keys used ....................................................... .................................................................... ........... 6-1866.2 DES Keys used ....................................................... .................................................................... ........... 6-1886.3 DES Key Used for PVV and CVC ........................................................... .............................................. 6-189


5/201

Using this Manual

2011 MasterCard

PayPassUser Guide for TIP Subsets December 2011 1-1

1 Using this Manual

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

1.1 Scope

This document lists thePayPassMag Stripe andPayPassM/Chip test cases and testscenarios used for thePayPassTIP or M-TIP.

1.2 Audience

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

obtain approval for theirPayPassimplementation.

1.3 Terminology

'Terminal' vs. 'reader'

[PayPass1.3] uses the term terminal in order to refer to the device supporting thePayPass application while [PayPass2.x] uses the term PayPassreader.

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

dealing with (M-)TIP it makes more sense to consider both the separate reader andthe POS terminal as a single device. Therefore this document will use the termterminal or PayPassterminal in order to refer to:

the device providing the contactless interface used by thePayPass card and

the device supporting thePayPass application and

the device sending the authorization/clearing messages online.

'Cards'

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

'(M-)TIP'

When a statement applies to both TIP and M-TIP, the term "(M-)TIP" is used.

However MasterCard did not define specificPayPassM-TIP subsets or cards so thecards listed in this document are the ones previously defined for the TIP process.Therefore this document will always mention the term "TIP cards", not "(M-)TIP

cards".


6/201

Using this Manual

1-2 2011 MasterCard


1.4 Language Use

The spelling of English words in this manual follows the convention used for U.S.English as defined in Websters New Collegiate Dictionary.MasterCard is

incorporated in the United States and publishes in the United States. Therefore, thispublication uses U.S. English spelling and grammar rules.

An exception to the above spelling rule concerns the spelling of proper nouns. In thiscase, we use the local English spelling.

1.5 Related Publications

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

AcqGuide2008 PPMCAIR V1.0-July 2008 +PayPassM/Chip ApplicationNote17 -

Oct 6, 2009

MaestroOnlinePIN MaestroPayPassOnline PIN - Acquirer Implementation Guide v2.0

PayPass2.1 PayPassM/Chip Reader Card Application Interface Specification

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

PayPass2.0 PayPassM/Chip Reader Card Application Interface Specification

(V2.0) +PayPassM/Chip ApplicationNote#15 (April 2, 2009)

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

PayPass1.3 PayPassM/Chip Technical Specifications (V1.3 - Sept2005) +

PayPassM/Chip ApplicationNote#11 (Aug 6, 2008)

MChip2010 M/Chip Requirements 11 June 2010

CustomerIntfce Customer Interface SpecificationApril 2009

TIPguide Terminal Integration Process Guide - January 2009

MTIPguide M-TIP Process Guide14 May 2010

EMV BOOK 1 ICC Specification for Payment Systems: Application Independent

ICC to Terminal Interface Requirements. Version 4.2, June 2008.

EMV BOOK 2 ICC Specification for Payment Systems: Security & Key

Management. Version 4.2, June 2008.

EMV BOOK 3 ICC Specification for Payment Systems: Application Specification.

Version 4.2, June 2008.

EMV BOOK 4 ICC Specification for Payment Systems: Cardholder, Attendant and

Acquirer Interface Requirements. Version 4.2, June 2008.


7/201

Using this Manual

2011 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

an Alphanumeric

ARQC Authorization Request Cryptogram

ATC Application Transaction Counterb Binary

CA Public Key Certification Authority Public Key

CDA Combined DDA/AC generation

CDOL Card Risk Management Data Object List

CVM Cardholder Verification Method

CVR Cardholder Verification Results

EMV Europay MasterCard Visa

FCI File Control Informationhex. Hexadecimal

IAC Issuer Action Code

ICC Integrated Circuit Card

M/Chip MasterCard Chip

n Numeric

PAN Primary Account Number

PDOL Processing Data Object List

PIN Personal Identification NumberPPSE PayPass Payment System Environment

RFU Reserved for Future Use

RID Registered Application Provider Identifier

SDA Static Data Authentication

TAC Terminal Authentication Code

TC Transaction Certificate

TRM Terminal Risk Management

TVR Terminal Verification Results


8/201

Using this Manual

1-4 2011 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.

# Number.

[] Optional part.

xx Any value.

1.8 History

The following lists the main changes:

Version Changes

March 2010 Original version

July 2010 Reviewed the tests to cover the [PayPass1.3] readers

- TestCase TC065b created

- TestCase TC069b created

- TestCase TC211, sub-case 06 created

Better test coverage for thePayPassMasterCard hard limit markets Other tests were created or updated:

- TC412 was created

- TC613 was updated (Issuer response '51' instead of '05')

August December

2011

Added the card version v2.1

Fixed issues with TVR B1b7 instead of B1b3

TC402 (SDA Maestro) does no longer apply for 1.3 because this could

be impossible to implement for 1.3 readers. MP72 T04 created

accordingly.

Refund: the terminal is not obliged to use the same amount as in the

purchase transaction (e.g.: a default zero value could be used instead).

Several tests modified accordingly.

Fixed an issue in TC065b and related scenarios: the transaction will

not abort after PPSE but after Select AIDs.

Added a pass criteria to ensure ARQC is validated

Fixed minor issues with the CVM 1F03 / 5F03

"(Please provide the receipt)" added in a few tests


9/201

Introduction

2011 MasterCard


2 Introduc t ion

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

2.1 Terminal Integration Testing Process

The M-TIP process defined in [MTIPprocess] is applicable forPayPassterminalssupporting [PayPass2.x]. In any other case, the TIP process defined in [TIPprocess]applies.

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 [AcqGuide2008].

The current document describes:

the (M-)TIP test cases that are defined to ensure the correct implementationof the MasterCard requirements. Each test case refers to a requirement in

[AcqGuide2008]

the test scenarios that must be executed in (M-)TIP. The test scenarios referto one or several test cases. Each test scenario involves a 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 figurebelow:

Test Case # 1 Objecti ve

+

Test Case # 2 Objecti ve+

Test Case # 3 Objecti ve

Card xx

Specifications

(requirements)Test Cases

Test Scenario

TIP

cards


10/201

Introduction

2-2 2011 MasterCard


2.2 Introduction to the TIP Cards

About TIP Cards

MasterCard has designed sets of test cards, to allow the acquirer to test that the hostand terminal payment applications are compliant with MasterCard requirements. TheTIP cards are grouped into different subsets in order to allow targeted testing. Forthe (M-)TIP process, the followingPayPass subsets are used.

ForPayPassM/Chip terminals, the Subset 6 ensures that thePayPassM/Chipterminals correctly work withPayPassMag Stripe cards.

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

The Subset 8 ensures that thePayPassM/Chip terminals correctly work withPayPassM/Chip cards.

Number of Cards

The following table summarizes the content of thePayPass TIP Subsets.

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 beconfigured as follows.

The list of Application Identifiers (AID) supported by the terminal must bethe ones intended for live deployment.

Application Version NumberPayPass Mag Stripe: Terminal Applicationversion number shall be set to 0001 forPayPassMag Stripe.

Application Version NumberPayPass M/Chip: Terminal Application version

number shall be set to 0002 forPayPassM/Chip.

Subset Type Number of cards

Subset 6

PayPassMag Stripe cards 6

PayPassM/Chip cards 1

Subset 8

MasterCardPayPassM/Chip cards 17

MaestroPayPassM/Chip cards 17

Total Number of cards 41


11/201

Introduction

2011 MasterCard


The Terminal Contactless Transaction Limit, when applicable, shall have thesame value as in the field for MasterCard and Maestro applications.

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

The Terminal CVM Required Limit, when applicable, shall have the samevalue as in the field for MasterCard and Maestro applications.

However the Certification Authority Public Keys shall be the test keys definedfurther in this document.


12/201


13/201

Test Cases

2011 MasterCard


3 Test Cases

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

3.1 Test Case Template DescriptionOverview

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

TC002 -RegressionCDA

Objective To ensure that thePayPassterminal performs CDA correctly.

Applicability

Conditions Terminal supports CDA

Reference

Documentation[AcqGuide2008]: 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 CriteriaThe terminal shall send request a TC with CDA (50) in the generate AC.

Transaction shall be approved offline.

Note*: most of the PayPass terminals will bypass the CDA if the transaction is declined orsent 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: CommonPayPassM/Chip Test Cases

TC2yy: MasterCardPayPassM/Chip Test Cases

TC4yy: MaestroPayPassM/Chip Test Cases

TC6yy:PayPassMag Stripe Test Cases

[Test category] can be the following:

"Regression": major Level2 tests that are re-performed during (M-)TIP toensure 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.


14/201

Test Cases

3-2 2011 MasterCard


"Integration": those tests ensure thePayPass terminal complies with theMasterCard requirements defined in [AcqGuide2008].

ObjectiveObjective To ensure that thePayPassterminal performs CDA correctly.

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

Applicability ConditionsApplicability

ConditionsTerminal supports CDA

This gives the conditions for the test to be applicable.

Reference Documentation

Reference


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

Test Conditions

Test Conditions


The AIP byte 1 indicates that CDA is supported.Data returned by card is such as the transaction can be approved offline*.

This lists all the conditions required for testing the objective.

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

Pass Criteria

Pass CriteriaThe 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.


15/201

Test Cases

2011 MasterCard


3.2 Common PayPass M/Chip Test Cases

The test cases described in this section apply to terminals that accept eitherMasterCardPayPassor MaestroPayPass.

TC001 - Regressioncard does not support any ODA

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

Applicability

ConditionsAlways applicable

Reference

Documentation

[AcqGuide2008]: Regression testno specific reference

Other: [PayPass2.x] section 4.3.6 Offline Data Authentication

Test Conditions


The AIP byte 1 indicates that SDA, DDA and CDA are NOT supported.Tests are run for MasterCard and Maestro applications, unless not applicable:

Case 01: amount is below the floor limit (and terminal is online capable)*

Case 02: amount is above the floor limit

Case 03: terminal is offline-only

Pass Criteria

The terminal will set the TVR byte 1 bit 8 (offline data authentication not performed).

Cases 01 & 02: Online capable terminals shall request an ARQC as per TAC settings,

even if the amount is below the floor limit.

Case 03: Offline-only terminals will decline the transaction offline as per TAC settings.

The terminal must not fallback to a contact or swipe transaction since thePayPassreaderrequested a card decline (see [AcqGuide2008] sections 2.4.10.3 and 2.6).

Note*: if the CVM limit is lower than the floor limit and if both the card and the terminalsupport OnlinePIN, the amount should be below the CVM limit in order to not set theTVR B3b3 (OnlinePIN entered).


16/201

Test Cases

3-4 2011 MasterCard



Objective To ensure that thePayPassterminal performs CDA correctly.

Applicability

ConditionsTerminal supports CDA

Reference


Test Conditions




Tests are run for MasterCard and Maestro applications, unless not applicable.

Pass Criteria

TVR byte 1 bit 8 is not set (offline data authentication was performed).

The terminal shall request a TC with CDA (50) in the generate AC.



TC003 - Regressiondifferent CA key lengths

ObjectiveTo ensure thePayPassterminal correctly supports different certification authority publickey lengths.

Applicability

Conditions Terminal supports SDA or CDA

Reference

Documentation


Other: [PayPass2.x] sections 4.3.13 Retrieve ICC key and VerifySDAD and 4.3.14 Static Data Authentication

Test Conditions


The AIP byte 1 indicates that SDA or/and CDA is supported.


Tests are run for MasterCard and Maestro applications, unless not applicable:

Case 01: CA key length is 1152/144



Pass CriteriaThe TVR shall indicate that the ODA was performed: TVR B1b8 =0.


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


17/201

Test Cases

2011 MasterCard


TC004 - Regressionexponent 2^16+1

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

Applicability

ConditionsTerminal supports SDA or CDA

Reference

Documentation


Other: [PayPass2.x] sections 4.3.13 Retrieve ICC key and Verify

SDAD and 4.3.14 Static Data Authentication

Test Conditions



ICC public key exponent is 2^16+1.



Pass Criteria The TVR shall indicate that the ODA was performed: TVR B1b8 =0.Transaction shall be approved offline.


TC005 - RegressionOffline-only & ARQC

ObjectiveTo ensure the offline-onlyPayPassterminal correctly behaves when the card erroneously

sends an ARQC.

Applicability

ConditionsTerminal is offline-only

Reference

Documentation


Other: Regression testno specific reference

Test Conditions



The card is such as it always returns an ARQC.


Pass Criteria

The offline-onlyPayPassterminal shall terminate the transaction upon reception of theARQC. The terminal must not fallback to a contact or swipe transaction since the

termination is due to an application layer error (see [AcqGuide2008] section 2.6).Note


18/201

Test Cases

3-6 2011 MasterCard


TC011 - Interoperabilityvarious unexpected data/length

ObjectiveTo ensure thePayPassterminal correctly behaves when it receives unexpected datavalue or length from the card.

Applicability

Conditions

Reference

Documentation

[AcqGuide2008]: Interoperability testno specific reference

Other: [PayPass2.x] Annex A Data Object Dictionary

Test Conditions


The card returns the data defined below.


Case 01: Unknown tags (e.g.: 88) in PPSE response

Case 02: Service Code inconsistency between track2 (57) and specific tag (5F30)

Case 03: Discretionary Data inconsistency between track2 (57) and specific tag

(9F20)Case 04: Track1 discretionary data (tag 9F1F) with maximum length (48 bytes)

Case 05: Track2 (57) with maximum acceptable length (37 digits)

Case 06: Unrecognized CVM returned in the CVM list

Case 07: IAD (9F10) with maximum length

Case 08: the signed record is padded up to 254 bytes with '00's. Card supports SDA only.

Case 09: the signed record is padded up to 254 bytes with '00's. Card supports CDA.

Case 10: the data records include the data object 9F6E PayPassthird party data.

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

Note

TC012 -InteroperabilityCDOL1 includes tags forbidden in DE055

ObjectiveTo ensure thePayPassterminal correctly behaves when the CDOL1 includes tags beingforbidden in the DE055.

Applicability

ConditionsTerminal is online capable.

Reference

Documentation

[AcqGuide2008]: Inherits from [MChip2010]

Other: [MChip2010] Section Contents of DE 55page 3-27

Test Conditions

The transaction amount must be below the Contactless transaction limit.The card requests 9F21 (Transaction Time) and 9F40 (Additional Terminal

Capabilities) in CDOL1. This data is forbidden in DE055.

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

(Approved).


Pass CriteriaThe Terminal shall not send the tags 9F21 and 9F40 to the network.

The Terminal shall approve the transaction.

Note

TC021 - Integration/capabilitiesOfflinePIN not supported inPayPass


19/201

Test Cases

2011 MasterCard


Objective To ensure thePayPassterminal does not support offlinePIN.

Applicability


ReferenceDocumentation

[AcqGuide2008]: 2.4.4.3 Offline PIN page 2-11

Test Conditions


The AIP byte 1 bit 5 indicates Cardholder Verification supported.

The first CVM in the card CVM list is OfflinePIN. The CVM list does not includeOnlinePIN.


Case 01: amount is below the CVM limit

Case 02: amount is above the CVM limit or CVM limit not supported

Pass Criteria

The terminal does not prompt for any PIN to be entered.

ThePayPasstransaction completes successfully. Neither Offline PIN nor Online PIN is

required.

NoteTerminals supporting only OnlinePIN (like CAT1) will set the TVR byte 3 bit 8Cardholder Verification was not successful.

TC022 - Integration/capabilitiesNo accumulated transaction amount

ObjectiveTo ensure that thePayPassterminal does not use an accumulated transaction amount bycard for the purpose of checking if the floor limit is exceeded.

ApplicabilityConditions

Terminal is offline/online capable.

If the terminal supports [PayPass1.3]: it does not support an accumulated transactionamount.

Reference

Documentation

[AcqGuide2008]: Section 2.4.7.1 Floor Limit Check Cumulative TransactionAmount Checking page 2-12

Test Conditions


All transaction amounts are below the floor limit.

Perform several offline initialization transactions so the sum of the transaction amounts

exceeds the floor limit.

E.g.: if the floor limit is 50, perform 1 initialization transaction of 40 and then a lasttransaction of 30.

Pass Criteria The terminal shall approve all the transactions offline, especially the last one, even if thesum of the previous transaction amounts exceeds the floor limit.

Note


20/201

Test Cases

3-8 2011 MasterCard


TC023 -Integration/capabilitiesNo Velocity Checking

Objective To ensure that thePayPassterminal does not perform Velocity Checking.

Applicability


Reference

Documentation[AcqGuide2008]: Section 2.4.7.3 Velocity Checking page 2-13

Test Conditions



TRM AIP bit set.

The tags 9F14 & 9F23 are returned by the card.

LastOnline Register ATC is returned, value =00

IAC denial set for new card, lower and upper consecutive

Pass Criteria The terminal shall approve the transaction. The TVR byte 2 bit 4 and byte 4 bits 6 and 7are not set.

Note

TC024 - Integration/capabilitiescardholder receipt below CVM limit

ObjectiveTo ensure that thePayPassterminal is able to print a cardholder receipt below the CVMlimit in case the cardholder requests it.


Always applicable

Reference

Documentation[AcqGuide2008]: Section 2.3.1.2 Terminal CVM Required Limit page 2-6

Test ConditionsThe transaction amount must be below the CVM limit.


Pass Criteria

The terminal shall approve thePayPasstransaction.

ThePayPassterminal shall be able to print a cardholder receipt below the CVM limit in

case the cardholder requests it.

Note


21/201

Test Cases

2011 MasterCard


TC031 - Integration/CVMonly NoCVM below the CVM limit

ObjectiveTo ensure that thePayPassterminal only supports No CVM as the CVM method forPayPasstransactions below or equal to the defined limit.

Applicability


Reference


Test Conditions

The transaction amount must be below the CVM limit.

The card CVM list includes other CVM methods before the noCVM one.


Case 01: Amount is below the CVM limit and below the floor limit (not applicable ifonline-only).

Case 02: Amount is equal to the CVM limit.

Pass Criteria

The terminal shall approve thePayPasstransaction.

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 '5F 03 00'

Note

TC032 - Integration/CVMonly NoCVM below the CVM limitonline transaction

Objective

To ensure that thePayPassterminal only supports No CVM as the CVM method forPayPasstransactions below or equal to the defined limit, even if the amount is above the

floor limit, if applicable.

Applicability

ConditionsFloor limit is smaller than the CVM limit

Reference


Test Conditions

The transaction amount must be below the CVM limit but above the floor limit.


Card contains (1F03) in the CVM list.

Pass Criteria

The terminal shall approve thePayPasstransaction online.

The terminal shall not prompt for PIN or print a signature receipt. The cardholder

verification shall be successful:


- CVM result shall be 1F 03 00 or '5F 03 00'

Note


22/201

Test Cases

3-10 2011 MasterCard


TC041 - Integration/online messageGratuities / Tips

Objective

To ensure thePayPassterminal correctly manages the gratuities, when supported.

To ensure thePayPassterminal offers the cardholder to enter the gratuity amount beforetapping, when gratuity is supported.

Applicability

ConditionsTerminal supports gratuities

Reference

Documentation[AcqGuide2008]: 2.4.3.1 Gratuities/Tips page 2-10

Test Conditions

The cardholder must enter a gratuity amount. The transaction amount plus the gratuityamount must be below the Contactless transaction limit.

The network simulator validates the authorization message and returns a successfulresponse.


Pass Criteria

ThePayPassterminal shall offer the cardholder to enter the gratuity amount beforetapping.

The online authorization request must contain the sum of initial amount and gratuity in

the 'Amount authorized' field (DE055 subfield 9F02) and in DE-004.

The 'Amount, other' field (DE055 subfield 9F03) must contain zeroes or be absent.

The transaction shall be approved.

Note

TC042 - Integration/online messageIssuer response: successful

Objective To ensure thePayPassterminal correctly manages the Issuer response 00 (successful).

Applicability

ConditionsTerminal is online capable

Reference

Documentation


Other: [MChip2010] Section Authorization Response Code page 3-31

Test Conditions


The network simulator validates the authorization message and returns the responses 00(successful).


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

Note


23/201

Test Cases

2011 MasterCard


TC043 - Integration/online messageIssuer response: unsuccessful

ObjectiveTo ensure thePayPassterminal correctly manages the Issuer responses 51 (insufficientfunds) and 57 (Transaction not permitted).

Applicability


Reference

Documentation

[AcqGuide2008]: Inherits from [CustomerIntfce]

Other: [CustomerIntfce] Section DE 39 - Response Code

Test Conditions


The network simulator validates the authorization message and returns the responses

below.


Case 01: network simulator response is 51 (insufficient funds)

Case 02: network simulator response is 57 (Transaction not permitted)

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

Note

Following an online decline, (Not Authorized) there is no restriction on performing asubsequent contact transaction, if supported by the terminal. ([AcqGuide2008] section

2.4.10.2)

TC045 - Integration/online messageIssuer response contains script

ObjectiveTo ensure thePayPassterminal does not process the ICC response data erroneously

returned by the issuer.

Applicability


Reference

Documentation[AcqGuide2008]: Section 4.3 Authorization Responses page 4-4

Test Conditions

The transaction amount must be above the floor limit and below the Contactlesstransaction limit.

Card is let on the terminal until the transaction is completed or the ticket is printed.

The network simulator validates the authorization message and returns the followingresponse:

- DE 039 (Response code) = '00' (Approved)

- DE 055 - PDS 91 (Issuer Authentication Data) is present

- DE 055 - PDS 72 (Issuer Script Template 2) with one script identifier and 6PIN Unblock commands followed by a PIN Change Unblock.


Pass Criteria

The terminal shall not forward any Application Block command to the card.

The end of the transaction is out of scope (the terminal may decline or not the

transaction).

Note

TC046 - Integration/online messageTerminal Country Code not in CDOL1


24/201

Test Cases



ObjectiveTo ensure thePayPassterminal transmits the Terminal Country Code (tag 9F1A) to thenetwork even if it is not requested by the card in the CDOL1.

Applicability


Reference

Documentation


Other: [MChip2010] Section Contents of DE 55 page 3-27

Test Conditions


The card does not request the Terminal Country Code (tag 9F1A) in the CDOL1.

The network simulator validates the authorization message (except ARQC) and returnsthe response '00' (Approved).


Pass CriteriaThe Terminal shall send the Terminal Country Code (tag 9F1A) to the network.


Note

TC047 -Integration/online messagePAN sequence number from chip

ObjectiveTo ensure thePayPassterminal transmits the PAN sequence number coming from thechip and not from the Track2 equivalent data item.

Applicability


Reference

Documentation


Other: [MChip2010] Section Data in the Authorization RequestMessage page 3-29

Test Conditions


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

Track2 equivalent data item.

The network simulator validates the authorization message and returns the response '00'(Approved).


Pass Criteria

The Terminal shall send the PAN sequence number value from the tag 5F34 to thenetwork.


Note


25/201

Test Cases

2011 MasterCard


TC048 -Integration/online messagePAN sequence number not returned

ObjectiveTo ensure thePayPassterminal does not transmit the PAN sequence number when it isnot returned by the card.

Applicability


Reference

Documentation


Other: [MChip2010] Section Data in the Authorization Request

Message page 3-29

Test Conditions


The PAN sequence number is not returned by the card.



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

Note

TC049 -Integration/online messageFull Grade

Objective To ensure that thePayPassterminal supports the Full Grade network messages.


Terminal is online capable

Reference

Documentation[AcqGuide2008]: Section 1.3 Implementation and Prerequisites Summary p1-1

Test Conditions




Pass CriteriaThe terminal shall send a DE055 message to the network.

The terminal shall approve the transaction.

Note


26/201

Test Cases



TC050 - Integration/online messageNew Values in Existing Authorization Fields

ObjectiveTo ensure thePayPassterminal correctly manages the new values in the existingauthorization fields.


Terminal is online capable

Reference

Documentation[AcqGuide2008]: Section 4.2 Authorization Requests page 4-2

Test Conditions

The transaction amount must be above the floor limit and below the Contactlesstransaction limit.


Several tests are run, unless not applicable:

Case 01:PayPassMag Stripe transaction (MasterCard application only)

Case 02:PayPassM/Chip transaction, tag 5F34 is returned by card*

Pass Criteria

Case 01: the network simulator shall receive the following:

DE022 SE 1 = 91

DE061 SE 11 = 3

Case 02: the network simulator shall receive the following:

DE022 SE 1 = 07

DE023 = 01

DE055 shall be present

DE061 SE 11 = 3


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


27/201

Test Cases

2011 MasterCard


TC051 - Integration/online messageOnline PIN

ObjectiveTo ensure thePayPassterminal correctly manages the OnlinePIN verification, whensupported.

Applicability

ConditionsTerminal supports OnlinePIN

Reference

Documentation


Other: [MChip2010] Annex A Data Dictionary

Test Conditions

The transaction amount must be above the CVM limit and below the Contactlesstransaction limit.

The AIP indicates that CVM is supported.

Data returned by card is such as OnlinePIN 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 OnlinePIN entered is correct:Case 01: OnlinePIN is 4 digits long

Case 02: OnlinePIN is 5 digits long

Case 03: OnlinePIN is 6 digits long.

Pass CriteriaThe TVR byte 3 bit 3 must be set (Online PIN entered).

The transaction shall be approved online.

Note


28/201

Test Cases



TC052 - Integration/online messageIssuer response: wrong online PIN

ObjectiveTo ensure thePayPassterminal correctly manages the Issuer responses 55 (wrong PIN)and 75 (Allowable number of PIN tries exceeded).


Terminal supports OnlinePIN

Reference

Documentation



Test Conditions

The transaction amount must be above the CVM limit and below the Contactlesstransaction limit.

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

Tests are run for MasterCard application:

Case 01: network response is 55 (wrong PIN)

Case 02: network response is 75 (Allowable number of PIN tries exceeded)

Pass Criteria

The TVR byte 3 bit 3 must be set (Online PIN entered).

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

Note

*: In case of a wrong PIN (case 01), one could expect the terminal to prompt thecardholder 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 ATC (transaction counter) value, even if the second PIN is correct.Therefore the terminal shall decline the transaction in order to avoid such issues in the

field.

Following an online decline, (Not Authorized) there is no restriction on performing a

subsequent contact transaction, if supported by the terminal. ([AcqGuide2008] section2.4.10.2)


29/201

Test Cases

2011 MasterCard


TC061 - Integration/configurationContactless Transaction Limit

ObjectiveTo ensure that thePayPassterminal correctly implements the Contactless TransactionLimit.


The terminal has a transaction limit for the MasterCard application.

Reference

Documentation

[AcqGuide2008]: Section 2.3.1.1 Terminal Contactless Transaction Limit p2-6 &section 3.4.2.1 Terminal Contactless Transaction Limit p3-5

Test Conditions


Case 01: amount is below the Contactless transaction limit

Case 02: amount is equal to the Contactless transaction limit (e.g.: 25.00)

Case 03: [if the terminal allows the user to enter amounts greater than the transaction

limit] the amount is one minor unit above the transaction limit (e.g.: 25.01)

Case 04: [if the terminal allows the user to enter amounts greater than the transactionlimit] the amount is greater than the transaction limit (e.g.: 50.00)

Case 05: [if the terminal does not allow the user to enter amounts greater than thetransaction limit] the user shall try to enter an amount greater than the transaction limit

Pass Criteria

Cases 01 & 02: the terminal shall approve the transaction.

Cases 03 & 04: the terminal shall not perform the transaction above the transaction limit.

The terminal will either abort after the PPSE response or will not activate thePayPassreader.

Case 05: the terminal shall not allow the user to enter an amount greater than thetransaction limit

Note

TC063 -IntegrationAmount known before

ObjectiveTo ensure that the final transaction amount is known before performing thePayPasstransaction.

Applicability

ConditionsTerminal is attended

Reference

Documentation[AcqGuide2008]: Section 2.4.3 Amount Entry at Attended POS page 2-10

Test Conditions

Pass CriteriaThe attended terminal shall request the amount before performing thePayPasstransaction. The cardholder must not be able to tap before entering the amount.

Note


30/201

Test Cases



TC065 -IntegrationPIX extension

Objective To ensure that thePayPassterminal correctly manages the extended AIDs.

Applicability

Conditions If the terminal supports [PayPass1.3]: it supports extended AIDs

Reference

Documentation

[AcqGuide2008]: Section 2.4.2 Application Selection and Cardholder

Confirmation page 2-10

Test Conditions


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

(Approved).


Case 01: AID is extended with the following: D056 01

Case 02: AID is extended with the following: C123456789

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

Note

TC065b -IntegrationPIX extension not supported

ObjectiveTo ensure that thePayPassterminal correctly behaves when it does not support extendedAIDs.

Applicability

ConditionsThe terminal supports [PayPass1.3] and does not support extended AIDs

Reference

Documentation

[AcqGuide2008]: Section 2.4.2 Application Selection and Cardholder

Confirmation page 2-10

Test Conditions



AID is extended with the following: D056 01

Pass CriteriaThe terminal shall abort the transaction. It shall not send the Get Processing Optionscommand.

Note

Only terminals supporting [PayPass1.3] do not support extended AIDs. This feature ismandatory in [PayPass2.x].

In [PayPass1.3], it is mandatory to use the list of applications method as described in

Section 12.3.3 of [EMV BOOK 1] when no matching application is found in the PPSEresponse.


31/201

Test Cases

2011 MasterCard


TC066 -Integrationservice code indicates a chip is present on card

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

Applicability


Reference

Documentation[AcqGuide2008]: Section 2.4.6 Service Code Checking page 2-12

Test Conditions


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


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

Note

TC067 -Integrationservice code indicates OnlinePIN

ObjectiveTo ensure that thePayPassterminal does not use the service code in order to requireonline authorization or online PIN.

Applicability


Reference

Documentation[AcqGuide2008]: Section 2.4.6 Service Code Checking page 2-12

Test Conditions

The transaction amount must be below the Contactless transaction limit.Tests are run for MasterCard and Maestro applications, unless not applicable:

CVM list does not include OnlinePIN.

Case 01: ServiceCode contained in Track2 is 206 (Normal Authorization, PIN if pinpad

present). Amount is below the CVM limit.

Case 02: ServiceCode contained in Track2 is 206(Normal Authorization, PIN if pinpadpresent). Amount is above the CVM limit.

Case 03: ServiceCode in Track2 is 220 (Issuer Authorization, PIN if pinpad present)

Case 04: ServiceCode contained in Track2 is 226 (Issuer Authorization, PIN required)

Pass Criteria

Cases 01: the terminal shall not prompt for PIN. The terminal shall approve thePayPasstransaction.

Case 02 & 03: the terminal shall not prompt for PIN. The terminal shall approve thePayPasstransaction offline.

Note


32/201

Test Cases



TC068 -IntegrationFollowing a card decline

ObjectiveTo ensure thePayPassterminal prompts the cardholder to perform a contact transaction,if supported, when the card declines and the terminal did not request a card decline.

Applicability

ConditionsThe terminal supports contact

Reference

Documentation[AcqGuide2008]: Section 2.4.10.3 Card Declines page 2-14

Test Conditions


Data returned by card are such as the terminal does not request an AAC in the GenAC.

The card returns an AAC to the Generate AC.


Case 01: amount is below the floor limit

Case 02: amount is above the floor limit

Pass Criteria

Case 01: the terminal shall request a TC in the Generate AC.

Case 02: the terminal shall request an ARQC in the Generate AC.

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

The terminal shall approve the contact transaction.

Note


33/201

Test Cases

2011 MasterCard


TC069 - Integration/capabilitiesrefund (v2.x)

Objective To ensure thePayPassterminal correctly performs refund.

Applicability

Conditions Terminal is attended and supports refund and follows [PayPass2.x].

Reference

Documentation[AcqGuide2008]: Section 2.4.1.3 Refunds page 2-9 *

Test Conditions

- First step is to perform the purchase:

The transaction amount must be below the transaction limit.

- Second step is to perform the refund:

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


Case 01:PayPassM/Chip MasterCard offline transaction to be refunded

Case 02:PayPassM/Chip MasterCard online transaction to be refunded

Case 03:PayPassM/Chip Maestro offline transaction to be refundedCase 04:PayPassM/Chip Maestro online transaction to be refunded

Case 05:PayPassMag Stripe MasterCard transaction

Pass Criteria

Cases 01 & 03:

The first transaction is approved offline.

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

refund process, the terminal displays a message to inform the cardholder that refundhas been done successfully.

Cases 02 & 04:

The first transaction is approved online.

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

refund process, the terminal displays a message to inform the cardholder that refundhas been done successfully.

Case 05:


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

cardholder that refund has been done successfully.

Note *: Please also see ApplicationNote17 for additional specification details.


34/201

Test Cases



TC069b - Integration/capabilitiesrefund (v1.3)

Objective To ensure thePayPassterminal correctly performs refund.

Applicability

Conditions Terminal is attended and supports refund and follows [PayPass1.3].

Reference

Documentation[AcqGuide2008]: Section 2.4.1.3 Refunds page 2-9 *

Test Conditions

- First step is to perform the purchase:

The transaction amount must be below the transaction limit.

- Second step is to perform the refund:

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


Case 01:PayPassM/Chip MasterCard offline transaction to be refunded

Case 02:PayPassM/Chip MasterCard online transaction to be refunded

Case 03:PayPassM/Chip Maestro offline transaction to be refundedCase 04:PayPassM/Chip Maestro online transaction to be refunded

Case 05:PayPassMag Stripe MasterCard transaction

Pass Criteria

Cases 01 & 03:

The first transaction is approved offline.

At the end of the second transaction, the terminal displays a message to inform the


Cases 02 & 04:


At the end of the second transaction, the terminal displays a message to inform the


Case 05:The first transaction is approved online.

At the end of the second transaction, the terminal displays a message to inform thecardholder that refund has been done successfully.

Note *: Please also see ApplicationNote17 for additional specification details.


35/201

Test Cases

2011 MasterCard


3.3 MasterCard PayPassM/Chip Test Cases

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

TC201 - RegressionSDA

Objective To ensure that thePayPassterminal performs SDA correctly.

Applicability

ConditionsTerminal supports SDA

Reference


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*: most of the PayPass terminals will bypass the SDA if the transaction is declined orsent online, see transaction flow in technical specifications.


36/201

Test Cases



TC221 - Integration/CVMattended terminal

ObjectiveTo ensure the attendedPayPassterminal correctly manages the cardholder verificationabove the CVM limit.


Terminal is attended and supports MasterCard

Reference

Documentation[AcqGuide2008]: Section 2.4.4.1 MasterCardPayPassCardholder Verificat p 2-10

Test Conditions


The network simulator validates the authorization message and returns 00 (successful).


Case 01: the card supports offlinePIN then Signature (5E 03) then noCVM. The

transaction amount must be the lowest value above the CVM limit (e.g.: 25.01).

Case 02: Terminal supports gratuity. The card supports offlinePIN then Signature (5E03) then noCVM. The sum of transaction and gratuity amounts must be the lowest value

above the CVM limit (e.g.: 25.01).Case 03: the card supports onlinePIN then noCVM (1F 03). Terminal does not support

OnlinePIN. The transaction amount must be above the CVM limit.

Case 04: card supports onlinePIN (02 03) then noCVM. Terminal supports OnlinePIN.

The transaction amount must be the lowest value above the CVM limit (e.g.: 25.01).

Case 05: card supports noCVM only (1F 03). The terminal supports noCVM above theCVM limit*. The amount is above the CVM limit.

Case 06: card supports noCVM only (1F 03). The terminal does not support noCVMabove the CVM limit*. The amount is above the CVM limit.

Pass Criteria


The cardholder verification shall be successful (except case 06): TVR byte 3 bit 8 = 0

Cases 01 & 02: The terminal shall print a signature receipt.- CVM result shall be 5E 03 00

Case 03: The terminal shall not prompt for PIN or print a signature receipt.

- CVM result shall be 1F 03 00

Case 04: 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

Case 05: The terminal shall not prompt for PIN or print a signature receipt.


Case 06: the cardholder verification shall fail:


- CVM result shall be 3F 00 01The terminal shall not prompt for PIN or print a signature receipt.

Note*: according to [MaestroOnlinePIN] section 2.4.4.2, a [PayPass1.3] reader supportinga single terminal capabilities parameter will not support 'noCVM' above the CVM limit.


37/201

Test Cases

2011 MasterCard


TC222 - Integration/CVMCAT1

ObjectiveTo ensure the CAT1PayPassterminal correctly manages the cardholder verificationabove the CVM limit.


Terminal supports MasterCard and is a CAT1

Reference

Documentation

[AcqGuide2008]: Section 2.4.4.1 MasterCardPayPassCardholder Verificationpage 2-10

Test Conditions


The network simulator validates the authorization message and returns the responses 00

(successful).


Case 01: the card supports offlinePIN then Signature then noCVM.

Case 02: the card supports onlinePIN then noCVM.

Case 03: the card supports noCVM only.

Pass Criteria





The terminal shall not prompt for PIN or print a signature receipt.

Case 02: the cardholder verification shall be successful:




The terminal shall request an ARQC.

The terminal shall prompt for PIN.





Note


38/201

Test Cases



TC223 - Integration/CVMCAT2 and CAT3

ObjectiveTo ensure the CAT2 and CAT3PayPassterminals correctly manage the cardholderverification above the CVM limit.


Terminal supports MasterCard and is a CAT2 or a CAT3

Reference

Documentation

[AcqGuide2008]: Section 2.4.4.1 MasterCardPayPassCardholder Verificationpage 2-10

Test Conditions

The transaction amount must be below the Contactless transaction limit and above theCVM limit.



Case 01: the card supports offlinePIN then Signature then noCVM

Case 02: the card supports onlinePIN then noCVM

Case 03: the card supports noCVM only

Pass Criteria














Note


39/201

Test Cases

2011 MasterCard


3.4 Maestro PayPassM/Chip Test Cases

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

TC401 - Integration/capabilitiesNoPayPassMag Stripe

ObjectiveTo ensure that the terminal terminates the transaction if thePayPass Maestro cardindicates that it does not supportPayPassM/Chip.

Applicability

ConditionsTerminal supports MaestroPayPass

Reference

Documentation[AcqGuide2008]: Section 2.2.1 AcceptingPayPassMag Stripe page 2-4

Test ConditionsTransaction amount is below the transaction limit.

The card indicates in the AIP that it does not supportPayPassM/Chip.

Pass Criteria

The terminal shall terminate the transaction.

The terminal must not fallback to contact or swipe transaction since the termination is

due to an application layer error (see [AcqGuide2008] section 2.6).

Note

TC402 - Integration/capabilitiesNo SDA

Objective To ensure that the MaestroPayPassterminal does not support SDA.


Terminal supports MaestroPayPass and follows [PayPass2.x] and is offline capable

Reference

Documentation[AcqGuide2008]: Section 2.4.5 Offline Data Authentication page 2-11

Test ConditionsTransaction amount is below the floor limit and the CVM limit.

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


40/201

Test Cases



TC410 - Integration/CVMOnlinePIN above the CVM limit (in Maestro OnlinePIN Market)

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

Applicability

Conditions Terminal supports Maestro in a Maestro OnlinePIN Market.

Reference

Documentation[MaestroOnlinePIN]: Section 2.4.4.2 MaestroPayPassCardholder Verification p 2

Test Conditions

Transaction amount is above the CVM limit and below the 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.The terminal shall prompt for PIN.


Note

TC411 - Integration/CVMnoCVM above the CVM limit (in Maestro OnlinePIN Market)

Objective

To ensure that transactions attempted above the CVM limit in a Maestro OnlinePINMarket with cards issued outside a Maestro OnlinePIN Market (i.e.: not supportingOnlinePIN in the CVM list) will be declined by the terminal.

Applicability

ConditionsTerminal supports Maestro in a Maestro OnlinePIN Market.

Reference

Documentation

[MaestroOnlinePIN]: Section 2.4.4.2 MaestroPayPassCardholder Verificationpage 2

Test Conditions

Transaction amount is above the CVM limit and below the transaction limit.


The card CVM list indicates noCVM.

Pass Criteria

The cardholder verification shall fail:

- TVR byte 3 bit 3 = 0 (Online PIN NOT entered)

- TVR byte 3 bit 8 = 1 (Cardholder verification failed)- CVM result shall be 3F 00 01

The terminal does not ask to enter PIN.

The terminal declines the transaction offline as per the TACs defined in[MaestroOnlinePIN].

Note


41/201

Test Cases

2011 MasterCard


TC412 - Integration/CVMHard limit market

ObjectiveTo ensure that MaestroPayPassis a hard limit implementation, except in MaestroOnline PIN markets.

Applicability

ConditionsTerminal supports Maestro and is not in a Maestro OnlinePIN Market.

Reference

Documentation[MaestroOnlinePIN]: Section 2.3.2 Hard and Soft Limit Implementations page 2

Test ConditionsTransaction amount is equal to the Maestro transaction limit.

The card CVM list indicates noCVM.

Pass Criteria


The cardholder verification shall be successful:



Note


42/201

Test Cases



3.5 PayPassMag Stripe Test Cases

The test cases described in this section apply to terminals that accept MasterCardPayPassMag Stripe.

TC601 - Interoperabilityvarious unexpected data/length

ObjectiveTo ensure thePayPassterminal correctly behaves when it receives unexpected datavalue or length from the card.

Applicability

ConditionsTerminal supports MasterCardPayPass

Reference

Documentation

[AcqGuide2008]: Interoperability testno specific reference

Other: [PayPass2.x] Annex A Data Object Dictionary

Test Conditions


The network simulator returns the responses 00 (successful).The card returns the data defined below.

Case 01: Track1 (tag 56) with maximum length (48 bytes)

Case 02: Track2 (9F6B) with maximum length (37 digits)

Case 03: Track1 discretionary data (tag 56) with minimum length (3 bytes)

Case 04: Track2 discretionary data (tag 9F6B) with minimum length (3 digits)

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

Note

TC611 - IntegrationService Code checking

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

Applicability


Reference

Documentation[AcqGuide2008]: Section 2.4.6 Service Code checking page 2-12

Test Conditions

The transaction amount is below the transaction limit.


The network simulator returns the responses 00 (successful).Case 01: card returns a service code 101

Case 02: card returns a service code 205



Pass Criteria The terminal shall approve the transaction.

Note


43/201

Test Cases

2011 MasterCard


TC612 - IntegrationATC in discretionary data

ObjectiveTo ensure that the terminal correctly copies the ATC in thePayPassTrack 1 and/orTrack 2 and pass the values to the network.


Terminal supports MasterCardPayPass

Reference

Documentation

[AcqGuide2008]: Integration/regression testno specific reference

Other: [PayPass2.x] section 4.3.5

Test Conditions

The transaction amount is below the transaction limit.


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

The network simulator returns the responses 00 (successful).

Pass CriteriaThe terminal shall approve all transactions and pass the correctPayPassTrack 1 and/orTrack 2 values to the network correctly.

Note

TC613 -IntegrationIssuer response: unsuccessful

ObjectiveTo ensure thePayPassterminal correctly manages the Issuer response 51 (Insufficientfunds/over credit limit).

Applicability


Reference

Documentation



Test ConditionsThe 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

Following an online decline, (Not Authorized) there is no restriction on performing asubsequent contact transaction, if supported by the terminal. ([AcqGuide2008] section2.4.10.2)


44/201

Test Cases



TC614 - IntegrationTraditional Mag Stripe

ObjectiveTo ensure the terminal still performs correctly a traditional Mag Stripe transaction whenit contains or is connected to aPayPassreader.


Terminal supports MasterCardPayPass

Reference

Documentation[AcqGuide2008]: Interoperability testno specific reference

Test Conditions


The card is swiped in the terminal

The network simulator returns the responses 00 (successful).

Pass Criteria

The network simulator shall receive the following:

DE022 SE 1 = 90 (POS entry mode: traditional Mag stripe)

DE061 SE 11 = 2 or 5 or 7 or 8 (card data terminal input capability :

traditional Mag stripe)


Note


45/201

Test Scenarios for TIP Subset 8

2011 MasterCard


4 Test Scenarios fo r TIP Subset 8This chapter lists the PayPass M/Chip (M-)TIP Test Scenarios.

4.1 TIP Subset 8 card details

PANs and PINs

Below are the TIP Subset 8 MasterCard card details:

Card Name ICC Track 2 equivalent data PIN

PPC MCD 01 5413330089600010D14122010123409172 4315

PPC MCD 02 5413330089600028D14122010123409172 4315

PPC MCD 03 5413330089600036D14122060123409172 4315

PPC MCD 04 5413330089600044D14122010123409172 4315

PPC MCD 06 5413330089600069D14122260123409172 4315

PPC MCD 07 5413330089600077D14122010123409172 4315

PPC MCD 09 5413330089600093D14122010123409172 4315

PPC MCD 10 5413330089600101D14122010123409172 4315

PPC MCD 11 5413330089600119D14122010123409172 4315

PPC MCD 12 5413330089600127D14126010123409172 4315

PPC MAP 01 5413330089601018D14122200123409172 4315

PPC MAP 03 5413330089601034D14122010123409172 4315

PPC MAP 04 5413330089601042D14122210123409172 4315

PPC MAP 06 5413330089601067D14122020123409172999F 4315

PPC MAP 07 5413330089601075D14122010123409172 4315

PPC MAP 08 5413330089601083D14122200123409172 4315

PPC MAP 10 5413330089601109D14122010123409172 4315


46/201




Below are the TIP Subset 8 Maestro card details:

Card Name ICC Track 2 equivalent data PIN

MP01 6799998900000060018D1412201012345678 4315

MP11 6799998900000060117D1412201012345678 4315

MP12 6799998900000060125D14122060123456789F 4315

MP13 6799998900000060133D1412226012345678 4315

MP14 6799998900000060141D1412220012345678 4315

MP15 6799998900000060158D1412201012345678 4315

MP16 6799998900000060166D1412222012345678 4315

MP17 67999989000000675D1412201012345678 4315

MP18 6799998900000060182D1412221012345678 4315

MP19 6799998900000060190D1412220012345678 4315

MP20 6799998900000060208D1412201012345678 4315

MP71 6799998900000060711D1412206012345678 4315

MP72 6799998900000060729D1412220012345678 4315

MP91 6799998900000060919D1412201012345678 4315

MP92 6799998900000060927D1412201012345678 4315

MP93 6799998900000060935D1412201012345678 4315

MP94 6799998900000060943D1412201012345678 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, inaccordance with MasterCard policy for debit/credit products.


47/201


2011 MasterCard


4.2 Using the Test Cards

Card log feature

All TIP Subset 8 cards have the ability to store the command and response exchangesbetween the terminal and the card. The stored exchanges can then be extracted fromthe 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 0]

4.3 Test Scenario Template Description

Overview

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

PPC MCD 02 Test 02 Scenario 01

Objective

To ensure thePayPassterminal correctly behaves when it receives unexpected datavalue or length from the card. Cases of Discretionary Data inconsistency and IAD

(9F10) with maximum length. [TC011-03 & 07]

Applicability

ConditionsTerminal supports MasterCard and has a transaction limit for the MasterCard application

Card

configuration

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

Download - PP MTIP UserGuide Dec2011

Top Related