MC_Member ICC Testing Procedures

Information about this Replacement

Replacement The May 2006 MasterCard Member ICC Testing Procedures - Credit replaces your existing manual.

What is in the new version?

This new version includes testing for PayPass as well as updates to the ICC test cases.

Please refer to:

• “Summary of Changes” for a comprehensive list of changes reflected in this update.

• “Using this Manual” for a complete list of the contents of this manual.

Questions? If you have questions about this manual, please contact the Customer Operations Services team or your regional help desk. Please refer to “Using this Manual” for more contact information.

MasterCard is Listening…

Please take a moment to provide us with your feedback about the material and usefulness of the MasterCard Member ICC Testing Procedures - Credit using the following e-mail address:

[email protected]

We continually strive to improve our publications. Your input will help us accomplish our goal of providing you with the information you need.

mailto:[email protected]

of 1

Summary of Changes MasterCard Member ICC Testing Procedures - Credit, May 2006

Change Summary Description of Change Where to Look

Test Case Selection A new section “ICC Network Interface Validation (NIV) Testing” has been added to advise customers and testers on which test cases should be executed, based on what ICC products they are implementing and which ones they have already implemented.

Chapter 1

New Simulator Screen Shots

The section describing simulator use (“MasterINQ Credit Authorization Simulator Set-up”) has been updated to reflect changes to the MasterINQ Credit Authorization simulator.

Chapter 2

New Online PIN for Purchase Test Cases

New test cases were added to the existing ICC (Contact Chip) test cases to test Online PIN for Purchase transactions.

Chapter 4

Chapter 5

Clarification of Clearing Testing

The “ICC Clearing — Transaction Lifecycle Testing” sections for the existing ICC (Contact Chip) Clearing testing in Chapters 4 and 5, have been modified to provide clearer instructions for Chip Clearing testing.

Chapter 4

Chapter 5

PayPass Magnetic Stripe Acquirer Tests

A new chapter describing all PayPass Magnetic Stripe Acquirer test procedures and cases has been added.

Chapter 6

PayPass Magnetic Stripe Issuer Tests

A new chapter describing all PayPass Magnetic Stripe Issuer test procedures and cases has been added.

Chapter 7

PayPass OneSMART Acquirer Tests

A new chapter describing all PayPass OneSMART (M/Chip) Acquirer test procedures and cases has been added.

Chapter 8

PayPass OneSMART Issuer Tests

A new chapter describing all PayPass OneSMART (M/Chip) Issuer test procedures and cases has been added.

Chapter 9

MasterCard Member ICC Testing Procedures - Credit

May 2006

© 2006 MasterCard International Incorporated

MasterCard Member ICC Testing Procedures - Credit • May 2006 Publication Code: ZQ

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

This material may not be duplicated, published, or disclosed, in whole or in part, without the prior written permission of MasterCard.

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.

Media This document is available:

• On MasterCard OnLine®

• On the MasterCard Electronic Library (CD-ROM)

MasterCard International Incorporated 2200 MasterCard Boulevard O’Fallon MO 63368-7263 USA

1-636-722-6100

www.mastercard.com

http://www.mastercard.com/

Table of Contents


MasterCard Member ICC Testing Procedures - Credit • May 2006 i

Using this Manual

Purpose...................................................................................................................1

Audience.................................................................................................................1

Overview ................................................................................................................2

Language Use .........................................................................................................3

Revisions .................................................................................................................3

Related Information................................................................................................4

Support ...................................................................................................................4 Member Relations Representative ...................................................................5

Regional Representative...................................................................................5

Chapter 1 MasterCard ICC Credit Testing Strategy

Introduction .........................................................................................................1-1

Terminal and ICC Type Approval Interoperability Testing ...............................1-2

EMV Specifications — A Foundation for Interoperability ...........................1-2

PayPass Card and Terminal Products Approval ..........................................1-3

Card and Terminal Products Type Approval Testing ..................................1-3

Terminal Type Approval...............................................................................1-4

ICC Card Approval ........................................................................................1-7

ICC Compliance Assessment and Security Testing......................................1-9

ICC Network Interface Validation (NIV) Testing ...............................................1-9 ICC Products and NIV Testing Projects........................................................1-9

Clearing .......................................................................................................1-17

ICC End-to-End Pre-production Testing...........................................................1-17

Table of Contents


ii May 2006 • MasterCard Member ICC Testing Procedures - Credit

Chapter 2 Chip Acquirer – Customer System Build-Up Testing

ICC Authorization – Customer System Build-Up Testing ..................................2-1 Test Procedure Pre-requisites .......................................................................2-1

Test Cases and Procedures ...........................................................................2-1

ICC Clearing – Customer System Build-up Testing .........................................2-22

Chapter 3 Chip Issuer — Customer System Build-Up Testing

Testing Procedure Pre-requisites ........................................................................3-1

Test Cases and Procedures ...........................................................................3-1


Chapter 4 Chip Acquirer — Transaction Lifecycle Testing

ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator ......................................................................................4-1

Testing Procedure Pre-requisites ........................................................................4-1 Test Procedures.............................................................................................4-1 Test Cases ......................................................................................................4-2

ICC Clearing — Transaction Lifecycle Testing.................................................4-17 Testing Procedure Pre-requisites ................................................................4-17 Test Procedures...........................................................................................4-17 Test Cases ....................................................................................................4-18

Chapter 5 Chip Issuer — Transaction Lifecycle Testing ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator ................................................................................5-1 Testing Procedure Pre-requisites ..................................................................5-1 Test Procedures.............................................................................................5-1 Test Cases ......................................................................................................5-3

Table of Contents


MasterCard Member ICC Testing Procedures - Credit • May 2006 iii

ICC Clearing — Transaction Lifecycle Testing...................................................5-7 Testing Procedure Pre-requisites ..................................................................5-7 Test Procedures.............................................................................................5-8 Test Cases ....................................................................................................5-11

Chapter 6 PayPass Acquirer — Magnetic Stripe Testing

PayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator ........................................................6-1

Testing Procedure Pre-requisites ..................................................................6-1

Test Procedures.............................................................................................6-1

Test Cases ......................................................................................................6-3

PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing — MasterCard Clearing and Presentation Simulator...............................................6-9


Test Procedures.............................................................................................6-9

Test Cases ....................................................................................................6-11

Chapter 7 PayPass Magnetic Stripe Issuer — Transaction Lifecycle Testing



Test Procedures.............................................................................................7-1

Test Cases ......................................................................................................7-3

PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing— MasterCard Clearing and Presentment Simulator ..................................................................7-5


Test Procedures.............................................................................................7-5

Table of Contents


iv May 2006 • MasterCard Member ICC Testing Procedures - Credit

Chapter 8 PayPass OneSMART Acquirer — Transaction Lifecycle Testing

PayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator ........................................................8-1


Test Procedures.............................................................................................8-1

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

PayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment Simulator..........................................................................8-7


Test Procedures.............................................................................................8-7

Test Cases ......................................................................................................8-8

Chapter 9 PayPass OneSMART Issuer — Transaction Lifecycle Testing



Test Procedures.............................................................................................9-1

Test Cases ......................................................................................................9-3

PayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator..........................................................................9-7


Test Procedures.............................................................................................9-8

Test Cases ....................................................................................................9-11

Appendix A Issuer Test Card Data for ICC-based Operations

Overview ............................................................................................................ A-1

General Information........................................................................................... A-1

Detailed Issuer Test Card Information .............................................................. A-3

Table of Contents


MasterCard Member ICC Testing Procedures - Credit • May 2006 v

Appendix B MasterCard Credit Authorization Simulator, Ordering Procedure

Ordering the MasterINQ Credit Authorization Simulator ................................. B-1

Appendix C Implementing Chip Card tests

NIV Procedures for customers connected to the APC...................................... C-1 Phase 1 – System Build-up .......................................................................... C-1

Phase 2 – Member Compliance Testing...................................................... C-1

NIV Test cases for customers connected to the APC........................................ C-2 Chip Acquirer –Normal ICC Test Cases ...................................................... C-2

Chip Issuer –Normal ICC Test Cases........................................................... C-3


MasterCard Member ICC Testing Procedures - Credit • May 2006 i

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

Purpose...................................................................................................................1

Audience.................................................................................................................1

Overview ................................................................................................................2

Language Use .........................................................................................................3

Revisions .................................................................................................................3

Related Information................................................................................................4

Support ...................................................................................................................4 Member Relations Representative ...................................................................5 Regional Representative...................................................................................5

Using this ManualPurpose


MasterCard Member ICC Testing Procedures - Credit • May 2006 1

Purpose When introducing integrated circuit card (ICC) for Credit products, MasterCard customers must integrate the interfaces of their existing systems with the MasterCard Authorization and Clearing Systems. This manual describes the MasterCard testing strategy, procedures and provides related test cases that issuers and acquirers must employ during this integration process.

MasterCard customers must first complete testing procedures, as described in the MasterCard Customer Testing Procedures - Credit manual. They must then follow the ICC Credit-related procedures described in this manual, to ensure that the ICC functions of their authorization and clearing host systems are correctly integrated online.

This manual provides procedures and test cases for Authorization and Clearing Systems.

By following these guidelines, MasterCard customers can be assured of the integrity of the MasterCard payments network and specifically the critical interoperability of integrated circuit (IC) cards issued under MasterCard brands.

Audience MasterCard provides this manual for customers and their authorized agents. Specifically, the following personnel should find this manual useful:

• Technical support staff

• Communications personnel

• Development and systems integration personnel

Using this Manual Overview


2 May 2006 • MasterCard Member ICC Testing Procedures - Credit

Overview The following table provides an overview of this manual:

Section Description

Table of Contents Lists the manual's chapters and subchapters. Each entry references a chapter and page number.

Using this Manual Describes the manual’s purpose and its contents.

1 MasterCard ICC Credit Testing Strategy

Explains the MasterCard testing approach and the rationale behind ICC implementation. It also discusses the different ICC products MasterCard supports and which tests apply to which products depending on the initial status of the customer.

2 Chip Acquirer – Customer System Build-Up Testing

Describes:

• The pre-requisites for offline acquirer system build-up testing

• The procedures for credit ICC that customers must perform prior to online credit ICC testing

3 Chip Issuer — Customer System Build-Up Testing

Describes:

• The pre-requisites for offline issuer system build-up testing

• The procedures for credit ICC that customers must perform prior to online credit ICC testing

4 Chip Acquirer — Transaction Lifecycle Testing

Describes the pre-requisites for testing and the procedures for credit ICC that chip acquirers must perform to test the transaction lifecycle with the issuer.

5 Chip Issuer — Transaction Lifecycle Testing

Describes the pre-requisites for testing and the procedures for credit ICC that chip issuers must perform to validate their ICC host implementations for the transaction lifecycle with the acquirer.

6 PayPass Acquirer — Magnetic Stripe Testing

Describes the pre-requisites for testing and the procedures for credit PayPass Magnetic Stripe that acquirers must perform to test the transaction lifecycle with the issuer.

7 PayPass Magnetic Stripe Issuer — Transaction Lifecycle Testing

Describes the pre-requisites for testing and the procedures for credit PayPass Magnetic Stripe that issuers must perform to validate their PayPass Magnetic Stripe host implementations for the transaction lifecycle with the acquirer.

8 PayPass OneSMART Acquirer — Transaction Lifecycle Testing

Describes the pre-requisites for testing and the procedures for credit PayPass OneSMART that acquirers must perform to test the transaction lifecycle with the issuer.

Using this ManualLanguage Use



Section Description

9 PayPass OneSMART Issuer — Transaction Lifecycle Testing

Describes the pre-requisites for testing and the procedures for credit PayPass OneSMART that issuers must perform to validate their PayPass OneSMART host implementations for the transaction lifecycle with the acquirer.

A Issuer Test Card Data for ICC-based Operations

Describes the information that issuers need to send to MasterCard regarding the setup of test parameters for online testing.

B MasterCard Credit Authorization Simulator, Ordering Procedure

Describes the procedure for ordering the MasterINQ Credit Simulator.

C Implementing Chip Card tests

Describes the steps necessary for implementing Chip Card tests. Due to the interface difference, these steps are specifically designed for APC members

Language Use The spelling of English words in this manual follows the convention used for U.S. English as defined in Merriam Webster’s Collegiate Dictionary. MasterCard is incorporated in the United States and publishes in the United States. Therefore, this publication uses U.S. English spelling and grammar rules.

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

In this manual, the terms integrated circuit card (ICC) and chip card are used interchangeably.

Revisions MasterCard periodically will issue revisions to this document as we implement enhancements and changes, or as corrections are required.

With each revision, the date of the revision appears in the footer of each page.

Occasionally, we may initially publish revisions or additions to this document in an operations bulletin or other bulletin. Revisions announced in another publication, such as a bulletin, are effective as of the date indicated in that publication, regardless of when the changes are published in this manual.

Using this Manual Related Information


4 May 2006 • MasterCard Member ICC Testing Procedures - Credit

Related Information The following documents and resources provide information related to the subjects discussed in this manual. Please refer to the Quick Reference Booklet for descriptions of these documents.

• Customer Interface Specifications manual

• MasterINQ Credit Authorization Simulator Guide

• MasterCard Clearing and Presentment Simulator Guide

• MasterCard Member Testing Procedures - Debit

• IPM Test Guide

To order MasterCard manuals, please complete the Publication Request Form and forward it to the address or fax noted on the form. Manuals are also available on MasterCard OnLine®.

Support Please address your questions to the Global Member Operations Support team as follows:

Phone: 1-636-722-6100

Fax: 1-636-722-7192

E-mail: [email protected]

Address: MasterCard International Incorporated Global Member Operations Support 2200 MasterCard Boulevard O’Fallon, MO 63366-7263 USA

Telex: 434800 answerback: 43800 ITAC UI


Using this ManualSupport



Member Relations Representative

Member Relations representatives assist U.S. members with marketing inquiries. They interpret member requests and requirements, analyze them, and if approved, monitor their progress through the various MasterCard departments. This does not cover support for day-to-day operational problems, which the Customer Operations Services team addresses.

To find out who your U.S. Member Relations representative is, contact your local Member Relations office:

Atlanta 1-678-459-9000 Chicago 1-847-375-4000 Purchase 1-914-249-2000 San Francisco 1-925-866-7700

Regional Representative

The regional representatives work out of the regional offices. Their role is to serve as intermediaries between the members and other departments in MasterCard. Members can inquire and receive responses in their own language and during their office’s hours of operation.

To find out the location of the regional office serving your area, call the Customer Operations Services team at:

Phone: 1-800-999-0363 or 1-636-722-6176

1-636-722-6292 (Spanish language support)


MasterCard Member ICC Testing Procedures - Credit • May 2006 1-i

1 MasterCard ICC Credit Testing Strategy This chapter describes the MasterCard approach to testing and integrating ICC PayPass and PayPass OneSMART acquirer and issuer member host implementations, with MasterCard network systems.

Introduction .........................................................................................................1-1

Terminal and ICC Type Approval Interoperability Testing ...............................1-2 EMV Specifications — A Foundation for Interoperability ...........................1-2 PayPass Card and Terminal Products Approval ..........................................1-3 Card and Terminal Products Type Approval Testing ..................................1-3 Terminal Type Approval...............................................................................1-4

Level 1 Type Approval ...........................................................................1-4 Level 2 Type Approval ...........................................................................1-4 Terminal Quality Management...............................................................1-5 MasterCard Terminal Integration Process (TIP).....................................1-6

ICC Card Approval ........................................................................................1-7 ICC Functional Approval ........................................................................1-7 ICC Card Quality Management...............................................................1-8 ICC Card Personalization Validation ......................................................1-8

ICC Compliance Assessment and Security Testing......................................1-9

ICC Network Interface Validation (NIV) Testing ...............................................1-9 ICC Products and NIV Testing Projects........................................................1-9

Contact Chip Implementation Only .....................................................1-10 PayPass Emulating Magnetic Stripe Chip Only ...................................1-10 PayPass Implementing Full M/Chip (OneSMART) ..............................1-10

PayPass OneSMART Transaction Types ........................................1-10 Requirements for PayPass OneSMART Acquirers .........................1-11 Requirements for PayPass OneSMART Issuers..............................1-11 PayPass OneSMART Network Impacts ..........................................1-12

Authorization Request/0100 Messages ....................................1-12 Authorization Request Response/0100 Messages....................1-13 Acquirer Reversal Request/0400 Message and Acquirer Reversal Advice/0420 Message ................................................1-13 1240 Clearing Presentment and 1420 Chargeback Messages...................................................................................1-13

PayPass OneSMART NIV Testing Scenarios ..................................1-14

MasterCard ICC Credit Testing Strategy


1-ii May 2006 • MasterCard Member ICC Testing Procedures - Credit

NIV Test Strategy ............................................................................1-14 Issuer Test Strategy.........................................................................1-15 Acquirer Test Strategy ....................................................................1-16

Clearing .......................................................................................................1-17

ICC End-to-End Pre-production Testing...........................................................1-17

MasterCard ICC Credit Testing StrategyIntroduction


MasterCard Member ICC Testing Procedures - Credit • May 2006 1-1

Introduction To ensure the global acceptance of integrated circuit cards (ICC), ICCs must be able to interact with EMV (Europay MasterCard Visa) chip-capable terminals, everywhere, every time. As chip technology improves, the ICC has to interact with terminals and issuers in new and more complex ways. As a result, existing systems become more complex.

MasterCard supports three ICC products:

• Contact chip using the M/Chip application

• Contactless magnetic stripe emulating PayPass™ (PayPass Magnetic Stripe)

• Contactless chip using the M/Chip application (PayPass OneSMART)

To enable issuers and acquirers to successfully integrate the chip technology with their infrastructure, MasterCard provides a three-step testing approach for each product, complementing the approach used to test magnetic stripe based systems. The approach includes:

• Terminal and Integrated Circuit Card (ICC) Type Approval Interoperability testing

• ICC Network Functional testing (includes Authorization and Clearing)

• ICC End-to-End pre-production testing.

This testing approach has proved to be valuable in regions where chip technology has already been widely adopted. It adds to member confidence at the time of deployment, and ensures that both mandatory and optional data in Credit ICC transactions are present and accurate. Cardholders can therefore be sure of successfully completing ICC transactions using ICC capabilities.

Figure 1.1 illustrates a high level overview of MasterCard testing strategy and the order in which the three testing cycles occur.

MasterCard ICC Credit Testing Strategy Terminal and ICC Type Approval Interoperability Testing


1-2 May 2006 • MasterCard Member ICC Testing Procedures - Credit

Figure 1.1—Overview of the Testing Strategy and Testing Schedule

Terminal and ICCType Approval

Interoperability Testing

ICC NetworkFunctional

Testing

ICC End-to-Endpre-production Testing

Phase 1Customer SystemBuild-up Testing

ICC TransactionLife Cycle

Testing

These steps may be repeated for different ICC Products and differences exist in the approval of supporting terminals and cards for PayPass and non-PayPass products. The following sections provide an overview for each of the steps in the testing process as well as a description of how these vary for different ICC Products. Finally there is a section that provides a guide for Acquirers and Issuers to choose which tests they will require, depending on which set of ICC products they support and their current testing stage.

Terminal and ICC Type Approval Interoperability Testing

EMV Specifications — A Foundation for Interoperability

To ensure that ICC and chip-capable terminals could interact effectively with each other, and to ensure interoperability at a global level, Europay, MasterCard and Visa developed the EMV Specifications for Payment Systems.

In February 1999, Europay International, MasterCard International and Visa International formed EMVCo, LLC. EMVCo’s objective is to manage, maintain, and enhance the EMV Specifications for Payment Systems as technology advances. As a result, the number of chip implementations has increased.

EMVCo develops single terminal approval processes, at a level that enables interoperability across the payment system, through compliance with the EMV specifications.

MasterCard ICC Credit Testing StrategyTerminal and ICC Type Approval Interoperability Testing



Card Type Approval is currently the responsibility of each EMV Payment System and is not within the scope of the EMVCo approval process.

PayPass Card and Terminal Products Approval

A description of the functions that must be executed to approve PayPass cards and terminals is beyond the scope of this document. All PayPass tests in this document specify that they must be executed using equipment approved for PayPass use by MasterCard. The list of approved PayPass card and terminal vendor products can be found at www.paypass.com.

The remainder of this section Terminal and ICC Type Approval describes the steps taken for contact chip systems. While PayPass terminals and ICC cards go through a similar process for, the procedure given here may not reflect the full process for approval. The customer should refer to www.paypass.com for more information about the PayPass terminal and ICC approval processes.

Card and Terminal Products Type Approval Testing

ICC cards and ICC terminals shall be Type Approved before they can be used in customer implementations. Testing responsibilities are shared between the vendor and the customer, depending on what sort of testing is undertaken. Table 1-1 specifies whether the vendor or the MasterCard customer will be responsible for type approval testing.

Table 1-1—Type approval responsibilities for vendor and member

Terminal Type Approval activities and services

ICC Card Approval activities and services

Vendor • Level 1 Type Approval

• Level 2 Type Approval

• MasterCard Terminal Quality Management (TQM)

• PIN Entry Device (PED) Security Assessment

• ICC Functional Approval

• MasterCard ICC Card Quality Management (CQM)

• MasterCard Compliance Assessment and Security Testing (CAST)

Member • MasterCard Terminal Integration Process (TIP)

• ICC Card Validation

As shown in Table 1-1, the vendor is responsible for the majority of type approval activities, which relieves MasterCard customers of most of type approval work. This approach enables a quicker time to market for chip implementation projects.

http://www.paypass.com/





Terminal Type Approval

There are four levels of Terminal Type Approval Interoperability testing:



• Terminal Quality Management

• MasterCard Terminal Level 2 Acquirer Integration Testing

The following sections describe each of these four levels in more detail.

Level 1 Type Approval

While EMVCo Level 1 Type Approval for contact terminals is payment system independent, Level 1 Type Approval for PayPass terminals is currently under the responsibility of MasterCard. The purpose of Level 1 Type Approval is to test the compliance of the terminal with the Analog and digital interfaces requirements, as defined in Book 1 of the EMV 2000 specifications for contact products and ISO/IEC 14443 for PayPass products.

• EMV contact terminal products

Level 1 type approval for EMV contact terminal products is performed in EMVCo accredited laboratories under the responsibility of the vendor. The terminal vendor then submits the laboratory test results to EMVCo, which provides the Level 1 Letter of Approval if the test results are satisfactory. You can view or download detailed EMVCo Level 1 Type Approval testing procedures and test requirements from the EMVCo web site at www.emvco.com

• PayPass terminal products

Level 1 type approval testing for PayPass terminal products is performed in MasterCard accredited laboratories under the responsibility of the vendor. The terminal vendor then submits the laboratory results to MasterCard which provides a level 1 conformity statement if the test results are satisfactory. PayPass Level 1 terminal type approval related process and test requirements can be obtained via www.paypass.com.

Level 2 Type Approval

While EMVCo Level 2 Terminal Type Approval for contact terminals is payment system independent, Level 2 Type Approval for PayPass terminals is currently under the responsibility of MasterCard.

http://www.emvco.com/





The purpose of Level 2 Type Approval is to test the compliance of the terminal with the debit or credit application requirements as defined in books 2, 3 and 4 of the EMV 2000 specifications and PayPass technical specifications contained on www.paypass.com.

• EMV contact terminal products

Level 2 type approval for EMV contact terminal products is performed in EMVCo accredited laboratories under the responsibility of the vendor. The terminal vendor then submits the laboratory test results to EMVCo, which provides the Level 2 Letter of Approval if the test results are satisfactory.

MasterCard sponsored laboratories use the MasterCard card simulator EVAL to perform the test cases for EMVCo Level 2 terminal Type Approval.

Detailed EMVCo Level 2 Type Approval testing procedures and test requirements are available to view or download at www.emvco.com.

• PayPass terminal products

Level 2 type approval testing for PayPass terminal products is performed in MasterCard accredited laboratories under the responsibility of the vendor. The terminal vendor then submits the laboratory results to MasterCard which provides a level 2 conformity statement if the test results are satisfactory.

PayPass Level 2 terminal type approval related process and test requirements can be obtained via www.paypass.com.

Terminal Quality Management

This third level of testing aims to promote support and trust for a single quality assurance process among acquirers and vendors. This single process simplifies relationships between vendors and their financial institution customers. MasterCard advises financial institutions who operate as acquirers to purchase only products with the MasterCard terminal quality management (TQM) label. For more information please contact [email protected].

MasterCard provides this service to terminal vendors to:

• Assist them in preparing a fully compliant Interface Module (IFM) or PayPass card reader.

• Confirm that they reproduce tested samples according to MasterCard’s quality requirements, (in terms of MasterCard quality management process, and the display of the quality label).

http://www.emvco.com/


mailto:[email protected].




The MasterCard quality management process ensures that, in their terminal manufacturing processes, terminal vendors:

• Properly identify each IFM and terminal.

• Prove that the approved IFM or PayPass card reader sample type is identical to the IFM or PayPass card reader shipped in the terminal product.

• Manage the terminal product configuration, including the IFM and/or PayPass card reader, using a configuration management infrastructure.

• Manufacture every terminal using a stable and controlled process that ensures consistent quality.

• Implement a terminal vendor process for equipment returned from the field, to analyze and react to the causes of equipment failure.

MasterCard issues the MasterCard quality management label when a vendor terminal product has successfully passed the quality assessment procedure.

MasterCard Terminal Integration Process (TIP)

MasterCard Terminal Integration Process ensures that terminals comply with the debit and credit application requirements defined in the MasterCard M/Chip Functional Architecture, PayPass Product guide and M/Chip PayPass acquirer implementation guide. The MasterCard TIP covers the testing of the following aspects:

• brand requirements

• script processing validations (EMV contact only)

• online context related validations

• known field interoperability issues

The acquirer performs terminal integration tests that relate to its final configuration and connection to the final environment (i.e. connected to the acquirer host system). MasterCard then provides the acquirer with the MasterCard Letter of Approval based on the test results.

To perform this testing, MasterCard has defined a series of ETEC tools

• ETEC Subset 1 and Field Interoperability Subset shall be used by customers implementing M/Chip contact.

• ETEC Subset 2 can optionally be used for regression testing by customers implementing M/Chip contact.

• ETEC Subset 6 shall be used by customers implementing PayPass Magnetic Stripe and PayPass OneSMART.




• ETEC Subset 8 shall be used by customers implementing PayPass OneSMART.

Each ETEC card sub set consists of a set of physical test cards and their corresponding scripts. It enables the acquirer to check that payment applications comply with MasterCard requirements.

The ETEC User Manuals describe the MasterCard Terminal Integration process in detail. For more information on these manuals, please contact your TIP specialist or send an email to:

[email protected].

Before performing Terminal Integration testing, members must successfully conduct Phase I Customer System Build-Up testing as part of their ICC network functional testing.

ICC Card Approval

ICC Card Approval assesses the security and tests the functionality, quality and the personalization of an ICC.

ICC Functional Approval

ICC Functional Approval tests the functional aspects of the ICC as defined in M/Chip version 4.0 specifications. The ICC Functional Approval covers the testing of the following aspects:

• Brand requirements

• Script processing (in scope of chip contact)

• Context-sensitive ICC validation during off-line and on-line transaction processing.

• Combination testing for PayPass products

MasterCard accredited laboratories perform the ICC functional tests at the request of the card vendor. The ICC card vendor then submits the laboratory test results to MasterCard, which delivers the related ICC conformity statements if the test results are satisfactory.

mailto:[email protected].




ICC Card Quality Management

MasterCard ICC Card Quality Management ensures that ICCs meet the following criteria:

• Reliability — ICCs must maintain their performance over a reasonable life span.

• Consistent Manufacturing process — MasterCard audits ICC vendor manufacturing processes against QS9000 or ISO9000 requirements.

• Hardware compliance — ICCs are tested against hardware specifications.

The Card Quality Management (CQM) documentation set describes in detail the requirements and procedures listed above. You can order this documentation by emailing your request to [email protected].

ICC Card Personalization Validation

The purpose of the ICC Card Personalization Validation is to test the personalization aspects of the ICC card against the requirements defined, as appropriate, in the M/Chip Functional Architecture, the PayPass Product guide and the M/Chip PayPass issuer implementation guide.

MasterCard performs the ICC Card Personalization Validation tests using card samples provided by the financial institution.

To support the ICC Card Personalization Validation, MasterCard developed the card personalization tool. This tool allows issuers and card personalization bureaus to check the EMV compliance of newly manufactured ICCs. In particular, ECAP can check that:

• issuer data for M/Chip contact and PayPass OneSMART is correctly personalized on the ICC

• the magnetic stripe-data and the equivalent data on the chip are consistent.

During that process, MasterCard ensures that the issuer is making use of a certified personalization bureau.


MasterCard ICC Credit Testing StrategyICC Network Interface Validation (NIV) Testing



ICC Compliance Assessment and Security Testing

ICC Compliance Assessment and Security Testing (CAST) evaluates the security of:

• Chip hardware

• Card operating systems

• Payment application software.

The Compliance Assessment and Security Testing (CAST) documentation describes related requirements and procedures. This documentation is available on MasterCard OnLine®.

Card vendors preparing card implementations must comply with CAST requirements.

ICC Network Interface Validation (NIV) Testing ICC NIV testing focuses on integrating ICC-related functionality with existing member authorization and clearing systems.

While Terminal Type Approval mainly focuses on interaction between ICCs and ICC terminals, ICC Authorization and Clearing System testing ensures that member host systems are fully integrated with network systems to support the complete credit ICC transaction life cycle.

Chapters 2, 3, 4 and 5 describe in detail the requirements and procedures relating to ICC Authorization and Clearing System testing for contact chip implementations. Chapters 6 and 7 describe in detail the requirements and procedures relating to ICC Authorization and Clearing System testing for PayPass Magnetic Stripe implementers. Chapters 8 and 9 describe in detail the requirements and procedures relating to ICC Authorization and Clearing System testing for PayPass OneSMART implementers.

ICC Products and NIV Testing Projects

The NIV testing strategies below assume that the customer already has an operational link with MasterCard for “pure” magnetic stripe transactions that is, transactions generated using a physical magnetic stripe, and has been tested for that operational profile. The customer may then be in a position to wish to implement any combination of the MasterCard supported ICC products.

MasterCard ICC Credit Testing Strategy ICC Network Interface Validation (NIV) Testing



Contact Chip Implementation Only

Before addressing ICC NIV testing for authorization, members must complete the “Customer System Build-up” testing procedures to ensure their host interface properly handles chip authorization messages.

Chapters 2 (Acquirers) and 3 (Issuers) describe Customer System Build-up testing procedures, while Chapters 4 (Acquirers) and 5 (Issuers) describe Transaction Lifecycle testing. These testing procedures complement the test procedures described in the MasterCard Testing Procedures – Credit manual, particularly those that focus on chip-related test cases. You must use the MasterINQ Credit Simulator to perform these procedures.

Acquirers must conduct Transaction Lifecycle testing procedures using chip terminals that have successfully passed terminal level two type approval. These terminals will ensure the system integrity during end-to-end testing with issuers.

PayPass Emulating Magnetic Stripe Chip Only

For NIV testing, customers implementing PayPass Magnetic Stripe only need complete the tests described in chapter 6 for Acquirers and chapter 7 for Issuers. These tests cover the transaction life cycle for the appropriate transactions and are generally executed using the MasterINQ Credit Simulator and the MasterCard Clearing and Presentment Simulator.

Acquirers must conduct testing procedures using terminals that have successfully passed PayPass terminal product approval. Issuer testing does not specify physical cards at this point, so no PayPass approval is required for NIV testing, although card validation testing will be executed as specified by the PayPass Issuer deployment team.

PayPass Implementing Full M/Chip (OneSMART)

Before considering which tests need to be run for customers implementing PayPass OneSMART, it will be useful to consider the types credit of transactions supported by MasterCard and the terminals that Acquirers may use. Identifying these beforehand will help to understand the directions later in this section on which tests to execute.

PayPass OneSMART Transaction Types

The transaction types in Table 1.2 are supported in PayPass. While acquirers may only be supporting some of them, issuers must be ready to accept all of them.




Table 1.2—Transaction types supported in PayPass

Name CVM

Retail POS signature

Retail POS on-line PIN

Manual Cash Advance signature

CAT1 on-line PIN

CAT2 no CVM

CAT3 (off-line only) no CVM

Acquirers must notify MasterCard of the transaction types they will be supporting in the PayPass environment they are deploying.

Requirements for PayPass OneSMART Acquirers

There are two different PayPass OneSMART terminal types. The following table indicates the type of ICC product transactions they support:

Table 1.3—Terminal Types

Terminal Type Pure Magnetic Stripe Contact Chip PayPass OneSMART1

1 Yes2 No Yes

2 Yes3 Yes Yes

Requirements for PayPass OneSMART Issuers

PayPass OneSMART cards must

• support PayPass OneSMART transactions

1 All terminals that support PayPass OneSMART must support PayPass Magnetic Stripe.

2 For technology fallback reasons, the PayPass product specifications require that when a merchant is deploying a PayPass-only capable terminal (either PayPass Magnetic Stripe or PayPass OneSMART only terminal), one the following technologies is used to accept the card i.e. Magnetic Stripe, key entry or imprint facilities.

3 Terminals supporting contact chip transactions shall be equipped with a physical Magnetic Stripe reader for fallback transactions. Fallback transactions are tested as part of the contact chip NIV tests.




• support contact Chip transactions

• support transactions using the PayPass Magnetic Stripe application

• be equipped with a physical Magnetic Stripe

Issuers deploying PayPass OneSMART cards without enrolling in the MasterCard Chip to Magnetic Stripe On Behalf Service PayPass OneSMART cards must be capable of supporting all of the following transaction profiles:

• PayPass OneSMART transactions

• contact Chip transactions including fallback to Magnetic Stripe

• PayPass Magnetic Stripe transactions

• physical Magnetic Stripe transactions

PayPass OneSMART Network Impacts

While all of the PayPass OneSMART impacts on network messages are defined elsewhere, it will be useful to review them here to indicate specific changes that will be examined in the testing.

Authorization Request/0100 Messages

PayPass OneSMART transactions are all full grade chip transactions including Data Element (DE) 55 – ICC System Related Data. In addition, all 0100 messages for PayPass OneSMART must:

• include DE 12 (Time, Local Transaction)

• include DE 13 (Date, Local Transaction)

• include DE 37 (Retrieval reference Number)




• include DE 41 (Card Acceptor Terminal ID)

• DE 22, subfield 1 (POS Terminal PAN Entry Mode) must be “07”

• include DE 23 (Card Sequence Number), if provided by the card to the terminal

• DE 61, subfield 11 (POS Card Terminal Data Input capability) must be “3”

Authorization Request Response/0100 Messages

When an acquirer receives data element 55, ICC System Related Data in the Authorization Response/0110 message for a PayPass OneSMART transaction, they may either send the data to the terminal or discard it, not sending it to the terminal. In either case, the transactions shall complete successfully with an approval or a decline. DE 55 may include Issuer Authentication Data (tag 91) and/or ICC post-issuance commands.

Acquirer Reversal Request/0400 Message and Acquirer Reversal Advice/0420 Message

Banknet 0420 messages are not impacted by PayPass OneSMART implementation. However, for 0420 messages on EPS-net and 0400 messages on BankNet, the new value of “07” must be supported for DE 22, subfield 1 (POS Terminal PAN Entry Mode).

1240 Clearing Presentment and 1420 Chargeback Messages

For clearing, customers need to support a new value of “M” in DE 22, subfield 1 (Card Data Input Capability) and DE 22, subfield 7 (Card data: Input Mode). In addition for PayPass OneSMART, DE 23 and 55 obey the same rules as for contact Chip transaction clearing messages.




PayPass OneSMART NIV Testing Scenarios

Customers will conform to one of the following profiles when beginning PayPass OneSMART implementation:

Table 1-4—PayPass OneSMART Initial Profiles

Profile Description

Initial Profile 1 Member not having done PayPass nor EMV contact before

Initial Profile 2 Member having done PayPass Magnetic Stripe but not EMV chip contact before

Initial Profile 3 Member not having done PayPass but having done EMV chip contact in either Magnetic Stripe grade or chip grade before

Initial Profile 4 Member having done PayPass Magnetic Stripe and EMV chip contact in either Magnetic Stripe grade or chip grade before

NIV Test Strategy

The general NIV test strategy for PayPass OneSMART is based on a test module for each basic profile as follows:

• Basic test module for PayPass OneSMART

• Basic test module for PayPass Magnetic Stripe

• Basic test module for contact chip with M/Chip




Issuer Test Strategy

The bulk of this document contains chapters defining different procedures and test cases for different ICC product deployments. To complete testing to deploy PayPass OneSMART, the customer must complete the Authorizations and Clearing testing specified in the indicated chapter numbers indicated to the right of their initial profile in the following table:

Table 1.5—Member Initial Profile - PayPass OneSMART

Test Chapters to execute for

Member Initial Profile EMV Contact PayPass Magnetic Stripe

PayPass OneSMART

Member having done neither PayPass nor EMV Contact

Chapters 3 and 5 Chapter 7 Chapter 9

Member having done PayPass Magnetic Stripe but not EMV Contact

Chapters 3 and 5 None Chapter 9

Member not having done PayPass but has done EMV Contact in either Magnetic Stripe grade or chip grade

None Chapter 7 Chapter 9

Member has done both PayPass Magnetic Stripe and EMV Contact in either Magnetic Stripe grade or chip grade

None None Chapter 9

Issuers should complete the tests in chapters 3 and 5 before beginning chapter 9. Issuers may execute tests in chapter 7 in parallel with any of the other test chapters.




Acquirer Test Strategy

Acquirer NIV test strategy depends on terminal type being deployed (type 1 or 2 as indicated previously) and existing infrastructure as follows:

Table 1.6—Acquirer NIV test Strategy - Terminal Type

Test Chapters to execute for

Member Initial Profile Terminal Type

EMV Contact PayPass Magnetic Stripe

PayPass OneSMART

1 None Chapter 6 Chapter 8 Member having done neither PayPass Magnetic Stripe nor EMV Contact in full grade mode

2 Chapters 2 and 4

Chapter 6 Chapter 8

1 None None Chapter 8 Member having done PayPass Magnetic Stripe but not EMV Contact in full grade mode

2 Chapters 2 and 4

None Chapter 8

1 None Chapter 6 Chapter 8 Member not having done PayPass Magnetic Stripe but has done EMV Contact in full grade mode

2 None Chapter 6 Chapter 8

1 None None Chapter 8 Member has done both PayPass Magnetic Stripe and EMV Contact in full grade mode

2 None None Chapter 8

MasterCard ICC Credit Testing StrategyICC End-to-End Pre-production Testing



Clearing

ICC Network Functional testing for clearing ensures that:

• chip transactions are properly identified

• chip data (as delivered to the member host via MasterCard network systems) is comprehensive

• chip data corresponds to transaction data captured during the original authorization.

The test cases for this method use data captured during authorization transactions.

To test using this method, members must have:

• converted to the Integrated Product Message (IPM)

• successfully conducted the relevant test procedures.

For different ICC products, different strategies are specified for clearing. In all cases, the clearing tests that a customer should execute are defined in the chapters containing test cases for the members profile as described in the earlier part of this section.

ICC End-to-End Pre-production Testing ICC End-to-End pre-production testing ensures that member systems are ready to accept ICC transactions in production mode, before card issuance, or terminal roll-out, or both.

To ensure that their system is ready to accept ICC transactions in production mode, issuers and acquirers must conduct a series of transactions, using:

• ICCs

• terminals with live keys (in their working environment)

• systems that will be used by the member, in production mode.

ICC End-to-End pre-production testing involves the entire life cycle of a transaction. This life cycle starts at authorization, and passes through clearing and settlement. It tests the entire transaction infrastructure, including:

• the merchant terminal

• the acquirer member infrastructure

MasterCard ICC Credit Testing Strategy ICC End-to-End Pre-production Testing



• the MasterCard network

• the issuer infrastructure.

ICC End-to-End pre-production testing requirements and procedures are not within the scope of this document



2 Chip Acquirer – Customer System Build-Up Testing This chapter describes test procedures and test pre-requisites that ICC acquirers must complete before Transaction Lifecycle testing.

ICC Authorization – Customer System Build-Up Testing ..................................2-1 Test Procedure Pre-requisites .......................................................................2-1 Test Cases and Procedures ...........................................................................2-1

Phase 1 – Basic ISO Message Flow with ICC Data Testing ..................2-2 MasterINQ Credit Authorization Simulator Set-up ..........................2-2

How to use Response Profiles to run Acquirer tests ................2-3 Basic ISO Message Flow with ICC Data Test Cases........................2-5

Phase 2 – Offline Testing with ETEC Subset 3 ......................................2-7 Chip Acquirer –Normal ICC Test Cases...........................................2-8

MasterCard Credit Authorization Simulator Set-up ...................2-8 Chip Acquirer – Exception Case ....................................................2-20


Chip Acquirer – Customer System Build-Up TestingICC Authorization – Customer System Build-Up Testing



ICC Authorization – Customer System Build-Up Testing

Test Procedure Pre-requisites

Acquirers must successfully conduct ICC Authorization Customer System Build-up testing, using related test cases and procedures, before they start Transaction Lifecycle testing using the MasterINQ Credit Authorization Simulator.

Prior to performing ICC Authorization Customer System Build-up testing, acquirers must fulfill the following conditions:

• Check for the latest version of the MasterINQ Credit Authorization Simulator on MasterCard Online®. If you do not have the latest version, please download it from MasterCard Online and install it on your simulator. This software must be available to the acquirer before undertaking the related testing procedures.

• Complete and sign a formal chip implementation project plan with the MasterCard regional chip project manager.

• Connect the acquirer host to the MasterINQ Credit Authorization Simulator using TCP/IP. For more information on installing the simulator and connecting it to the customer host, see the MasterCard Credit Authorization Simulator Guide.

• Establish, in coordination with the CIS Implementation Specialist assigned to this NIV test project, the acquirer member profile and, therefore, the list of applicable test cases. The test cases to be performed depends on:

• the acquirer member profile

• the variety of terminal types being used in conjunction with the acquirer host infrastructure.

Test Cases and Procedures

When the acquirer has fulfilled the testing pre-requisites, ICC Authorization Customer System Build-up testing can start, using the MasterINQ Credit Authorization Simulator. The testing process will ensure that the acquirer authorization application is able to:

• Send ICC Credit Authorization Requests in the correct format

• Process the resulting Authorization Responses.

Chip Acquirer – Customer System Build-Up Testing ICC Authorization – Customer System Build-Up Testing



Phase 1 – Basic ISO Message Flow with ICC Data Testing

The purpose of these tests is to ensure that messages can be successfully exchanged between the acquirer host and the MasterINQ Credit Authorization Simulator. The focus is on the inclusion of the ICC data elements in the Authorization Request message from the acquirer host, and verification that the Authorization Response message from the simulator is correctly processed by the acquirer host. This message flow should not be impacted by the inclusion of the ICC data in the authorization process.

To ensure that basic messages are exchanged correctly with the inclusion of ICC data elements within the authorization request and response messages, acquirers should perform the tests described in Table 2.2.

MasterINQ Credit Authorization Simulator Set-up

To avoid duplication of information, this manual assumes basic familiarity with the MasterINQ Credit Authorization Simulator. For additional information about the features and functions of the simulator, please refer to the MasterCard Credit Authorization Simulator Guide.

The ETEC 3 test card deck is used in conjunction with the Network Integration Process described in this manual.




How to use Response Profiles to run Acquirer tests

To use Response Profiles to run Acquirer tests, proceed as follows:

1. Open the Navigator window, click the Testing tab and select APS Host Testing mode.

Figure 2.1—APS Host Testing

2. Press the Test Results button (as shown in Figure 2.1) to open the Test Results window.

3. Before starting any test using ETEC3 test cards, clear the log (to remove any transaction not related to this test) by pressing the Clear Log icon, as shown in Figure 2.2.




Figure 2.2—Clear Log icon

4. Conduct Network interface validation testing using the ETEC 3 test cards and the test scripts described in the following sections. The simulator will generate Response messages using the Response Profiles.

5. Once the tests are completed, click the Save Log as command in the File menu to save the log file. The suggested name of the file is XXXXX_ETEC3_mmddyy, where “XXXXX” is the ICA and “mmddyy” the test date.

6. Send the XXXXX_ETEC3_mmddyy file to MasterCard for review.

The following section contains a list of the test cases.




Basic ISO Message Flow with ICC Data Test Cases

Note Note: All test cases in this chapter are marked M(andatory) or C(onditional). Acquirers execute the Conditional test cases, only if they support the condition described in the “Transaction” column.

Table 2.1—Basic ISO Message Flow with ICC Data Test Cases

Test ID Transaction Card ID Expected RC in 0110 message

M/C Full grade

Partial grade

Success criteria Comments/ Purpose

CAACQ001 ICC Credit retail signature-based

EC-MC 103

00 C a a The terminal must approve the transaction after IC card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 05x

• DE23 = 000

• DE55 / tag 9F34 (if present) = 1E0000

• DE61 subfield 11 = 5, 8 or 9

Check business transaction format and content





M/C Full grade

Partial grade


CAACQ002 ICC Credit retail offline PIN

EC-MC 101


• DE22 = 051

• DE23 = 000

• DE55 / tag 9F34 (if present) = 010002






Phase 2 – Offline Testing with ETEC Subset 3

In preparation for online testing, which is described in Chapter 4, acquirers must perform the online test cases in an offline mode with the MasterINQ Credit Authorization Simulator first. This will provide an additional level of confidence to acquirers and assist in ensuring efficient online testing sessions.




Chip Acquirer – Normal ICC Test Cases

MasterCard Credit Authorization Simulator Set-up

Follow the same steps as outlined in step 1 above to prepare the simulator to undertake these tests.

Table 2.2—Chip Acquirer – Normal ICC Test Cases


M/C Full grade

Partial grade



EC-MC 103


• DE22 = 05x

• DE23 = 000



• ARQC will be valid for full grade.






M/C Full grade

Partial grade



EC-MC 101


• DE22 = 051

• DE23 = 000





CAACQ003 ICC Credit retail online PIN

EC-MC 104


• DE22 = 051

• DE23 = 000


• DE55 / tag 95 / byte 3 / bit 3 = 1








M/C Full grade

Partial grade


CAACQ004 ICC Credit cash advance signature-based

EC-MC 103


• DE3 = 17xxxx

• DE22 = 05x

• DE23 = 000





CAACQ005 ICC Credit cash advance offline PIN

EC-MC 101


• DE3 = 17xxxx

• DE22 = 051

• DE23 = 000









M/C Full grade

Partial grade


CAACQ006 ICC Credit cash advance online PIN

EC-MC 101


• DE3 = 17xxxx

• DE22 = 051

• DE23 = 000









M/C Full grade

Partial grade


CAACQ007 ICC Credit CAT level 1 retail online PIN

EC-MC 104


• DE3 = 00xxxx

• DE22 = 051

• DE23 = 000


• DE55 / tag 95 / byte 3 / bit 3 = 1


• DE61 subfield 10 = 1







M/C Full grade

Partial grade


CAACQ008 ICC Credit CAT level 1 retail offline PIN

EC-MC 101


• DE22 = 051

• DE23 = 000






CAACQ009 ICC Credit CAT level 2 retail no CVM

EC-MC 105


• DE22 = 05x

• DE23 = 000

• DE55 / tag 9F34 (if present) = 1F0002


• DE61 subfield 10 = 2 ARQC will be valid for full grade.






M/C Full grade

Partial grade



EC-MC 105

N.A. C N.A. N.A. The terminal must approve the transaction after IC card and terminal interaction.

This transaction is not online (CAT level 3 terminal). It shall be performed as a pre-requisite to the ICC clearing tests


EC-MC 105


• DE22 = 05x

• DE23 = 000










M/C Full grade

Partial grade


CAACQ012 ICC Credit business transaction of customer choice

EC-MC 111 or 112

00 M a The terminal must set DE23 in the authorization request message to "1", and approve the transaction after IC card and terminal interaction. The terminal must set the following elements in the 0100 message:

• DE22 = 05x

• DE23 = 001

• DE55 / tag 9F34 (if present) = 410302 or 5E0300 or 420300 or 1F0300

• ARQC will be valid.

Check the acceptance of a non-zero Card Sequence Number





M/C Full grade

Partial grade



EC-MC 113

00 M a The terminal must set the corresponding TVR bits (B2-b6 and B2-b8) in DE55 of the 0100 message to "1". It must go online for the transaction, and approve it after IC card and terminal interaction. The terminal must set the following elements in the 0100 message:

• DE22 = 05x


• DE55 / tag 95 / byte 2 / bit 8 = 1

• DE55 / tag 95 / byte 2 / bit 6 = 1


Check EMV tag 95 for (1) ICC and terminal having different application versions and (2) card application not yet effective





M/C Full grade

Partial grade


CAACQ014 ICC Credit business transaction of customer choice - 3 transactions

EC-MC 114

00 M a The terminal must decline transactions with invalid Issuer Authentication Data, after interaction between the IC card and the terminal. The terminal:

• Approves the first transaction (amount= 2000) and uses it to reset the card status (CVR in 9F10 = A42004)

• Uses the second transaction (use any amount but 2000) to get an invalid IAD. The terminal must decline this transaction

• Uses the third transaction (amount = 2000) to verify that CVR in 9F10 = A42804 (corresponding to invalid IAD at previous transaction)

Check EMV tag 95 for invalid processing of the Issuer Authentication Data


EC-MC 115

00 M a The terminal must approve the transaction.

Check issuer authorization response with no ICC system related data (DE 055) after a full grade request





M/C Full grade

Partial grade



EC-MC 116

00 M a The terminal must approve both transactions. It must then increment the issuer script command counter in CVR (B4-b8tob6) between the 2 transactions. ARQC will be valid for both transactions.

Check receipt of response containing issuer script data (less than or equal to 25 bytes in length)1

CAACQ017 ICC Credit business transaction of customer choice – 2 transactions

EC-MC 117

00 M a The terminal must approve both transactions. The terminal must increment the issuer script command counter in CVR (B4-b8tob6) by 2 between the 2 transactions. Note that up to 3 transactions may be required to complete this test case (the acquirer may need to use one to reset the script command counter on the card). ARQC will be valid for both transactions.

Check receipt of response containing multiple

Issuer Script Templates.

Each template contains multiple issuer scripts, one of the templates having a total length of scripts being up to, or equal to, 127 bytes.

1 The second transaction is to check that the Issuer Script Command counter has been correctly incremented on the ICC after

processing the response to the first transaction (i.e. to check that the Issuer Script information has been fully and correctly passed to the ICC by the acquirer terminal)





M/C Full grade

Partial grade


CAACQ018 ICC Credit business transaction of customer choice, where fallback is permitted

EC-MC 118

00 M a The terminal must approve the transaction. DE22 in the 0100 request message shall equate "80x"

Check fallback to magnetic stripe on hybrid cards (DE 022='80x')


EC-MC 117

00 C a The terminal must approve the transaction. Optional EMV tags 9F33, 9F34, 9F35, 9F1E, 9F53, 84, 9F09 and 9F41 must be present in DE55 of the 0100 request message (if the terminal supports the functionality for sending all optional tags)

Check authorization request containing optional EMV tags in 0100 request message


EC-MC 117

05 M a Amount has to be 2000.

The terminal must decline the transaction. The terminal must use DE39 of 0110 to decline the transaction while setting the ARPC response code to '3030'

Check authorization request response containing an ARPC response code (in EMV tag 91) that is different from the authorization response code (DE 39) in the 0110.




Chip Acquirer – Exception Case

Use the same MChip Key Set as for the other test cases

Table 2.3—Chip Acquirer – Exception Case


M/C Full grade

Partial grade



EC-MC 119

M` a The terminal must set Tag 9F10 to its maximum length in the 0100 message. Although the response code is set to '00' in the 0110, the terminal will decline the transaction after interaction between the card and the terminal

Check authorization request containing Issuer Application Data set to its maximum length. (IAD is part of EMV tag 9F10).

Since the aim of this test is to verify the Acquirer’s ability to send 32 bytes of the Issuer Application Data (9F10), any cryptogram error message can be ignored.

Upon completion of all test cases, the acquirer must submit the MasterINQ Credit Authorization Simulator log files to MasterCard for validation. Once MasterCard has reviewed the log files generated for this test and confirmed that the testing was successful, acquirers will be authorized to schedule and proceed with online testing with the MasterINQ Credit Authorization Simulator.

Chip Acquirer – Customer System Build-Up TestingICC Clearing – Customer System Build-up Testing



ICC Clearing – Customer System Build-up Testing If acquirers wish to send ICC related data (DE 055) in their clearing presentments they must be using the Integrated Product Message (IPM) format via the MasterCard Global Clearing Management System (GCMS).

There are no additional specific offline testing cases defined for ICC Clearing – Customer System Build-up Testing. Acquirers wishing to provide ICC related data in the clearing presentment transactions should refer to ICC Clearing – Online Testing in Chapter 4 of this manual.



3 Chip Issuer — Customer System Build-Up Testing This chapter describes test procedures and test pre-requisites that ICC issuers must complete prior to addressing the Transaction Lifecycle testing.

Testing Procedure Pre-requisites ........................................................................3-1 Test Cases and Procedures ...........................................................................3-1

Step 1 – Basic ISO Message Flow with ICC Data Testing.....................3-2 MasterINQ Credit Authorization Simulator Set-up ..........................3-2

M/Chip Cryptography ................................................................3-2 Issuer Master Key Setup.............................................................3-4 How to Set up M/Chip Key Set with Issuer’s own keys ..........3-4 How to Run Transactions ..........................................................3-6

Basic ISO Message Flow with ICC Data Test Cases......................3-10 Step 2 – Offline Testing........................................................................3-11

MasterCard Credit Authorization Simulator Set-up........................3-11 Chip Issuer – Normal ICC Test Cases ............................................3-11 Chip Issuer – Exception Case ........................................................3-15

M/Chip Cryptography ..............................................................3-15


Chip Issuer — Customer System Build-Up TestingTesting Procedure Pre-requisites



Testing Procedure Pre-requisites Issuers must successfully conduct ICC Authorization Customer System Build-up testing, using related test cases and procedures, before they start Transaction Lifecycle testing using the MasterINQ Credit Authorization Simulator.

Prior to performing ICC Authorization Customer System Build-up testing, issuers must fulfill the following conditions:

• Obtain the MasterINQ Credit Authorization Simulator (version 4.2 or higher). This software must be available to the issuer before undertaking the related testing procedures.

• Complete and sign a formal chip implementation project plan with the MasterCard regional chip project manager.

• Connect issuer host to the MasterINQ Credit Authorization Simulator using TCP/IP. For more information on installing the simulator and connecting it to the customer host, see the MasterCard Credit Authorization Simulator User Guide.

• The test cases to be performed depend on the issuer member profile and, in particular, on the types of script commands or applications supported on the chip cards to be issued. The issuer member profile and, therefore, the list of applicable test cases, must be established in coordination with your regional operations manager.

Test Cases and Procedures

When the issuer has fulfilled the testing pre-requisites, ICC Authorization Customer System Build-up testing can start using the MasterINQ Credit Authorization Simulator. The testing process will ensure that the issuer authorization application is able to:

• Receive ICC Credit Authorization Request messages

• Return correctly formatted ICC Credit Authorization Response messages.

Note The MasterINQ Credit Authorization Simulator will validate the structure and format of issuer scripts sent in tags 71 and 72 in DE55 of the 0110/Authorization Response message. The Simulator will not validate the script instructions sent in these tags or verify whether the instructions sent were successfully processed by the issuer’s smart card.

Chip Issuer — Customer System Build-Up Testing Testing Procedure Pre-requisites



Step 1 – Basic ISO Message Flow with ICC Data Testing

The purpose of these tests is to ensure that messages can be successfully exchanged between the issuer host and the MasterINQ Credit Authorization Simulator. The focus is on the inclusion of the ICC data elements in the Authorization Request message sent to the issuer host, and verification that the Authorization Response message generated by the issuer host is successfully returned to the simulator. This message flow should not be impacted by the inclusion of the ICC data in the authorization process.

MasterINQ Credit Authorization Simulator Set-up

To avoid duplication of information, this manual assumes basic familiarity with the MasterINQ Credit Authorization Simulator. For additional information about the features and functions of the simulator, please refer to the MasterCard Credit Authorization Simulator User Guide.

M/Chip Cryptography

To successfully complete the tests, an issuer must know the type of cryptography used by their chip cards. There are six options available to issuers using M/Chip. Table 3.1 identifies these options. The MasterCard key values are provided in the “MChip Key Set Reference” column.

Example:

The Issuer has M/Chip 2.0 Select cards and is using the key values supplied by MasterCard.

The tester for that issuer must proceed as follows:

1. In the Testing tab of the Navigator window, click the Set Options icon. The Options window opens.

Figure 3.1—Selecting the correct key set




2. Under MChipKeySet_Reference, click on Key Set 92021, as shown in Figure 3.1.

3. Verify that the host system has the same key set values as the simulator.

For information on how to link a test to an M/Chip Key Set, refer to the section “How to Run Transactions”, later in this chapter.

Table 3.1—M/Chip Key Set references

M/Chip Type Description M/Chip Key Set Reference

M/Chip 2.0 Select M/Chip 2.1 Select application

92021

M/Chip 2.1 Lite M/Chip 2.1 Lite application 92022

M/Chip 4.0 M/Chip 4.0 application with EMV96 Session key derivation

92040

M/Chip 4.0 M/Chip 4.0 application with EMV2000 Session key derivation using H=8 and b=4 initialization vector

92041

M/Chip 4.0 M/Chip 4.0 application with EMV2000 Session key derivation using H=16 and b=2 initialization vector

92042

Common Core Definition M/Chip 4.1 application 92043

If the Issuer decides to use their own keys instead of the standard MasterCard keys, they must copy the corresponding M/Chip Key Set from the Reference section to an M/Chip Key Set in the User section and assign a new unique numeric value to that key set. The user must then enter the values of their keys into the relevant fields. For more information, refer to the section “Issuer Master Key Setup”.

Note A Reference section is provided as a template. Data in the Reference section cannot be modified or renamed but can be copied to the User section, where the user is free to make any necessary modifications.




Issuer Master Key Setup

This section describes the setup of the various Issuer Master keys, which are always in Triple DES – double key format. These keys are used to derive ICC Master keys and Session keys for each transaction.

Issuers can provide their own test Issuer Master Key clear key parts to the simulator, if they wish.

The following example illustrates how to set up an M/Chip Key Set when an issuer wants to use their own keys.

How to Set up M/Chip Key Set with Issuer’s own keys

To Set up the M/Chip Key Set with the Issuer’s own keys, proceed as follows:

1. In the Navigator window, click on the Set Options icon.

Figure 3.2—Set Options icon




2. Assuming the issuer has M/Chip 2.1 Select, the user can copy the M/Chip Key Set 91021 from MChipKeySet_Reference to MChipKeySet_User and assign a new ID of 91028.

Figure 3.3—Creating a new M/Chip Key Set in the User folder

3. Once M/Chip Key Set 91028 has been created in the User set, the user can enter the key values for the AC, SMI and SMC keys.

Figure 3.4—Updating the newly added M/Chip Key Set

For more information on entering key values, please refer to the MasterCard Credit Authorization Simulator Guide.

Normally, members only need to set up the M/Chip Key Set once.




How to Run Transactions

To run transactions, proceed as follows:

1. Open the Navigator window, click the Testing tab and select IPS Host Testing mode.

Figure 3.5—Set up Simulator for IPS testing mode

2. Press the Test Preparation button (as shown in Figure 3.5) to open the Test Preparation window.

3. Before starting any issuer test, clear the log (to remove any transaction not related to this test) by pressing the Clear Log icon as shown in Figure 3.6.

Figure 3.6—Clearing the log




In the Test Preparation window, there is a folder containing transactions which match the issuer test cases in this manual. These transactions are grouped by application type (MChip21_Select Group, MChip21_Lite Group, MChip40 Group).

4. Open the appropriate folder (under Issuer Host Test scripts – see Figure 3.7).

Figure 3.7—Choosing Issuer test scripts




5. Customize the records in the Test Preparation window to include issuer-specific data, e.g. Account number (PAN), Card Sequence Number, Track data and PIN data. See Figure 3.8.

Figure 3.8—Customizing data in the test cases

6. Prior to submitting the transactions, link the correct key set to the transactions to be processed, using an Instruction command, which can be selected from the Test Preparation window.

Figure 3.9—Instruction command on the Test Preparation window




7. Select the SetMChipKeySet command then click the arrow to the right of the key set box and select the correct key set from the drop-down list that appears. In the example below, the Instruction points to M/Chip Key Set 91028. All transactions will therefore use the key values in 91028 for all cryptographic computation.

Figure 3.10—Updating the Instruction command

8. When the tests are completed, copy the “log.mdb” log to a new “mdb” file. The suggested name of the file is XXXXX_IssuerChip_mmddyy, where “XXXXX” is the ICA and “mmddyy” the test date.

9. Send the XXXXX_IssuerChip_mmddyy file to MasterCard for review.

The simulator is now configured to perform the basic ISO message flow with ICC data test cases.




Basic ISO Message Flow with ICC Data Test Cases

Note All test cases in this chapter, with the exception of CAISS019, are mandatory. Issuers must execute CAISS019 only if they intend to send scripts to their cards in a live environment in the future.

Table 3.2—Basic ISO Message Flow with ICC Data Test Cases

Test ID Transaction Card ID Retrieval Reference Number

RC in 0110 message

Success criteria Comments/Purpose

CAISS001 ICC Credit retail signature

MC:101-105

CAISS0010001 00 Transaction is approved

ARQC must be successfully validated and Valid ARPC returned in 0110

Full grade - Check business transaction format and content

CAISS002 ICC Credit retail offline PIN

MC:101-105







Step 2 – Offline Testing

In preparation for online testing, which is described in Chapter 5, issuers must perform the online test cases in an offline mode with the MasterCard Credit Authorization Simulator first. This provides an additional level of confidence for issuers and it will assist in ensuring efficient online testing sessions - reducing time-to-market and minimizing online testing fees.

MasterCard Credit Authorization Simulator Set-up

Follow the same steps as outlined in step 1 to prepare the simulator to undertake these tests.

Chip Issuer – Normal ICC Test Cases

Table 3.3—Chip Issuer – Normal ICC Test Cases


Expected RC in 0110 message



MC:101-105





MC:101-105




CAISS003 ICC Credit retail CAT Level 1 online PIN

MC:101-105










CAISS004 ICC Credit retail CAT Level 1 offline PIN

MC:101-105




CAISS005 ICC Credit retail CAT Level 2 no CVM

MC:101-105





MC:101-105




CAISS007 ICC Credit cash advance signature

MC:101-105




CAISS008 ICC Credit cash advance offline PIN

MC:101-105





MC:101-105

CAISS0090001 00 Transaction is approved Partial grade


MC:101-105

CAISS0100001 00 Transaction is approved Partial grade - Check business transaction format and content








MC:101-105



MC:101-105



MC:101-105



MC:101-105



MC:101-105


CAISS016 ICC Credit cash advance offline PIN

MC:101-105









MC:101-105



Full grade - Transaction contains only the mandatory data elements. However, to ensure proper cryptogram validation EMV tag 9F10 is present

CAISS018 ICC Credit retail online PIN (e.g. fuel pump)

MC:101-105



Full grade - Transaction contains mandatory and optional data elements


MC:106 CAISS0190001 00 Transaction is approved

ARQC must be successfully validated, Valid ARPC and valid ICC issuer scripts are returned in 0110

Full grade - Check issuer returns one or more issuer script command in the authorization response


MC:101-105

CAISS0210001 00 Transaction is approved Partial grade – Containing only the mandatory data elements


MC:101-105

CAISS0220001 00 Transaction is approved Partial grade – Containing all mandatory and optional data elements


MC:101-105

CAISS0230001 00 Transaction is approved Fallback to magnetic stripe on hybrid cards (DE 022 = '80x')




Chip Issuer – Exception Case

To perform this exception test case, issuers can use any test case previously used with a modified AC keys.

M/Chip Cryptography

Use the following steps to alter the clear key parts for the Master Keys to produce the desired test result of sending a bad ARQC to the issuer host:

1. Go to Set Options and click on the MChip Key Set tab.

2. Go to the MChip Key Set created at the beginning of the Issuer test.

3. Open the AC keys and re-enter the values of the keys, with the last character of that key being altered to create a key different from what is on your issuing host.

4. Click OK.

Table 3.4—Chip Issuer – Exception Test Case

Test ID Transaction Expected RC in 0110 message Success Criteria Comments/Purpose

Exception Case Any valid transaction used in Network Validation testing

57 Transaction is declined. ARPC not present in 0110

Full grade – invalid ARQC

Upon completion of all test cases, the issuer must submit the MasterINQ Credit Authorization Simulator log files to MasterCard for validation. Once MasterCard has reviewed the log files, and has confirmed that the testing was successful, issuers will be authorized to schedule and proceed with online testing using the MasterINQ Credit Authorization Simulator.

Chip Issuer — Customer System Build-Up TestingICC Clearing – Customer System Build-up Testing



ICC Clearing – Customer System Build-up Testing There are no specific offline test cases defined for ICC Clearing – Customer System Build-up Testing. Issuers wishing to receive ICC related data in the clearing presentment transactions should refer to ‘ICC Clearing – Online Testing’ in Chapter 5 of this manual.



4 Chip Acquirer — Transaction Lifecycle Testing This chapter describes test pre-requisites, procedures and test cases that ICC acquirers must fulfill and successfully complete to validate correct interfacing of the ICC functionality of their host systems with MasterCard network systems.


Testing Procedure Pre-requisites ..................................................................4-1 Test Procedures.............................................................................................4-1 Test Cases ......................................................................................................4-2

ICC Clearing — Transaction Lifecycle Testing.................................................4-16 Testing Procedure Pre-requisites ................................................................4-16 Test Procedures...........................................................................................4-16 Test Cases ....................................................................................................4-17

Chip Acquirer — Transaction Lifecycle TestingICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator

Testing Procedure Pre-requisites

Prior to performing the ICC Authorization Transaction Lifecycle testing, acquirers must fulfill the following conditions:

• Successfully complete the test cases described in Chapter 2.

• Have available the ETEC cards - subset 3 used for the test cases executed in Chapter 2.

• If executing offline testing, connect the acquirer host to the MasterINQ Credit Authorization Simulator. For more information on installing the simulator and connecting it to the acquirer host, see the MasterCard Credit Authorization Simulator Guide.

• If executing online testing, coordinate with the CIS Implementation Specialist assigned to this project to schedule testing and agree support to connect to, and use, the MasterCard Test Facility (MTF).

• Ensure that only terminals that have successfully passed Terminal Level 2 Type Approval testing (including MasterCard Terminal Integration Process testing) are used during the testing cycle.

Test Procedures

Acquirers must follow the procedures described below to perform Transaction Lifecycle testing using the MasterINQ Credit Authorization Simulator:

1. Determine the terminal’s profile. Based on the terminal types supported on the host infrastructure, the acquirer must work with the MasterCard CIS Implementation Specialist assigned to this project to determine the test cases to be run to mirror production scenarios.

2. Connect the ICC acquirer host to the MasterINQ Credit Authorization Simulator to conduct Transaction Lifecycle testing.

Note Acquirers may not be able to conduct regular or standard non-ICC testing in parallel with chip testing if executing online with MTF.

Chip Acquirer — Transaction Lifecycle Testing ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



As soon as the acquirer completes his set-up, the MasterINQ Credit Authorization Simulator system can run unattended as an issuer. The MasterINQ Credit Authorization Simulator is therefore always available for acquirer testing.

3. Schedule formal testing with the MasterCard regional operations manager, as soon as all individual tests have been successfully performed.

Technical expertise and support services are available for the duration of the scheduled testing.

Test Cases

The following tables provide all the required data for test cases. These test cases are designed to ensure that your acquirer authorization application is able to:

• Send correctly formatted ICC Credit Authorization Requests

• Process the resulting Authorization Responses

The test cases model your business activities. They include transactions commonly encountered as well as less common conditions that relate to the authorization system.

Note For partial grade transactions, DE23 and DE55 are not present in the Authorization Request/0100 message. Acquirers should read the success criteria accordingly. Since January 1, 2006, partial grade Chip Acquirer implementations are no longer allowed. The column specifying these cases is included for historical reference only.

Note All test cases in this chapter are marked mandatory (M) or conditional (C). Acquirers must execute the conditional tests only if they support the condition described in the “Transaction” column.




Table 4.1—Acquirer Test Cases


M/C Full grade

Partial grade



EC-MC 103


• DE22 = 05x

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9




EC-MC 101


• DE22 = 051

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9







M/C Full grade

Partial grade


CAACQ003 ICC Credit retail online PIN

EC-MC 104


• DE22 = 051

• DE23 = 000


• DE55 / tag 95 / byte 3 / bit 3 = 1

• DE61 byte 11 = 5, 8 or9



CAACQ004 ICC Credit cash advance signature-based

EC-MC 103


• DE3 = 17xxxx

• DE22 = 05x

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9







M/C Full grade

Partial grade


CAACQ005 ICC Credit cash advance offline PIN

EC-MC 101


• DE3 = 17xxxx

• DE22 = 051

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9



CAACQ006 ICC Credit cash advance online PIN

EC-MC 101


• DE3 = 17xxxx

• DE22 = 051

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9







M/C Full grade

Partial grade


CAACQ007 ICC Credit CAT level 1 retail online PIN

EC-MC 104


• DE3 = 00xxxx

• DE22 = 051

• DE23 = 000


• DE55 / tag 95 / byte 3 / bit 3 = 1

• DE61 byte 11 = 5, 8 or 9

• DE61 byte 10 = 1







M/C Full grade

Partial grade


CAACQ008 ICC Credit CAT level 1 retail offline PIN

EC-MC 101


• DE22 = 051

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9

• DE61 byte 10 = 1




EC-MC 105


• DE22 = 05x

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9

• DE61 byte 10 = 2







M/C Full grade

Partial grade



EC-MC 105

N.A. C N.A. N.A. The terminal must approve the transaction after IC card and terminal interaction.

This transaction is not online (CAT level 3 terminal). It shall be performed as a pre-requisite to the ICC clearing tests


EC-MC 105


• DE22 = 05x

• DE23 = 000


• DE61 byte 11 = 5, 8 or 9

• DE61 byte 10 = 4







M/C Full grade

Partial grade



EC-MC 111 or 112

00 M a The terminal must set DE23 in the authorization request message to "1", and approve the transaction after IC card and terminal interaction. The terminal must set the following elements in the 0100 message:

• DE22 = 05x

• DE23 = 001



Check the acceptance of a non-zero Card Sequence Number





M/C Full grade

Partial grade



EC-MC 113

00 M a The terminal must set the corresponding TVR bits (B2-b6 and B2-b8) in DE55 of the 0100 message to "1". It must go online for the transaction, and approve it after IC card and terminal interaction. The terminal must set the following elements in the 0100 message:

• DE22 = 05x


• DE55 / tag 95 / byte 2 / bit 8 = 1

• DE55 / tag 95 / byte 2 / bit 6 = 1


Check EMV tag 95 for (1) ICC and terminal having different application versions and (2) card application not yet effective





M/C Full grade

Partial grade



EC-MC 114

00 M a The terminal must decline transactions with invalid Issuer Authentication Data, after interaction between the IC card and the terminal. The terminal:

• Approves the first transaction (amount = 2000) and uses it to reset the card status (CVR in 9F10 = A42004)

• Uses the second transaction (use any amount but 2000) to get an invalid IAD. The terminal must decline this transaction

• Uses the third transaction (amount = 2000) to verify that CVR in 9F10 = A42804 (corresponding to invalid IAD at previous transaction)

Check EMV tag 95 for invalid processing of the Issuer Authentication Data





M/C Full grade

Partial grade



EC-MC 115

00 M a The terminal must approve the transaction. ARQC will be valid.

Check issuer authorization response with no ICC system related data (DE 055) after a full grade request


EC-MC 116

00 M a The terminal must approve both transactions. It must then increment the issuer script command counter in CVR (B4-b8tob6) between the 2 transactions. ARQC will be valid for both transactions.

Check receipt of response containing issuer script data (less than or equal to 25 bytes in length)1

1 The second transaction is to check that the Issuer Script Command counter has been correctly incremented on the ICC after processing the response

to the first transaction (i.e. to check that the Issuer Script information has been fully and correctly passed to the ICC by the acquirer terminal)





M/C Full grade

Partial grade



EC-MC 117

00 M a The terminal must approve both transactions. The terminal must increment the issuer script command counter in CVR (B4-b8tob6) by 2 between the 2 transactions. Note that up to 3 transactions may be required to complete this test case (the acquirer may need to use one to reset the script command counter on the card). ARQC will be valid for both transactions.

Check receipt of response containing multiple issuer script templates.

Each template contains multiple issuer scripts, one of the templates having a total length of scripts being up to, or equal to, 127 bytes.2


EC-MC 118

00 M a The terminal must approve the transaction. DE22 in the 0100 request message shall equate "80x".

Check fallback to magnetic stripe on hybrid cards (DE 022='80x')

2 The second transaction is to check that the Issuer Script Command counter has been correctly incremented on the ICC after

processing the response to the first transaction (i.e. to check that the Issuer Script information has been fully and correctly passed to the ICC by the acquirer terminal)





M/C Full grade

Partial grade



EC-MC 117

00 C a The terminal must approve the transaction. Optional EMV tags 9F33, 9F34, 9F35, 9F1E, 9F53, 84, 9F09 and 9F41 must be present in DE55 of the 0100 request message (if the terminal supports the functionality for sending all optional tags). ARQC will be valid.

Check authorization request containing optional EMV tags in 0100 request message


EC-MC 119

M` a The terminal must set Tag 9F10 to its maximum length in the 0100 message. Although the response code is set to '00' in the 0110, the terminal will decline the transaction after interaction between the card and the terminal. Response contains result of issuer processing in

Additional Processing Results (PDS 74 in

DE 048). Although the expected RC = ‘00’, the transaction will be declined by the ICC.

Check authorization request containing Issuer Application Data set to its maximum length. (IAD is part of EMV tag 9F10).





M/C Full grade

Partial grade



EC-MC 117

05 M a Amount has to be 2000.

The terminal must decline the transaction. The terminal must use DE39 of 0110 to decline the transaction while setting the ARPC response code to '3030'

Check authorization request response containing an ARPC response code (in EMV tag 91) that is different from the authorization response code (DE 39) in the 0110.

Chip Acquirer — Transaction Lifecycle Testing ICC Clearing — Transaction Lifecycle Testing



ICC Clearing — Transaction Lifecycle Testing


Prior to performing the Transaction Lifecycle testing, acquirers must:

• Obtain the MasterCard Clearing Presentment Simulator (MCPS). The order form for the MCPS can be obtained via MasterCard OnLine™ at www.mastercardonline.com. For options for online testing, please contact the MasterCard CIS Implementation Specialist assigned to this project.

• Be able to successfully use the Integrated Product Message (IPM) format for clearing. The acquirer must perform the related test cases listed in the IPM test guide.

Test Procedures

Figure 4.1—General Acquirer Testing Scheme

MasterINQ Credit Simulator

MasterCard Clearing and Presentment Simulator

Acquirer’s Authorization and Clearing Systems

Card Reading Terminal

Subm

it Tr

ansa

ctio

ns

usin

g ET

EC3

Car

ds

Cre

dit

Sim

ulat

or

Acts

as

Issu

er

Submit First Presentment File to MCPS for Validation

Clearing System Creates First

Presentment File

http://www.mastercardonline.com/

Chip Acquirer — Transaction Lifecycle TestingICC Clearing — Transaction Lifecycle Testing



Figure 4.1 shows the general scheme for acquirer clearing testing. The following are the specific steps that the acquirer must perform to test the ICC Acquirer Clearing Transaction Lifecycle:

1. Based on the terminal types supported on the acquirer’s host infrastructure, the acquirer must work with the MasterCard CIS Implementation Specialist to determine the test cases to perform with that terminal.

2. Execute the equivalent authorization test for each clearing test agreed to in step 1. These test cases should be executed using the acquirer’s terminal with the MasterINQ Credit Authorization Simulator acting as the Issuer.

3. Use the test transactions to create a file of First Presentment records from the acquirer’s clearing system. These records will contain clearing records which may include DE55.

4. Submit the First Presentment file to MasterCard Clearing and Presentment Simulator to validate the overall format of the outgoing file using the CEE component of the MCPS.

5. Submit results of the successful tests to MasterCard for validation based on the test schedule agreed with MasterCard.

Technical expertise and support services are available for the duration of the testing period.

Test Cases

By performing the following test cases, acquirers will ensure that their clearing and settlement applications can build and send valid outgoing files, made from correctly formatted ICC clearing messages containing DE0553.

When DE22 is present in presentment message MasterCard will ensure the following checks are made:

• DE22 subfield 1 shall be equal to "5", "C", "D" or "E"

• DE22 subfield 7 shall be equal to “2”, "C" or “F”

• DE22 subfield 10 shall be equal to "3".

3 DE055 presence denotes a full grade transaction. Partial grade test cases and procedures

are addressed as part of IPM testing.




The test cases cover business transactions commonly encountered in your business activities, and all message types impacted by ICC-based operations.

Acquirers must conduct these test cases for:

• Traffic other than inter-regional non-ATM credit

• Inter-regional non-ATM credit traffic.

The following two tables list the test cases.

Note To find out how to validate the cryptogram in each clearing message, please refer to the section “Validate DE55 Cryptogram” in the MasterCard Clearing and Presentment Simulator Guide available with the simulator or from MasterCard Online.

Chip Acquirer — Transaction Lifecycle TestingICC Clearing — Transaction Lifecycle Testing



Table 4.2—1240 Presentment Messages

Test ID Equivalent Auth Test ID Transaction M/C Success Criteria Comments/Purpose

CCACQ001 CAACQ001 ICC Credit retail signature-based

C The presentment message must be accepted. Cryptogram will validate correctly.


CCACQ002 CAACQ002 ICC Credit retail offline PIN



CCACQ003 CAACQ004 ICC Credit cash advance signature



CCACQ004 CAACQ005 ICC Credit cash advance offline PIN



CCACQ005 CAACQ007 or CAACQ008 ICC Credit CAT level 1 retail offline or online PIN



CCACQ006 CAACQ009 ICC Credit CAT level 2 retail no CVM

C The presentment message must be accepted. Cryptogram






will validate correctly.







Table 4.3—Reversal Messages

Test ID Transaction M/C Success Criteria Comments/Purpose

CCACQ009 Any agreed test from Table 4.2

Full reversal of presentment

M The reversal message must be accepted


4 This transaction is an offline transaction. To include this transaction in the First Presentment file exported from the acquirer’s clearing system to

the Clearing Simulator, the record must be transmitted from the authorizing terminal to the Credit Simulator using the batch file transfer capability of the acquirer’s terminal. Please refer to the reference manual for your terminal for instructions on how to transmit the batch file.



5 Chip Issuer — Transaction Lifecycle Testing This chapter describes test pre-requisites, procedures and test cases that ICC issuers must fulfill and successfully complete to validate the correct interfacing of the ICC functionality of their host systems with MasterCard network systems.



ICC Clearing — Transaction Lifecycle Testing...................................................5-6 Testing Procedure Pre-requisites ..................................................................5-6 Test Procedures.............................................................................................5-7 Test Cases ......................................................................................................5-9

Chip Issuer — Transaction Lifecycle TestingICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator


Prior to performing the ICC authorization Transaction Lifecycle testing, issuers must fulfill the following conditions:

• Successfully complete all test cases for Chip Issuer — Customer System Build-up testing, as described in Chapter 3.

• Make issuer test card data available to MasterCard. For this purpose, the issuer must complete and return the relevant Information to the MasterCard regional office. For more information, refer to Appendix A.

Test Procedures

Test procedures are as follows:

• If performing offline testing, connect the issuer host to the MasterCard Credit Authorization Simulator. For more information on installing the simulator and connecting it to the acquirer host, see the MasterCard Credit Authorization Simulator Guide.

• If executing online testing, coordinate with the CIS Implementation Specialist assigned to this project to schedule testing and for support to connect to and use the MasterCard Test Facility (MTF).

Technical expertise and support service is available during the scheduled test slot.

Note Note that you cannot conduct regular or standard non-ICC testing in parallel with chip testing when using MTF.

Chip Issuer — Transaction Lifecycle Testing ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



Test Cases

Note All test cases in this chapter, with the exception of CAISS019, are mandatory. Issuers must execute CAISS019 only if they intend to send scripts to their cards in a live environment in the future.

Table 5.1—Test Case for Test ID




MC:101-105 00 Transaction is approved
































CAISS008A ICC Credit cash advance offline PIN




CAISS008B ICC Credit cash advance online PIN





MC:101-105 00 Transaction is approved Partial grade - Check business transaction format and content





Chip Issuer — Transaction Lifecycle Testing ICC Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator













CAISS016A ICC Credit cash advance offline PIN


CAISS016B ICC Credit cash advance online PIN





Full grade - Transaction contains only the mandatory data elements. However, to ensure proper cryptogram validation EMV tag 9F10 is present









Full grade - Transaction contains mandatory and optional data elements


MC:106 00 Transaction is approved

ARQC must be successfully validated, Valid ARPC and valid ICC issuer scripts are returned in 0110

Full grade - Check issuer returns one or more issuer script command in the authorization response


MC:101-105 57 Transaction is declined. ARPC may not be present in 0110 depending on ICC card application specification

Full grade - Bad ARQC


MC:101-105 00 Transaction is approved Partial grade – Containing only the mandatory data elements


MC:101-105 00 Transaction is approved Partial grade – Containing all mandatory and optional data elements


MC:101-105 00 Transaction is approved Fallback to magnetic stripe on hybrid cards (DE 022 = '80x')

Chip Issuer — Transaction Lifecycle Testing ICC Clearing — Transaction Lifecycle Testing



ICC Clearing — Transaction Lifecycle Testing


Issuers must fulfill the following conditions before undertaking ICC Clearing — Transaction Lifecycle testing:

• Obtain the MasterCard Clearing Presentment Simulator (MCPS). Issuers need this to conduct ICC Issuer Clearing Transaction Lifecycle testing procedures.

The MCPS is available via MasterCard OnLine® (www.mastercardonline.com) in the Featured Products & Services section. Click the MasterCard Simulator Suite link to open the download page, then click the Order/Update link beside MasterCard Clearing Presentment Simulator.

For options for online testing, please contact the MasterCard CIS Implementation Specialist assigned to this project.

• Be able to successfully use the Integrated Product Message (IPM) format for clearing. The issuer must perform the related test cases listed in the IPM Test Guide.


Chip Issuer — Transaction Lifecycle TestingICC Clearing — Transaction Lifecycle Testing



Test Procedures

Figure 5.1—General Issuer Clearing Testing Scheme

MasterINQ Credit Simulator MasterCard Clearing and Presentment Simulator

Issuer’s Authorization and Clearing Systems

Use Credit Simulator to Create Transaction Log

Cre

ate

Firs

t Pr

esen

tmen

t File

usi

ng

MC

PS a

nd S

ubm

it to

C

lear

ing

Syst

em

Create C

hargeback

File and Validate using M

CPS

Figure 5.1 shows the general scheme for Issuer Clearing testing. The following are the specific steps that the acquirer must perform to test the ICC Issuer Clearing Transaction Lifecycle:

1. Execute the indicated authorization test for each clearing test as indicated in Table 5.2. These test cases should be executed on the MasterINQ Credit Authorization Simulator.

2. Create an output file from the MasterINQ Credit Authorization Simulator for import into the MasterCard Clearing and Presentment Simulator. For more information about creating this file, please refer to the “Generating a History Log as a Text File” Section, in Chapter 4 of the MasterCard Credit Authorization Simulator manual, available with the simulator or from MasterCard Online.




3. Create the Clearing Incoming File by importing the file created on the MasterINQ Credit Authorization Simulator in step 2 into the MasterCard Clearing and Presentment Simulator (MCPS). For more information about importing the file, please refer to the “Authorization Message Conversion” section in Chapter 4 of the MasterCard Clearing Presentment Simulator Guide available with the simulator or from MasterCard Online. These records will contain clearing records which may include DE55.

4. Submit the incoming file (1240 messages) to the Issuer’s Clearing system. All records should process correctly.

5. Generate a 1442 chargeback message for each of the 1240 messages in the incoming file from the Issuer’s Clearing system.

6. Submit the Chargeback file created in step 5 to MCPS and confirm that it was validated.




Test Cases

The following test cases are designed to ensure that your issuer clearing and settlement application is able to receive and process a valid incoming file. To be valid, the incoming file must contain ICC clearing messages that, in turn, contain DE055 — ICC System Related Data1. These test cases and message types mirror the types of business transaction that issuers encounter in their ICC–related activities.

Note For Test Case CISSP005: CAT Level 3 devices like that used in CISSP005 always authorize offline. To create this clearing test case, copy the First Presentment record used for test case CISSP004 and make the following modifications:

Data element 22, subfield 7 should be “F”.

Byte 3 of the Issuer Application data (Data Element 55, tag 9F10) should be “95”.


Test ID Equivalent Auth Test ID Transaction Success Criteria Comments/Purpose

CCISSP001 CAISS001 ICC Credit retail signature-based

The presentment message, including DE55, must be accepted by the issuer host. If the cryptogram 9F26 is validated, the validation must be correct


1 DE055 presence denotes an ICC full grade transaction. Partial grade test cases and procedures are addressed as part of IPM testing.




Test ID Equivalent Auth Test ID Transaction Success Criteria Comments/Purpose

CCISSP002 CAISS002 ICC Credit retail offline PIN



CCISSP003 CAISS004 ICC Credit CAT Level 1 retail offline PIN



CCISSP004 CAISS005 ICC Credit CAT Level 2 retail no CVM



CCISSP005 See note for Test Case CCISSP005 above

ICC Credit CAT Level 3 retail no CVM



CCISSP006 CAISS006 ICC Credit CAT Level 4 retail no CVM



CCISSP007 CAISS007 ICC Credit cash advance signature-based



CCISSP008A CAISS008A ICC Credit cash advance offline PIN



CCISSP008B CAISS008B ICC Credit cash advance offline PIN






Table 5.3—1442 Chargeback messages

Test ID Transaction Success Criteria Comments/Purpose

CCISSC101 ICC Credit retail signature-based

The chargeback message is not rejected. If DE55 is present in the chargeback message, then it must correspond to the 1st presentment message.


CCISSC102 ICC Credit retail offline PIN



CCISSC103 ICC Credit CAT Level 1 retail offline PIN



CCISSC104 ICC Credit CAT Level 2 retail no CVM

The chargeback message is not rejected.

If DE55 is present in the chargeback message, then it must correspond to the 1st presentment message.








If DE55 is present in the charge-back message, then it must correspond to the 1st presentment message.


CCISSC107 ICC Credit cash advance signature-based








CCISSC108A ICC Credit cash advance offline PIN




CCISSC108B ICC Credit cash advance online PIN






6 PayPass Acquirer — Magnetic Stripe Testing This chapter describes test pre-requisites, procedures and test cases that acquirers must fulfill and successfully complete to validate correct interfacing of the PayPass Magnetic Stripe functionality of their host systems with MasterCard network systems.



PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing — MasterCard Clearing and Presentation Simulator...............................................6-8

Testing Procedure Pre-requisites ..................................................................6-8 Test Procedures.............................................................................................6-9 Test Cases ....................................................................................................6-10

PayPass Acquirer — Magnetic Stripe TestingPayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization

Simulator



PayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator


Prior to performing the PayPass Magnetic Stripe Authorization Transaction Lifecycle testing, acquirers must fulfill the following condition:

• Purchase and make available ETEC cards - subset 6. Please contact your PayPass Deployment team representative to obtain these cards.

Test Procedures


1. Select a terminal approved for PayPass Magnetic Stripe use. Information on all approved PayPass products may be found on www.paypass.com, Approved PayPass Products. All Acquirers should work with their MasterCard PayPass Acquirer/Merchant deployment team to select products for use prior to testing.

2. If testing offline, connect the PayPass Magnetic Stripe acquirer host to the MasterINQ Credit Authorization Simulator to conduct Transaction Lifecycle testing.


3. If executing online testing, coordinate with the CIS Implementation Specialist assigned to this project to schedule testing and for support to connect to and use the MasterCard Test Facility (MTF).



PayPass Acquirer — Magnetic Stripe Testing PayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



Test Cases


• Send correctly formatted PayPass Magnetic Stripe Credit Authorization Requests

• Process the resulting Authorization Responses.


Note All test cases in this chapter are mandatory (M).

Each test case, except where indicated, must be run using the PayPass Magnetic Stripe contactless capability as well as using the physical Magnetic Stripe as a “fallback”. Results are given for both tests.

Test cases PPMSACQMC007, PPMSACQMC008 and PPMSACQMC009 must be run in succession with card EC-MC 356 to generate the correct results.

PayPass Acquirer — Magnetic Stripe TestingPayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator





Contactless Magnetic Stripe Fallback

Success criteria: Contactless

Success/criteria: Fallback

PPMSACQMC001

PayPass Magnetic Stripe Credit Retail

EC-MC 351

00 a a The terminal must approve the transaction after PayPass Magnetic Stripe card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 91x

• DE61, SE11 = 4

The terminal must approve the transaction after PayPass Magnetic Stripe card used with physical Magnetic Stripe It must set the following elements in the 0100 message:

• DE22 = 90x

• DE61, SE11 = 4

PPMSACQMC002

PayPass Magnetic Stripe Credit Retail – Maximum Track Data Sizes– Service Code 205

EC-MC 352


• DE22 = 91x

• DE61, SE11 = 4


• DE22 = 90x

• DE61, SE11 = 4








PPMSACQMC003

PayPass Magnetic Stripe Credit Retail – Declined Transaction

EC-MC 352

51 a a The terminal must decline the transaction after PayPass Magnetic Stripe card and terminal interaction.

The terminal must decline the transaction after PayPass Magnetic Stripe card used with physical Magnetic Stripe

PPMSACQMC004

PayPass Magnetic Stripe Credit Retail – Service Code 502

EC-MC 353


• DE22 = 91x

• DE61, SE11 = 4


• DE22 = 90x

• DE61, SE11 = 4

PPMSACQMC005

PayPass Magnetic Stripe Credit Retail – Service Code 601

EC-MC 354


• DE22 = 91x

• DE61, SE11 = 4


• DE22 = 90x

• DE61, SE11 = 4








PPMSACQMC006

PayPass Magnetic Stripe Credit Retail – Service Code 817 – Maximum Track Data Sizes

EC-MC 354


• DE22 = 91x

• DE61, SE11 = 4


• DE22 = 90x

• DE61, SE11 = 4

PPMSACQMC007

PayPass Magnetic Stripe Credit Retail – Service Code 101 – ATC Test Case 1

EC-MC 356


• DE22 = 91x

• DE61, SE11 = 4

Discretionary Data ATC must be 1


• DE22 = 90x

• DE61, SE11 = 4








PPMSACQMC008


EC-MC 356

00 a The terminal must approve the transaction after PayPass Magnetic Stripe card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 91x

• DE61, SE11 = 4


N/A

PPMSACQMC009


EC-MC 356

00 a The terminal must approve the transaction after PayPass Magnetic Stripe card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 91x

• DE61, SE11 = 4


N/A








PPMSACQMC010

PayPass Magnetic Stripe Credit Retail – PayPass M/Chip Card Interoperability Test

EC-MC 406


• DE22 = 91x

• DE61, SE11 = 4

The terminal must approve the transaction after PayPass Magnetic Stripe card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 90

• DE61, SE11 = 4

PayPass Acquirer — Magnetic Stripe TestingPayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing — MasterCard Clearing and

Presentation Simulator



PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing — MasterCard Clearing and Presentation Simulator


Prior to performing the PayPass Magnetic Stripe Transaction Lifecycle testing, acquirers must:

• Obtain the MasterCard Clearing Presentment Simulator (MCPS). The order form for the MCPS can be obtained via MasterCard OnLine™ at www.mastercardonline.com. For options for online testing, please contact the MasterCard CIS Implementation Specialist assigned to this project.

• Be able to successfully use the Integrated Product Message (IPM) format for clearing. The acquirer must perform the related test cases listed in the IPM test guide.


PayPass Acquirer — Magnetic Stripe TestingPayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing — MasterCard Clearing and

Presentation Simulator



Test Procedures

Figure 6.1—General Acquirer Clearing Test Scheme





Subm

it Tr

ansa

ctio

ns

usin

g ET

EC3

Car

ds

Cre

dit

Sim

ulat

or

Acts

as

Issu

er



Presentment File

Figure 6.1 shows the general scheme for Acquirer Clearing testing. The following are the specific steps that the acquirer must perform to test the PayPass Magnetic Stripe Acquirer Clearing Transaction Lifecycle:

1. Select a terminal approved for PayPass Magnetic Stripe use. Information on all approved PayPass products may be found on www.paypass.com, Approved PayPass products. All Acquirers should work with their MasterCard PayPass Acquirer/Merchant deployment team to select products for use prior to testing.

2. Perform at least one each PayPass Magnetic Stripe Authorization test for Contactless and at least one Fallback Magnetic Stripe Authorization test defined above. These test cases should be determined in consultation with the CIS Implementation Specialist assigned to this project.

3. Use the test transactions to create a file of First Presentment records from the Acquirer’s Clearing system. These records will contain clearing records which may include DE55.


PayPass Acquirer — Magnetic Stripe Testing PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing — MasterCard Clearing and Presentation Simulator



4. Submit the First Presentment file to MasterCard Clearing and Presentment Simulator to validate the overall format of the outgoing file using the CEE component of the MCPS.

5. Submit results of the successful tests to MasterCard for validation, based on the test schedule agreed with MasterCard.

Technical expertise and support services are available for the duration of the testing period

Test Cases

By performing the following test cases, acquirers will ensure that their clearing and settlement applications can build and send valid outgoing files including the specific values associated with PayPass Magnetic Stripe transactions in contactless and fallback modes.

For a PayPass Magnetic Stripe Contactless transaction, when DE22 is present in presentment message MasterCard will ensure the following checks are made:

• DE22 subfield 1 shall be equal to "A" (or to “M” for PayPass OneSMART customers verifying PayPass Magnetic Stripe interoperability)

• DE22 subfield 7 shall be equal to "A"

For a PayPass Magnetic Stripe Contactless transaction, when DE22 is present in presentment message MasterCard will ensure the following checks are made:

• DE22 subfield 7 shall be equal to "2"

The test cases cover business transactions commonly encountered in your business activities.



PPMSACQPR001

PayPass Magnetic Stripe – Contactless transaction

M The presentment message must be accepted


PPMSACQPR002

PayPass Magnetic Stripe – Fallback transaction

M The presentment message must be accepted




7 PayPass Magnetic Stripe Issuer — Transaction Lifecycle Testing This chapter describes test pre-requisites, procedures and test cases that PayPass Magnetic Stripe issuers must fulfill and successfully complete to validate the correct interfacing of their host systems with MasterCard network systems.



PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing— MasterCard Clearing and Presentment Simulator...............................................7-3

Testing Procedure Pre-requisites ..................................................................7-3 Test Procedures.............................................................................................7-4

PayPass Magnetic Stripe Issuer — Transaction Lifecycle TestingPayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization

Simulator



PayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator


Prior to performing the PayPass Magnetic Stripe Authorization Transaction Lifecycle, issuers must fulfill the following condition:

• Make issuer test card data available to MasterCard. For this purpose, the issuer must complete and return the relevant Information to the MasterCard regional office. Appendix A of this book describes this information.

Test Procedures

The test procedures are as follows:

• If executing offline testing, connect the issuer host to the MasterCard Credit Authorization Simulator.

• If executing online testing, coordinate with the CIS Implementation Specialist assigned to this project to schedule testing and for support to connect to and use the MasterCard Test Facility (MTF).

PayPass Magnetic Stripe Issuer — Transaction Lifecycle Testing PayPass Magnetic Stripe Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



Test Cases

Note All test cases in this chapter are mandatory. Recommended service code field value is 502.

Table 7.1—Issuer Test Cases

Test ID Transaction Card ID DE 4 DE 22.1 DE 61.11 Expected Results Comments/Purpose

PPMSISS001CR PayPass Magnetic Stripe Credit Retail

MC:101-105 10.00 91 4 Approve Valid contactless transaction


MC:101-105 10.00 00 4 Approve or Decline1

Invalid value in DE 22.1.



Invalid value in DE61.11.

PPMSISS004CR Fallback Magnetic Stripe Credit Retail

MC:101-105 15.00 90 2 Approve Normal mag stripe transaction with track 2 and CVC1

PPMSISS005CR Fallback Manual Credit Retail

MC:101-105 10.00 01 1 Approve PAN Manual entry transaction with CVC2



Invalid combination of DE22.1 and DE61.11


MC:101-105 10.00 91 3 Approve Valid transaction.

1 Issuers may choose to approve or decline messages when they contain incorrect values in DE22.1 and DE61.11. Issuers

declining the transactions may choose the response code used in the decline. The Issuer should inform the CIS Implementation Specialist of the results they expect for these tests before executing them.

PayPass Magnetic Stripe Issuer — Transaction Lifecycle TestingPayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing— MasterCard Clearing and

Presentment Simulator



PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing— MasterCard Clearing and Presentment Simulator


Issuers must fulfill the following conditions before undertaking PayPass Magnetic Stripe Clearing — Transaction Lifecycle testing:

• Obtain the MasterCard Clearing Presentment Simulator (MCPS). Issuers need this to conduct PayPass Magnetic Stripe Issuer Clearing Transaction Lifecycle testing procedures.

The MCPS is available via MasterCard OnLine® (www.mastercardonline.com) in the Featured Products & Services section. Click the MasterCard Simulator Suite link to open the download page, then click the Order/Update link beside MasterCard Clearing Presentment Simulator.

For options for online testing, please contact the MasterCard CIS Implementation Specialist assigned to this project.



PayPass Magnetic Stripe Issuer — Transaction Lifecycle Testing PayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing— MasterCard Clearing and Presentment Simulator



Test Procedures

Figure 7.1—General Issuer Clearing Test Scheme




Cre

ate

Firs

t Pr

esen

tmen

t File

usi

ng

MC

PS a

nd S

ubm

it to

C

lear

ing

Syst

em

Create C

hargeback


CPS

Figure 7.1 shows the general scheme for Issuer Clearing testing. The following are the specific steps that the acquirer must perform to test the PayPass Magnetic Stripe Issuer Clearing Transaction Lifecycle:

1. Execute all of the Authorization test cases in Table 7.1 using the MasterINQ Credit Authorization Simulator.

2. Create an output file from the MasterINQ Credit Authorization Simulator for import into the MasterCard Clearing and Presentment Simulator. For more information about creating this file, please refer to “Generating a History Log as a Text File” in Chapter 4, “Issuer Testing” of the MasterCard Credit Authorization Simulator guide available with the simulator or from MasterCard Online.

3. Create the Clearing Incoming File by importing the file created in step 2 on the MasterINQ Credit Authorization Simulator into the MasterCard Clearing and Presentment Simulator (MCPS). For more information about importing the file, please refer to the “Authorization Message Conversion” section in Chapter 4 of the MasterCard Clearing Presentment Simulator Guide available with the simulator or from MasterCard Online.

PayPass Magnetic Stripe Issuer — Transaction Lifecycle TestingPayPass Magnetic Stripe Clearing — Transaction Lifecycle Testing— MasterCard Clearing and

Presentment Simulator



4. Submit the incoming file (1240 messages) to the issuer’s clearing system. All records should process correctly.

5. Generate a 1442 chargeback message for each of the 1240 messages in the incoming file from the Issuer’s Clearing system.

6. Submit the chargeback file created in step 5 to MCPS and confirm that it was validated.



8 PayPass OneSMART Acquirer — Transaction Lifecycle Testing This chapter describes test pre-requisites, procedures and test cases that PayPass OneSMART acquirers must fulfill and successfully complete to validate the correct interfacing of their host systems with MasterCard network systems.



PayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment Simulator..........................................................................8-7


PayPass OneSMART Acquirer — Transaction Lifecycle TestingPayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization

Simulator



PayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator


Prior to performing the PayPass OneSMART Authorization Transaction Lifecycle testing, acquirers must fulfill the following conditions:

• Successfully complete the test cases described in Chapter 2 and Chapter 4.

• Successfully complete or be co-executing the test cases described in Chapter 6.

• Purchase and make available ETEC cards - subset 7, the PayPass OneSMART subset.

Test Procedures


1. Select a terminal approved for PayPass OneSMART use. Information on all approved PayPass products may be found on www.paypass.com, Approved PayPass Products. All Acquirers should work with their MasterCard PayPass Acquirer/Merchant deployment team to select products for use prior to testing.

2. If performing offline testing, connect the issuer host to the MasterCard Credit Authorization Simulator. For more information on installing the simulator and connecting it to the acquirer host, see the MasterCard Credit Authorization Simulator Guide.

3. If executing online testing, coordinate with the Customer Implementation Services (CIS) Implementation Specialist assigned to this project to schedule testing and for support to connect to and use the MasterCard Test Facility (MTF).

Note Acquirers may not be able to conduct regular or standard non-ICC testing in parallel with chip testing if testing online with MTF.



PayPass OneSMART Acquirer — Transaction Lifecycle Testing PayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



4. Schedule formal testing with the MasterCard regional operations manager, as soon as all individual tests have been successfully performed.


PayPass OneSMART Acquirer — Transaction Lifecycle TestingPayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



Test Cases


• Send correctly formatted PayPass OneSMART credit authorization requests.

• Process the resulting authorization responses.


Note All test cases in this chapter are marked mandatory (M) or conditional (C). Acquirers must execute the conditional tests only if they support the condition described in the “Transaction” column.






M/C Success criteria Comments/Purpose

PPOSACQMC001

PayPass OneSMART Retail POS Signature

EC-MC 403 00 C The terminal must approve the transaction after IC card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3


PPOSACQMC002

PayPass OneSMART Cash Advance Signature


• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3


PPOSACQMC003

PayPass OneSMART Cash Advance Online PIN


• DE22 = 07x

• DE23 included

• DE52 included

• ARQC Valid

• DE61, SE11 = 3


PayPass OneSMART Acquirer — Transaction Lifecycle TestingPayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator





PPOSACQMC004

PayPass OneSMART CAT1 Online PIN


• DE22 = 07x

• DE23 included

• DE52 included

• ARQC Valid

• DE61, SE11 = 3


PPOSACQMC005

PayPass OneSMART Credit CAT level 2 No CVM


• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3


PPOSACQMC006

PayPass OneSMART Credit CAT level 3 no CVM

EC-MC 405 00 C The terminal must approve the transaction after IC card and terminal interaction.

This transaction is not online (CAT level 3 terminal). It shall be performed as a pre-requisite to the PayPass OneSMART clearing tests.






PPOSACQMC007

PayPass OneSMART Credit Transaction type of members choice

EC-MC 412 00 M The terminal must approve the transaction after IC card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3

Transaction type of member choice when card sequence number is not equal to “0”

PPOSACQMC008

PayPass OneSMART Credit Transaction type of member choice

EC-MC 415 N.A. M The terminal must approve the transaction after IC card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3

Ensure acquirer is able to cope with transaction response containing ICC data after full grade request – IAD (tag 91) and ICC post-issuance command are present

PayPass OneSMART Acquirer — Transaction Lifecycle TestingPayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment

Simulator



PayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment Simulator


Prior to performing the PayPass OneSMART Transaction Lifecycle testing, acquirers must:

• Obtain the MasterCard Clearing Presentment Simulator (MCPS). The order form for the MCPS can be obtained via MasterCard OnLine® at www.mastercardonline.com. For options for online testing, please contact the MasterCard CIS Implementation Specialist assigned to this project.

• Be able to successfully use the Integrated Product Message (IPM) format for clearing. The acquirer must perform the related test cases listed in the IPM test guide.Test Procedures

Figure 8.1—General Acquirer Testing Scheme





Subm

it Tr

ansa

ctio

ns

usin

g ET

EC3

Car

ds

Cre

dit

Sim

ulat

or

Acts

as

Issu

er



Presentment File


PayPass OneSMART Acquirer — Transaction Lifecycle Testing PayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment Simulator



Figure 8.1 shows the general scheme for acquirer clearing testing. The acquirer must perform the following specific procedures when conducting PayPass OneSMART acquirer clearing online testing:

1. Based on the terminal types supported on the acquirer’s host infrastructure, the acquirer must work with the MasterCard Customer Implementation Services (CIS) Implementation Specialist to determine the test cases to perform with that terminal.

2. Execute the equivalent authorization test for each clearing test agreed to in step 1. These test cases should be executed using the acquirer’s terminal with the MasterINQ Credit Authorization Simulator acting as the Issuer.

3. Use the test transactions to create a file of first presentment records from the acquirer’s clearing system. These records will contain clearing records which may include DE55.

4. Submit the first presentment file to MasterCard Clearing Presentment Simulator to validate the overall format of the outgoing file using the CEE component of the MCPS.

5. Submit results of the successful tests to MasterCard for validation, based on the test schedule agreed with MasterCard.

Technical expertise and support services are available for the duration of the testing period.

Test Cases

By performing the following test cases, acquirers will ensure that their clearing and settlement applications can build and send valid outgoing files, generated from correctly formatted PayPass OneSMART clearing messages.

When DE22 is present in presentment message MasterCard verify the following:

• DE22 subfield 7 is equal to "M"

The test cases cover business transactions commonly encountered in your business activities, and all message types impacted by ICC-based operations.

Acquirers must execute these test cases for all non-ATM transactions

The following two tables list the test cases.

PayPass OneSMART Acquirer — Transaction Lifecycle TestingPayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment Simulator





PPOSACQPR001

PPOSACQMC001 PayPass OneSMART Credit retail signature-based

C The presentment message must be accepted. Cryptogram must validate correctly.


PPOSACQPR002

PPOSACQMC002 PayPass OneSMART Credit cash advance signature



PPOSACQPR003

PPOSACQMC003 PayPass OneSMART Credit cash advance online PIN



PPOSACQPR004

PPOSACQMC004 PayPass OneSMART Credit CAT level 1 retail offline or online PIN



PPOSACQPR005

PPOSACQMC005 PayPass OneSMART Credit CAT level 2 retail no CVM

C The presentment message must be accepted. Cryptogram


PayPass OneSMART Acquirer — Transaction Lifecycle Testing PayPass OneSMART Clearing — Transaction Lifecycle Testing— MasterCard Clearing Presentment Simulator




must validate correctly.

PPOSACQPR006

PPOSACQMC0061 PayPass OneSMART Credit CAT level 3 retail no CVM



PPOSACQPR007

PPOSACQMC007 Transaction type of member choice

M The presentment message must be accepted. Cryptogram must validate correctly..

Check business transaction format and content with card sequence number check

Table 8.3—Reversal Messages


PPOSACQPR008

Full reversal of presentment

M The reversal message must be accepted


1 This transaction is an offline transaction. To include this transaction in the First Presentment file exported from the Acquirer’s

Clearing System to the Clearing Simulator, the record must be transmitted from the Authorizing Terminal to the Credit Simulator using the Batch file transfer capability of the Acquirer’s terminal. Please refer to the reference manual for your terminal for instructions on how to transmit the batch file.



9 PayPass OneSMART Issuer — Transaction Lifecycle Testing This chapter describes test pre-requisites, procedures and test cases that PayPass OneSMART issuers must fulfill and successfully complete to validate the correct interfacing of their host systems with MasterCard network systems.



PayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator..........................................................................9-5


PayPass OneSMART Issuer — Transaction Lifecycle TestingPayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization

Simulator



PayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator


Prior to performing the PayPass OneSMART Authorization Transaction Lifecycle testing using the MasterINQ Credit Authorization Simulator, issuers must fulfill the following conditions:

• Successfully complete all test cases in chapters 3 and 5.

• Successfully complete or be co-executing the test cases described in chapter 7.

• Make issuer test card data available to MasterCard. For this purpose, the issuer must complete and return the relevant Information to the MasterCard regional office. Appendix A of this book describes this information.

Test Procedures • If performing offline testing, connect the issuer host to the MasterCard Credit

Authorization Simulator. For more information on installing the simulator and connecting it to the acquirer host, see the MasterINQ Credit Authorization Simulator Guide.

• If executing online testing, coordinate with the Customer Implementation Services (CIS) Implementation Specialist assigned to this project to schedule testing and for support to connect to and use the MasterCard Test Facility (MTF).

Note You cannot conduct regular or standard non-ICC testing in parallel with chip testing when testing online with MTF.

Technical expertise and support service is available during the scheduled testing period.

PayPass OneSMART Issuer — Transaction Lifecycle Testing PayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator



Test Cases

Note All test cases in this section are mandatory for PayPass OneSMART Issuers.

Table 9.1—Test Case for Test ID



PPOSISSMC001 PayPass OneSMART Credit retail signature

MC:401-405 00 The terminal must approve the transaction after IC card and terminal interaction. It must set the following elements in the 0100 message:

• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3

Full Grade - Check business transaction format and content

PPOSISSMC002 PayPass OneSMART Credit retail CAT Level 1 online PIN


• DE22 = 07x

• DE23 included

• DE52 included

• ARQC Valid

• DE61, SE11 = 3


PayPass OneSMART Issuer — Transaction Lifecycle TestingPayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator





PPOSISSMC003 PayPass OneSMART Credit retail CAT Level 2 no CVM


• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3


PPOSISSMC004 PayPass OneSMART Credit Cash Advance Signature


• DE22 = 07x

• DE23 included

• ARQC Valid

• DE61, SE11 = 3


PPOSISSMC005 PayPass OneSMART Credit Cash Advance Online PIN


• DE22 = 07x

• DE23 included

• DE52 included

• ARQC Valid

• DE61, SE11 = 3


PPOSISSMC006 PayPass OneSMART Credit Retail Signature

MC:401-405 00 Transaction is approved Partial Grade - Check business transaction format and content

PayPass OneSMART Issuer — Transaction Lifecycle Testing PayPass OneSMART Authorization — Transaction Lifecycle Testing — MasterCard Credit Authorization Simulator





PPOSISSMC007 PayPass OneSMART Credit retail CAT Level 1 online PIN


• DE52 included

Partial Grade - Check business transaction format and content

PPOSISSMC008 PayPass OneSMART Credit retail CAT Level 2 no CVM


PPOSISSMC009 PayPass OneSMART Credit Cash Advance Signature


PPOSISSMC010 PayPass OneSMART Credit Retail

MC:401-405 00 Transaction is approved Full and Partial Grade -Check advice message format and content

PayPass OneSMART Issuer — Transaction Lifecycle TestingPayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment

Simulator



PayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator


Issuers must fulfill the following conditions before undertaking PayPass OneSMART Clearing — Transaction Lifecycle testing:

• Obtain the MasterCard Clearing Presentment Simulator (MCPS). Issuers need this to conduct PayPass OneSMART Issuer Clearing Transaction Lifecycle testing procedures.

The MCPS is available via MasterCard OnLine®. (www.mastercardonline.com) in the Featured Products & Services section. Click the MasterCard Simulator Suite link to open the download page, then click the Order/Update link beside MasterCard Clearing Presentment Simulator.

For options for online testing, please contact the MasterCard Customer Implementation Services (CIS) Implementation Specialist assigned to this project.



PayPass OneSMART Issuer — Transaction Lifecycle Testing PayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator



Test Procedures

Figure 9.1—General Issuer Clearing Test Scheme




Cre

ate

Firs

t Pr

esen

tmen

t File

usi

ng

MC

PS a

nd S

ubm

it to

C

lear

ing

Syst

em

Create C

hargeback


CPS

Figure 9.1 shows the general scheme for Issuer Clearing testing. Issuers must perform the following procedures when conducting Issuer PayPass OneSMART Clearing Life Cycle testing:

1. Execute the equivalent authorization test for each clearing test as indicated in Table 9.2. These test cases should be executed on the MasterINQ Credit Authorization Simulator.

2. Create an output file from the MasterINQ Credit Authorization Simulator for import into the MasterCard Clearing and Presentment Simulator. For more information about creating this file, please refer to “Generating a History Log as a Text File” in Chapter 4, “Issuer Testing”, of the MasterCard Credit Authorization Simulator manual available with the simulator or from MasterCard Online.

PayPass OneSMART Issuer — Transaction Lifecycle TestingPayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment

Simulator



3. Create the Clearing Incoming File by importing the file created on the MasterINQ Credit Authorization Simulator in step 2 into the MasterCard Clearing and Presentment Simulator (MCPS). For more information about importing the file, please refer to the “Authorization Message Conversion” section in Chapter 4 of the MasterCard Clearing Presentment Simulator Guide available with the simulator or from MasterCard Online. These records will contain clearing records which may include DE55.

4. Submit the incoming file (1240 messages) to the Issuer’s Clearing system. All records should process correctly.

5. Generate a 1442 chargeback message for each of the 1240 messages in the incoming file from the issuer’s clearing system.

6. Submit the chargeback file created in step 5 to MCPS and confirm that it was validated.

PayPass OneSMART Issuer — Transaction Lifecycle TestingPayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator



Test Cases

The following test cases are designed to ensure that your issuer clearing and settlement application is able to receive and process a valid incoming file. For full grade transactions to be valid, the incoming file must contain ICC clearing messages that, in turn, contain DE055 — ICC System Related Data. These test cases and message types mirror the types of business transaction that issuers encounter in their ICC–related activities.


Test ID Equivalent Authorization Test ID

Transaction Success Criteria Comments/Purpose

PPOSISSPR001 PPOSISSMC001 PayPass OneSMART Credit retail signature-based

The presentment message, including DE55, must be accepted by the issuer host. If the cryptogram 9F26 is validated, the validation must be correct.

Check business transaction format and content for Full Grade Transaction.

PPOSISSPR002 PPOSISSMC002 PayPass OneSMART Credit CAT Level 1 retail offline PIN



PPOSISSPR003 PPOSISSMC003 PayPass OneSMART Credit CAT Level 2 retail no CVM



PPOSISSPR004 PPOSISSMC004 PayPass OneSMART Cash Advance signature



PayPass OneSMART Issuer — Transaction Lifecycle TestingPayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator



Test ID Equivalent Authorization Test ID

Transaction Success Criteria Comments/Purpose

PPOSISSPR 005 PPOSISSMC005 PayPass OneSMART Cash Advance on line PIN



PPOSISSPR006 PPOSISSMC006 PayPass OneSMART Credit retail signature-based

The presentment message must be accepted by the issuer host.

Check business transaction format and content for Partial Grade Transaction.

PPOSISSPR007 PPOSISSMC007 PayPass OneSMART Credit CAT Level 1 retail offline PIN



PPOSISSPR008 PPOSISSMC008 PayPass OneSMART Credit CAT Level 2 retail no CVM



PPOSISSPR009 PPOSISSMC009 PayPass OneSMART Credit cash advance signature-based



Table 9.3—1442 Chargeback messages


PPOSISSCB001 PayPass OneSMART Credit retail signature-based



PayPass OneSMART Issuer — Transaction Lifecycle Testing PayPass OneSMART Clearing — Transaction Lifecycle Testing — MasterCard Clearing Presentment Simulator




PPOSISSCB002 PayPass OneSMART Credit CAT Level 1 retail offline PIN



PPOSISSCB003 PayPass OneSMART Credit CAT Level 2 retail no CVM



PPOSISSCB004 PayPass OneSMART Cash Advance signature




PPOSISSCB005 PayPass OneSMART Cash Advance online PIN




PPOSISSCB006 PayPass OneSMART Credit retail signature-based

The chargeback message is not rejected. Check business transaction format and content for Partial Grade Transaction.

PPOSISSCB007 PayPass OneSMART Credit CAT Level 1 retail offline PIN


PPOSISSCB008 PayPass OneSMART Credit CAT Level 2 retail no CVM


PPOSISSCB009 PayPass OneSMART Credit cash advance signature-based



MasterCard Member ICC Testing Procedures - Credit • May 2006 A-i

A Issuer Test Card Data for ICC-based Operations This appendix describes the information that issuers need to send to MasterCard regarding the setup of test parameters for online testing.

Overview ............................................................................................................ A-1

General Information........................................................................................... A-1

Detailed Issuer Test Card Information .............................................................. A-3

Issuer Test Card Data for ICC-based OperationsOverview


MasterCard Member ICC Testing Procedures - Credit • May 2006 A-1

Overview In ICC testing, the MasterCard test systems use information provided by the issuer to create messages for the issuer to use during System Build-up and online testing.

MasterCard test systems only support cryptogram algorithms for the standard calculation methods described in the M/Chip Lite and M/Chip Select version 2.1 and M/Chip version 4.0 documentation.

The MasterCard test systems will not generate valid cryptograms or validate cryptograms for:

• Other card schemes

• Non-standard methods of cryptogram calculation

You do not have to answer questions relating to ‘Cryptogram Calculation Methods’ or ‘Cryptogram Key Information’ if you use other card schemes, or non-standard methods of cryptogram calculation.

However, MasterCard may support other cryptographic algorithms as MasterCard test systems evolve. Contact your MasterCard regional office for more information on this subject.

General Information MasterCard uses the general test information below to set up the MasterCard test system for either:

• validating chip card test results

• generating chip card cryptograms.

Issuing members must send the information listed in Table A.1 and Table A.2 to their MasterCard CIS specialist by e-mail, prior to the start of online testing:

Issuer Test Card Data for ICC-based Operations General Information


A-2 May 2006 • MasterCard Member ICC Testing Procedures - Credit

Table A.1—Issuer Testing Information

Issuer Card Scheme Which issuer card scheme is applicable to your cards? Please select ( ) one box.

M/Chip Lite

M/Chip Select

Other1 (Please provide application

name & version)

The specifications relating to your choice of Issuer Card Scheme will indicate a standard cryptogram calculation method.

Is your cryptogram calculation method the standard method specified?

Please select ( ) one box.

Yes

No2

Cryptogram Calculation method

To which version of the EMV specifications does your cryptogram calculation conform? Please select ( ) one box.

EMV '96

EMV 2000

EMV CCD

Cryptogram Key Information

Please provide the value of the test IMK (test Issuer DES Master Key) used3

IMK Value (32 digits):

Please provide the lowest card number in the test card range

Test Card Range4

Please provide the highest card number in the test card range

1 If the answer is 'other', then you do not have to answer the 'cryptogram Calculation

Method' and 'Cryptogram Key Information' questions. Go straight to the 'Test Card Range' and 'Test Card Data' list.

2 If the answer is 'No', then you do not have to complete the 'Cryptogram Key Information' question. Go straight to the Test Card Range and Test Card Data list

3 MasterCard test systems use the PAN and Card Sequence Number to derive the key from the IMK you specify here.

4 The test card range you supply here will be considered a test range on a network-wide basis.

Issuer Test Card Data for ICC-based OperationsDetailed Issuer Test Card Information


MasterCard Member ICC Testing Procedures - Credit • May 2006 A-3

Detailed Issuer Test Card Information Please provide test card data for each test card ID. If you do not support issuer scripts, you may omit test card IDs 106 and 107. Provide the information in ascending order of PAN and preferably as contiguous PANs. The Test Card ID shown in the table corresponds to the Test Card ID shown in the appropriate test case table.

Issuing members must send the information listed in Table A.1 and Table A.2 to their MasterCard CIS specialist by e-mail, prior to the start of online testing:

Table A.2—Test Card Information

Test Card ID Description of Test Card Use

Track 2 Data Card sequence Number (Tag 5F34)5

Issuer Application Data (Tag 9F10)6

101 Used randomly in the issuer test cases where the test cases does not require the card account to have any special attributes




5 A card sequence number value of '0' is assumed if no value is supplied.

6 The issuer must supply default Issuer Application Data for M/Chip Lite and M/Chip Select card applications. The issuer must also supply data for any other applicable card applications.

Issuer Test Card Data for ICC-based Operations Detailed Issuer Test Card Information


A-4 May 2006 • MasterCard Member ICC Testing Procedures - Credit

Test Card ID Description of Test Card Use

Track 2 Data Card sequence Number (Tag 5F34)5

Issuer Application Data (Tag 9F10)6


106 Used in the issuer script test cases. Required only if issuer scripts are supported

107 Used in issuer script test cases. Only needed if issuer scripts are supported


MasterCard Member ICC Testing Procedures - Credit • May 2006 B-i

B MasterCard Credit Authorization Simulator, Ordering Procedure This appendix describes the procedure to follow when ordering the MasterINQ Credit Authorization Simulator.

Ordering the MasterINQ Credit Authorization Simulator ................................. B-1

MasterCard Credit Authorization Simulator, Ordering ProcedureOrdering the MasterINQ Credit Authorization Simulator


MasterCard Member ICC Testing Procedures - Credit • May 2006 B-1

Ordering the MasterINQ Credit Authorization Simulator MasterCard OnLine provides you with the fastest way to order copies and updates of the MasterINQ Credit Authorization Simulator.

To order the MasterINQ Credit Authorization Simulator, proceed as follows:

1. Navigate to www.mastercardonline.com.

2. Log on to the site with your existing UserID and SecurID. If you do not have a UserID, click Enroll Now under MasterCard OnLine, and follow the registration process, providing the information requested.

3. Once you have logged on to the site, click Featured Products & Services under Products. The Featured Products & Services page appears.

Figure B.1—Featured products

4. Click MasterCard Simulator Suite to access the simulator suite page.

5. Click Order/Update to the right of the MasterCard Credit Authorization Simulator – MasterINQ Platform entry. The Product Catalog opens.

Figure B.2—Simulator Suite page before registration


MasterCard Credit Authorization Simulator, Ordering Procedure Ordering the MasterINQ Credit Authorization Simulator


B-2 May 2006 • MasterCard Member ICC Testing Procedures - Credit

6. Click the New Product Request or the Update Product Request button, as appropriate, beside the simulator product you want to download and follow the registration instructions.

Once you have been registered for a simulator, the Order/Update link on the Simulator Suite page (see Figure B.2) will be replaced by a Download button as shown in Figure B.3.

Figure B.3—Simulator Suite page after registration

7. Click the Download button to open the Simulator download page

8. If this is the first time the MasterINQ simulator has been installed on this PC, download and install (1), (2) and (3), as shown in Figure B.4, in that order.

If this is an upgrade, download and install (2) and (3), as shown in Figure B.4 in that order.

MasterCard Credit Authorization Simulator, Ordering ProcedureOrdering the MasterINQ Credit Authorization Simulator


MasterCard Member ICC Testing Procedures - Credit • May 2006 B-3

Figure B.4—Credit Authorization Simulator download page

For a full description of the installation procedure for the MasterINQ Credit Authorization Simulator, refer to chapter 2 of the MasterCard Credit Authorization Simulator Guide.


MasterCard Member ICC Testing Procedures - Credit • May 2006 C-i

C Implementing Chip Card tests This chapter provides specific procedural information and lists the Network Interface Validation (NIV) test cases for MasterCard members who are implementing chip and that are connected through the Australian Processing Centre (APC) using the AS2805 network interface messages.

NIV Procedures for customers connected to the APC...................................... C-1 Phase 1 – System Build-up .......................................................................... C-1

Procedure: .............................................................................................. C-1 Phase 2 – Member Compliance Testing...................................................... C-1

Procedure: .............................................................................................. C-1

NIV Test cases for customers connected to the APC........................................ C-2 Chip Acquirer –Normal ICC Test Cases ...................................................... C-2 Chip Issuer –Normal ICC Test Cases........................................................... C-3

Implementing Chip Card testsNIV Procedures for customers connected to the APC


MasterCard Member ICC Testing Procedures - Credit • May 2006 C-1

NIV Procedures for customers connected to the APC

Phase 1 – System Build-up

During this initial stage of member testing, intensive support to member will be provided by the Australian Processing Center (APC) Member Implementation (MI) team to verify customer host connectivity and validate the chip data element flow between the APC and the customer host.

Procedure:

1. For acquirer testing, the member shall send a paper trace of the request message to APC MI. The APC MI team shall then verify this paper trace and provide member support as appropriate.

2. The member and the APC MI team shall ensure initial network connectivity between the member host and the APC.

3. For issuer testing, the APC MI team shall send five basic chip authorization requests to the member host through the APC.

4. The APC MI team shall verify that all chip data elements are passing successfully through the end-to-end APC network infrastructure.

Phase 2 – Member Compliance Testing

During this stage, the APC MI team support to the member will be reduced. The APC MI team will still ensure all test cases are executed by members as required.

Procedure:

1. Member shall complete all required test cases provided by MasterCard.

2. Member shall verify that all chip data elements are passing through the network successfully.

3. The APC MI team shall provide on-site support to member for any testing issues.

Implementing Chip Card tests NIV Test cases for customers connected to the APC


C-2 May 2006 • MasterCard Member ICC Testing Procedures - Credit

NIV Test cases for customers connected to the APC

Chip Acquirer –Normal ICC Test Cases

The APC acquiring member conducts the ICC test cases listed in Table C.1, below. For a complete description and full instructions on these test cases, refer to Table 2.2 of this manual.

Table C.1—Chip Acquirer –Normal ICC Test Cases

Test ID Transaction Comment

CAACQ001 ICC Credit retail Signature-based As per instructions

CAACQ002 ICC Credit retail offline PIN As per instructions

CAACQ003 ICC Credit retail online PIN As per instructions

CAACQ004 ICC Credit cash Advance signature-based As per instructions

CAACQ005 ICC Credit cash Advance offline PIN Not Applicable

CAACQ007 ICC Credit CAT level 1 retail online PIN As per instructions

CAACQ008 ICC Credit CAT level 1 retail offline PIN As per instructions

CAACQ009 ICC Credit CAT level 2 retail no CVM As per instructions




As per instructions


As per instructions


As per instructions


As per instructions


As per instructions

Implementing Chip Card testsNIV Test cases for customers connected to the APC


MasterCard Member ICC Testing Procedures - Credit • May 2006 C-3



As per instructions


As per instructions


As per instructions


Send reversal (420)


As per instructions

Chip Issuer –Normal ICC Test Cases

The APC issuing member conducts the ICC test cases listed in Table C.2, below. For a complete description and full instructions on these test cases, refer to Table 3.2 of this manual.

Table C.2—Chip Issuer –Normal ICC Test Cases


CAACQ001 ICC Credit retail Signature-based. As per instructions

CAACQ002 ICC Credit retail offline PIN. As per instructions

CAACQ003 ICC Credit retail online PIN. As per instructions

CAACQ004 ICC Credit cash Advance signature-based. As per instructions

CAACQ005 ICC Credit cash Advance offline PIN. Not Applicable

CAACQ007 ICC Credit CAT level 1 retail online PIN. As per instructions

CAACQ008 ICC Credit CAT level 1 retail offline PIN. As per instructions

CAACQ009 ICC Credit CAT level 2 retail no CVM. As per instructions



CAACQ012 ICC Credit business transaction of customer choice.

As per instructions


As per instructions

Implementing Chip Card tests NIV Test cases for customers connected to the APC


C-4 May 2006 • MasterCard Member ICC Testing Procedures - Credit


CAACQ014 ICC Credit business transaction of customer choice – 3 transactions.

As per instructions


As per instructions


As per instructions


As per instructions

CAACQ018 ICC Credit business transaction of customer choice, where fallback is permitted.

As per instructions


As per instructions


Send reversal (420)


As per instructions

MC_Member ICC Testing Procedures

Documents

Transcript of MC_Member ICC Testing Procedures