Terminal Integration Process Guide. August 2012

Transcription

1 Terminal Integration Process Guide August 2012

2 Proprietary Rights The information contained in this document is proprietary and confidential to MasterCard International Incorporated, one or more of its affiliated entities (collectively MasterCard ), or both. This material may not be duplicated, published, or disclosed, in whole or in part, without the prior written permission of MasterCard. Trademarks Trademark notices and symbols used in this document 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. Billing Information Available Online For printed documents, MasterCard will bill principal members. Please refer to the appropriate MasterCard Consolidated Billing System (MCBS) document for billing-related information. MasterCard provides details about the standards used for this document including times expressed, language use, and contact information on the Member Publications Support page available on MasterCard OnLine. Go to Member Publications Support for centralized information. August 2012 Terminal Integration Process Guide

3 Summary of Changes Terminal Integration Process Guide, August 2012 To locate changes online, search on the date associated with this revision. On the Adobe toolbar, click Find. In the Find box, type Jan 2008, and then press ENTER. To move to the next revision bar, press ENTER again. Description of Change To ensure that members have access to current contact information and standards used for MasterCard documentation, MasterCard has created the Member Publications Support page. As a result, MasterCard has removed some content from this document, including times expressed, language use, and contact information, which members now can find online. Added paragraph regarding the M-TIP replacement and when TIP is applicable. Where to Look Member Publications Support page on MasterCard OnLine Chapter 1 Terminal Integration Process Guide August

4 Table of Contents Chapter 1 Introduction... 1-i About the Terminal Integration Process 1-1 Purpose of this Document Audience What Is the Terminal Integration Process? When to Do the Terminal Integration Process Types of TIP Prerequisites for Doing TIP Selection of an Approved Terminal Successful Completion of Network Interface Validation Terminal Acquirer Host System Setup TIP Contact Information Related Information Business Process Diagram Conventions Chapter 2 The TIP Process... 2-i Implementation Overview Establish Order With TIP Service Provider ICS Validation Acquirer Preparation TIP Workshop Acquirer Testing Approval Review Chapter 3 Establish Order with TIP Service Provider... 3-i Overview Process Chapter 4 ICS Validation... 4-i Overview Process Chapter 5 Acquirer Preparation... 5-i Overview Process Terminal Integration Process Guide August 2012 i

5 Table of Contents Chapter 6 Acquirer Testing... 6-i Overview Process Rename TIP Test Report Test Authorization or Financial Messages Overview Process Test Clearing Presentment Messages Overview Process Chapter 7 Approval Review... 7-i Overview Process Appendix A Understanding the TIP Test Scenarios...A-i Example of a TIP Test Scenario...A-1 Header Scenario Identification Information...A-2 Body Scenario Details...A-2 Objective...A-2 Applicability Conditions...A-2 Transaction Type...A-2 Reference Documentation...A-2 Card Configuration...A-3 User Action...A-3 Simulator Configuration...A-3 Pass Criteria...A-3 Note...A-4 Appendix B File Naming Conventions... B-i TIP INFO Filename...B-1 TIP Acquirer ICS Filename...B-1 TIP Test Report Filename...B-1 Card-Terminal Log Filenames...B-1 MasterCard Authorization and MasterCard Debit Financial Simulator Log Filenames...B-2 Appendix C How to Update the TIP Test Report... C-i TIP Test Report Cells... C-1 ii August 2012 Terminal Integration Process Guide

6 Table of Contents ACQ DATE... C-1 ACQ TIME... C-1 ACQ RESULTS... C-1 ACQ STATUS... C-2 ACQ SPY Log File Name... C-2 ACQ SIM Log File Name... C-2 Appendix D How to Use the Simulator...D-i Introduction... D-1 Setting Up the Simulator for TIP Testing... D-1 TIP Testing... D-5 Appendix E How to Validate the IPM File Using the MCPS... E-i Process... E-1 Glossary Terminal Integration Process Guide August 2012 iii

7 Chapter 1 Introduction This chapter provides an introduction to Terminal Integration Process, detailing what it is, what products are subject to it, and when it should be done. About the Terminal Integration Process Purpose of this Document Audience What Is the Terminal Integration Process? When to Do the Terminal Integration Process Types of TIP Prerequisites for Doing TIP Selection of an Approved Terminal Successful Completion of Network Interface Validation Terminal Acquirer Host System Setup TIP Contact Information Related Information Business Process Diagram Conventions Terminal Integration Process Guide August i

8 Introduction Purpose of this Document About the Terminal Integration Process Terminal Integration Process (TIP) has been replaced by MasterCard Terminal Integration Process (M-TIP) for contact and contactless terminal interfaces. This guide remains applicable for contactless readers implementing PayPass 1.3 specifications. Overview of this Document The MasterCard Terminal Integration Process must happen before a terminal can be deployed and used in the production environment. This guide details the process that you, the acquirer, must perform. Audience MasterCard provides this document for members and their authorized agents. Specifically, the following personnel should find this document useful: Members of staff who will perform the Terminal Integration Process (TIP) testing Program Managers and Project Managers for acquirers migrating to chip, (either contact, contactless, or both) Member service providers working with acquirers migrating to chip, (either contact, contactless, or both) Vendors who develop EMV-compliant terminals or PayPass compliant terminals What Is the Terminal Integration Process? The Terminal Integration Process is a key testing process designed to test the terminal, intermediate connections, and the interface with the acquirer host system, in conditions that are as close as possible to its final environmental use. This includes the complete connection path from your terminal to either: The MasterCard Debit Switch (MDS) system if you are using the MDS single message format, or The Banknet, RSC/APC, or EPS-Net MasterCard network systems using the CIS, AS2805, or V5 authorization format and to the Global Clearing Management System (GCMS) using the IPM clearing message format. The interface to GCMS shall only be tested if you are sending DE 55-ICC system related data, in clearing presentment messages MasterCard and Maestro Europe region acquirers must supply the correct chip data in their first presentment messages for intra-european chip transactions as of April , as described in the European Operation Bulletin No. 1 dated 3 January Terminal Integration Process Guide August

9 Introduction When to Do the Terminal Integration Process The objectives of the Terminal Integration Process are to: Ensure that your terminal meets MasterCard brand requirements: For a contact-based terminal, the requirements are in M/Chip Requirements. For a contactless terminal, the requirements are in PayPass M/Chip, Acquirer Implementation Requirements (available on and Maestro PayPass Acquirer Implementation Requirement (which can be obtained by sending a request to specifications@paypass.com) If the terminal does not support Maestro PayPass, it must only support the requirements specified in the M/Chip Requirements and the PayPass M/Chip Acquirer Implementation Requirements. Ensure that your terminal and in particular its EMVCo approved kernel and/or PayPass application(s), meets your business needs Test your terminal s capabilities in terms of interoperability, and detect issues at an early stage, thus saving you both time and money When to Do the Terminal Integration Process You need to do the TIP when any of the following happens: A new terminal is selected for deployment. An existing terminal that already has TIP approval is upgraded and the changes are major. Examples of major changes are: Existing and approved EMV terminal which is upgraded with a new EMV kernel version (must be submitted for TIP of an EMV contact interface terminal) Existing EMV terminal with TIP approval is upgraded to include PayPass M/Chip (must be submitted for TIP of a dual interface terminal) Existing PayPass M/Chip terminal with TIP approval is upgraded to include EMV (must be submitted for TIP of a dual interface terminal) Existing and approved PayPass Mag Stripe terminal is upgraded to include EMV and/or PayPass M/Chip (must be submitted for TIP of a dual interface terminal) Existing and approved terminal is deployed in a different country If an approved version of the terminal application is modified, please inform the TIP Team. The TIP Team will advise on whether a TIP or some regression tests must be performed based on the reported modifications. If you are clearing the ICC system-related data in the presentment messages (DE55), the TIP testing for the Clearing Presentment messages must be performed for every new terminal type (either Attended POS, Unattended POS, Bank Branch Terminal, or ATM) that you are implementing. If you are clearing the ICC system-related data in the presentment messages and implementing additional terminals of a same type, the TIP testing for Clearing Presentment messages is optional. 1-2 August 2012 Terminal Integration Process Guide

10 Introduction Prerequisites for Doing TIP NOTE A PayPass M/Chip terminal also supports PayPass Mag Stripe. During TIP of a PayPass M/Chip or dual interface terminal, PayPass Mag Stripe requirements are tested. However, there is no TIP for PayPass Mag Stripe only terminals. Types of TIP There are two types of TIP: Type First TIP Additional TIP Description A first TIP is always part of a chip implementation project. The project s Chip Implementation Plan includes the activities related to this First TIP. A MasterCard Regional Customer Representative is appointed to support you during your implementation project. For first TIP, TIP service provider offers a two-day workshop. Once you have completed your First TIP, you may contact the TIP service provider directly for all subsequent projects (using the contact details provided in the M/Chip Accredited Third Parties guide available at MasterCard OnLine on the Chip Information Center.) For Additional TIPs, a workshop is not included unless you specifically request it. Prerequisites for Doing TIP There are three prerequisites that must be met before you can complete TIP. Selection of an Approved Terminal Successful Completion of Network Interface Validation Terminal Acquirer Host System Setup NOTE To reduce your project duration, you can start TIP immediately and do Establish order with TIP Service Provider, ICS Validation, and Acquirer Preparation, then do the remaining subprocesses once you have successfully completed Network Interface Validation. For more information see Chapter 2, The TIP Process. Terminal Integration Process Guide August

11 Introduction Types of TIP Selection of an Approved Terminal You must ensure that you select a terminal that: Thoroughly meets your business needs Passed the required tests and the vendor obtained the required letters of approval, as listed in the following sections. For a terminal with a contact interface: You need to ensure that it has: Passed EMVCo Terminal Type Approval Level 1 Passed EMVCo Terminal Type Approval Level 2 MasterCard recommends that you use the most recent Level 2 application kernel. For further information refer to the list of approved kernels on Obtained the TQM Label (or the vendor must have started the Terminal Quality Management process and provide the reference of the TQM Action Plan.) Obtained, if applicable, PCI-PED security approval. MasterCard recommends that you select a terminal from the M/Chip Approved Products list, in the Smart Card category of Member Publications on MasterCard OnLine. For a terminal with a contactless interface (PayPass): You need to ensure that it has a PayPass Letter of Approval. MasterCard recommends that you select a terminal or card reader from the PayPass Approved Products list on For a dual interface terminal (which has both a contact and a contactless interface): You need to ensure that it meets the approval requirements for terminals with both contact and contactless interfaces, as detailed above. NOTE Adding the contactless interface to an approved terminal with a contact interface may impact the application kernel in such a way that the existing EMVCo approval is no longer valid. This terminal needs a reapproval for the updated kernel by EMVCo. Successful Completion of Network Interface Validation Before starting the TIP, you must have successfully completed Network Interface Validation testing. 1-4 August 2012 Terminal Integration Process Guide

12 Introduction Related Information Terminal Acquirer Host System Setup You must ensure that the terminal, all intermediate connections, and its interfaces (including the clearing interface), together with the Acquirer Host System (AHS) also referred to as the Authorization System are set up according to your own functional requirements and have been thoroughly tested before starting the TIP. This includes the single or dual message interfaces to the MasterCard network systems: Connection Type Message Types Message Format Specifications Dual Authorization / clearing message connection 0100/0110 Authorization messages 1240 Clearing presentment message Customer Interface Specification (CIS) message format AS 2805 message format V5 interface specification IPM clearing format Single message connection 0200/0210 Financial messages MDS message format TIP Contact Information Service providers delivering TIP services are listed in the M/Chip Accredited Third Parties manual, available at MasterCard Online on the Chip Information Center. Acquirers should contact their TIP service provider for any questions about TIP. MasterCard offers support and advice through the chip support services, chip_help@mastercard.com and the chip service management team, chipservicesmanagement@mastercard.com. Terminal Integration Process Guide August

13 Introduction TIP Contact Information Related Information The following documents and resources provide information related to the subjects discussed in this document: General MasterCard Credit Authorization Simulator MasterCard Debit Financial Simulator MasterCard Clearing Presentment Simulator Guide For Contactless Chip PayPass M/Chip, Acquirer Implementation Requirements Maestro PayPass Online PIN Acquirer Implementation Guide v2.0 PayPass User Guide for TIP Subsets Definitions of specific terms used in this document are available in the Glossary. Other terms are explained in the MasterCard Dictionary. To order MasterCard documents, please use the Ordering Publications tool, available in the Quick Links section on the Member Publications home page, or contact the Customer Operations Services team. To order PayPass manuals, please use the ordering publication service on or contact 1-6 August 2012 Terminal Integration Process Guide

14 Business Process Diagram Conventions The business process diagrams in this guide use symbols as shown below: A pool is used to contain activities within an organization. An activity can be atomic (a task) or compound (contain multiple activities). An activity is started (or triggered) by a Start Event, a Time-based Trigger, or a sequence or message flow from another activity. Sequence flow lines (with solid lines and arrowheads) connect one activity to another, to a gateway or to an end event. Gateways signal a split in a process flow or a merger of multiple process flows. Message flow lines (with dashed lines and open arrowheads) connect activities across pools (usually via an artifact). A process contains activities interconnected by means of flow lines. Terminal Integration Process Guide August

15 The TIP Process Implementation Chapter 2 The TIP Process This chapter provides an overview of the Terminal Integration Process and a summary of its subprocesses. Implementation Overview Establish Order With TIP Service Provider ICS Validation Acquirer Preparation TIP Workshop Acquirer Testing Approval Review Terminal Integration Process Guide August i

16 The TIP Process Implementation Implementation Overview The Terminal Integration Process is a collaboration process involving the following entities: The Acquirer (which is you) A TIP Service Provider MasterCard The Terminal Integration Process comprises six subprocesses: Establish order with TIP Service Provider ICS Validation Acquirer Preparation TIP Workshop Acquirer Testing Approval Review NOTE To reduce your project duration, you can do Establish order with TIP Service Provider, ICS Validation, and Acquirer Preparation, then do the remaining subprocesses once you have successfully completed Network Interface Validation (if not already done so). Terminal Integration Process Guide August

17 The TIP Process Establish Order With TIP Service Provider The following figure shows the process and the sequence flow between its constituent subprocesses: Figure 2.1 Terminal Integration Process Establish Order With TIP Service Provider In this subprocess you contact a TIP Service Provider and complete the necessary administrative tasks. This is because the TIP Testing is performed by a Service Provider which you need to pay for. This subprocess is detailed in Chapter 3, Establish Order with TIP Service Provider. ICS Validation In this subprocess the letters of approval, ICS information, terminal and network configuration are checked by the TIP Service Provider and the TIP Test Procedure generated. 2-2 August 2012 Terminal Integration Process Guide

18 The TIP Process Acquirer Testing This subprocess is detailed in chapter Chapter 4, ICS Validation. This subprocess can be done in parallel with Acquirer Preparation. Acquirer Preparation In this subprocess you do the pre-testing preparation. This subprocess is detailed in Chapter 5, Acquirer Preparation. This subprocess can be done in parallel with ICS Validation. TIP Workshop In this subprocess, which only applies if this is your first TIP, TIP service provider presents a two-day onsite workshop which explains the TIP and provides training to your staff that will perform the TIP. If you are carrying out an Additional TIP, there is no TIP Workshop, unless specifically requested. The objectives of the workshop are to: 1. Provide a general overview of the TIP. This part of the workshop is a general presentation of the TIP. It may be of interest to management, as well as to the staff that will perform the TIP. 2. Give hands-on technical training. The technical training consists of: Verification of the terminal configuration The use of Qualified Test Tools (as listed in M/Chip Qualified Test Tools) to save and analyze the dialogue between card and terminal Verification of the MasterCard network simulator configuration Explanations on how to save the MasterCard network simulator and card-terminal logs Explanations on how to use the MCPS simulator to validate the chip data in the clearing presentment messages and save the related MCPS validation logs Explanations on how to interpret the test results Explanations on how to complete the TIP Test Report For the technical training part of the workshop, we recommend that the participants are only those individuals who will be carrying out the actual TIP testing and complete the TIP Test Report. 3. Demonstrate how to run a test. If required, the TIP Workshop can also be used to help you complete the Acquirer ICS (which is part of the ICS Validation.) Terminal Integration Process Guide August

19 The TIP Process Acquirer Preparation Acquirer Testing In this subprocess you do the TIP Scenario Tests that are specified in the TIP Test Report. This subprocess is detailed in Chapter 6, Acquirer Testing. Approval Review In this subprocess you provide your TIP Service Provider with the results of the TIP Test Scenarios that you performed during Acquirer Testing and request approval. The result of the approval review will be one of the following: You are asked to redo some or all or the TIP Tests (that is, another iteration of testing). You have successfully passed TIP, and a Letter of Approval, digitally signed by MasterCard, is issued. This subprocess is detailed in Chapter 7, Approval Review. 2-4 August 2012 Terminal Integration Process Guide

20 Establish Order with TIP Service Provider Overview Chapter 3 Establish Order with TIP Service Provider This chapter details the subprocess where you contact a TIP Service Provider and establish an order for their provision of services for TIP. Overview Process Terminal Integration Process Guide August i

21 Overview The following figure shows the Establish Order with TIP Service Provider subprocess: Figure 3.1-Establish Order with TIP Service Provider Subprocess Establish Order with TIP Service Provider Issuer Vendor 1. Get EMVCo LoA from Terminal Vendor EMVCo LoA and Vendor ICS 2. Get forms from MasterCard OnLine 3. Complete TIP Information Form MasterCard Online TIP Information Form Acquirer ICS Form Terminal and Network Configuration 4. Complete Acquirer ICS Form 5. Complete Terminal and Network Config. 6. Submit forms Forms Letters of Approval TIP Information Form Acquirer ICS Form Terminal and Network Configuration TIP Service Provider 7. Receive Order Form Order Form 8. Complete Order Form 9. Submit completed Order Form 10. Receive order confirmation and invoice Order Form [completed] Order confirmation and Invoice Terminal Integration Process Guide August

22 Establish Order with TIP Service Provider Process Process 1. Get, from your vendor, the appropriate approval documents for the terminal. The approval documents that you need depend upon the type of interface it has. For a terminal with a... You need to obtain the following documents... Contact interface The EMVCo Level 1 approval A copy of the official EMVCo Level 2 Letter of Approval (including the vendor ICS.) The TQM Label or the TQM Action Plan The PCI-PED compliance letter NOTE Ensure that you provide the official EMVCo document, which should look similar to the sample shown in the figure below, and that it has not expired. If the ICS is not part of the Letter of Approval, request it from the vendor as you will need to provide this information to the TIP Service Provider in a later step. Contactless interface (PayPass) Dual Interface A copy of the PayPass Letter of Approval (ensure that it has not expired) The ICS details from the terminal vendor The TQM Label or the TQM Action Plan. All of the above 3-2 August 2012 Terminal Integration Process Guide

23 Establish Order with TIP Service Provider Process Example of an official EMVCo document: 2. You need to get the following documents from They are on the same web page as this process guide: TIP Information Form Terminal and Network Configuration Form If this is the first time that you are doing Terminal Integration, you also need to get Acquirer Implementation Conformance Statement (Acquirer ICS) NOTE There are two variants of the Information and Acquirer ICS forms: one for use when doing TIP for a terminal with a contact interface, and another for use when doing TIP for a terminal with a contactless interface. When doing TIP for a Dual Interface Terminal, you need to get both forms. 3. Complete the TIP Information Form(s), which allows you to provide the administrative information necessary for the TIP to continue. Terminal Integration Process Guide August

24 Establish Order with TIP Service Provider Process 4. Complete the Acquirer ICS Form(s), which allows you to provide the technical information necessary for the TIP to continue. This is a Microsoft Excel worksheet. On the first sheet, MENU, are instructions for how to complete this form; the second sheet, ACQ_ICS_HELP, provides additional help. NOTE If at any point during the TIP there are changes to the information you provide in the Acquirer ICS, you must inform the TIP team immediately. An essential element of information that you provide in the Acquirer ICS is the set of Terminal Action Codes (TACs). The TACs tell the terminal how you want the transaction to be processed in specific situations (such as card authentication failure, expired application, and so forth). To ensure that specific brand requirements are properly handled during terminal risk management, MasterCard has specified required values and settings for the TACs: For terminals with a contact interface, this information is provided in M/Chip Requirements (available on MasterCard OnLine). For terminals with a contactless (PayPass) interface this information is provided in PayPass M/Chip Aquirer Implementation Requirements (available on and Maestro PayPass Online PIN Acquirer Implementation Guide v2.0 (which can be obtained by sending a request to specification@paypass.com) For the TIP, you must select the profile that corresponds to the terminal being tested, and ensure that you: Set the TACs in the terminal accordingly Provide the TACs in the Acquirer ICS Form When completing the Acquirer ICS Form, please pay attention to the following: Ensure that the form is completed by someone who is fully cognizant of your acquirer requirements (do not ask your terminal vendor to complete it) Provide information specific to the terminal being tested (you may use information about the terminal provided by your vendor) If required, and for a First TIP, the TIP Workshop may be used to help you complete the Acquirer ICS and to do the Acquirer Testing (which implies that you have completed both this ICS Validation and the Acquirer Preparation subprocesses.) 3-4 August 2012 Terminal Integration Process Guide

25 Establish Order with TIP Service Provider Process 5. On the Terminal and Network Configuration Form you need to indicate the type of network configuration that you use so that details of how your terminal is connected to the MasterCard network are specified. The Terminal and Network Configuration Form contains four basic scenarios. To complete the document, you should: Choose a scenario, and add and/or delete elements so that it reflects your configuration Complete the questionnaire corresponding to the selected scenario If your setup does not correspond to any of the basic scenarios (that is, you are using a non-standard scenario), you should provide a diagram that describes your complete terminal and network configuration. For a dual interface terminal, if the network path for contact and contactless (PayPass) are different, you need to complete a Terminal and Network Configuration Form for each. 6. Send the completed forms, the Letter(s) of Approval, and the Acquirer ICS information from the terminal vendor, to the TIP service provider. 7. As aspects of the Terminal Integration Process are performed in collaboration with a TIP Service Provider, you will receive an Order Form to cover the provision of their testing services in this regard, and a tracking number. 8. Complete the Order Form. 9. Send the completed Order Form to the TIP Service Provider. NOTE The ICS Validation subprocess cannot take place until the TIP Service Provider has received and confirmed the necessary Order Form. Therefore, to avoid future delays, you must send the Order Form without delay. 10. You receive a confirmation, from the TIP Service Provider, regarding your order and will also receive an accompanying invoice to cover one iteration of TIP Testing. Terminal Integration Process Guide August

26 Chapter 4 ICS Validation This chapter details the subprocess where the letters of approval, ICS information, Terminal and Network Configuration are validated by the TIP Service Provider and the Test Procedure that you need to do is made. This subprocess can be done in parallel with Acquirer Preparation. Overview Process Terminal Integration Process Guide August i

27 ICS Validation Overview Overview The following figure shows the ICS Validation and Test Procedure subprocess: Figure 4.1 ICS Validation Subprocess Process The TIP Service Provider will analyze the information in the forms that you sent them, and you will receive one of the following responses specified in step #1, step #4, or step #7. 1. If there is a problem with the Acquirer ICS, you will receive an to that effect from the TIP Service Provider. NOTE The suffix of the files will be changed by the TIP Service Provider from _MBR to _MCD, and the iteration number incremented. For further information refer to Appendix B, File Naming Conventions. Terminal Integration Process Guide August

28 ICS Validation Process 2. Make the necessary corrections. Each time you resubmit the Acquirer ICS, you are doing an iteration of ICS validation, therefore you must rename the file using the format detailed in Appendix B, File Naming Conventions, as appropriate for the iteration, by: changing the _MCD suffix to _MBR, and incrementing the iteration number. For example: on the first resubmission iteration, you would rename the file ACQICS_ICC_12345_MCD_00.xls to ACQICS_ICC_12345_MBR_01.xls; on the second resubmission iteration you would rename ACQICS_ICC_12345_MCD_01.xls to ACQICS_ICC_12345_MBR_02.xls. 3. Send the corrected Acquirer ICS and TIP Information Form files to the TIP Service Provider. The TIP Service Provider will analyze the information in the forms that you sent them, and you will receive one of the following responses specified in step #1, step #4, step #7. 4. If the Acquirer ICS and the Letter(s) of Authority are not compliant with each other you will receive an to that effect from the TIP Service Provider. NOTE The suffix of the files will be changed by the TIP Service Provider from _MBR to _MCD, and the iteration number incremented. For further information refer to Appendix B, File Naming Conventions. 5. Make the necessary corrections. Each time you resubmit the Acquirer ICS, you are doing an iteration of Acquirer ICS validation, therefore you must rename the file using the format detailed in Appendix B, File Naming Conventions, as appropriate for the iteration, by: changing the _MCD suffix to _MBR, and incrementing the iteration number. 6. Send the corrected file back to the TIP Service Provider. The TIP Service Provider will analyze the information in the forms that you sent them, and you will receive one of the following responses specified in step #4 or step #7. 7. The TIP Service Provider will determine which TIP Tests need to be performed, and you will receive, in an , the TIP Test Procedure and a TIP Test Report. 4-2 August 2012 Terminal Integration Process Guide

29 Chapter 5 Acquirer Preparation This chapter details the subprocess where you do the preparation that must be done before you are able to being the testing. This subprocess can be done in parallel with ICS Validation. It is recommended that you do this subprocess as soon as possible as any delays in obtaining the tools and simulators (such as due to problems with shipping or customs) could impact your ability to start the Acquirer Testing subprocess. Overview Process Terminal Integration Process Guide August i

30 Acquirer Preparation Overview Overview The following figure shows the Acquirer Preparation subprocess: Figure 5.1 Acquirer Preparation Subprocess Process There are four tasks within this subprocess, which may be done in parallel with each other: Obtain latest TIP Test Tool (A) You must obtain a Qualified TIP Test Tool that meets your needs for TIP. For details of available tools and their vendors for contact-based terminals, refer to M/Chip Qualified Test Tools; available at MasterCard OnLine on the Chip Information Center. If the terminal that you are testing has a contactless (PayPass) interface or is a Dual Interface Terminal, you also need to obtain the TcMonitor software which is available on request to chipservicesmanagement@mastercard.com. Terminal Integration Process Guide August

31 Acquirer Preparation Process Obtain and connect latest version of the Network Simulator (B) You must ensure that you have obtained and installed the latest version of the MasterCard Network Simulator, which is available on MasterCard OnLine. The simulator that you need to use depends upon the network interface message format: For CIS format: MasterCard Authorization Simulator (MAS) For MDS format: MasterCard Debit Financial Simulator (MDFS) Connect your Acquirer Host System (AHS) to the Network Simulator. Obtain latest version of the MasterCard Clearing Presentment Simulator (MCPS) (C) NOTE This task is only applicable if you are using a dual authorization/clearing interface and you are clearing the ICC system-related data (DE55) in the presentment messages. You must obtain and install the latest version of the MCPS, which is available on MasterCard OnLine. For information on how to install and use the MCPS, refer to MasterCard Clearing Presentment Simulator Guide in Appendix E, How to Validate the IPM File Using the MCPS provides additional information for specific use during the TIP. Connect and configure terminal (D) You need to connect your terminal to your Acquirer Host System (AHS) as it will be connected in the live environment after approval, including all intermediate connections, where possible. Configure the terminal exactly as it will be used in the live environment. 5-2 August 2012 Terminal Integration Process Guide

32 Acquirer Preparation Process You must also ensure that you set up your terminal according to the following specifications: The list of Application Identifiers (AID) supported by the terminal must be the same as the one that is used in the field. All the applications must be loaded onto the terminal (MasterCard applications and proprietary applications, if any). This ensures that the proprietary applications do not interfere with the expected behavior of the terminal, in accordance with MasterCard rules. The pre-defined test keys (the MasterCard Payment System test public keys) must be loaded onto the terminal for the offline CAM check. These keys can be found in the user manual accompanying your Qualified TIP Test Tool. For online capable attended, and unattended, POS terminals that support floor limits, the amount must be set to (or ). For offline only terminals, the floor limit must be set to (or ). For contact terminal applications, the Terminal Application Version Number must be set to 0002 for MasterCard, Maestro and Cirrus AIDs. For contactless (PayPass) terminal applications, the Terminal Application Version Number must be set to 0002 for PayPass M/Chip and Maestro PayPass, and to 0001 for PayPass Mag Stripe. For contactless (PayPass) terminal applications, if the terminal supports Optimized Flow (previously known as Offline-Only Flow ), MasterCard recommends that you set the floor limit to a maximum value. This ensures the transaction amount is not greater than the floor limit. The Issuer Action Codes (IAC) on the TIP test tool are set such that the terminal declines if the transaction amount is greater than the floor limit. NOTE The amount value follows ISO If the amount indicated is equal to , and the currency is EUR, you must enter 1500; this is because the currency field automatically includes a 2-digit exponent, and you must not input leading zeros. Terminal Integration Process Guide August

33 Chapter 6 Acquirer Testing This chapter details the subprocess where you do the TIP testing and package the test results for subsequent analysis. Overview Process Rename TIP Test Report Test Authorization or Financial Messages Overview Process Test Clearing Presentment Messages Overview Process Terminal Integration Process Guide August i

34 Acquirer Testing Overview Overview The following figure shows the Acquirer Testing subprocess: Figure 6.1 Acquirer Testing Subprocess Process The Acquirer Testing subprocess comprises one task and two activities, which are detailed in the following sections. 1. Rename TIP Test Report 2. Test Authorization or Financial Messages 3. Test Clearing Presentment Messages 1. Rename TIP Test Report Each time you start the Acquirer Testing subprocess you are doing a new test iteration, therefore you must rename the TIP Test Report, using the format detailed in Appendix B, File Naming Conventions, as appropriate for the iteration, by: changing the _MCD suffix to _MBR, and incrementing the iteration number. For example: on the first test iteration, you would rename the file TIP_ICC_12345_MCD_00.xls to TIP_ICC_12345_MBR_01.xls; on the second test iteration you would rename TIP_ICC_12345_MCD_01.xls to TIP_ICC_12345_MBR_02.xls. Terminal Integration Process Guide August

35 Acquirer Testing 2. Test Authorization or Financial Messages 2. Test Authorization or Financial Messages Overview In this subprocess, you test your terminal with 0100/0110 Authorization Messages or 0200/0210 Financial Messages. The following figure shows the Test Authorization or Financial Messages subprocess: Figure 6.2 Test Authorization or Financial Messages Subprocess 6-2 August 2012 Terminal Integration Process Guide

36 Acquirer Testing 3. Test Clearing Presentment Messages Process Follow the process below to show the Test Authorization or Financial Messages subprocess: 1. Start the MasterCard simulator. Refer to Appendix D, How to Use the Simulator, for specific information. 2. You need to initialize (delete or create) logs made by the MasterCard simulator. If you are using CIS or MDS message formats, then delete any previous logs captured by the MAS or MDFS. a) Go to Test Results window. b) Click the Delete Log button. 3. Do the test transaction. Each time you do this task, you need to do a TIP Test Scenario, as listed in the TIP Test Report, which you have not previously done. NOTE The tests you need to do in this subprocess are those that are not prefixed with Clearing in the Card ID column. Refer to Appendix A, Understanding the TIP Test Scenarios, for details of how the scenarios are documented and need to be done. Use the card terminal logger in your TIP Test Tool to record the interaction between the card and the terminal during the test transaction. Refer to the documentation from your TIP Test Tool vendor for details of how this is achieved. 4. Save the card terminal log. After you have performed the TIP Test Scenario, you need to save the card terminal interaction that was logged by your TIP Test Tool. Refer to the documentation from your TIP Test Tool vendor for details of how this is achieved. NOTE The file must be saved using the format detailed in Appendix B, File Naming Conventions. Terminal Integration Process Guide August

37 Acquirer Testing 3. Test Clearing Presentment Messages 5. Update the TIP Test Report to record information, particularly the date and time, regarding the test you just performed. Refer to Appendix C, How to Update the TIP Test Report, for further information If you have more TIP Test Scenarios to do, go to step #3 otherwise continue to step #6 if it is the end of the testing day. 6. Save the simulator log. Name the file ddmmyy.mdb, where dd is the day, mm is the month, and yy is the year, for example, mdb. For more information, refer to the user guide accompanying your simulator. If you have more TIP Test Scenarios to on the test day, wait until the next test day and go to step #2. 7. If any of the tests failed, that is, an ACQ_STATUS was NOK, then: Make the appropriate changes required to remedy the problem Go back to step #2 to repeat the tests that failed. NOTE Depending on which TIP Test Scenario failed and/or the reason why it failed, you can decide not to make any changes and instead to finish this subprocess. However, by choosing to finish, there is a risk that when you submit your test results that you will not be granted TIP approval and have to do another iteration of testing, which results in increased cost and time to complete the TIP. 3. Test Clearing Presentment Messages NOTE In this subprocess, you test your terminal for clearing presentment messages. This subprocess is only required if you are using a dual authorization/clearing interface and you are clearing the ICC system-related data (DE55) in the presentment messages. In the Europe region, DE55 is mandatory in clearing messages; in other regions it is highly recommended that you include this data in your clearing messages. 6-4 August 2012 Terminal Integration Process Guide

38 Acquirer Testing 3. Test Clearing Presentment Messages Overview Figure 6.3-Test Clearing Presentment Messages Subprocess Test Clearing Presentment Messages Acquirer 1. Reset terminal approved trans. log 2. Reset clearing batch on AHS 3. Do a test transaction 4. Save the card-terminal log 5. Update TIP Test Report More tests? All tests done 6. Download terminal clearing transactions 7. Transfer IPM file from AHS to MCPS 8. Validate IPM File using MCPS Simulator 9. Save MCPS log Errors encountered during testing? 10. Make changes to fix error(s) Terminal Integration Process Guide August

39 Acquirer Testing 3. Test Clearing Presentment Messages Process Follow the process below to test your terminal for clearing presentment messages. 1. Reset the Terminal Approved Transaction Log (or Terminal Clearing Batch). To ensure that the IPM file that will be validated only includes clearing presentment messages that are related to the TIP testing, the terminal approved transaction log (or terminal clearing batch) is reset prior to the TIP test. This can either be done by one of the following (depending upon your infrastructure): Via a specific reset function on the terminal (if available) By doing a terminal clearing batch download to the acquirer host 2. Reset the Clearing Batch on your Acquirer Host System. The IPM file that will be validated needs to be reset so that when it is validated it only includes clearing presentment messages that are related to the TIP Testing. The mechanism you need to reset the clearing batch depends upon your member host implementation. 3. Do a test transaction. You need to do a TIP Test Scenario as listed in the TIP Test Report. Refer to Appendix A, Understanding the TIP Test Scenarios, for details of how the scenarios are documented. NOTE The tests you need to do in this subprocess are prefixed with Clearing in the Card ID column in the TIP Test Report. Use the card terminal logger in your TIP Test Tool to record the interaction between the card and the terminal during the test transaction. Refer to the documentation from your TIP Test Tool vendor for details of how this is achieved. 4. Save the card terminal log. After you have performed the TIP Test Scenario, you need to save the card terminal interaction that was logged by your TIP Test Tool. Refer to the documentation from your TIP Test Tool vendor for details of how this is achieved. NOTE The file must be saved using the filename schema detailed in Appendix B, File Naming Conventions. 5. Update the TIP Test Report to record information regarding the test you just performed. Refer to Appendix C, How to Update the TIP Test Report, for further information Go back to step #3 if you have more tests to do, otherwise continue to step # August 2012 Terminal Integration Process Guide

40 Acquirer Testing 3. Test Clearing Presentment Messages 6. Download the Resulting Terminal Clearing Transactions and Generate Corresponding IPM Clearing File. Initiate the download of the terminal approved transaction log (or terminal clearing batch) to the acquirer host. This procedure depends upon your infrastructure. Usually, this is done by using the standard terminal batch download (or batch data capture) function which can either be initiated from the terminal or by the acquirer host. 7. Transfer the IPM file from your host system onto the computer where you installed the MCPS. The mechanism to transfer the IPM depends upon your infrastructure. 8. Validate the IPM File using the MCPS. For guidance on how to do this, refer to Appendix E, How to Validate the IPM File Using the MCPS. 9. Save the MCPS Log. NOTE The file must be saved using the filename schema detailed in Appendix B, File Naming Conventions. 10. If you have encountered errors during testing, make changes to fix the error, and then go to step #1. Terminal Integration Process Guide August

41 Chapter 7 Approval Review This chapter details the subprocess where you provide the TIP Service Provider with the results of the TIP Test Scenarios that you performed and request an assessment. If the assessment is positive you will receive a TIP Letter of Approval; if the assessment is negative you will receive a list of TIP Test Scenarios that you must do in another iteration of testing. Overview Process Terminal Integration Process Guide August i

42 Approval Review Overview Overview The following figure shows the Approval Review subprocess: Figure 7.1 Approval Review Subprocess Process 1. Send an to your TIP service provider. The TIP Test Report NOTE When doing TIP for a Dual Interface Terminal, remember to send the TIP Test Reports for both the contact (EMV) and contactless (PayPass) parts. The card terminal logs. The simulator log(s). If applicable, the IPM file. Terminal Integration Process Guide August

43 Approval Review Process 2. You will receive, by from the TIP Service Provider, the result of their analysis. This is done by returning the TIP Test Report which have been annotated as appropriate. NOTE The filename of the TIP Test Report returned to you will have the suffix _MBR changed to _MCD. For a successful approval review, there will be an additional suffix of _FINAL. For an unsuccessful approval review, the iteration number incremented. For more information, refer to Appendix B, File Naming Conventions. The rows within the report will be colored using the following schema: Gray (Closed): The test is successfully closed, everything is OK and the member does not have to do anything for this test (so no need to redo it or resend the test results) Yellow (Pending): the test was performed by the member, it failed however and the line in Yellow contains the data as entered by the member with MC comments added to explain why the test failed. White: This is a copied line of the pending test which the member can fill out when he re-performs his tests. This is to keep a history of what goes on. There will also be four new columns added (if not already present): MC Results Contains the same data as ACQ Results, and may include additional comments (in red) as a result of the analysis review. MC Status: This will contain one of the following: PASS: The results match the criteria described in the TIP Test Scenario. PENDING: The TIP Service Provider does not have all the information to determine whether the test has successful or not, and may request additional information. FAIL: The results do not match the criteria described in the TIP Test Scenario. You need to contact the TIP Service Provider for further information. N/R: The test is Not Required (N/R) MC Test Status: Once a test is passed (that is, MC Status is set to PASS), this is set to CLOSED, otherwise it remains OPEN. MC Test Status Date: Date on which the TIP Service Provider makes a decision on the test results. 3. If the Approval Review was successful, you will receive a Letter of Approval which has been digitally signed by MasterCard. 4. If the Approval Review was successful, and there was more than one iteration of approval review, the TIP Service Provider will send you an invoice to cover these additional iterations. 7-2 August 2012 Terminal Integration Process Guide

44 Appendix A Understanding the TIP Test Scenarios This appendix details how the TIP Test scenarios are documented so that you can understand what you need to do to perform the test. Example of a TIP Test Scenario...A-1 Header Scenario Identification Information...A-2 Body Scenario Details...A-2 Objective...A-2 Applicability Conditions...A-2 Transaction Type...A-2 Reference Documentation...A-2 Card Configuration...A-3 User Action...A-3 Simulator Configuration...A-3 Pass Criteria...A-3 Note...A-4 Terminal Integration Process Guide August 2012 A-i

45 Understanding the TIP Test Scenarios Example of a TIP Test Scenario Example of a TIP Test Scenario Figure A.1-Example of a TIP Test Scenario REQ01 MASTERCARD Objective Applicability Condition Simulator Status Test 02 Scenario 01 To ensure that the terminal is able to receive and correctly transmit the issuer decision in its final environment of use. Terminal supports MasterCard. Terminal is not offline only. Terminal is not identified as an On-board. Terminal does not support Voice on a consistent basis. NA Transaction Type Online Credit-Debit Online Test: Yes Reference Documentation Card configuration User Action Simulator Configuration See document [6], chapter 10-9 EMV Online processing. The AlP (tag 82) returned by the ICC during GET PROCESSING OPTION command indicates that ICC does not support Offline Data Authentication (tag 82 = => EXTERNAL AUTHENTICATE command is not supported). Please, use the following test card REQ01 MASTERCARD I 5.0.A Insert card in the chip reader and follow the instructions. Amount must be equal to or For REQ01 MASTERCARD I 5.0.A test card, PIN value is 4315 (if requested). Issuer response message: DE 039 (Response code)= '00' (Approved). DE 055- PDS 91 (Issuer Authentication Data) is present Issuer script = none. MasterCard application is selected and the terminal requests an online authorization. In online authorization request, 'amount other' field (DE 055- PDS 9F03) must either contain ' ' or must not be present Pass Criteria Even though an lad is sent by the Issuer, the card must not receive an EXTERNAL AUTHENTICATE command after the first Generate AC as Issuer Authentication using External Authenticate is not supported by the card TVR byte 1, bit 8 = '1' --> Offline data authentication was not performed The transaction will be approved. Note NIA Each row of the TIP Test Scenario is described in detail in the following sections. Terminal Integration Process Guide August 2012 A-1

46 Understanding the TIP Test Scenarios Header Scenario Identification Information Header Scenario Identification Information The following table describes the header information: Cell Information Description Top left ETEC Test Identification Identifies the TIP test name (for example, REQ01 MASTERCARD). Top middle Test Number Indicates the number of the Test (for example, Test 02). There may be more than one test for the same TIP test name. The Test Number is linked to the Objective in the scenario details. Top right Scenario Number Indicates the number of the scenario (for example, Scenario 01). There may be more than one scenario per test. The scenario number is linked to the Applicability Conditions in the scenario details. Body Scenario Details Objective The following sections describe the body information. The Objective section describes the specific purpose of the test. In this scenario, the objective is to determine if the terminal behaves correctly during an online transaction. Applicability Conditions The Applicability Conditions section describes the transaction environment in which the test should be carried out. They are linked to a specific scenario number, in this instance Scenario 01. Transaction Type The Transaction Type section describes if the transaction is debit, credit or both, and if the test should be run online or offline. When a test indicates online, this means that the authorization request must pass through the MasterCard network simulator. Reference Documentation The Reference Documentation section provides a reference to a specific chapter, or section, of the relevant reference documentation. A-2 August 2012 Terminal Integration Process Guide

47 Understanding the TIP Test Scenarios Body Scenario Details Card Configuration The Card Configuration section describes the card settings related to the test. In this scenario, the AIP profile is set to 1800 to ensure that the card does not request the terminal to perform offline card authentication (SDA or DDA process). User Action The User Action section describes the tasks you must perform during a test. These may include: 1. Card name that can be used for the specific test 2. Enter a PIN (use the number specified in the User Action row according to the card use). 3. Enter an amount (use the amount specified in the User Action row). NOTE You must use the correct PIN, or amount, to force the correct response from the MasterCard network simulator. The amount value follows the ISO 4217 specifications. If the amount indicated is equal to , and the currency is EUR, you must enter 15. This is because the currency field automatically includes a 2-digit exponent, and you must not input leading zeros. Simulator Configuration For authorization or financial message testing, the Simulator Configuration section describes the response expected from the MasterCard network simulator, which acts as the issuer. If the response you receive is different, you should check that you sent the correct PAN and amount to the MasterCard network simulator based on the combination of PAN and amount, the MasterCard network simulator automatically selects the appropriate type of response it should send back. For clearing message testing, the Simulator Configuration section describes the additional setup of the MCPS simulator. Pass Criteria The Pass Criteria describes all the criteria that must be met for the test to pass successfully. When you complete a test, you must indicate the results in the ACQ RESULTS section of the TIP Test Report. See Appendix C, How to Update the TIP Test Report. Terminal Integration Process Guide August 2012 A-3

48 Note Where appropriate, additional information may be provided in this field. A-4 August 2012 Terminal Integration Process Guide

49 Understanding the TIP Test Scenarios Body Scenario Details Appendix B File Naming Conventions This appendix details the naming conventions that are used for the files that are used during TIP. TIP INFO Filename...B-1 TIP Acquirer ICS Filename...B-1 TIP Test Report Filename...B-1 Card-Terminal Log Filenames...B-1 MasterCard Authorization and MasterCard Debit Financial Simulator Log Filenames...B-2 Terminal Integration Process Guide August 2012 B-i

50 File Naming Conventions MasterCard Authorization and MasterCard Debit Financial Simulator Log Filenames TIP INFO Filename An example: TIP-INFO_ICC_ _MCD_01.xls The TIP INFO Filename contains: TIP_INFO which identifies the TIP step concerned ICC or PPC depending if the TIP is EMV contact or PayPass related The TIP Activity Number The end of the filename indicates whether the file is from MasterCard (MCD), or the acquirer (MBR) The iteration number of the file exchange The TIP Acquirer ICS Filename and TIP Test Report Filename are managed similarly. TIP Acquirer ICS Filename An example: ACQ-ICS_ICC_ _MCD_01.xls The TIP Acquirer ICS Filename contains: ACQ-ICS, that identifies the TIP step concerned ICC or PPC depending if the TIP is EMV contact or PayPass related The TIP Activity Number The end of the filename, that indicates whether the file is from MasterCard (MCD), or the acquirer (MBR) The iteration number of the file exchange TIP Test Report Filename An example: TIP_ICC_ _MCD_01.xls The TIP Test Report contains: ICC or PPC if the TIP is EMV contact or PayPass related The TIP Activity Number The end of the filename, that indicates whether the file is from MasterCard (MCD), or the acquirer (MBR) The iteration number of the file exchange Card-Terminal Log Filenames An example: MC_REQ01_t02_s01.txt When you save the card-terminal log for each test, you should name it as follows: PD_RQ#_T#_S#.txt Terminal Integration Process Guide August 2012 B-1

51 Where: PD is the card product name MC MasterCard MS Maestro CI Cirrus RQ# is the ETEC card number For example: REQ01, REQ02, Interop12, PPS01, PPC02, etc. T# is the test number For example: T01, T02, etc. S# is the scenario number NOTE For example: S01, S02, etc. The log filenames do not have an iteration number as they are always sent together with the TIP Test Report which has a unique identification. MasterCard Authorization and MasterCard Debit Financial Simulator Log Filenames An example: mdb When you save the MasterCard Authorization or MasterCard Debit Financial simulator log, you should name it as follows: ddmmyy.mdb Where: dd is the day mm is the month yy is the year B-2 August 2012 Terminal Integration Process Guide

52 How to Update the TIP Test Report TIP Test Report Cells Appendix C How to Update the TIP Test Report This Appendix describes how to update the TIP Test Report. TIP Test Report Cells... C-1 ACQ DATE... C-1 ACQ TIME... C-1 ACQ RESULTS... C-1 ACQ STATUS... C-2 ACQ SPY Log File Name... C-2 ACQ SIM Log File Name... C-2 Terminal Integration Process Guide August 2012 C-i

53 How to Update the TIP Test Report TIP Test Report Cells TIP Test Report Cells After completing a TIP Test Scenario, you need to update the following cells for the entry in the TIP Test Report for the TIP Test Scenario on the Reports sheet: ACQ DATE ACQ TIME Enter the date you ran the test. Enter the time you started the test. ACQ RESULTS This cell is prefilled with the expected results of the TIP Test Scenario. Against each expected result will be OK/NOK or OK/NOK/Not Applicable. You need to delete the status that does not apply, and may optionally add a comment directly after the status (OK or NOK) to clarify the test results. For example: Checking according test pass criteria: Test settings: - For REQ01 MASTERCARD / 5.0.A test card, PAN = OK/NOK - Amount is or or or OK/NOK - Issuer simulator ARC = 00 - OK/NOK Terminal behavior: - Terminal does not send Internal Authenticate command - OK/NOK - TVR B1b8 = 1 - OK/NOK - CDOL2 ARC (Tag 8A) = OK/NOK Card behavior: - The card replies with a TC in response to the second GENERATE AC command - OK/NOK - The transaction is approved - OK/NOK Terminal Integration Process Guide August 2012 C-1

54 Would be changed to the following (assuming all tests were successfully passed): Checking according test pass criteria: Test settings: - For REQ01 MASTERCARD / 5.0.A test card, PAN = OK - Amount is or or or OK - Issuer simulator ARC = 00 - OK Terminal behavior: - Terminal does not send Internal Authenticate command - OK - TVR B1b8 = 1 - OK - CDOL2 ARC (Tag 8A) = OK Card behavior: - The card replies with a TC in response to the second GENERATE AC command - OK - The transaction is approved - OK ACQ STATUS Indicate your assessment of status of the test: The results match the test criteria as described in the Test Scenario: set to OK. You do not have all the elements to run the test, or to provide a test analysis (for example, the specific environment is not yet ready): set to PENDING The results do not match the test criteria as described in the Test Scenario: set to NOK The test is not applicable. Set to N/A and explain why you feel that the test does not apply to your terminal. ACQ SPY Log File Name Enter the name of the card terminal log file that you created for this TIP Test Scenario. Remember to follow the convention specified in Appendix B, File Naming Conventions. ACQ SIM Log File Name Remember to follow the convention specified in Appendix B, File Naming Conventions. C-2 August 2012 Terminal Integration Process Guide

55 How to Use the Simulator Introduction Appendix D How to Use the Simulator This appendix provides supplementary information on how to use the MasterCard Authorization Simulator (MAS) and the MasterCard Debit financial Simulator (MDFS) when performing the Terminal Integration Process. Introduction... D-1 Setting Up the Simulator for TIP Testing... D-1 TIP Testing... D-5 Terminal Integration Process Guide August 2012 D-i

56 How to Use the Simulator Introduction Introduction For specific information on how to use these simulators refer to the documentation that accompanies them. It is assumed that: That you have the latest version of the simulator software. Check MasterCard OnLine for the latest versions and service packs. The simulator software has been installed. The computer running the simulator software is connected to your acquirer host infrastructure via a TCP/IP network Setting Up the Simulator for TIP Testing To setup the simulator in the appropriate mode for TIP Testing, do: 1. From the Navigator window, select the APS Host testing mode and wait for the indicator to change from orange ( connecting ) to green ( connected ), Terminal Integration Process Guide August 2012 D-1

57 How to Use the Simulator Setting Up the Simulator for TIP Testing 2. From the Navigator window, click Set Options to display the Options window. 3. In the Options window select the Acquirer Table tab 4. Click the new button to create an AID entry or AID range in the AcquirerID_User subtree for your ICA. D-2 August 2012 Terminal Integration Process Guide

58 How to Use the Simulator Setting Up the Simulator for TIP Testing 5. Select the Test Mode Options table and ensure that the following options are set to true: Network always Forwards Request Messages Network Always Forwards Response Messages 6. From the Navigator window, click on Test Monitor to display the Test monitor window. Terminal Integration Process Guide August 2012 D-3

59 How to Use the Simulator Setting Up the Simulator for TIP Testing 7. In the Test Monitor window, ensure that the ETEC response profiles are enabled for the TIP Testing that you will be performing. Specifically: When testing against a contact terminal, ensure that TIP Test Cases is enabled. When testing against a contactless (PayPass) terminal, ensure that OneSMART PayPass ETEC8 is enabled. D-4 August 2012 Terminal Integration Process Guide

60 How to Use the Simulator TIP Testing TIP Testing When performing the TIP Tests, it is recommended that the Test Results window is opened. Click Test Results on the Navigator window. The Test Results window is opened. Terminal Integration Process Guide August 2012 D-5

61 Appendix E How to Validate the IPM File Using the MCPS This appendix provides general guidance on how to use the MCPS to validate an IPM File. Refer to MasterCard Clearing Presentment Simulator Guide for more detailed information. Process... E-1 Terminal Integration Process Guide August 2012 E-i

62 How to Validate the IPM File Using the MCPS Process Process 1. If not already done, install the MCPS. 2. Start the MCPS. 3. Start the Clearing Emulation Engine (CEE) component. 4. Set the CEE Preferences. From the File menu, select CEE Preferences. In the CEE Preferences dialog, ensure that Validate DE55 Cryptogram is checked and then click OK. Terminal Integration Process Guide August 2012 E-1

63 How to Validate the IPM File Using the MCPS Process 5. Reset the CEE log. From the View menu select Log. In the View Log dialog, click Clear Log. E-2 August 2012 Terminal Integration Process Guide

64 How to Validate the IPM File Using the MCPS Process 6. Add the IMP File From the File menu select Add File. In the Open dialog choose the IPM file. 7. Verify the results. From the View menu select Log. Terminal Integration Process Guide August 2012 E-3

65 How to Validate the IPM File Using the MCPS Process A successful test is when all records in the IPM file are valid. 8. Copy and rename the MCPS log The MCPS-CEE Log Filename and path is displayed in Log File Name. Copy this file into a convenient location and rename it using the convention specified in Appendix B, File Naming Conventions. E-4 August 2012 Terminal Integration Process Guide