0% found this document useful (0 votes)

654 views63 pages

PayPass v3 TTAL2-Testing Env Nov2013

Paypass testing EMV

Uploaded by

Phạm Tiến Thành

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

654 views63 pages

PayPass v3 TTAL2-Testing Env Nov2013

Paypass testing EMV

Uploaded by

Phạm Tiến Thành

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 63

PayPass Testing

Environment
Version 3 Level 2 Reader Testing
November 2013

Proprietary Rights

The information contained in this document is proprietary and

confidential to MasterCard International Incorporated, one or more of its
affiliated entities (collectively MasterCard), or both.
This material may not be duplicated, published, or disclosed, in whole or
in part, without the prior written permission of MasterCard.

Trademarks

Trademark notices and symbols used in this manual reflect the

registration status of MasterCard trademarks in the United States. Please
consult with the Customer Operations Services team or the MasterCard
Law Department for the registration status of particular product,
program, or service names outside the United States.
All third-party product and service names are trademarks or registered
trademarks of their respective owners.

MasterCard Worldwide
Chip Centre of Excellence
Chausse de Tervuren 198A
B-1410 Waterloo
Belgium.
www.mastercard.com

Table of Contents

1 Introduction ................................................................................................................. 1
Purpose ..................................................................................................................................................... 1
Audience ................................................................................................................................................... 2
Reader Guidance ....................................................................................................................................... 2
Related Information .................................................................................................................................. 3
Acronyms .................................................................................................................................................. 3
Document History ..................................................................................................................................... 3
Terminology ............................................................................................................................................. 4

2 Test Tool Environment Description............................................................................ 5

Card simulator........................................................................................................................................... 5
DEK-DET xml files .................................................................................................................................. 5

3 Requirements for Product Test Environment ............................................................ 6

Whats new? ............................................................................................................................................. 6
Test Environment architecture for an intelligent reader ........................................................................... 7
Test Environment architecture for an Integrated Terminal ....................................................................... 9
Requirements for the PayPass Product................................................................................................... 11
Requirements for the Test Environment Interface .................................................................................. 13
Requirements for the transaction related data ......................................................................................... 14
Requirements for the configuration data sets.......................................................................................... 15

4 Requirements for Product Test Environment (Data Exchange) ............................. 18

Test Environment architecture ................................................................................................................ 18
Requirements for the PayPass Product................................................................................................... 21
Requirements for the Test Environment Interface .................................................................................. 22

5 Annex A: Configuration and Transaction related data sets ................................... 24

Default Transaction related data ............................................................................................................. 24
Default Transaction related data values (Mag-Stripe) ........................................................................ 24
Default Transaction related data values (EMV) ................................................................................. 24
Default Configuration data sets .............................................................................................................. 26
Default Configuration Data values (Mag-Stripe)................................................................................ 26
Default Configuration Data values (EMV) ......................................................................................... 27
Configuration data sets ........................................................................................................................... 30
Configuration data set definitions (Mag-Stripe) ................................................................................. 30
2013 MasterCard

PayPass Testing Environment November 2013

Table of Contents

Configuration data set definitions (EMV) ........................................................................................... 35

Configuration data set definitions (Mag-Stripe Data Exchange) ........................................................ 42
Configuration data set definitions (EMV Data Exchange) ................................................................. 43

6 Annex B: CA Public Keys ...........................................................................................48

CA Public keys related to the RID A0 00 00 00 04 ............................................................................. 48
CA Public keys related to the RID B0 12 34 56 78 .............................................................................. 52

7 Annex C: Data Exchange XMLs definition ...............................................................54

XML graphic view .................................................................................................................................. 54
XML attribute definition ......................................................................................................................... 55
XML example ......................................................................................................................................... 56
Document Type Definition ..................................................................................................................... 58

2013 MasterCard

PayPass Testing Environment November 2013

Introduction

1 Introduction
This chapter provides an introduction to the PayPass Testing Environment for
readers implementing [PayPassV3].

Purpose
MasterCard requires that PayPass Products implementing [PayPassV3] and
submitted for PayPass Type Approval Level 2 (PayPass TTA L2) are to be tested
against the relevant specification.
To test the compliance of the PayPass Product implementation to [PayPassV3], the
PayPass Product has to be tested in a determined PayPass Testing Environment, as
described below and further detailed in this document.
Figure 1-1: Schematic View of the PayPass Testing Environment

Configuration
data sets

Test
Environment
Interface

DEK-DET
xml files

Transaction
related
data

PayPass Product

Product Test Environment

Card simulator

Test Tool Environment

The PayPass Testing Environment is composed of two parts:

The Test Tool Environment is qualified by MasterCard. It allows the control and
the observation of the interface between the PayPass Product and the card
simulator. The Test Tool Environment also includes DEK-DET xml files in order
to test PayPass Products that support Data Exchange.

The Product Test Environment is composed itself of four sub-parts:

The Test Environment Interface allows the configuration of the PayPass

Product data and parameters and the observation of the PayPass transaction
data output. When the PayPass Product supports Data Exchange, the Test
Environment Interface acts as a Terminal application simulator receiving the
DEKs and returning DETs as defined in the DEK-DET xml files.
The Test Environment Interface must be provided by the vendor at the same
time as the PayPass Product samples.

2013 MasterCard

PayPass Testing Environment November 2013

Introduction

The library of configuration data sets (e.g.: AIDs, Terminal Action Codes)
as defined in the current document.

The transaction related data objects (e.g.: amount, transaction currency) as

defined in the current document.

The PayPass product itself embedding the PayPass application to be tested.

The PayPass product could be an Intelligent reader or an Integrated terminal.

The purpose of this document is to describe the requirements of the PayPass Testing
Environment. This document is structured as follows:

Chapter 2: Laboratory Test Tool Description

Chapter 3: Requirements for Product Test Environment

Chapter 4: Requirements for Product Test Environment (Data Exchange)

Audience
This document is intended for use by Vendors, that is, by manufacturers and
suppliers of PayPass Products.
This document is aimed at the Program Manager or Project Manager responsible for
the delivery of their PayPass Products through the PayPass Vendor Product
Approval Process.

Reader Guidance
This document describes the PayPass Testing Environment for PayPass Products
supporting all types of PayPass applications.
Information specific to Products not supporting the EMV implementation option is
indicated with the following symbol in the margin:
Mag Stripe

If the vendor submits a PayPass Product not supporting the EMV implementation
option, he can skip the information specific to Products supporting this option. Such
information is indicated with the following symbol in the margin:
M/Chip

2013 MasterCard

PayPass Testing Environment November 2013

Introduction

Related Information
The following reference materials may be of use to the reader of this document.
NOTE:
MasterCard reserves the right to release updates to these documents and any
documents it references. Vendors must therefore check for the latest documentation
versions and the impact of any amendments they contain before starting the
vendor testing process.

EMV Contactless Protocol

EMV Contactless Communication Protocol Specification 2.0.x (where x can be any

value.)
PayPassV3

PayPass M/Chip Reader Card Application Interface Specification V3.x

Mag Stripe

M/Chip

The EMV implementation option is not implemented.

The EMV implementation option is implemented.

Acronyms
The following acronyms are used in this document:
Acronym

Description

EMV

Europay MasterCard Visa

TTA L1

Terminal Type Approval Level 1

TTA L2

Terminal Type Approval Level 2

Document History
The following lists the main changes:
Version

Changes

16 May 2012

Initial version

05 December 2012

- moved requirement B'6 to A'3

- clarified the section 'Default Transaction related data
values (Mag-Stripe)' so it applies only to products NOT
supporting EMV
- sorted the configuration data sets in alphabetical order
- PPS_NoDefault_2 and PPS_NoDefault_3: removed the
sentence " The TLV database must NOT contain the
Interface Device Serial Number data object ('9F1E')."
- PPS_MC_prop2: AFL must be present with any value
- removed 'PPS_MS_MonoAppli' as not used.

2013 MasterCard

PayPass Testing Environment November 2013

Introduction

Version

Changes

26 February 2013

- Tag '5F53' added in the configuration PPMC_DE4

- PPS_MCnoMSI was modified

November 2013

- Configuration 'PPS_MC_prop3' added

Terminology
This section explains the terms used in this specification.
Contactless Card Reader Product integrating a PCD, to be connected to a
Terminal, to allow the Terminal to perform the financial transaction. A Contactless
Card Reader may also include other components such as PED, PayPass Application,
contact interface module, printer.
(Fully) Integrated Terminal A PayPass Product integrating a PCD and the
PayPass Application and which can process a Payment transaction without needing
to be connected to a Contactless Card Reader. It may also include other components
and interfaces such as PIN Entry Devices (PED), printer or host communications.
Intelligent (Contactless Card) Reader A Contactless Card Reader which also
integrates a PayPass Application.
Operational Terminal Any terminal hardware/software not part of the submitted
product that enables terminal functionality, i.e. hardware into which a submitted
product must be integrated to form a payment/service providing system e.g. vending
machine.
PayPass Application The software module or kernel residing on a PayPass
Product and which implements the [PayPassV3].
PayPass Product A product or combination of products incorporating at least a
PCD or a PayPass Application. Only PayPass Products integrating a PCD and a
PayPass Application and a PED, if available on that PayPass Product, will be
approved by MasterCard.
PayPass Product Component Component whose assessment is relevant for
PayPass Product Approval. There are three PayPass Product Components: the PCD,
the PayPass Application and the PIN Entry Device (if any).
PayPass Terminal A Fully Integrated Terminal or the combination of a
Contactless Card Reader and a terminal covering the PayPass Application.
Proximity Coupling Device (PCD) A product component constituted of a
combination of hardware and software and which implements [EMV Contactless
Protocol]. The PCD uses inductive coupling to provide power to the PICC and also
controls the data exchange with the PICC, up to and including the transport layer.
Sample A PayPass Product picked out of production for testing.
Transparent Contactless Card Reader A Contactless Card Reader that does not
integrate the PayPass Application.

2013 MasterCard

PayPass Testing Environment November 2013

Test Tool Environment Description

2 Test Tool Environment Description

This section details the elements included in the Test Tool Environment:
-

the card simulator and

the DEK-DET xml files (when PayPass Product supports Data Exchange)

Card simulator
Card simulator

The card probe test application simulates different card profiles to check whether the
submitted PayPass Product supports all the mandatory features of the [PayPassV3].
TTA L2, as performed by a Test Laboratory, includes confidence tests with PayPass
TIP cards. This enhances interoperability and increases the confidence that the
PayPass Product will function correctly during integration and network testing.
The list of the tool vendors selling the MasterCard TIP test cards for TTA L2 testing
can be obtained by contacting [email protected].

DEK-DET xml files

DEK-DET
xml files

The DEK-DET xml files only apply when the PayPass Product supports the Data
Exchange implementation option. They are provided by MasterCard. More details
about the xml format are provided further in the document.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

3 Requirements for Product Test

Environment
This chapter details the requirements the Product Test Environment must meet when
a Product is submitted for PayPass Type Approval Level 2.
This chapter does not deal with Data Exchange. The Product Test Environment
additional requirements specific to Data Exchange are detailed in the next chapter
"Requirements for Product Test Environment (Data Exchange)".

Whats new?
The previous TTA Level 2 test suites included many implementation options like
Online capable or Integrated Terminal. Those options were listed in the
Implementation Conformance Statement the vendor had to fill-in before entering the
TTA Level 2 test process. The PayPass Product was approved for a determined
configuration, for example Online Capable and Integrated Terminal.
The current [PayPassV3] explicitly states that only 2 implementation options exist:
EMV and Data Exchange. The PayPass product under test must therefore
support all features defined in the specification with the only exception of the 2
implementation options.
In other words, all PayPass Products must support for example - online capable and
offline-only transactions. Similarly Integrated Terminal is no longer an option so
the Integrated Terminals must be tested in a manner similar to intelligent readers.
This may be a problem when for example the test requires the transaction amount to
not be passed to the Product. Some Integrated Terminals may not allow a transaction
to start unless the amount has been entered.
The below sections describe one way to implement the Product Test Environment
requirements depending on whether the Product is an intelligent reader or an
integrated terminal.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Test Environment architecture for an intelligent reader

When deployed, the set-up of an intelligent reader is described below.
Figure 3-1: Intelligent reader set-up

Terminal

PayPass Product
(intelligent reader)

Card

During the TTA Level 2 tests, the Terminal and Card are replaced respectively by the
Test Environment Interface and the Card Simulator as shown on the figure below.
Figure 3-2: PayPass Testing Environment for an intelligent reader

Configuration
data sets

Test
Environment
Interface

Transaction
related
data

PayPass Product

Product Test Environment

Card simulator

Test Tool Environment

Before running the tests, the Product must be set-up with the appropriate
configuration data set. The next figure shows how this is done.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Figure 3-3: loading the configuration data set in the intelligent reader

Configuration
data sets

Test
Environment
Interface

Test conf
#1

PayPass Product

Product Test Environment

Once the PayPass Product is configured, the transaction can be launched. This may
be done through an Activation command embedding the transaction related data
objects.
The transaction output data are then returned to the Test Environment Interface.
Figure 3-4: launching the transaction

Test
Environment
Interface

Transaction related
data (Amount,
Currency, Date, )

Output data

Test conf
#1

PayPass
Product

Test conf
#1

PayPass
Product

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Test Environment architecture for an Integrated Terminal

The set-up of an Integrated Terminal is described below.
Figure 3-5: Integrated Terminal set-up

PayPass Product
(integrated reader)

Terminal

Card

Intelligent
reader

The terminal logic talks to the intelligent reader portion and will only send the
instructions that are relevant for the specific usage of the integrated terminal.
As an example: if the integrated terminal is only used as portable POS, it will not
start a transaction before the amount has been entered. This type of decision logic and
I/O control is implemented in the terminal logic.
In order to have access to (test) the full functionality of the kernel, the terminal logic
must be bypassed. The extent to which it can be bypassed impacts the Test
Environment.
Depending on the integrated terminal architecture, the Product may not accept the
transaction to be launched through an Activation command embedding the
transaction related data objects. If so, it is still possible to load the transaction related
data objects (including or not the amount, currency) during a parameter setting
phase, before doing the transaction. This is illustrated in the figure below.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Figure 3-6: loading the parameters in an integrated terminal

Configuration
data sets

Test
Environment
Interface

Test conf
#1

Transaction related data

(amount, currency, )

PayPass Product

Product Test Environment

Once the configuration data set and the transaction related data (including or not the
amount, currency) are loaded in the PayPass product, the test operator can launch
the transaction. At the end of the transaction, the outcome data are passed to the Test
Environment Interface for verification.
Figure 3-7: launching the transaction

Test conf
#1

PayPass
Product

Test
Environment
Interface

Transaction
related
data

Output data

Test conf
#1

PayPass
Product

Transaction
related
data

Card simulator

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Requirements for the PayPass Product

PayPass Product

The PayPass Product must comply with the [PayPassV3]. All features must be
implemented apart from the implementation options defined in the specifications that
are by definition optional.
The PayPass Product must also meet the following requirements.
A1.

Data Record &

Discretionary
Data

The PayPass Product must comply with the requirements defined in [PayPassV3]
section Lists of Data Objects in OUT. That is, the reader must return the Data
Record and the Discretionary Data.
Note that the Discretionary Data includes the Error Indication data object.

A2.

Outcome
Parameter Set

The [PayPassV3] section 2.2.1 Simple Payment Transaction lists the relevant
information from the Outcome Parameter Set to be passed to the Terminal in the
transaction output data.
For testing needs, the PayPass product must provide all Outcome Parameter Set
information to the Test Environment Interface, that is:

A3.

MSG signal

Status

Start

Online Response Data

CVM

UI Request on Outcome Present

UI Request on Restart Present

Data Record Present

Discretionary Data Present

Receipt

Alternate Interface Preference

Field Off Request

Removal Timeout

The PayPass Product must permit to observe the MSG signal output as returned
by the kernel.
Note that in some cases the kernel will return several MSG signals in the same
transaction (see diagram flow S14, card read OK then clear display). In such a
case all MSG signals must be provided in a chronological order.

A4.

Phone message
Table

For all AIDs, the reader must support the Phone Message Table defined in
[PayPassV3] section Phone Message Table.

A5.

Error Indication

As described in the requirement A1 above, the Error Indication data object must
be returned in the Discretionary Data.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

A6.

A7.

Select Next

Default
Transaction
Type

The PayPass Product must also permit to observe the Outcome Parameter Set and
the Error Indication as provided by the kernel to the Application Selection module
when the kernel detects an issue leading to a Select Next outcome. Please see the
example below.

MasterCard AID is selected

the kernel detects an issue leading to a Select Next outcome

the PayPass Product must return the Outcome Parameter Set and the
Error Indication data

Select Next: Maestro AID is selected

the kernel completes the transaction successfully

In some circumstances, the Transaction Type may not be provided to the reader.
When this occurs the reader must use a configurable default Transaction Type
value.
During the tests, the default Transaction Type value shall be 09 (Purchase with
Cashback).

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Requirements for the Test Environment Interface

Test
Environment
Interface

Ideally, the Test Environment Interface is integrated in a single environment, running

on a PC (Personal Computer).
The Test Environment Interface must also meet the following requirements.
B1.

Configuration
data setting

The Test Environment Interface must permit to load the Configuration data sets
define further in Annex A: Configuration and Transaction related data sets.
The vendor must provide the related data sets to the laboratory.

B2.

Transaction
related data
setting

The Test Environment Interface must permit to easily configure the transaction
related data objects (Amount, Transaction Currency) as defined in Annex A:
Configuration and Transaction related data sets.

B3.

Transaction data
outputs

The Test Environment Interface must provide access to the transaction data
outputs:

B4.

Symbolic values

Data record

Discretionary data

Outcome Parameter Set

Error Indication (see also requirement A1 above)

MSG signal (see also requirement A2 above)

The Test Environment must display the symbolic values (e.g. "CAM FAILED")
instead of the hexadecimal values (e.g.: '02') for the below transaction data
outputs:

Outcome Parameter Set

Error Indication

MSG signal (i.e.: User Interface Request Data)

The displayed symbolic values must be the ones given in [PayPassV3] section
'Data Dictionary'.

This will allow the test operator to easily verify test pass criteria like:
In Outcome Parameter Set, Status must indicate Online Request.
B5.

ASCII /
hexadecimal

When displayed, Track 1 must appear in ASCII notation. Other data elements
must appear in hexadecimal notation.

B6.

Cut & paste

Means must be provided so that the Transaction data output can be cut & paste
into a document (e.g. using CTRL C on screen capture).

B7.

Autorun

The Testing Environment must permit configuration of the Autorun parameter. By

default, the value must be No.

B8.

STOP/ABORT

The Test Environment must permit to send a STOP or an ABORT signal to the
reader during a transaction (when, for example, the card does not respond to a
CAPDU but endlessly returns S(WTX) blocks). The Test Environment must also
permit observation of the STOP_ACK signal returned by the reader.
If the Product is an Integrated terminal, the STOP or ABORT signal may be
triggered by pressing a key on the terminal itself.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Requirements for the transaction related data

Transaction
related
data

The Test Environment must permit to configure the transaction-related data objects.

C1.

Transaction
related data
objects

The test environment must permit the sending of the transaction related data
objects as defined in the [PayPassV3], that is:

Amount, Authorized (Numeric)

Amount, Other (Numeric)

Balance Read Before Gen AC

Balance Read After Gen AC

Merchant Custom Data

Transaction Currency Code

Transaction Currency Exponent

Transaction Date

Transaction Time

Transaction Type

Data Exchange data objects, when supported

C2.

Updating the
data objects

The Test Environment must permit to easily edit the list and value of the
transaction related data objects.

C3.

Zero length

The test environment must permit to send transaction related data objects without
any value (i.e.: zero length)

C4.

Additional
objects

The test environment must also permit to send additional data objects not listed
above.

C5.

Transaction
related data
values

The section Annex A: Configuration and Transaction related data sets defines
the default transaction related data values.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Requirements for the configuration data sets

Configuration
data sets

The kernel database must be configurable with any of the permitted data items
specified in [PayPassV3]. The Test Environment must be able to store these data
objects so they can be easily re-used from one transaction to another.
This section defines the testing configuration requirements the submitted PayPass
Product must meet when testing the PayPass Application.
The requirements are split into 2 categories:
-

requirements common to PayPass Mag-Stripe and PayPass M/Chip products

requirements for PayPass M/Chip products

The following Product Test Environment requirements are common to PayPass

Mag-Stripe and PayPass M/Chip products.
D1.

List of AIDs

Unless otherwise specified in section Annex A: Configuration and Transaction

related data sets, the submitted PayPass Product must contain the list of AIDs
listed in Table 3-1: Supported AIDs.

D2.

Kernel ID

For all AIDs, the Kernel ID must indicate Kernel 2 unless otherwise specified in
the configuration data sets.

D3.

Transaction
Type

The following Transaction Types must be supported for all AIDs:

Payment (00)

Cash (01)

Purchase with Cashback (09)

Refund (20)

Table 3-1: Supported AIDs

Transaction Types: Payment, Cash, Cashback, Refund
MasterCard AID

Maestro AID

Test AID

A0000000041010

A0000000043060

B012345678

Kernel 2

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

D4.

Zero length

The Test Environment must permit to send a configuration data object without any
value (i.e.: zero length)

D5.

Additional
objects

The Test Environment must also permit to send additional configuration data
objects not listed in the specifications

D6.

Configuration
data set values

The section Annex A: Configuration and Transaction related data sets defines
the Configuration data sets. They must be provided to the lab.

M/Chip

D7.

D8.

The following Product Test Environment requirements apply to PayPassM/Chip

Products only.

Configuration
options

Certificate
Revocation list

Unless otherwise specified in the Annex A: Configuration and Transaction

related data sets section, here is how the configuration options must be set:

EMV mode only: see Kernel Configuration data element in table 3-5

Mag-Stripe mode only: see Kernel Configuration data element in table

3-5

Balance reading and display: activated

Torn transaction recovery: activated

IDS: as defined in the Annex A: Configuration and Transaction

related data sets section.

The Certificate Revocation List must include the data defined in Table 3-2:
Certificate Revocation List data.
The Product Test Environment must permit to add and remove an item from the
Certificate Revocation list.

D9.

CA Public Keys

The CA Public Keys related data elements are defined in section Annex B: CA
Public Keys.

The following requirements concern functionalities that are not specified in

[PayPassV3].
As stated in [PayPassV3] section 6 Kernel State Diagrams, they can be considered
optional for the implementation.
D10.

Exception file

If supported by the submitted PayPass Product, the exception file must include the
following data:
PAN: 54 13 33 90 00 00 15 96
PAN sequence number: 00

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment

Table 3-2: Certificate Revocation List data

RID: A0 00 00 00 04

RID: B0 12 34 56 78

CA PK Index: F8

Certificate Serial Number:

00 00 10

00 00 11

00 01 01

00 01 10

00 01 11

00 10 00

00 10 01

00 10 10

00 10 11

00 11 00

00 11 01

00 11 10

00 11 11

01 00 00

01 00 01

01 00 10

01 00 11

01 01 00

01 01 01

01 01 11

01 10 00

01 10 01

01 10 10

01 10 11

01 11 00

01 11 01

01 11 10

01 11 11

10 00 00

10 00 01

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment (Data Exchange)

4 Requirements for Product Test

Environment (Data Exchange)
This chapter details the Product Test Environment requirements specific to Data
Exchange. When a PayPass Product supports Data Exchange, it must fulfill the
below requirements as well as those defined in the previous chapter "Requirements
for Product Test Environment".

Test Environment architecture

This section does not distinguish between the Test Environment architecture for
intelligent readers and integrated terminals. This section will consider the PayPass
Product separate from the Terminal as shown in the below figure. For further details
about Test Environment architecture for an integrated terminal please see the
previous chapter "Requirements for Product Test Environment".
Figure 4-1: Test environment architecture

Terminal

DEKs
DETs

PayPass Product

Card

During the TTA Level 2 tests, the Terminal and Card are replaced respectively by the
Test Environment Interface and the Card Simulator as shown on "Figure 4-2:
PayPass Testing Environment (Data Exchange supported)".
Figure 4-2: PayPass Testing Environment (Data Exchange supported)

Configuration
data sets

Test
Environment
Interface

DEK-DET
xml files

Transaction
related
data

PayPass Product

Product Test Environment

Card simulator

Test Tool Environment

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment (Data Exchange)

In addition to the features already detailed in the previous chapter "Requirements for
Product Test Environment", the Test Environment Interface simulates a live Terminal
application using the information provided by the PayPass Product through the DEK
signals to update the PayPass Product data via DET signals.
This Terminal application simulator may run in the Test Environment Interface or in
the Product itself. This document will assume that it runs in the Test Environment
Interface.
The Terminal application simulator (Test Environment Interface) uses as input the
DEK-DET xml file provided by MasterCard. These files, usually one per test case,
provide the list of DET signals to be returned for every DEK signal expected during
the Data Exchange test. The DEK-DET xml file format is defined further in "Annex
C: Data Exchange XMLs definition".
Before running the tests, the Product must therefore be set-up with the appropriate
configuration data set and DEK-DET xml file, as shown in the figure below.
Figure 4-3: loading test data

Test
Environment
Interface

Configuration
data sets

DEK-DET
xml file
#1
DEK-DET
xml files

Test conf
#1

PayPass Product

Product Test Environment

2013 MasterCard

PayPass Testing Environment November 2013

Test Tool Environment

Requirements for Product Test Environment (Data Exchange)

Once the PayPass Product is configured, the transaction can be started. The
Transaction Related Data are passed to the kernel. The kernel may request data from
the Test Environment Interface by sending DEKs signals. The Test Environment
Interface will return the requested data in DETs signals. The transaction output data
are then returned to the Test Environment Interface.
Figure 4-4: Data Exchange transaction

DEK-DET
xml file Test
#1
Environment

Interface

Transaction
related data
(Amount,
Currency, )

DEKs

Test conf
#1

DETs

Output
data

PayPass
Product

Card simulator

Product Test Environment

Test Tool Environment

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment (Data Exchange)

Requirements for the PayPass Product

PayPass Product

The PayPass Product supporting Data Exchange must meet the following
requirements.

A'1.

Transaction log

The Product must generate a transaction log including:

CAPDUs

RAPDUs

DEKs

DETs

The transaction log must list the APDU/DEK/DET signals in the order they have
been treated by the PayPass Product. Especially the log must show when a DEK
was sent.
A'2.

Unexpected
DEK

The transaction log must include a message like "Unexpected DEK" when the
DEK sent was not expected, i.e.: the DEK is not listed in the DEK-DET xml file.

A'3.

Tag Order

In order to correctly match the DEK value, some ordering requirements are
needed. They are listed below.
When filling the DEK, the PayPass product must:
1) Follow the specification order (e.g.: CDOL missing data (S4.ED29 in
[PayPassV3]) are requested in Data Needed before the DSDOL missing data
(S4.ED33).
2) Follow the Tags To Read Yet order. When several data items identified in Tags
To Read Yet are available they must be put in the Data To Send list in the order
they appear in the Tags To Read Yet list.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment (Data Exchange)

Requirements for the Test Environment Interface

Test
Environment
Interface

Ideally, the Test Environment Interface is integrated in a single environment, running

on a PC (Personal Computer).
When the PayPass Product supports Data Exchange, the Test Environment Interface
must also meet the following requirements.

B'1.

XML format

The Test Environment Interface must be capable of interpreting the DEK-DET

xml files. Further details about the XML format are given in "Annex C: Data
Exchange XMLs definition".
The PayPass Product provider is free to perform any type of conversion to
accommodate the xml files provided to its implementation choice (e.g.: different
tags) but he must keep in mind that the xml files may change quite often and
should automate these conversions.

B'2.

First DEK
match basis

When the Test Environment Interface receives a DEK signal from the PayPass
Product it must read the related DEK-DET xml file from the beginning until the
same DEK is found. The DET(s) associated to this DEK is (are) then returned to
the PayPass Product.

B'3.

Unpredictable
Number '9F7F'
and '9F37'

The value of the Unpredictable Number actually used during a test is by nature not
known at the DEK-DET xml file generation. Routines developed by the PayPass
Product supplier to parse and use the DEK-DET xml files shall therefore ignore
the Unpredictable Number value provided in the files and keep as only applicable
criteria the presence and the length of the data element.

B'4.

DEK identifier
'5F53'

Some DEKs defined in the xml files will include a tag '5F53' coded on 1 byte in
the Data To Send list. This tag is a key used to differentiate the DEKs in the xml
file.

B'5.

Unexpected
DEK

When the PayPass Product sends a DEK that is not listed in the DEK-DET xml
file, the Test Environment Interface must inform the PayPass Product that an
"Unexpected DEK was received" (See also requirement A'2).

B'6.

Several DETs

The DEK-DET xml file could include several DETs for the same DEK meaning
that the Test Environment Interface shall return several DETs upon reception of
the related DEK.
The Test Environment Interface shall return all the DET signals in the same order
as in the DEK-DET xml file.

B'7.

No DET

When the DEK-DET xml file includes an empty DET, the Test Environment
Interface shall not return any DET upon reception of the related DEK.

B'8.

Transaction log
file

The transaction log (see also requirement A'1) must be made available at the end
of each test, be easily readable by the test operator and allow a simple Copy in
text format (Ctrl + C).
The Test Environment Interface must allow saving the transaction log.

2013 MasterCard

PayPass Testing Environment November 2013

Requirements for Product Test Environment (Data Exchange)

B'9.

Transaction log
tags

The DEK-DET tags recorded in the transaction log must be the tags defined in
[PayPassV3] (e.g.: 'FF8104') even if the PayPass Product implementation uses
proprietary tags.

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

5 Annex A: Configuration and

Transaction related data sets
This annex defines the data sets required during the tests. It is split into 3 subsections:
-

Default Transaction related data (e.g.: amount is by default 15.00)

Default Configuration data sets (e.g.: TACs are by default set to all zeroes)

Configuration data sets: the list of Mag-Stripe and EMV data sets.

Note: this section uses the "Services" 'IsEmpty', 'IsPresent' and 'IsKnown' defined in
[PayPassV3].

Default Transaction related data

This section lists the transaction related data commonly used in the Level2 tests.
Additional requirements are available in the section Requirements for the
transaction related data.

Default Transaction related data values (Mag-Stripe)

The table below defines the default transaction related data values for the PayPass
Products not supporting the EMV implementation option.
Table 3: Default transaction related data values Mag-Stripe
Data Object Name

Value

Amount Authorized (Numeric)

000000 001500 (15.00)

Default Transaction related data values (EMV)

The table below defines the default transaction related data values for the PayPass
Products supporting the EMV implementation option.
Table 4: Default transaction related data values EMV

Data Object Name

Value

Amount Authorized (Numeric)

000000 001500 (15.00)

Amount Other (Numeric)

All zeroes

Balance Read Before Gen AC

Tag not present

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Balance Read After Gen AC

Tag not present

Merchant Custom Data

Any value different from zero

Transaction Category Code

Any value different from zero in line with the Merchant

Category Code

Transaction Currency Code

0978 (euro)

Transaction Currency Exponent 2

Transaction Date

Current (if fixed, must be later than December 2010)

Transaction Time

Current (may be fixed)

Transaction Type

00 (goods and services)

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Default Configuration data sets

Default Configuration Data values (Mag-Stripe)
The below table defines the default Configuration data set for Mag-Stripe
transactions. This corresponds to the data set "PPS_MStripe1" defined further.
The Terminal Country Code is a terminal-dependent data item so it should have the
same value (defined below) for all AIDs and all Transaction Types.
Unless otherwise specified, all other data item values must be the same for all AIDs
and for the following Transaction Types:
-

Payment (00)

Cash (01)

Purchase with Cashback (09)

Refund (20).

Table 5: Default Configuration Data set Mag-Stripe

Data Object Name

Test value

Default UDOL

9F6A04

Hold Time Value

Tag not present

Kernel Configuration

If the product does not support EMV:

MasterCard AID:

Maestro AID:

Test AID:

If the Product supports EMV:

Kernel ID

MasterCard AID:

Maestro AID:

Test AID:

Mag-Stripe Application Version 0001

Number

Mag-Stripe CVM Capability

CVM Required

10 (Signature)

Mag-Stripe CVM Capability

No CVM Required

00 (noCVM)

Message Hold Time

Tag not present

Mobile Support Indicator

No value (i.e.: IsEmpty(T)=True)

Reader CTL (No On-device

CVM)

300.00

Reader CTL (On-device CVM)

500.00

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Reader CVM Required Limit

Transaction Type= 00 (payment):

MasterCard AID:

10.00

Maestro AID:

300.00

Test AID:

10.00

Other Transaction Types:

MasterCard AID:

200.00

Maestro AID:

300.00

Test AID:

100.00

Terminal Country Code

0056 (terminal-dependent data item)

Terminal Identification

No value (i.e.: IsEmpty(T)=True)

--- The details below only apply to products supporting Data Exchange --Proceed To First Write Flag

Tag not present

Tags To Read

Tag not present

Time Out Value

Tag not present

Default Configuration Data values (EMV)

The below table defines the EMV default Configuration data set. It is only applicable
when the product supports the EMV implementation option. This corresponds to the
data set "PPS_MChip1" defined further.
The Interface Device Serial Number and the Terminal Country Code are terminaldependent data items so they should have the same value for all AIDs and all
Transaction Types.
Unless otherwise specified, all other data item values must be the same for all AIDs
and for the following Transaction Types:
-

Payment (00)

Cash (01)

Purchase with Cashback (09)

Refund (20).

Table 6: Default Configuration Data set EMV supported

Data Object Name

Test value

Account Type

No value (i.e.: IsEmpty(T)=True)

Acquirer Identifier

No value (i.e.: IsEmpty(T)=True)

Additional Terminal Capabilities 0000000000'

Application Version Number

0002

Balance Read Before Gen AC

Tag not present

Balance Read After Gen AC

Tag not present

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Card Data Input Capability

CVM Capability CVM

Required

60 (Signature and OnlinePIN)

CVM Capability No CVM

Required

08 (noCVM)

Default UDOL

9F6A04

Hold Time Value

Tag not present

Interface Device Serial Number Any value (terminal-dependent data item)

Kernel Configuration

Kernel ID

MasterCard AID:

Maestro AID:

A0 (EMV only)

Test AID:

Mag-Stripe Application Version 0001

Number
Mag-Stripe CVM Capability
CVM Required

10 (Signature)

Mag-Stripe CVM Capability

No CVM Required

00 (noCVM)

Max Lifetime of Torn

Transaction Log Record

0000

Max Number of Torn

Transaction Log Records

Merchant Category Code

Any value different from zero

Merchant Identifier

No value (i.e.: IsEmpty(T)=True)

Merchant Name and location

No value (i.e.: IsEmpty(T)=True)

Message Hold Time

Tag not present

Mobile Support Indicator

No value (i.e.: IsEmpty(T)=True)

Reader Contactless Floor Limit 100.00

Reader CTL (No On-device
CVM)

300.00

Reader CTL (On-device CVM)

500.00

Reader CVM Required Limit

Transaction Type= 00 (payment):

- MasterCard AID: 10.00
- Maestro AID:

300.00

- Test AID:

10.00

Other Transaction Types:

- MasterCard AID: 200.00

Security Capability

- Maestro AID:

300.00

- Test AID:

100.00

08 (CDA)

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Terminal Action Codes

All zeroes

Terminal Capabilities

No value (i.e.: IsEmpty(T)=True)

Terminal Country Code

0056 (terminal-dependent data item)

Terminal Identification

No value (i.e.: IsEmpty(T)=True)

Terminal Type

When Transaction Type = 01 (Cash),

Terminal Type must be 14 (Unattended,
online-only) for all AIDs.
For the following Transaction Types,
Terminal Type must be 22 (attended,
online capable) for all AIDs
- 00 (Payment)
- 09 (Purchase with Cashback)
- 20 (Refund)

--- The details below only apply to products supporting Data Exchange --DS AC Type

No value (i.e.: IsEmpty(T)=True)

DS Input (Card)

No value (i.e.: IsEmpty(T)=True)

DS Input (Term)

No value (i.e.: IsEmpty(T)=True)

DS ODS Info

No value (i.e.: IsEmpty(T)=True)

DS ODS Info For Reader

No value (i.e.: IsEmpty(T)=True)

DS ODS Term

No value (i.e.: IsEmpty(T)=True)

DS Requested Operator ID

Tag not present

DSVN Term

No value (i.e.: IsEmpty(T)=True)

Proceed To First Write Flag

Tag not present

Tags To Read

Tag not present

Tags To Write After Gen AC

Tag not present

Tags To Write Before Gen AC

Tag not present

Time Out Value

Tag not present

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Configuration data sets

This section lists the Configuration data sets used in the Level2 tests. A simple means
to set them must be provided.
Additional requirements are available in the section Requirements for the
configuration data sets.
The configuration data sets are split into 2 categories:
-

Testing Configurations for all products

Testing Configurations for products supporting the EMV implementation option

Configuration data set definitions (Mag-Stripe)

The following Device Testing Environment requirements apply to all PayPass
products.
Unless otherwise specified, the values defined in the below configuration data sets
apply to all AIDs and any Transaction Type.
Configuration Data
set ID

Description

PPS_MStripe1

The submitted PayPass Product follows the configuration

requirement listed in 'Table 5: Default Configuration Data set
Mag-Stripe'.
If the reader supports EMV, all other data items not listed in
'Table 5: Default Configuration Data set Mag-Stripe' must be
absent (i.e.: IsPresent(T)=false).

PPS_MS_Limit_1

Same as PPS_MStripe1 except for:

1. MasterCard AID:
- Reader CTL (no On-device CVM) = 9000.00
- Reader CTL (On-device CVM) = 6000.00
- Terminal/Reader CVM Required Limit = 51.50
- Terminal/Reader Contactless floor limit = 100.00
2. Maestro AID:
- Reader CTL (no On-device CVM) = 9000.00
- Reader CTL (On-device CVM) = 10.00
- Terminal/Reader CVM Required Limit = 75.00
- Terminal/Reader Contactless floor limit = 200.00
3. Test AID:
- Reader CTL (no On-device CVM) = 9000.00
- Reader CTL (On-device CVM) = 7000.00
- Terminal/Reader CVM Required Limit = 102.50
- Terminal/Reader Contactless floor limit = 150.00

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_MS_Limit_2

Same as PPS_MStripe1 except for:

1. MasterCard AID:
- Reader CTL (no On-device CVM) = 2.00
- Reader CTL (On-device CVM) = 6000.00
- Terminal/Reader CVM Required Limit = 51.50
- Terminal/Reader Contactless floor limit = 100.00
2. Maestro AID:
- Reader CTL (no On-device CVM) = 2.00
- Reader CTL (On-device CVM) = 10.00
- Terminal/Reader CVM Required Limit = 75.00
- Terminal/Reader Contactless floor limit = 200.00
3. Test AID:
- Reader CTL (no On-device CVM) = 2.00
- Reader CTL (On-device CVM) = 7000.00
- Terminal/Reader CVM Required Limit = 102.50
- Terminal/Reader Contactless floor limit = 150.00

PPS_MS_Limit_3

Same as PPS_MStripe1 except for:

1. MasterCard AID:
- Reader CTL (no On-device CVM) = 20.00
- Terminal/Reader CVM Required Limit = 51.50
- Terminal/Reader Contactless floor limit = 100.00
2. Maestro AID:
- Reader CTL (no On-device CVM) = 300.00
- Terminal/Reader CVM Required Limit = 75.00
- Terminal/Reader Contactless floor limit = 200.00
3. Test AID:
- Reader CTL (no On-device CVM) = 400.00
- Terminal/Reader CVM Required Limit = 102.50
- Terminal/Reader Contactless floor limit = 150.00

PPS_MS_Limit_3b

Same as PPS_MS_Limit_3 except for:

MasterCard AID:
Kernel Configuration is 40 (On-device cardholder verification
NOT supported, Mag-Stripe mode only)

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_MS_prop

Same as PPS_MStripe1 except for:

- the proprietary tag 9F05 (EMV tag Application Discretionary
Data) is present in the TLV database with no value (i.e.:
IsKnown=False, IsPresent=True, IsEmpty=True). The update
condition includes RA.
- the proprietary tag 9F17 (EMV tag PIN try counter) is present
in the TLV database with no value (i.e.: IsKnown=False,
IsPresent=True, IsEmpty=True). The update condition includes
RA.
- The proprietary tag 81 (EMV tag Amount Authorized (binary))
is present in the TLV database with any value (i.e.:
IsKnown=False, IsPresent=True, IsEmpty=False). The update
condition does not include RA.
- The kernel data object Terminal Identification (9F1C) is not
present in the TLV database.

PPS_MS_prop2

Same as PPS_MStripe1 except:

- For MasterCard AID: the tag 9F65 (PCVC3track2) is present
in the TLV database with any value.
- For Maestro AID: the tag 94 (AFL) is present in the TLV
database

PPS_MS_prop3

(This configuration does not apply when the Product supports

Data Exchange)
Same as PPS_MStripe1 except:
- the proprietary tag DF62 is present in the TLV database with
no value (i.e.: IsKnown=False, IsPresent=True, IsEmpty=True).
The update condition includes RA.

PPS_NoDefault_1

Same as PPS_MStripe1 except:

For both MasterCard and Maestro AIDs, the TLV database must
not contain the data objects listed in the table Configuration Data
in TLV Database that Require Default Value where
Implementations indicates Always:
- Default UDOL
- Kernel Configuration
- Kernel ID
- Mag-stripe Application Version Number (Reader)
- Mag-stripe CVM Capability CVM Required
- Mag-stripe CVM Capability No CVM Required
- Message Hold Time
- Reader CTL (No On-device CVM)
- Reader CTL (On-device CVM)
- Reader CVM Required Limit
- Terminal Country Code (this one is a terminal-dependent data
object so it will be absent from the TLV database for all AIDs)

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_NoDefault_2

Same as PPS_NoDefault_1 except:

For MasterCard AID, the TLV database must contain the
following data object value:
- Reader CTL (No On-device CVM): 100.00
For Maestro AID, the TLV database must contain the following
data object values:
- Reader CTL (On-device CVM): 100.00
- Reader CVM Required limit: 50.00
- Kernel Configuration is 60 (On-device cardholder verification
supported)

PPS_NoDefault_3

Same as PPS_NoDefault_1 except:

For all AIDs:
- Reader CTL (No On-device CVM): 100.00
- Reader CVM Required limit must be set to50.00
For Maestro AID:
- Kernel Configuration is 40 (only Mag Stripe mode supported)
For MasterCard AID:
- Mag-stripe CVM Capability No CVM Required set to 10
- Kernel Configuration is 40 (only Mag Stripe mode supported)
For Test AID:
- Kernel Configuration is 60 (On-device cardholder verification
supported; only Mag Stripe mode supported)

PPS_perf_MS

Same as PPS_MStripe1 plus, for all AIDs:

- Reader CTL (No On-device CVM): 9000.00
- Reader CTL (On-device CVM): 9000.00
- Reader CVM Required Limit: 9000.00

PPS_Select1

Same as PPS_MStripe1 plus:

The combination data sets are as per the below tables.
The Kernel7 is void. That is, a GET PROCESSING OPTIONS
command will never be sent whenever the Kernel7 is selected.

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Transaction Types: Payment ('00'), Cash ('01')

Kernel 2

MasterCard AID

Maestro AID

Test AID

A0000000041010

A0000000043060

B012345678

Transaction Type: Cashback ('09')

MasterCard AID

Maestro AID

Test AID

A0000000041010

A0000000043060

B012345678

Kernel 2

Kernel 7

Transaction Type: Refund ('20')

Kernel 2

MasterCard AID

Maestro AID

Test AID

A0000000041010

A0000000043060

B012345678

MasterCard AID

Maestro AID

Test AID

A0000000041010

A0000000043060

B012345678

Transaction Type 88

Kernel 2

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Configuration data set definitions (EMV)

M/Chip

The following Device Testing Environment requirements apply to PayPass Products

supporting the EMV implementation option:
Unless otherwise specified, the values defined in the below configuration data sets
apply to all AIDs and any Transaction Type.
Configuration Data
Set ID

Description

PPS_MChip1

The submitted PayPass Product follows the configuration

requirement listed in Table 6: Default Configuration Data set
EMV supported.

PPS_Bal

Same as PPS_MChip1except:
- Balance Read Before Gen AC: no value (i.e.: IsEmpty(T) = True)
- Balance Read After Gen AC: no value (i.e.: IsEmpty(T) = True)

PPS_Bal2

Same as PPS_MChip1except:
- Balance Read Before Gen AC: 111111 222222
- Balance Read After Gen AC: 333333 444444

PPS_CVM_1

Same as PPS_MChip1 except for:

For all AIDs and all Transaction Types:
- Reader CTL (no On-device CVM)=1000.00
- Reader CTL (On-device CVM)=1000.00

MCD
20
20

AID
Mstro
08
08

Test
60
40

Transaction Type=01
(Terminal Type = 14)
CVM Capability CVM Required
CVM Capability no CVM Required

MCD
40
40

AID
Mstro
48
08

Test
60
--

Transaction Type=09
(Terminal Type = 22)
CVM Capability CVM Required
CVM Capability no CVM Required

MCD
60
40

AID
Mstro
48
08

Test
---

Transaction Type=00
(Terminal Type = 22)
CVM Capability CVM Required
CVM Capability no CVM Required

The configuration 'PPS_MChip1' does not include any dataset for

the Transaction Type 12. The dataset shall be the same as for the
Transaction Type 00 except for the CVM as defined below.
AID
Transaction Type=12
(Terminal Type = 22)
MCD Mstro
Test
CVM Capability CVM Required
60
48
-CVM Capability no CVM Required
08
48
40
2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_CVM_2

Same as PPS_MChip1 except:

- Transaction Type=00 and 01 and 09 and 12, AID
MasterCard:
- CVM Capability CVM Required=F8
- CVM Capability no CVM Required=28 (Signature and no
CVM)

PPS_Limit_1

Same as PPS_MChip1 except for:

1. MasterCard AID:
- Reader CTL (no On-device CVM) = 20.00
- Terminal/Reader Contactless floor limit = 100.00
- Terminal/Reader CVM Required Limit = 51.50
2. Maestro AID:
- Reader CTL (no On-device CVM) = 400.00
- Terminal/Reader Contactless floor limit = 200.00
- Terminal/Reader CVM Required Limit = 75.00
3. TEST AID:
- Reader CTL (no On-device CVM) = 600.00
- Terminal/Reader Contactless floor limit = 150.00
- Terminal/Reader CVM Required Limit = 102.50
- Kernel Configuration is 60 (Mag-Stripe only, on-device
cardholder verification supported).

PPS_Limit_1b

Same as PPS_Limit_1 except for:

MasterCard AID:
- Kernel Configuration is 00 (On-device cardholder verification
NOT supported)
Maestro AID:
- Kernel Configuration is 80 (On-device cardholder verification
NOT supported; only EMV mode supported)

PPS_Limit_2

Same as PPS_MChip1 except for:

1. MasterCard AID:
- Reader CTL (no On-device CVM) = 200.00
- Terminal/Reader CVM Required Limit = 100.00
- Terminal/Reader Contactless floor limit = 150.00
2. Maestro AID:
- Reader CTL (no On-device CVM) = 200.00
- Terminal/Reader CVM Required Limit = 120.00
- Terminal/Reader Contactless floor limit = 100.00
3. Test AID:
- Reader CTL (no On-device CVM) = 100.00
- Terminal/Reader CVM Required Limit = 100
- Terminal/Reader Contactless floor limit = 100

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_Limit_3

Same as PPS_MChip1 except for:

PPS_MC_ATM

Same as PPS_MChip1 except:

- For all AIDs: Additional Terminal Capabilities B1 = '80' (Cash)
- For MasterCard AID: Terminal Type is '14'
- For Maestro AID: Terminal Type is '15'
- For Test AID: Terminal Type is '16'

PPS_MC_notATM

Same as PPS_MChip1 except:

- For MasterCard AID: Terminal Type is '11' and Additional
Terminal Capabilities B1 = 'FF'
- For Maestro AID: Terminal Type is '24' and Additional Terminal
Capabilities B1 = 'FF'
- For Test AID: Terminal Type is '14' and Additional Terminal
Capabilities B1 = '7F'

PPS_MC_prop

Same as PPS_Mchip1 except for:

- the proprietary tag 9F05 (EMV tag Application Discretionary
Data) is present in the TLV database with no value (i.e.:
IsKnown=False, IsPresent=True, IsEmpty=True). The update
condition includes RA.
- The proprietary tag 81 (EMV tag Amount Authorized (binary)) is
present in the TLV database with any value (i.e.: IsKnown=False,
IsPresent=True, IsEmpty=False). The update condition does not
include RA
- The kernel data object Acquirer Identifier (9F01) is not present
in the TLV database
- the proprietary tag 9F3B (EMV tag Application Reference
Currency) is present in the TLV database with no value (i.e.:
IsKnown=False, IsPresent=True, IsEmpty=True). The update
condition includes RA.

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_MC_prop2

Same as PPS_Mchip1 except:

- For MasterCard AID: the tag 5F24 (Application Expiration Date)
is present in the TLV database with value 241115.
- For Maestro AID: the tag 94 (AFL) is present in the TLV
database with any value.

PPS_MC_prop3

Same as PPS_Mchip1 except:

- For MasterCard AID and Purchase transaction type: the
proprietary tag 9F1D is present in the TLV database with value
'6CFF0000 00000000'.
- For MasterCard AID and Purchase with cashback transaction type:
the proprietary tag 9F1D is NOT present in the TLV database.
- For Maestro AID: the proprietary tag 9F1D is present in the TLV
database with value '44FF8000 00000000'.

PPS_MCerrKernelConf Same as PPS_Mchip1 except:

- For the Test AID, Kernel configuration indicates Only Magstripe mode and Only EMV mode.
PPS_MChip2

Same as PPS_MChip1 except for:

- TAC online = '7C D8 FC F8 F0' (for All AIDs TAC)
- Terminal Type = Online-only 11 (MasterCard AID)
- Terminal Type = Offline with online capability 12 (Maestro
AID)
- Terminal Type = Offline-only 13 (Test AID).

PPS_MChip3

Same as PPS_MChip1 except for:

- TAC denial = 7C D8 FC F8 F0 (for All AIDs TAC)
- Terminal Type = Online-only 14 (MasterCard AID)
- Terminal Type = Offline with online capability 15 (Maestro
AID)
- Terminal Type = Offline-only 16 (Test AID)

PPS_MChip4

Same as PPS_MChip1 except for:

- TAC online = 00 20 00 00 00 (for All AIDs TAC)
- Terminal Type = Online-only 21 (MasterCard AID)
- Terminal Type = Offline with online capability 22 (Maestro
AID)
- Terminal Type = Offline-only 23 (Test AID).

PPS_MChip5

Same as PPS_MChip1 except for:

- TAC denial = 00 20 00 00 00 (for All AIDs TAC)
- Terminal Type = Online-only 24 (MasterCard AID)
- Terminal Type = Offline with online capability 25 (Maestro
AID)
- Terminal Type = Offline-only 26 (Test AID).

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_MChip6

Same as PPS_MChip1 except for:

- TAC default = 00 40 00 00 00 (for All AIDs TAC)
- Terminal Type = Online-only 34 (MasterCard AID)
- Terminal Type = Offline with online capability 35 (Maestro
AID)
- Terminal Type = Offline-only 36 (Test AID).

PPS_MChip7

Same as PPS_MChip1 except for:

- Terminal Type = Online-only 11 (MasterCard AID)
- Terminal Type = Offline with online capability 12 (Maestro
AID)
- Terminal Type = Offline-only 13 (Test AID).

PPS_MChip8

Same as PPS_MChip1 plus:

- Card Data Input Capability = '20' ("IC with contacts")

PPS_MCnoDefault_1

Same as PPS_Mchip1 except:

For all AIDs and all Transaction Types:
- the TLV database must not contain the data objects listed in the
table Configuration Data in TLV Database that Require Default
Value where Implementations is Always or EMV.
- the TLV database includes the proprietary tag 9F05 (EMV tag
Application Discretionary Data) with value 9876.*
For Maestro AID (and all Transaction Types):
- Kernel Configuration is 20 (On-device cardholder verification
supported)
*: setting the proprietary tag with a value implies that this tag
becomes a kernel tag as per [PayPassV3] Table 5.1 "Access
Conditions". This does not follow EMV where the tag '9F05' is a
card tag but this remains valid in PayPass since this tag is anyway
proprietary/unknown.

PPS_MCnoDefault_2

Same as PPS_MCnoDefault_1 except:

- The TLV database must NOT contain the Interface Device Serial
Number data object ('9F1E').
For all AIDs:
- Reader CTL (No On-device CVM): 100.00
- Reader CTL (On-device CVM): 100.00
For Maestro and Test AIDs:
- Reader CVM Required limit must be set to50.00

PPS_MCnoDefault_3

Same as PPS_MCnoDefault_1 except:

For all AIDs:
- Reader CTL (no On-device CVM): 100.00
- Reader CTL (On-device CVM): 100.00
For Maestro and Test AIDs:
- Reader CVM Required limit must be set to50.00
- Security Capability is set to 08 (CDA supported)

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_MCnoDefault_4

Same as PPS_MCnoDefault_1 except:

For all AIDs:
- Reader CTL (No On-device CVM): 100.00
- Reader CTL (On-device CVM): 100.00
- Terminal Type must be set to23 (Attended, offline-only)
For Maestro and Test AIDs:
- Reader CVM Required limit must be set to50.00
- Security Capability is set to 08 (CDA supported)

PPS_MCnoDefault_5

Same as PPS_MCnoDefault_1 except:

The TLV database must NOT contain the Interface Device Serial
Number data object ('9F1E').
For all AIDs:
- Reader CTL (No On-device CVM): 100.00
- Reader CTL (On-device CVM): 100.00
For Maestro and Test AIDs:
- Reader CVM Required limit must be set to50.00

- Mag-stripe CVM Capability No CVM Required set to 10

PPS_MCnoMSI

Same as PPS_Mchip1 except:

- For Maestro AID: the Mobile Support Indicator data object has the
value 02 in the reader TLV database.
- For MasterCard AID: the Application version Number (reader) has
value '0003'.

PPS_MConlineonly

Same as PPS_Mchip1 except:

- For all AIDs, Terminal Type = 11 (attended online-only)
- For Maestro AID, Security Capability = 00 (no SDA, no CDA)

PPS_perf_MC

Same as PPS_Mchip1 plus, for all AIDs:

- Additional Terminal Capabilities: 60 00 F0 00 01
- Card Data Input Capability: 60
- Reader Contactless Floor Limit: 9000.00
- Reader CTL (No On-device CVM): 9000.00
- Reader CTL (On-device CVM): 9000.00
- Reader CVM Required Limit: 9000.00
- Terminal Action Code Default: 04 00 80 00 00
- Terminal Action Code Denial: DC 50 00 00 00
- Terminal Type: 26

PPS_PostBal

Same as PPS_MChip1except:
- Balance Read Before Gen AC is not present
- Balance Read After Gen AC: no value (i.e.: IsEmpty(T) = True)

PPS_PostBal2

Same as PPS_MChip1except:
- Balance Read Before Gen AC is not present
- Balance Read After Gen AC: 112233 445566

PPS_PreBal

Same as PPS_MChip1except:
- Balance Read Before Gen AC: no value (i.e.: IsEmpty(T) = True)
- Balance Read After Gen AC is not present

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPS_PreBal2

Same as PPS_MChip1except:
- Balance Read Before Gen AC: 000088 776655
- Balance Read After Gen AC: is not present

PPS_TIP_offline

Same as PPS_Mchip1 except for:

- TAC denial: 'FC 50 80 80 00' (for all AIDs)
- TAC online: '00 00 00 00 00' (for all AIDs)
- TAC default: '00 00 00 00 00' (for all AIDs)
- The Product must include the 'FA' CA Public Key defined in "CA
Public keys related to the RID A0 00 00 00 04".

PPS_TIP_online

Same as PPS_Mchip1 except for:

- TAC denial: '00 00 00 00 00' (for all AIDs)
- TAC online: 'FC 50 9C 88 00' (for all AIDs)
- TAC default: 'FC 50 9C 88 00' (for all AIDs)
- The Product must include the 'FA' CA Public Key defined in "CA
Public keys related to the RID A0 00 00 00 04".

PPS_Torn_Bal

Same as PPS_Bal plus:

- Max Lifetime of Torn Transaction Log Record = 0E10
- Max Number of Torn Transaction Log Records = 01

PPS_Torn3min

Same as PPS_MChip1 plus:

- Max Lifetime of Torn Transaction Log Record = 00B4
- Max Number of Torn Transaction Log Records = 02

PPS_Torn5sec

Same as PPS_MChip1 plus:

- Max Lifetime of Torn Transaction Log Record = 0005
- Max Number of Torn Transaction Log Records = 02

PPS_TornMax1

Same as PPS_MChip1 plus:

- Max Lifetime of Torn Transaction Log Record = 0E10
- Max Number of Torn Transaction Log Records = 01

PPS_TornMax1_contact Same as PPS_MChip1 plus:

- Max Lifetime of Torn Transaction Log Record = 0E10
- Max Number of Torn Transaction Log Records = 01
- Card Data Input Capability = '20' (IC with contacts)
PPS_TornMax2

Same as PPS_MChip1 plus:

- Max Lifetime of Torn Transaction Log Record = 0E10
- Max Number of Torn Transaction Log Records = 02

PPS_TrxTypeOther

Same as PPS_MChip1 plus:

- Create a new dataset [Transaction Type=21; AID MasterCard]
and set the same values as for the dataset [Transaction Type=00;
AID MasterCard].
- Create a new dataset [Transaction Type=12; AID Maestro] and
set the same values as for the dataset [Transaction Type=00; AID
Maestro] plus: Reader CVM Required Limit = 250.00.

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Configuration data set definitions (Mag-Stripe Data Exchange)

Configuration Data
Set ID

Description

PPMS_DEreferce

PPS_MStripe1 plus:
- Proceed To First Write Flag: DF8110 01 00

The following data sets inherit from 'PPMS_DEreferce' defined above.

Configuration Data
Set ID

Description

PPMS_DE1

PPMS_DEreferce plus:
- Tags To Read is present in the TLV database with zero length
- Proprietary Tag: C7 04 AABBCCDD is present in the TLV
database (DET Access Conditions)

PPMS_DE2

PPMS_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read: DF8112 02 5F 53

PPMS_DE3

PPMS_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read: DF8112 06 5F 53 50 87 5F 2D

PPMS_DE4

PPMS_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read: DF8112 04 5F 53 82 94

PPMS_DE5

PPMS_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read: DF8112 08 5F 53 50 87 5F 2D 82 94

PPMS_DE6

PPMS_DEreferce plus:
- Proceed To First Write Flag is present in the TLV database with
zero length

PPMS_DE7

PPMS_DEreferce plus:
- Tags To Read: DF8112 01 5A

PPMS_DE8

PPMS_DEreferce plus:
- Tags To Read is present in the TLV database with zero length

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

Configuration data set definitions (EMV Data Exchange)

Configuration Data
Set ID

Description

PPMC_DEreferce

PPS_MChip1 plus:
- DS Requested Operator ID: '9F5C 08 7A45123EE59C7F40'
- DSVN Term: 'DF810D 01 02'
- Proceed To First Write Flag: 'DF8110 01 00'
- Protected Data Envelopes 1 to 5: No value (i.e.:
IsEmpty(T)=True)
- Unprotected Data Envelopes 1 to 5: No value (i.e.:
IsEmpty(T)=True)

PPMC_DETTR_referce

PPMC_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read: 'DF8112 02 5F53'
- Proprietary Tag: 'C7 04 AABBCCDD'

The following data sets inherit from 'PPMC_DEreferce' defined above.

Configuration Data
Set ID

Description

PPMC_DE1

PPMC_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read: 'DF8112 06 5F53 9F5D 9F75'

PPMC_DE2

PPMC_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read with several entries: 'DF8112 0E 5F53 9F5D 9F75
9F76 9F77 9F78 9F79'

PPMC_DE3

PPMC_DEreferce plus:
- Proceed To First Write Flag: Not present
- Tags To Read with several entries: 'DF8112 03 5F21 5A'
- Proprietary tag '5F21' is NOT present in the TLV database
- 'DS Requested Operator ID' is present in the TLV database with
zero length

PPMC_DE4

PPMC_DEreferce plus:
- Proprietary Tag '5F53' is present in the TLV database with zero
length
- Tags To Read with several entries: 'DF8112 0E 5F53 9F5D 9F75
9F76 9F77 9F78 9F79'
- Proceed To First Write Flag is present in the TLV database with
zero length

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPMC_DE5

PPMC_DEreferce plus:
- DS Requested Operator ID is not present
- Proceed To First Write Flag is present in the TLV database with
zero length

PPMC_DE6

PPMC_DEreferce plus:
- Proceed To First Write Flag is present in the TLV database with
zero length

PPMC_DE7

PPMC_DEreferce plus:
- Proceed To First Write Flag is present in the TLV database with
zero length
- DS ID is present in the TLV database with zero length

PPMC_DE8

PPMC_DEreferce plus:
- Proceed To First Write Flag is present in the TLV database with
zero length
- ACI is present in the TLV database with zero length

PPMC_DE9

PPMC_DEreferce plus:
- Tags To Read: 'DF8112 01 5A'
- DS Requested Operator ID is not present

PPMC_DE10

PPMC_DEreferce plus:
- Proceed To First Write Flag: Not present
- Tags To Read: 'DF8112 07 C1 C2 C3 C4 C5 C6 5A'
- Proprietary tags 'C1', 'C2', 'C3', 'C4', 'C5', 'C6' are present in the
TLV database with zero length
- DS Requested Operator ID is present in the TLV database with
zero length

PPMC_DE_Torn_Empty PPMC_DEreferce plus:

- Proprietary tag '5F53' is present in the TLV database with zero
length
- Tags To Read: 'DF8112 02 5F53'
- Max Lifetime of Torn Transaction Log Record: '0E10'
- Max Number of Torn Transaction Log Records: '00'
PPMC_IDS_Torn

PPMC_DEreferce plus:
- Proprietary tag '5F53' is present in the TLV database with zero
length
- Tags To Read: 'DF8112 02 5F53'
- Max Lifetime of Torn Transaction Log Record: '0E10'
- Max Number of Torn Transaction Log Records: '02'

PPMC_IDS_TornBalance PPMC_DEreferce plus:

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPMC_IDS_TornMax1

PPMC_SDS_Torn

PPMC_DEreferce plus:
- Proceed To First Write Flag: Not present
- Max Lifetime of Torn Transaction Log Record: '0E10'
- Max Number of Torn Transaction Log Records: '02'
- Protected Data Envelopes 1 to 5: Not present
- Unprotected Data Envelopes 1 to 5: Not present

The following data sets inherit from ' PPMC_DETTR_referce' defined above.
Configuration Data
Set ID

Description

PPMC_DETTR1

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 02 9F47'

PPMC_DETTR2

PPMC_DETTR_referce except:
- DS Requested Operator ID: '9F5C 08 7345123215904501'

PPMC_DETTR3

PPMC_DETTR_referce except:
- Tags To Read is not present
- DS Requested Operator ID: '9F5C 08 7345123215904501'

PPMC_DETTR4

PPMC_DETTR_referce except:
- Tags To Read is present in the TLV database with zero length

PPMC_DETTR5

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 06 5F 53 50 87 5F 2D'

PPMC_DETTR6

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 04 5F 53 82 94'

PPMC_DETTR7

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 08 5F 53 50 87 5F 2D 82 94'

PPMC_DETTR8

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 02 5F53'
- Tags To Write Before Gen AC is present in the TLV database
with zero length

PPMC_DETTR9

PPMC_DETTR_referce except:
- Tags To Write Before Gen AC: 'FF8102 66
9F753000112233445566778899AABBCCDDEEFF001122334455
66778899AABBCCDDEEFF00112233445566778899AABBCCD
DEEFF9F7630FFEEDDCCBBAA99887766554433221100FFEE
DDCCBBAA99887766554433221100FFEEDDCCBBAA9988776
6554433221100'

PPMC_DETTR10

PPMC_DETTR_referce except:
- Tags To Write After Gen AC is present in the TLV database with
zero length

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPMC_DETTR11

PPMC_DETTR_referce except:
- Tags To Write After Gen AC: 'FF8102 66
9F753000112233445566778899AABBCCDDEEFF001122334455
66778899AABBCCDDEEFF00112233445566778899AABBCCD
DEEFF9F7630FFEEDDCCBBAA99887766554433221100FFEE
DDCCBBAA99887766554433221100FFEEDDCCBBAA9988776
6554433221100'

PPMC_DETTR12

PPMC_DETTR_referce except:
- Tags To Read is not present
- DSVN Term: 'DF810D 04 88776655'

PPMC_DETTR13

PPMC_DETTR_referce except:
- Proceed To First Write Flag is not present
- Tags To Read: 'DF8112 03 5F53 82'
- DS Requested Operator ID is not present

PPMC_DETTR14

PPMC_DETTR_referce except:
- Proceed To First Write Flag: 'DF8110 01 01'
- Tags To Read: 'DF8112 03 5F53 82'
- DS Requested Operator ID is set with all zeroes: '9F5C 08
0000000000000000'
- DSVN Term is present in the TLV database with zero length

PPMC_DETTR15

PPMC_DETTR_referce except:
- Proceed To First Write Flag: 'DF8110 01 01'
- Tags To Read: 'DF8112 03 5F53 82'
- DSVN Term is present in the TLV database with zero length

PPMC_DETTR16

PPMC_DETTR_referce except:
- Proceed To First Write Flag is not present
- Tags To Read: 'DF8112 03 5F53 82'
- DS Requested Operator ID is not present
- DSVN Term is not present

PPMC_DETTR17

PPMC_DETTR_referce except:
- Proceed To First Write Flag is not present
- Tags To Write Before Gen AC is present in the TLV database
with zero length
- Tags To Read: 'DF8112 03 9F47 5A'
- DS Requested Operator ID is not present

PPMC_DETTR18

PPMC_DETTR_referce except:
- Proceed To First Write Flag is not present
- Tags To Read: 'DF8112 02 9F47'
- DS Requested Operator ID is not present

PPMC_DETTR19

PPMC_DETTR_referce except:
- Proceed To First Write Flag is present in the TLV database with
zero length
- Tags To Read: 'DF8112 03 9F47 82'
- DS Requested Operator ID is not present

PPMC_DETTR20

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 03 5F53 82'

2013 MasterCard

PayPass Testing Environment November 2013

Annex A: Configuration and Transaction related data sets

PPMC_DETTR21

PPMC_DETTR_referce except:
- The tag 'Balance Read Before Gen AC' is present: 'DF8104 06
000000000000'
- The tag 'Balance Read After Gen AC' is present: 'DF8105 06
000000000000'
- DS input (Term) is not present

PPMC_DETTR22

PPMC_DETTR_referce except:
- Proprietary tag 'C7' is present in TLV database with zero length

PPMC_DETTR23

PPMC_DETTR_referce except:
- Proceed To First Write Flag is present in the TLV database with
zero length
- Tags To Read: 'DF8112 03 5F53 5A'
- Proprietary tag '5F21' is present in TLV database with zero length

PPMC_DETTR24

PPMC_DETTR_referce except:
- Tags To Read: 'DF8112 03 5F53 5A'

PPMC_DETTR25

PPMC_DETTR_referce except:
- Tags To Read is not present
- Proceed To First Write Flag is not present
- DS Requested Operator Id is present in the TLV database with
zero length

PPMC_DETTR26

PPMC_DETTR_referce except:
- Tags To Read is not present
- DS Requested Operator Id is not present

PPMC_DETTR27

PPMC_DETTR_referce except:
- Tags To Read is not present
- Proceed To First Write Flag: 'DF8110 01 01'
- DS Requested Operator Id is not present

PPMC_DETTR28

PPMC_DETTR_referce except:
- Tags To Read is not present
- Application version Number (reader) is not present
- TAC Online is not present

PPMC_DETTR29

PPMC_DETTR_referce except:
- DS Requested Operator Id is not present

PPMC_SDSTTR_Torn

2013 MasterCard

PayPass Testing Environment November 2013

Annex B: CA Public Keys

6 Annex B: CA Public Keys

M/Chip

This section applies to PayPassM/Chip Products only.

The following tables list the CA Public Keys used for testing.
-

Index identifies the CA Public Key Index

Modulus identifies the CA Public Key Modulus

Length identifies the CA Public Key Modulus Length in bytes

Exp identifies the CA Public Key Exponent

Checksum is calculated as follow: SHA-1(RID + Index + Modulus + Exp)

Testing identifies whether the related key is used for the Level 2 card simulator
testing (L2) or the Level 2 confidence tests using the PayPass TIP cards
(TIP) or both.

Note that for all keys specified below, the CA Hash Algorithm Indicator is 01
(SHA-1) and the CA Public Key Algorithm Indicator is 01.

CA Public keys related to the RID A0 00 00 00 04

Index

Modulus

Length

Exp

Check Sum

Testing

9C 6B E5 AD B1 0B 4B E3 DC E2 09 9B 4B 21 06 72

160

EC 0A 59

B8 96 56 EB A0 91 20 4F 61 3E CC 62 3B ED C9 C6

D3 5D 19

D7 7B 66 0E 8B AE EA 7F 7C E3 0F 1B 15 38 79 A4

F0 31 E9

E3 64 59 34 3D 1F E4 7A CD BD 41 FC D7 10 03 0C

E8 CB EC

2B A1 D9 46 15 97 98 2C 6E 1B DD 08 55 4B 72 6F

56 DB 80

5E FF 79 13 CE 59 E7 9E 35 72 95 C3 21 E2 6D 0B

E2 2B 1D

8B E2 70 A9 44 23 45 C7 53 E2 AA 2A CF C9 D3 08

E1 30

50 60 2F E6 CA C0 0C 6D DF 6B 8D 9D 9B 48 79 B2
82 6B 04 2A 07 F0 E5 AE 52 6A 3D 3C 4D 22 C7 2B
9E AA 52 EE D8 89 38 66 F8 66 38 7A C0 5A 13 99
05

A1 F5 E1 C9 BD 86 50 BD 43 AB 6E E5 6B 89 1E F7

128

53 D0 49

45 9C 0A 24 FA 84 F9 12 7D 1A 6C 79 D4 93 0F 6D

03 B4 96

B1 85 2E 25 10 F1 8B 61 CD 35 4D B8 3A 35 6B D1

F5 95 44

90 B8 8A B8 DF 04 28 4D 02 A4 20 4A 7B 6C B7 C5

A8 43 09

55 19 77 A9 B3 63 79 CA 3D E1 A0 8E 69 F3 01 C9

AF 16 92

5C C1 C2 05 06 95 92 75 F4 17 23 DD 5D 29 25 29

51 F2 89

05 79 E5 A9 5B 0D F6 32 3F C8 E9 27 3D 6F 84 91

68 74

98 C4 99 62 09 16 6D 9B FC 97 3C 36 1C C8 26 E1

2013 MasterCard

PayPass Testing Environment November 2013

Annex B: CA Public Keys

A1 91 CB 87 47 3F 29 34 9B 5D 60 A8 8B 3E AE E0

21 76 6E

TIP +

97 3A A6 F1 A0 82 F3 58 D8 49 FD DF F9 C0 91 F8

248

BB 0E E1

99 ED A9 79 2C AF 09 EF 28 F5 D2 24 04 B8 8A 22

22 AF B6

93 EE BB C1 94 9C 43 BE A4 D6 0C FD 87 9A 15 39

5D 78 45

54 4E 09 E0 F0 9F 60 F0 65 B2 BF 2A 13 EC C7 05

B7 3D B4

F3 D4 68 B9 D3 3A E7 7A D9 D3 F1 9C A4 0F 23 DC

6B AB 65

F5 EB 7C 04 DC 8F 69 EB A5 65 B1 EB CB 46 86 CD

42 7A

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
F1

A0 DC F4 BD E1 9C 35 46 B4 B6 F0 41 4D 17 4D DE

D8 E6 8D

TIP +

29 4A AB BB 82 8C 5A 83 4D 73 AA E2 7C 99 B0 B0

176

A1 67 AB

53 A9 02 78 00 72 39 B6 45 9F F0 BB CD 7B 4B 9C

5A 85 D8

6C 50 AC 02 CE 91 36 8D A1 BD 21 AA EA DB C6 53

C3 D5 5E

47 33 7D 89 B6 8F 5C 99 A0 9D 05 BE 02 DD 1F 8C

CB 9B 05

5B A2 0E 2F 13 FB 2A 27 C4 1D 3F 85 CA D5 CF 66

17 A1 A5

68 E7 58 51 EC 66 ED BF 98 85 1F D4 E4 2C 44 C1

B4 BB

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
F3

98 F0 C7 70 F2 38 64 C2 E7 66 DF 02 D1 E8 33 DF

144

A6 9A C7

F4 FF E9 2D 69 6E 16 42 F0 A8 8C 56 94 C6 47 9D

60 3D AF

16 DB 15 37 BF E2 9E 4F DC 6E 6E 8A FD 1B 0E B7

56 6E 97

EA 01 24 72 3C 33 31 79 BF 19 E9 3F 10 65 8B 2F

2D ED C2

77 6E 82 9E 87 DA ED A9 C9 4A 8B 33 82 19 9A 35

CB 43 3E

0C 07 79 77 C9 7A FF 08 FD 11 31 0A C9 50 A7 2C

07 E8 B0

3C A5 00 2E F5 13 FC CC 28 6E 64 6E 3C 53 87 53

1A 9A

5D 50 95 14 B3 B3 26 E1 23 4F 9C B4 8C 36 DD D4
4B 41 6D 23 65 40 34 A6 6F 40 3B A5 11 C5 EF A3

2013 MasterCard

PayPass Testing Environment November 2013

Annex B: CA Public Keys

A6 E6 FB 72 17 95 06 F8 60 CC CA 8C 27 F9 9C EC

248

65537

C2 23 98

D9 4C 7D 4F 31 91 D3 03 BB EE 37 48 1C 7A A1 5F

04 C8 09

23 3B A7 55 E9 E4 37 63 45 A9 A6 7E 79 94 BD C1

81 70 BE

C6 80 BB 35 22 D8 C9 3E B0 CC C9 1A D3 1A D4 50

52 D6 D5

DA 30 D3 37 66 2D 19 AC 03 E2 B4 EF 5F 6E C1 82

D4 15 9E

82 D4 91 E1 97 67 D7 B2 45 42 DF DE FF 6F 62 18

81 CE 84

55 03 53 20 69 BB B3 69 E3 BB 9F B1 9A C6 F1 C3

66 BF

0B 97 D2 49 EE E7 64 E0 BA C9 7F 25 C8 73 D9 73
95 3E 51 53 A4 20 64 BB FA BF D0 6A 4B B4 86 86
0B F6 63 74 06 C9 FC 36 81 3A 4A 75 F7 5C 31 CC
A9 F6 9F 8D E5 9A DE CE F6 BD E7 E0 78 00 FC BE
03 5D 31 76 AF 84 73 E2 3E 9A A3 DF EE 22 11 96
D1 14 83 02 67 7C 72 0C FE 25 44 A0 3D B5 53 E7
F1 B8 42 7B A1 CC 72 B0 F2 9B 12 DF EF 4C 08 1D
07 6D 35 3E 71 88 0A AD FF 38 63 52 AF 0A B7 B2
8E D4 9E 1E 67 2D 11 F9
F6

A2 5A 6B D7 83 A5 EF 6B 8F B6 F8 30 55 C2 60 F5

224

50 29 09

F9 9E A1 66 78 F3 B9 05 3E 0F 64 98 E8 2C 3F 5D

ED 54 5E

1E 8C 38 F1 35 88 01 7E 2B 12 B3 D8 FF 6F 50 16

3C 8D BD

7F 46 44 29 10 72 9E 9E 4D 1B 37 39 E5 06 7C 0A

00 EA 58

C7 A1 F4 48 7E 35 F6 75 BC 16 E2 33 31 51 65 CB

2D 06 17

14 2B FD B2 5E 30 1A 63 2A 54 A3 37 1E BA B6 57

FE E9 F6

2D EE BA F3 70 F3 37 F0 57 EE 73 B4 AE 46 D1 A8

F6 84

BC 4D A8 53 EC 3C C1 2C 8C BC 2D A1 83 22 D6 85
30 C7 0B 22 BD AC 35 1D D3 60 68 AE 32 1E 11 AB
F2 64 F4 D3 56 9B B7 12 14 54 50 05 55 8D E2 60
83 C7 35 DB 77 63 68 17 2F E8 C2 F5 C8 5E 8B 5B
89 0C C6 82 91 1D 2D E7 1F A6 26 B8 81 7F CC C0
89 22 B7 03 86 9F 3B AE AC 14 59 D7 7C D8 53 76
BC 36 18 2F 42 38 31 4D 6C 42 12 FB DD 7F 23 D3
F7

94 EA 62 F6 D5 83 20 E3 54 C0 22 AD DC F0 55 9D

128

65537

EE B0 DD

8C F2 06 CD 92 E8 69 56 49 05 CE 21 D7 20 F9 71

9B 24 77

B7 AE A3 74 83 0E BE 17 57 11 5A 85 E0 88 D4 1C

BE E3 20

6B 77 CF 5E C8 21 F3 0B 1D 89 04 17 BF 2F A3 1E

9A 91 4C

59 08 DE D5 FA 67 7F 8C 7B 18 4A D0 90 28 FD DE

DB A9 4C

96 B6 A6 10 98 50 AA 80 01 75 EA BC DB BB 68 4A

1C 4A 9B

96 C2 EB 63 79 DF EA 08 D3 2F E2 33 1F E1 03 23

DE D9

3A D5 8D CD B1 E6 E0 77 CB 9F 24 EA EC 5C 25 AF
F8

A1 F5 E1 C9 BD 86 50 BD 43 AB 6E E5 6B 89 1E F7

128

F0 6E CC

45 9C 0A 24 FA 84 F9 12 7D 1A 6C 79 D4 93 0F 6D

6D 2A AE

B1 85 2E 25 10 F1 8B 61 CD 35 4D B8 3A 35 6B D1

BF 25 9B

90 B8 8A B8 DF 04 28 4D 02 A4 20 4A 7B 6C B7 C5

7E 75 5A

55 19 77 A9 B3 63 79 CA 3D E1 A0 8E 69 F3 01 C9

38 D9 A9

5C C1 C2 05 06 95 92 75 F4 17 23 DD 5D 29 25 29

B2 4E 2F

05 79 E5 A9 5B 0D F6 32 3F C8 E9 27 3D 6F 84 91

F3 DD

98 C4 99 62 09 16 6D 9B FC 97 3C 36 1C C8 26 E1

2013 MasterCard

PayPass Testing Environment November 2013

Annex B: CA Public Keys

A9 9A 6D 3E 07 18 89 ED 9E 3A 0C 39 1C 69 B0 B8

192

33 67 12

04 FC 16 0B 2B 4B DD 57 0C 92 DD 5A 0F 45 F5 3E

DC C2 85

86 21 F7 C9 6C 40 22 42 66 73 5E 1E E1 B3 C0 62

54 80 9C

38 AE 35 04 63 20 FD 8E 81 F8 CE B3 F8 B4 C9 7B

6A A9 B0

94 09 30 A3 AC 5E 79 00 86 DA D4 1A 6A 4F 51 17

23 58 DE

BA 1C E2 43 8A 51 AC 05 3E B0 02 AE D8 66 D2 C4

6F 75 51

58 FD 73 35 90 21 A1 20 29 A0 C0 43 04 5C 11 66

64 DB

4F E0 21 9E C6 3C 10 BF 21 55 BB 27 84 60 9A 10
64 21 D4 51 63 79 97 38 C1 C3 09 09 BB 6C 6F E5
2B BB 76 39 7B 97 40 CE 06 4A 61 3F F8 41 11 85
F0 88 42 A4 23 EA D2 0E DF FB FF 1C D6 C3 FE 0C
98 21 47 91 99 C2 6D 85 72 CC 8A FF F0 87 A9 C3
FA

A9 0F CD 55 AA 2D 5D 99 63 E3 5E D0 F4 40 17 76

144

5B ED 40

99 83 2F 49 C6 BA B1 5C DA E5 79 4B E9 3F 93 4D

68 D9 6E

44 62 D5 D1 27 62 E4 8C 38 BA 83 D8 44 5D EA A7

A1 6D 2D

41 95 A3 01 A1 02 B2 F1 14 EA DA 0D 18 0E E5 E7

77 E0 3D

A5 C7 3E 0C 4E 11 F6 7A 43 DD AB 5D 55 68 3B 14

60 36 FC

74 CC 06 27 F4 4B 8D 30 88 A4 92 FF AA DA D4 F4

7A 16 0E

24 22 D0 E7 01 35 36 C3 C4 9A D3 D0 FA E9 64 59

A9 9C

TIP

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

2013 MasterCard

PayPass Testing Environment November 2013

Annex B: CA Public Keys

CA Public keys related to the RID B0 12 34 56 78

Index

Modulus

Length

Exp

Check Sum

Testing

9C 6B E5 AD B1 0B 4B E3 DC E2 09 9B 4B 21 06 72

160

5D 29 70

B8 96 56 EB A0 91 20 4F 61 3E CC 62 3B ED C9 C6

E6 46 75

D7 7B 66 0E 8B AE EA 7F 7C E3 0F 1B 15 38 79 A4

72 7E 60

E3 64 59 34 3D 1F E4 7A CD BD 41 FC D7 10 03 0C

46 07 65

2B A1 D9 46 15 97 98 2C 6E 1B DD 08 55 4B 72 6F

A8 DB 75

5E FF 79 13 CE 59 E7 9E 35 72 95 C3 21 E2 6D 0B

34 2A E1

8B E2 70 A9 44 23 45 C7 53 E2 AA 2A CF C9 D3 08

47 83

50 60 2F E6 CA C0 0C 6D DF 6B 8D 9D 9B 48 79 B2
82 6B 04 2A 07 F0 E5 AE 52 6A 3D 3C 4D 22 C7 2B
9E AA 52 EE D8 89 38 66 F8 66 38 7A C0 5A 13 99
02

A9 9A 6D 3E 07 18 89 ED 9E 3A 0C 39 1C 69 B0 B8

192

29 4B E2

04 FC 16 0B 2B 4B DD 57 0C 92 DD 5A 0F 45 F5 3E

02 39 AB

86 21 F7 C9 6C 40 22 42 66 73 5E 1E E1 B3 C0 62

15 24 5A

38 AE 35 04 63 20 FD 8E 81 F8 CE B3 F8 B4 C9 7B

63 BE A4

94 09 30 A3 AC 5E 79 00 86 DA D4 1A 6A 4F 51 17

6C C6 C1

BA 1C E2 43 8A 51 AC 05 3E B0 02 AE D8 66 D2 C4

75 A2 55

58 FD 73 35 90 21 A1 20 29 A0 C0 43 04 5C 11 66

62 D1

A1 F5 E1 C9 BD 86 50 BD 43 AB 6E E5 6B 89 1E F7

128

B9 A1 D6

45 9C 0A 24 FA 84 F9 12 7D 1A 6C 79 D4 93 0F 6D

5C AF E0

B1 85 2E 25 10 F1 8B 61 CD 35 4D B8 3A 35 6B D1

6B 05 4E

90 B8 8A B8 DF 04 28 4D 02 A4 20 4A 7B 6C B7 C5

DD 7E A8

55 19 77 A9 B3 63 79 CA 3D E1 A0 8E 69 F3 01 C9

25 97 AB

5C C1 C2 05 06 95 92 75 F4 17 23 DD 5D 29 25 29

85 F1 30

05 79 E5 A9 5B 0D F6 32 3F C8 E9 27 3D 6F 84 91

E6 63

98 C4 99 62 09 16 6D 9B FC 97 3C 36 1C C8 26 E1
F3

94 EA 62 F6 D5 83 20 E3 54 C0 22 AD DC F0 55 9D

128

65537

56 94 B0

8C F2 06 CD 92 E8 69 56 49 05 CE 21 D7 20 F9 71

D2 78 48

B7 AE A3 74 83 0E BE 17 57 11 5A 85 E0 88 D4 1C

18 14 A0

6B 77 CF 5E C8 21 F3 0B 1D 89 04 17 BF 2F A3 1E

5E 12 B5

59 08 DE D5 FA 67 7F 8C 7B 18 4A D0 90 28 FD DE

58 CE C1

96 B6 A6 10 98 50 AA 80 01 75 EA BC DB BB 68 4A

23 48 65

96 C2 EB 63 79 DF EA 08 D3 2F E2 33 1F E1 03 23

AA 5D

3A D5 8D CD B1 E6 E0 77 CB 9F 24 EA EC 5C 25 AF

2013 MasterCard

PayPass Testing Environment November 2013

Annex B: CA Public Keys

98 F0 C7 70 F2 38 64 C2 E7 66 DF 02 D1 E8 33 DF

144

F7 81 13

F4 FF E9 2D 69 6E 16 42 F0 A8 8C 56 94 C6 47 9D

E8 60 F0

16 DB 15 37 BF E2 9E 4F DC 6E 6E 8A FD 1B 0E B7

30 A8 72

EA 01 24 72 3C 33 31 79 BF 19 E9 3F 10 65 8B 2F

92 3F CE

77 6E 82 9E 87 DA ED A9 C9 4A 8B 33 82 19 9A 35

93 E3 38

0C 07 79 77 C9 7A FF 08 FD 11 31 0A C9 50 A7 2C

1C 77 A4

3C A5 00 2E F5 13 FC CC 28 6E 64 6E 3C 53 87 53

2A 30

5D 50 95 14 B3 B3 26 E1 23 4F 9C B4 8C 36 DD D4
4B 41 6D 23 65 40 34 A6 6F 40 3B A5 11 C5 EF A3
F8

A9 9A 6D 3E 07 18 89 ED 9E 3A 0C 39 1C 69 B0 B8

192

66 46 9C

04 FC 16 0B 2B 4B DD 57 0C 92 DD 5A 0F 45 F5 3E

88 E7 DC

86 21 F7 C9 6C 40 22 42 66 73 5E 1E E1 B3 C0 62

11 15 29

38 AE 35 04 63 20 FD 8E 81 F8 CE B3 F8 B4 C9 7B

C7 D3 79

94 09 30 A3 AC 5E 79 00 86 DA D4 1A 6A 4F 51 17

D7 93 8C

BA 1C E2 43 8A 51 AC 05 3E B0 02 AE D8 66 D2 C4

8D F3 E4

58 FD 73 35 90 21 A1 20 29 A0 C0 43 04 5C 11 66

C2 5E

2013 MasterCard

PayPass Testing Environment November 2013

Annex C: Data Exchange XMLs definition

7 Annex C: Data Exchange XMLs

definition
This section details the formatting definitions for the Data Exchange XML files.

XML graphic view

The following schematic describes the DEK-DET xml file structure.
Figure 7-1: XML graphic view

2013 MasterCard

PayPass Testing Environment November 2013

Annex C: Data Exchange XMLs definition

XML attribute definition

Attribute

Description

HEADER

This administrative section includes several data items. The most critical one is the
TEMPLATE_VERSION used to build this xml file. The version is changed
anytime a non-backward compatible change is made.

TRAILER

This administrative section includes so far only a Signature. This one is actually
not used.

BODY

The section gathers a set of events (EVT) that will be used during the test
execution.

EVT

When with the type attribute set to "DEKRECEIVED", this element lists a set of
Data Exchange messages (DEK and associated DET Signals).
Other types may be added in the future typically to address other signals defined
in MasterCard specification like the ACTIVATE, UPDATE or the OUTCOME.

DEK

This element fully describes a DEK-DET exchange by providing for a specific

DEK the DET(s) to be returned. The number of DETs may vary from 1 to several.

DEKVALUE

This element contains the DEK value using TLV tags defined in [PayPassV3].

DEKPROPERTIES

This element contains a set of properties assign to a specific DEK.

Currently only the STATE is documented. Additional properties may be
introduced in the future.

STATE

In case of a DEK this property defines the PayPass Product state when the DEK
signal is expected to be sent. States are those described in [PayPassV3].

DET

This element describes a DET signal.

There is always at least one DET element per DEK, but this one may be empty (no
DETVALUE).

DETVALUE

Provides the value of the DET signal to be returned. The value uses TLV tags
defined in [PayPassV3].
An empty DETVALUE means that no DET must be returned (see requirement B'7).

DETPROPERTIES

This element contains a set of properties assigned to this specific DET.

Currently only the STATE is documented. Additional properties may be
introduced in the future.

STATE

In case of a DET this property defines the PayPass Product state when the DEK
signal is expected to be sent.

2013 MasterCard

PayPass Testing Environment November 2013

Annex C: Data Exchange XMLs definition

XML example
Below is an example of XML file.

<?xml version="1.0" encoding="UTF-8"?>

<MESSAGE>
<HEADER>
<FILE_NAME>DEKDET_0040v0.3</FILE_NAME>
<FILE_DATE>2011/11/23</FILE_DATE>
<TEMPLATE_VERSION>0.5</TEMPLATE_VERSION>
<GENERATED_BY>
<COMPANY_NAME>MASTERCARD</COMPANY_NAME>
<PRODUCT_NAME>R3TESTTOOLINQ</PRODUCT_NAME>
<PRODUCT_VERSION>1.0</PRODUCT_VERSION>
<OPERATOR_NAME>XXX</OPERATOR_NAME>
</GENERATED_BY>
</HEADER>
<BODY>
<EVT type="DEKRECEIVED">
<DEK>
<DEKVALUE> FF 81 04 04 5F 53 01 10 DF 81 06 00 </DEKVALUE>
<DEKPROPERTIES>
<STATE> </STATE>
</DEKPROPERTIES>
<DET>
<DETVALUE> FF 81 02 23 9F 75 20 00 11 22 33 44 55 66 77 88 99 AA BB CC
DD EE FF 00 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF </DETVALUE>
<DETPROPERTIES>
<STATE> </STATE>
</DETPROPERTIES>
</DET>
<DET>
<DETVALUE> DF 81 10 01 01 </DETVALUE>
<DETPROPERTIES>
<STATE> S12-9 </STATE>
</DETPROPERTIES>
</DET>
</DEK>
<DEK>
<DEKVALUE> FF 81 04 04 5F 53 01 20 DF 81 06 00 </DEKVALUE>
<DEKPROPERTIES>
<STATE> </STATE>
</DEKPROPERTIES>
<DET>

2013 MasterCard

PayPass Testing Environment November 2013

Annex C: Data Exchange XMLs definition

2013 MasterCard

PayPass Testing Environment November 2013

Annex C: Data Exchange XMLs definition

Document Type Definition

The below Document Type Definition (DTD) declares the elements and attributes
appearing in the XMLs.

<?xml version="1.0" encoding="UTF-8"?>

<!ELEMENT TRAILER ((SIGNATURE))>
<!ELEMENT TEMPLATE_VERSION (#PCDATA)>
<!ELEMENT STATE (#PCDATA)>
<!ELEMENT SIGNATURE (#PCDATA)>
<!ELEMENT PRODUCT_VERSION (#PCDATA)>
<!ELEMENT PRODUCT_NAME (#PCDATA)>
<!ELEMENT OPERATOR_NAME (#PCDATA)>
<!ELEMENT MESSAGE ((HEADER, BODY, TRAILER))>
<!ELEMENT HEADER ((FILE_NAME, FILE_DATE, TEMPLATE_VERSION,
GENERATED_BY))>
<!ELEMENT GENERATED_BY ((COMPANY_NAME, PRODUCT_NAME,
PRODUCT_VERSION, OPERATOR_NAME))>
<!ELEMENT FILE_NAME (#PCDATA)>
<!ELEMENT FILE_DATE (#PCDATA)>
<!ELEMENT EVT ((DEK+))>
<!ATTLIST EVT
type CDATA #IMPLIED
>
<!ELEMENT DETVALUE (#PCDATA)>
<!ELEMENT DETPROPERTIES ((STATE))>
<!ELEMENT DET ((DETVALUE, DETPROPERTIES))>
<!ELEMENT DEKVALUE (#PCDATA)>
<!ELEMENT DEKPROPERTIES ((STATE))>
<!ELEMENT DEK ((DEKVALUE, DEKPROPERTIES, DET+))>
<!ELEMENT COMPANY_NAME (#PCDATA)>
<!ELEMENT BODY ((EVT+))>

2013 MasterCard

PayPass Testing Environment November 2013

Annex C: Data Exchange XMLs definition

NOTE:
The information in this document was valid at the time of publication. MasterCard
reserves the right to amend this information and release new versions or updates
without prior notification.
It is a vendor responsibility to check for the current release or updates to this
document at www.PayPass.com before commencing the vendor testing process and
submitting their PayPass Products for formal testing.

2013 MasterCard

PayPass Testing Environment November 2013

CQM Requirements V2.22
No ratings yet
CQM Requirements V2.22
441 pages
0ikL3QgQKCejxyundxQ8 CoursematerialA4-1569849373450
No ratings yet
0ikL3QgQKCejxyundxQ8 CoursematerialA4-1569849373450
82 pages
Ic Card Specification 20 Eng
100% (1)
Ic Card Specification 20 Eng
124 pages
UGRD CS6105 Discrete Mathematics Legit Not Quizzess
100% (1)
UGRD CS6105 Discrete Mathematics Legit Not Quizzess
8 pages
JaniceNew Thesis Study
No ratings yet
JaniceNew Thesis Study
104 pages
7 EMVCo Level3 Framework Implementation Guidelines V 1 1 20190411
No ratings yet
7 EMVCo Level3 Framework Implementation Guidelines V 1 1 20190411
103 pages
EMV Master Class: Join The Master Class! Stay Ahead of The Competition!
No ratings yet
EMV Master Class: Join The Master Class! Stay Ahead of The Competition!
2 pages
PayPass MChip Requirements 2013 PDF
No ratings yet
PayPass MChip Requirements 2013 PDF
75 pages
Nexo FAST: PURE Kernel
No ratings yet
Nexo FAST: PURE Kernel
35 pages
book2-EMV v4.2 Book 2 Security and Key Management CR05 - 20090122094212
100% (1)
book2-EMV v4.2 Book 2 Security and Key Management CR05 - 20090122094212
176 pages
Imported Items 2018
No ratings yet
Imported Items 2018
52 pages
EMV v4.3 Book 3 Application Specification 20120607062110791
No ratings yet
EMV v4.3 Book 3 Application Specification 20120607062110791
230 pages
Standard 70 Book 1 - Apr 15 PDF
No ratings yet
Standard 70 Book 1 - Apr 15 PDF
146 pages
EMV CPS v1.1
67% (3)
EMV CPS v1.1
104 pages
EMV Third Edition
From Everand
EMV Third Edition
Gerardus Blokdyk
No ratings yet
MC PayPass Terminals
No ratings yet
MC PayPass Terminals
31 pages
Nursing Intervention For Chest Pain
100% (3)
Nursing Intervention For Chest Pain
2 pages
Proverbs and Psalms
100% (1)
Proverbs and Psalms
3 pages
PRESENTATION ON Annotated Bibliography
40% (5)
PRESENTATION ON Annotated Bibliography
19 pages
PayPass - MChip - Acquirer - Imlementation - Requirements - PPMCAIR (V1.0 - July 2008)
No ratings yet
PayPass - MChip - Acquirer - Imlementation - Requirements - PPMCAIR (V1.0 - July 2008)
88 pages
Collis b2 Emv and Contactless Offering
100% (1)
Collis b2 Emv and Contactless Offering
52 pages
PP MTIP UserGuide Dec2011
No ratings yet
PP MTIP UserGuide Dec2011
201 pages
R4 Discover D-PASU.S.terminalGuide2017
No ratings yet
R4 Discover D-PASU.S.terminalGuide2017
40 pages
MC Onbehalf Key MGMT Interface Spec
100% (1)
MC Onbehalf Key MGMT Interface Spec
100 pages
Users Manual 3704697
No ratings yet
Users Manual 3704697
442 pages
M Tip
No ratings yet
M Tip
60 pages
VSDC Perso 1 0 Mar 2009
No ratings yet
VSDC Perso 1 0 Mar 2009
118 pages
EMVCo Software Based Mobile Payment Security Requirements - V1.0 - 20161213 - 20161213093622436
No ratings yet
EMVCo Software Based Mobile Payment Security Requirements - V1.0 - 20161213 - 20161213093622436
42 pages
JCB TCI 1.9 - Test Cases
No ratings yet
JCB TCI 1.9 - Test Cases
8 pages
EMV - Understanding
No ratings yet
EMV - Understanding
3 pages
Mpos Development Guidelines
100% (1)
Mpos Development Guidelines
10 pages
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
No ratings yet
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
88 pages
csfb400 Icsf Apg hcr77d1 PDF
No ratings yet
csfb400 Icsf Apg hcr77d1 PDF
1,720 pages
M Chip 4 Brochure
No ratings yet
M Chip 4 Brochure
8 pages
Part V Contactless Integrated Circuit Card Payment Specification
100% (1)
Part V Contactless Integrated Circuit Card Payment Specification
103 pages
VISA CEMEA Personalisation Templates Version 1.5, August 2003
No ratings yet
VISA CEMEA Personalisation Templates Version 1.5, August 2003
107 pages
Part II Extended Purchase Specification Based On Contactless Low-Value Payment Application
No ratings yet
Part II Extended Purchase Specification Based On Contactless Low-Value Payment Application
67 pages
M/Chip Functional Architecture For Debit and Credit: Applies To: Summary
No ratings yet
M/Chip Functional Architecture For Debit and Credit: Applies To: Summary
12 pages
CR - SingleMessageSystemSpecifications - Abril 2024
No ratings yet
CR - SingleMessageSystemSpecifications - Abril 2024
1,028 pages
Visa ADVT
No ratings yet
Visa ADVT
10 pages
Security Rules and Procedures 30 July 2015
100% (1)
Security Rules and Procedures 30 July 2015
227 pages
Kms Case Study - Mastercard: Centralized Key Management
No ratings yet
Kms Case Study - Mastercard: Centralized Key Management
4 pages
Fime Academy Emv Contactless Specifications
No ratings yet
Fime Academy Emv Contactless Specifications
2 pages
US Quick Chip and ADVT-CDET Use Cases v2.7
No ratings yet
US Quick Chip and ADVT-CDET Use Cases v2.7
43 pages
Personalization Data Specifications: For Debit and Credit On Chip
100% (1)
Personalization Data Specifications: For Debit and Credit On Chip
71 pages
Mastercard CPV Information Request v2
No ratings yet
Mastercard CPV Information Request v2
5 pages
UPI QuickPass Testing Guide For Acquirers - V201905
100% (1)
UPI QuickPass Testing Guide For Acquirers - V201905
14 pages
Part IV Debit Credit Application Security Specification
100% (1)
Part IV Debit Credit Application Security Specification
87 pages
VISA Dynamic Passcode Authentication
No ratings yet
VISA Dynamic Passcode Authentication
4 pages
17.1.115 Iso Iec 7816 9 1
No ratings yet
17.1.115 Iso Iec 7816 9 1
26 pages
UPI QR Code Acceptance
No ratings yet
UPI QR Code Acceptance
22 pages
Terminal Information To Enhance Contactless Application Selection
No ratings yet
Terminal Information To Enhance Contactless Application Selection
10 pages
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
100% (1)
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
18 pages
Visa TADG
100% (1)
Visa TADG
212 pages
POS Specification PDF
No ratings yet
POS Specification PDF
5 pages
UPI QuickPass Implementation Guide For Acquirers v1.4.0
No ratings yet
UPI QuickPass Implementation Guide For Acquirers v1.4.0
14 pages
CONTACTLESS v1.2
No ratings yet
CONTACTLESS v1.2
16 pages
Refreshment Training On All Digital Products and Services
No ratings yet
Refreshment Training On All Digital Products and Services
132 pages
Part I Contactless Reader Interface Specification
100% (1)
Part I Contactless Reader Interface Specification
124 pages
Sunmi KLD KeyManagement V2.101
No ratings yet
Sunmi KLD KeyManagement V2.101
7 pages
Applet Card PDF
No ratings yet
Applet Card PDF
8 pages
Datacard Affina SDK
No ratings yet
Datacard Affina SDK
8 pages
Advt User Guide v7
100% (1)
Advt User Guide v7
116 pages
Arnaud Du Chene: Mastercard Paypass Vendor Product - Letter of Approval
No ratings yet
Arnaud Du Chene: Mastercard Paypass Vendor Product - Letter of Approval
2 pages
Oracle CRM On Demand Administration Essentials
From Everand
Oracle CRM On Demand Administration Essentials
Padmanabha Rao
No ratings yet
Power of Nature / Ep. 1 "Network": Chinese Zero TO Hero
No ratings yet
Power of Nature / Ep. 1 "Network": Chinese Zero TO Hero
20 pages
All India CW Pricelist Wef 01.08.2022
No ratings yet
All India CW Pricelist Wef 01.08.2022
6 pages
Get Hopped Up On Powerful Combat Elixirs With The Emperor's Children On Crusade
No ratings yet
Get Hopped Up On Powerful Combat Elixirs With The Emperor's Children On Crusade
12 pages
10 Billion Days 100 Billion Nights
100% (1)
10 Billion Days 100 Billion Nights
372 pages
Using Pool Noodles To Teach Mitosis and Meiosis
No ratings yet
Using Pool Noodles To Teach Mitosis and Meiosis
3 pages
Champion
0% (1)
Champion
12 pages
SHCherbal Health
No ratings yet
SHCherbal Health
281 pages
Unofficial Transcript
No ratings yet
Unofficial Transcript
2 pages
Venkata Ravi Kadali: Snowflake Architect/BI Analytics
No ratings yet
Venkata Ravi Kadali: Snowflake Architect/BI Analytics
2 pages
முத்திநிச்சயம்
No ratings yet
முத்திநிச்சயம்
172 pages
Karnataka 9th MidTerm SA1 2019 English Question Paper5
No ratings yet
Karnataka 9th MidTerm SA1 2019 English Question Paper5
2 pages
Seminar 6 - Directors Duty of Care
No ratings yet
Seminar 6 - Directors Duty of Care
32 pages
Awards Level A2 June 2015
No ratings yet
Awards Level A2 June 2015
12 pages
Sei Shonagon - The Pillow Book
No ratings yet
Sei Shonagon - The Pillow Book
1 page
Advertising and Brand Management
No ratings yet
Advertising and Brand Management
2 pages
Schema Refinement: Dr. Jyotismita Chaki
No ratings yet
Schema Refinement: Dr. Jyotismita Chaki
44 pages
WWW Worldslastchance Com Luni-Solar-Calendar How-Did-Yo
No ratings yet
WWW Worldslastchance Com Luni-Solar-Calendar How-Did-Yo
3 pages
Heart Beat: 15 Reasons To Take Up The Drums: Mamiverse Team
No ratings yet
Heart Beat: 15 Reasons To Take Up The Drums: Mamiverse Team
7 pages
Member 17
No ratings yet
Member 17
21 pages
Css Platform Vocabulary
No ratings yet
Css Platform Vocabulary
65 pages
Cultural Expectations and Leadership: Before Reading
100% (1)
Cultural Expectations and Leadership: Before Reading
5 pages
Obie e Course Contents
No ratings yet
Obie e Course Contents
7 pages
BK O Donationdraft 1&2
No ratings yet
BK O Donationdraft 1&2
27 pages
Jay Chou
No ratings yet
Jay Chou
13 pages
Director Seymore Butts Tells You The Truth About What Really Happens in Porn Men's Health
No ratings yet
Director Seymore Butts Tells You The Truth About What Really Happens in Porn Men's Health
1 page