SELF-CERTIFICATION USING THE UL STP

Transcription

1 SELF TEST PLATFORM SELF-CERTIFICATION USING THE UL STP 1

2 TABLE OF CONTENTS INTRODUCTION 3 ACCESS AND LOGIN 3 DASHBOARD/HOME 4 PROJECTS 5 Project Dashboard and Details 6 Overview tab 7 Project Management tab 8 Users tab 8 Documents tab 9 Notifications tab 10 Project Comments tab 10 Audit Log tab 11 SETTINGS 11 General Settings tab 12 Connectivity tab 13 CONFIGURATION 14 CONTACT INFORMATION TAB 15 Terminal Information tab 16 Acquirer Information 17 Test Tool 17 Brands tab 18 Moving your Project to Test Plan Settings 19 TEST PLAN SETTINGS 20 American Express 20 Discover 21 MasterCard 21 Visa 22 Moving your Project to Pre-Certification 22 PRE-CERTIFICATION 23 Actions menu 23 Pre-Certification Tests 24 Moving your Project to Certification 29 CERTIFICATION 30 POST-CERTIFICATION REVIEW 30 2

3 INTRODUCTION This user manual details the process of submitting a project for self-certification using the UL Self-Test Platform (STP). UL STP is designed to automate testing and facilitate unattended testing of projects by Acquirers and Merchants, allowing tracking of the Terminal Certification Process. After completing integration, you can start the process of self-certification using the UL STP. The STP walks your project through a series of steps that include: Setup and Configuration Test Plan Pre-Certification Certification Some of the steps are dependent on the steps completed previously, and cannot be completed until you complete the previous steps. For example, you cannot move forward with Pre-Certification until you have completed Configuration and Test Plan. ACCESS AND LOGIN The UL STP is a web-based application that requires an internet connection and supported browser (Google Chrome is recommended). Login to the UL STP with your provided credentials. If you do not have credentials, STPAccounts@epx.com. NOTE: IF THIS IS YOUR FIRST TIME LOGGING INTO THE UL STP, YOU ARE PROMPTED TO CHANGE YOUR PASSWORD. FOLLOW THE PRO- VIDED INSTRUCTIONS. 3

4 DASHBOARD/HOME Upon login, you are presented with your dashboard. On this screen you can: View your name View project activity for the last 24 hours View shortcuts that you have configured View starred projects Navigate to the Projects, Customer, Transaction History, and Reports tabs Perform Administrative functions View Help Logout To navigate to the list of existing projects, and also begin a new project, click the Project tab. 4

5 PROJECTS Typically, users navigate to Projects to cover two scenarios: New integration to EPX, such as new software, and/or new vendor, which requires EMV. Existing Integrations with EPX that want to add EMV. The Projects screen lists all currently active projects, sorted by Creation Date. Project Name, Type, Customer (if applicable) current Step, State, and Creation Date displays for every project on the list. Click on a column headers to sort by ascending or descending order, to help find projects easier. You may also use the Search function to narrow the project list. To view/edit an existing project, click the project Name. To start a new project, click the New Project button. When starting a new Project, the Create New Project pop-up displays. You are required to enter a Project Name. The project Type defaults to Authorization, and no other types are available to select at this time. Click the Save button. YOUR NEW PROJECT HAS BEEN CREATED, AND THE PROJECT DASH- BOARD SCREEN DISPLAYS. 5

6 PROJECT DASHBOARD AND DETAILS The Project Dashboard screen displays when you have created a project, or selected a project to view its details. The Project Dashboard initial view displays: The name of the Project An illustration of the Steps, and project status related to these steps A section displaying tabbed pages, and a display section to view/edit the details of each tab. 6

7 OVERVIEW TAB The overview tab displays details about the project, including: Creation Date (and time) Last Audited Action date (and time) Project Name Project Type Current State (the current state of the project) Current Step (the current step the project is on) Last Activity 7

8 PROJECT MANAGEMENT TAB The Project management tab displays: Current Step dropdown: select the step the project is currently performing. Some steps are dependent on completing previous steps. Current state: the current state on the project. Draft is the only option available until test cases have been generated in STP for at least one brand. When you have finished making edits to the Project Management tab, click the Save button. USERS TAB The users tab allows you to add users to your project. Note: users must have an access to the UL STP in order to be added to your project. If a user does not currently have access to UL STP, you will need to request access. Once the user has access, s/he can be added to projects. To add a user, click in the user box and start typing the user s name. The tool automatically starts to search and display a list of matching users. Click the user that matches, and then click the Save button. The user is now added to your project. 8

9 DOCUMENTS TAB The documents tab allows you to upload documents to your project, such as Word docs, pdfs of requirements needed for testing, Test cases and XML files. To upload a document, click the Upload a File button. This opens a dialog that allows you to select and upload files. NOTIFICATIONS TAB The Notifications tabs displays status notifications that come thru during the lifecycle of the project. 9

10 PROJECT COMMENTS TAB The Project Comments tab allows you and your users to enter and view comments about the project. To add a new comment, click the Add Comment tab. Type your comment into the provided box and Save. The comment then displays on the tab with your name, date and time. AUDIT LOG TAB The Audit Log tab displays a list of actions related to the project, such as Project Created, Project File Uploaded, and Project Step Changed. 10

11 SETTINGS Click the Settings icon to go to the Settings screen. GENERAL SETTINGS TAB The General Settings tab displays the name of the project (which can be changed) and the Customer field. 11

12 To add a Customer to the project, the Customer must be active in the UL STP. Click in the Customer box and start typing the customer s name. When the matching customer appears on the list, click to select, and then click the Save button to associate the customer with the project. If your customer does not appear on the list, save your project (so that you don t lose your work), and click the Customers tab in the top navigation bar. Click the the Add button to open the Add Customer box. Enter the customer name and select a type, and then click the Add button. You can then navigate back to your project and the customer will appear on the list. 12

13 CONNECTIVITY TAB The connectivity tab displays the Merchant IDs (MIDs) and Terminal IDs (TIDs) that are associated with the project. You MUST add MIDs and TIDs to your project to test. MIDs and TIDs are assigned to your project during Integration. Depending on your project, you need to add MIDs and TIDs for each brand/network. Usually, projects have 1 MID and TID for Visa/MasterCard, another MID and TID for Discover, and a third for Amex. TIDs may vary in the characters and configuration, depending on the brand/network. For instance one network may need it to be and another may need a 1 with 7 spaces after. To add a Merchant ID or Terminal ID, click the Add Identifier button. This opens the fields for entry. Ensure you have the MIDs and TIDs assigned to your project during the Integration process. Select the Active checkbox to make the MID/TID active for the project. Select the Type from the dropdown (MID or TID) Enter the identifier for the MID or TID, depending on the type. MIDs have 6 to 15 alphanumeric characters, depending on the brand; and TIDs have 8 alphanumeric characters. See above for additional details on MID and TID character configuration. You may add as many identifiers as needed for a project. When finished, click the Save button. 13

14 CONFIGURATION The Configuration screen has tabs containing information about the project that must be completed in order to start the testing phase. 14

15 CONTACT INFORMATION TAB The contact information tab must be completed to begin testing. All fields are required, except for Contact Province/State. When finished, click the Save Questionnaire button. 15

16 TERMINAL INFORMATION TAB The Terminal Information tab displays information related to the terminal you are using for testing. You must complete the minimum required fields before you can proceed with testing. These fields include: Brand Model Supplier Name (not required) Supplier Country (not required) Card Reader Brand Card Reader Model Card Reader Name Card Reader Supplier Country EMV Kernel Name Payment Application Software and Version Countries of Deployment Currency Code (ISO 4217 Numeric) EMVCo Level 1 LOA (file upload) EMVCo Level 2 LOA (file upload) When finished, click the Save Questionnaire button. 16

17 ACQUIRER INFORMATION The Acquirer Information tab displays information regarding the acquirer, but is not required for testing. TEST TOOL Enter the name of the test tool you are using into the provided field. This is not required for testing. If using UL s BTT tool, make sure you have the latest version, as new versions are released quarterly and fixes are released weekly. You can find the latest version of the BTT test tool In the BTT Update project, located in the Projects section. Open the BTT Update project and navigate to Dashboard/Documents. Click on the file to download the update. 17

18 BRANDS TAB Select the brands that you ll be using for testing. The Brands displayed depends on the customer you selected on the Settings/General Settings tab, as the customer has the brands configured to them as part of the Customer Setup. Select the brands in scope for the project, and then click the Save Questionnaire button. If a brand is not displayed, you need to add that brand to the customer. Save your project, then navigate to the Customers tab, find your customer, and activate the brand for that customer. 18

19 MOVING YOUR PROJECT TO TEST PLAN SETTINGS Once you have completed all sections in the Settings and Configuration screens, you can move your project to the Test Plan Settings step. You can accomplish this one of two ways: Navigate to Dashboard/Project Management, select the Test Plan Settings from the Current Step dropdown, and click Save; or: Click the Test Plan settings task on the Step List. The Test Plan Settings screen displays with a warning highlighted in yellow. Click the Move this project to step Test Plan Settings link. Once you move your project to Test Plan Settings, the project step illustration updates to show your progress: NOTE THE GREEN CHECKMARK ON THE CONFIGURATION STEP TO DENOTE THAT YOU HAVE COMPLETED IT. 19

20 TEST PLAN SETTINGS The Test Plan Settings screen displays the brands selected in the Configuration/Brands tab, and sub-tabs that are associated the information needed for those brands. Each card brand tab and subtab contents are addressed in the below sub-chapters. 20

21 AMERICAN EXPRESS If your project includes American Express, complete the following sub-tabs (if applicable to your project): Contact Details - general contacts details from the project. Some fields are prefilled; you need to Save in order for the fields to be considered complete. Device Type and Certification Details - complete information on the device being used for testing. Device Capabilities - complete information on your device s capabilities such as Contact CVM, Contactless CVM, and Offline Authentication Device Details - provide details on your device such as name/model, Provider, PCI, and countries deployed Device Approval Details Contact Test Plan Specific Configuration Contactless Test Plan Specific Configuration DISCOVER If your project includes Discover, complete the following sub-tabs (if applicable to your project): Customer Information Service Information Expansion Type DPAS Kernel Functional Approval Terminal Configuration and Card Input Supported Card and Cardholder Authentication Methods Fallback to Magnetic Stripe Modes Supported MPOS Specific configuration Contact-D-PAS Specific Configuration Terminal Action Codes (on contact interface) Contactless D-PAS Specific Configuration 21

22 MASTERCARD If your project includes Master Card, complete the following sub-tabs (if applicable to your project) Acquiring Environment Deployment Country Terminal Details Test Session Information Contactless Interface - Terminal Configuration and Approvals Contactless Interface - Card Reader Details Contact Interface - Terminal Configuration and Approvals Terminal Type Contact Interface - Reference M-TIP LoA Terminal Capabilities Contactless Interface - MasterCard MCL 3.x Information Contactless Interface - MasterCard - Limits Contactless Interface - MasterCard - CVM Supported above CVM Required Limit Contactless Interface - Maestro - MCL 3.x Information Contactless Interface - Maestro - Limits Contactless Interface - Maestro - CVM Supported above CVM Required Limit Contactless Interface - US Maestro AID - MCL 3.x Information Contactless Interface - US Maestro AID - Transaction Limit (CDCVM) Value Contactless Interface - US Maestro AID - Limits Contactless Interface - US Maestro AID - CVM Supported above CVM Required Limit VISA If your project includes Visa, complete the following sub-tabs: Client Information Compliance Test Information Payment Applications and EMV General - Card Data input and Capability/Supported AIDs ADVT - Terminal Resident Data Objects ADVT - Terminal Details ADVT - Application Selection ADVT Data Authentication /Card Verification Method ADVT Terminal Risk Management/Terminal Action Analysis/Completion process qvsdc/cdet Reader Configuration Details ADVT Test Plan Specific Configuration CDET Test Plan Specific Configuration qvsdc Test Plan Specific Configuration US Covered Visa Debit Card 22

23 MOVING YOUR PROJECT TO PRE-CERTIFICATION Once you have completed all sections in the Test Plan Settings screen, you can move your project to the Pre-Certification step. You can accomplish this one of two ways: Navigate to Dashboard/Project Management, select Pre-Certification from the Current Step dropdown, and then change the Current State dropdown to Active, and then click Save; or: Click the Pre-Certification task on the Step List. The Pre-Certification screen displays with a warning highlighted in yellow. Click the Move this project to step Pre-Certification link. Once you move your project to Pre-Certification, the project step illustration updates to show your progress: NOTE THE GREEN CHECKMARK ON THE TEST PLAN SETTINGS STEP TO DENOTE THAT YOU HAVE COMPLETED IT. PRE-CERTIFICATION The Pre-Certification screen is where the actual pre-certification test results display for review by the users assigned to this project. Once the Pre-Certification tests have passed, your project is ready to move to the Certification step. 23

24 ACTIONS MENU The Actions menu displays on the Pre-Certification step and contains a number of options: Export to BTT: Exports the Pre-Certifications tests associated with your project to a.tpp file. You need to use this in order to run any test cases. Import from BTT: Import a.tpp file to your project s precertification step. This is is not needed if you have completed the User Validations and import the Card Logs as the tests are run. Print Test Script: downloads the test scripts associated with your project to a.txt file, which can then be opened and printed Export Test Script: exports and downloads the test scripts associated with your project to an.xlsx file Download Results: opens the Download Results box, which allows you to select the Brand results for downloading. After selecting the brand, click the Download Result button. The file then downloads as a.zip file. testsession.cleartestresults: opens the Clear Test Results box. If you click the testsession. ClearTestResults button, the test results will clear. You need to have the appropriate access rights to clear test results. 24

25 PRE-CERTIFICATION TESTS The tests are built based on what you gave entered in the previous steps: Settings, Configuration, and Test Plan Settings. After those steps have been completed, the system builds out the tests and paths needed for certification into the Pre-Certification step. The test steps interface as a web based application, which is used in combination with a Test Tool for terminal brand testing ( Test Tool ) on the tester s computer. The Test Tool is used to capture test evidence, which can be uploaded to the test step as test results. Below is a high-level workflow of how the web application works with the test tool: *IMAGE SOURCE: UL SELF-TEST PLATFORM TRAINING DOCUMENTATION Depending on your project, the tests are arranged by Card Brand. If you have multiple card brands configured for your project, the tests display by brand and each brand needs to be expanded to see all the tests associated with the brand. Use the down-facing arrow to expand, and the up-facing arrow to collapse. 25

26 With the brand expanded to display the tests, each test has a series of indicators on the left and right hand sides of the screen. The indicators are used to denote status (on the left) and actions (on the right) for each test step. Please note: If you are testing with MasterCard, you must point your Terminal to the URL SecurePOC.epxuap. com on a port provided by Integration. Please reach out to the Integration team for this information. Below is an example of the three status indicators: Square: indicates that the test has not yet been run. Red X: indicates that the test failed Green check: indicates that the test passed Below is an example of Action indicators. The action indicators display in black font when the test has not been run/saved. After the test has been run and saved, the Action Indicators display in red or green font depending on the result of the test. Green always indicates pass, red always indicates fail. Eye - user validation step. Card - Card log validation Arrows - host validation Paperclip - receipts are attached to the test scenario Exclamation - an indicator that there is a problem with the test scenario that must be addressed. Down arrow/up arrow expand or collapse the test details. To run your tests, expand each test scenario in turn and follow the instructions in the Test Procedures section. 26

27 Answer the questions/report the results in the User Validation section. Select a value from the dropdown for each question in the section, and then click SAVE. Next, upload the card log validation file to the test step. Click the Choose File button and navigate to the file location to select the file. If using BTT for your test tool, an example file location is: C:\UL Test Tools\BTT 5.2.1\Reports\dgicu74w\ E2E_49\ \ In the above example, under the \Reports\ directory, you find a folder created on the date testing was performed it s named with random 8 characters (dgicu74w, in the above). Drill into the test case you ran (E2E_49, in the above). Under that folder, open the folder with the most current date. Select the.json file that starts with the date you ran the transaction (see screenshot above for an example). When finished selecting your file, click Upload File. 27

28 The results of the file upload appear next to the validation steps. Red X indicates that the step failed, and a green check indicates that the step passed. The goal is to have all passing steps. If you get a red X you can expand the Report View and drill down for a complete explanation. Host validation is received back from the host and displayed. 28

29 If you wish to request a waiver for this test scenario, click the Request Waiver button. Upload a receipt scan to the test scenario in the Receipt section: You may also leave comments using the Comment section. Type your comment into the provided field and click Save Comment. The Request Waiver form displays. Type in your reason for requesting the waiver, and then click Save Waiver: The waiver request saves and is displayed on the step. You may edit or remove by clicking the associated buttons. NOTE, WHEN A WAIVER IS REQUESTED, A FLAG ICON DISPLAYS NEXT TO THE TEST STEP: The above steps are repeated for all tests in the Pre-Certification step in the process. Please note that all tests should be completed and passed (or waived) before the Pre-Certification Review and moving your project to the last step, Certification. 29

30 MOVING YOUR PROJECT TO CERTIFICATION Once you have completed all sections in the Pre-Certification screen, you can move your project to the Certification step. Please note, not all brand require the Certification step - see the chapter on Post-Certification Review for more information. You can move your project to the Certification step one of two ways: Navigate to Dashboard/Project Management, select Certification from the Current Step dropdown, and then change the Current State dropdown to Active, and then click Save; or: Click the Certification task on the Step List. The Certification screen displays with a warning highlighted in yellow. Click the Move this project to step Certification link. You may also see a message warning you that no transactions are available for Certification. These generate as part of the process of moving your project to Certification. Once you move your project to Pre-Certification, the project step illustration updates to show your progress: NOTE THE GREEN CHECKMARK ON THE PRE-CERTIFICATION STEP TO DENOTE THAT YOU HAVE COMPLETED IT. CERTIFICATION The Certification step is the last step in the certification process. However, some brands do not require Certification testing using the STP as they have their own tools or steps that must be completed outside of the STP. See the chapter on Post-Certification Review for more information. If required by the brand, the same tests and tasks run in the Pre-Certification process are run again in the Certification process. See the chapter on Pre-Certification for descriptions of the test cases. 30

31 POST-CERTIFICATION REVIEW Once all the test steps have been completed, you need to work with the EPX team to complete testing. The submission process differs depending on the test brand. American Express, Discover, MasterCard and Visa each have unique requirements that need satisfying before submitting the client s final test results for certification review. American Express: Further testing must be performed with the EPX team in the ATS. You will be given instructions by the team members, but the high-level process includes EPX team members moving the connection to the ATS; then as test cases are run, EPX sees the Host File results. Your project team needs to send the Card Logs and Receipts. For this phase, the card logs are the.xml version instead of the.json but are located in the same file folder. All tests must pass, and all receipts attached, before the EPX team can complete the submission using tools that American Express provides. Discover: All pre-certification and certification testing must be completed in STP, with all test cases passed or containing a valid waiver. The final test results are then submitted along with the completed Response Form (RF) summary document to Discover via Acquirer Systems, where a final review is performed. Discover responds within 5-7 business days with a final certification approval, or notice that one or more issues have been uncovered and must be returned to the client for correction. MasterCard: All pre-certification testing must be completed in STP, with all test cases passed or containing a valid waiver. EPX then links to a test simulator provided by MasterCard to execute final certification. This necessitates pointing your Terminal to the URL SecurePOC.epxuap.com on a port provided by Integration. For final certification testing, you re-point your terminal to SecureCERT.epxuap.com on that same port. After Certification testing is completed, the final test results are imported and EPX creates a.tsez file, which is submitted to MasterCard for final review. Visa: All pre-certification and certification testing must be completed in STP, with all test cases passed or containing a valid waiver. EPX then manually enters and/or upload the final certification results into the Visa Online (VOL) test portal for electronic submission to Visa for final review. 31