SELF-CERTIFICATION - NAB Velocity

1SELF-CERTIFICATION USING THE UL STP

SELF TESTPLATFORM

SELF-CERTIFICATIONUSING THE UL STP


INTRODUCTION 3

ACCESS AND LOGIN 3

DASHBOARD/HOME 4

PROJECTS 5

Project Dashboard and Details 6Overview tab 7Project Management tab 8Users tab 8Documents tab 9Notifications tab 10Project Comments tab 10Audit Log tab 11

SETTINGS 11

General Settings tab 12Connectivity tab 13

CONFIGURATION 14

CONTACT INFORMATION TAB 15

Terminal Information tab 16Acquirer Information 17Test Tool 17Brands tab 18Moving your Project to Test Plan Settings 19

TEST PLAN SETTINGS 20

American Express 20Discover 21MasterCard 21Visa 22Moving your Project to Pre-Certification 22

PRE-CERTIFICATION 23

Actions menu 23Pre-Certification Tests 24Moving your Project to Certification 29

CERTIFICATION 30

POST-CERTIFICATION REVIEW 30

TABLE OF CONTENTS


INTRODUCTION

This user manual details the process of submitting a project for self-certification using the UL Self-Test Plat-form (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:

•SetupandConfiguration • Test Plan •Pre-Certification •Certification

Some of the steps are dependent on the steps completed previously, and cannot be completed until you com-plete the previous steps. For example, you cannot move forward with Pre-Certification until you have complet-ed 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, email [email protected].

NOTE: IF THIS IS YOUR FIRST TIME LOGGING INTO THE UL STP, YOU AREPROMPTEDTOCHANGEYOURPASSWORD.FOLLOWTHEPRO-VIDEDINSTRUCTIONS.


Upon login, you are presented with your dashboard. On this screen you can:

•Viewyourname •Viewprojectactivityforthelast24hours •Viewshortcutsthatyouhaveconfigured •Viewstarredprojects •NavigatetotheProjects,Customer,TransactionHistory,andReportstabs •PerformAdministrativefunctions •ViewHelp •Logout

To navigate to the list of existing projects, and also begin a new project, click the Project tab.

DASHBOARD/HOME


PROJECTSTypically, users navigate to Projects to cover two scenarios:

•NewintegrationtoEPX,suchasnewsoftware,and/ornewvendor,whichrequiresEMV. •ExistingIntegrationswithEPXthatwanttoaddEMV.

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-BOARDSCREENDISPLAYS.


PROJECT DASHBOARD AND DETAILSThe Project Dashboard screen displays when you have created a project, or selected a project to view its de-tails. The Project Dashboard initial view displays:

•ThenameoftheProject •AnillustrationoftheSteps,andprojectstatusrelatedtothesesteps •Asectiondisplayingtabbedpages,andadisplaysectiontoview/editthedetailsofeachtab.


OVERVIEW TABThe overview tab displays details about the project, including:

•CreationDate(andtime) •LastAuditedActiondate(andtime) •ProjectName •ProjectType •CurrentState(thecurrentstateoftheproject) •CurrentStep(thecurrentsteptheprojectison) •LastActivity


PROJECT MANAGEMENT TAB

The Project management tab displays:

•CurrentStepdropdown:selectthesteptheprojectiscurrentlyperforming.Somestepsaredepen-dentoncompletingprevioussteps.

•Currentstate:thecurrentstateontheproject.“Draft’istheonlyoptionavailableuntiltestcaseshavebeengeneratedinSTPforatleastonebrand.

When you have finished making edits to the Project Management tab, click the Save button.

USERS TABThe 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.


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.

DOCUMENTS TAB

NOTIFICATIONS TAB

The Notifications tabs displays status notifications that come thru during the lifecycle of the project.


PROJECT COMMENTS TABThe 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 Upload-ed, and Project Step Changed.


SETTINGSClick 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.


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.


CONNECTIVITY TABThe 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 00000001 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.

•EnsureyouhavetheMIDsandTIDsassignedtoyourprojectduringtheIntegrationprocess.•SelecttheActivecheckboxtomaketheMID/TIDactivefortheproject.•SelecttheTypefromthedropdown(MIDorTID)•EntertheidentifierfortheMIDorTID,dependingonthetype.MIDshave6to15alphanumeric

characters,dependingonthebrand;andTIDshave8alphanumericcharacters.Seeaboveforaddi-tionaldetailsonMIDandTIDcharacterconfiguration.

•Youmayaddasmanyidentifiersasneededforaproject.Whenfinished,clicktheSavebutton.


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


CONTACT INFORMATION TAB

The contact information tab must be completed to begin testing. All fields are required, except for Contact Prov-ince/State. When finished, click the Save Questionnaire button.


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 •SupplierName(notrequired) •SupplierCountry(notrequired) •CardReaderBrand •CardReaderModel •CardReaderName •CardReaderSupplierCountry •EMVKernelName •PaymentApplicationSoftwareandVersion •CountriesofDeployment •CurrencyCode(ISO4217Numeric) •EMVCoLevel1LOA(fileupload) •EMVCoLevel2LOA(fileupload)

When finished, click the Save Questionnaire button.


ACQUIRER INFORMATIONThe Acquirer Information tab displays information regarding the acquirer, but is not required for testing.

TEST TOOLEnter 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, makesureyouhavethelatestversion, 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.


BRANDS TABSelect 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 Cus-tomer 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.


MOVING YOUR PROJECT TO TEST PLAN SETTINGSOnce 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:

•NavigatetoDashboard/ProjectManagement,selectthe“TestPlanSettings”fromtheCurrentStepdropdown,andclickSave;or:

•ClicktheTestPlansettingstaskontheStepList.TheTestPlanSettingsscreendisplayswithawarninghighlightedinyellow.Clickthe“MovethisprojecttostepTestPlanSettingslink.

Once you move your project to Test Plan Settings, the project step illustration updates to show your progress:

NOTETHEGREENCHECKMARKONTHECONFIGURATIONSTEPTODENOTETHATYOUHAVECOMPLETEDIT.


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.


AMERICAN EXPRESS If your project includes American Express, complete the following sub-tabs (if applicable to your project):

•ContactDetails-generalcontactsdetailsfromtheproject.Somefieldsareprefilled;youneedtoSaveinorderforthefieldstobeconsideredcomplete.

•DeviceTypeandCertificationDetails-completeinformationonthedevicebeingusedfortesting. •DeviceCapabilities-completeinformationonyourdevice’scapabilitiessuchasContactCVM,

ContactlessCVM,andOfflineAuthentication •DeviceDetails-providedetailsonyourdevicesuchasname/model,Provider,PCI,andcountries

deployed •DeviceApprovalDetails •ContactTestPlanSpecificConfiguration •ContactlessTestPlanSpecificConfiguration

DISCOVERIf your project includes Discover, complete the following sub-tabs (if applicable to your project):

•CustomerInformation •ServiceInformation •ExpansionType •DPASKernelFunctionalApproval •TerminalConfigurationandCardInputSupported •CardandCardholderAuthenticationMethods •FallbacktoMagneticStripeModesSupported •MPOSSpecificconfiguration •Contact-D-PASSpecificConfiguration •TerminalActionCodes(oncontactinterface) •ContactlessD-PASSpecificConfiguration


MASTERCARDIf your project includes Master Card, complete the following sub-tabs (if applicable to your project)

•AcquiringEnvironment •DeploymentCountry •TerminalDetails •TestSessionInformation •ContactlessInterface-TerminalConfigurationandApprovals •ContactlessInterface-CardReaderDetails •ContactInterface-TerminalConfigurationandApprovals •TerminalType •ContactInterface-ReferenceM-TIPLoA •TerminalCapabilities •ContactlessInterface-MasterCardMCL3.xInformation •ContactlessInterface-MasterCard-Limits •ContactlessInterface-MasterCard-CVMSupportedaboveCVMRequiredLimit •ContactlessInterface-Maestro-MCL3.xInformation •ContactlessInterface-Maestro-Limits •ContactlessInterface-Maestro-CVMSupportedaboveCVMRequiredLimit •ContactlessInterface-USMaestroAID-MCL3.xInformation •ContactlessInterface-USMaestroAID-TransactionLimit(CDCVM)Value •ContactlessInterface-USMaestroAID-Limits •ContactlessInterface-USMaestroAID-CVMSupportedaboveCVMRequiredLimit

VISAIf your project includes Visa, complete the following sub-tabs:

•ClientInformation •ComplianceTestInformation •PaymentApplicationsandEMV •General-CardDatainputandCapability/SupportedAIDs •ADVT-TerminalResidentDataObjects •ADVT-TerminalDetails •ADVT-ApplicationSelection •ADVT–DataAuthentication/CardVerificationMethod •ADVTTerminalRiskManagement/TerminalActionAnalysis/Completionprocess •qVSDC/CDETReaderConfigurationDetails •ADVTTestPlanSpecificConfiguration •CDETTestPlanSpecificConfiguration •qVSDCTestPlanSpecificConfiguration •USCoveredVisaDebitCard


MOVING YOUR PROJECT TO PRE-CERTIFICATIONOnce 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 highlight-ed 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:

NOTETHEGREENCHECKMARKONTHETESTPLANSETTINGSSTEPTODENOTETHATYOUHAVECOMPLETEDIT.

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.


ACTIONS MENUThe Actions menu displays on the Pre-Certification step and contains a number of options:

•ExporttoBTT:ExportsthePre-Certificationstestsassociatedwithyourprojecttoa.tppfile.Youneedtousethisinordertorunanytestcases.

•ImportfromBTT:Importa.tppfiletoyourproject’sprecertificationstep.ThisisisnotneededifyouhavecompletedtheUserValidationsandimporttheCardLogsasthetestsarerun.

•PrintTestScript:downloadsthetestscriptsassociatedwithyourprojecttoa.txtfile,whichcanthenbeopenedandprinted

•ExportTestScript:exportsanddownloadsthetestscriptsassociatedwithyourprojecttoan.xlsxfile

•DownloadResults:openstheDownloadResultsbox,whichallowsyoutoselecttheBrandresultsfordownloading.Afterselectingthebrand,clicktheDownloadResultbutton.Thefilethendown-loadsasa.zipfile.

•testsession.ClearTestResults:openstheClearTestResultsbox.Ifyouclickthetestsession.ClearTestResultsbutton,thetestresultswillclear.Youneedtohavetheappropriateaccessrightstocleartestresults.


PRE-CERTIFICATION TESTSThe 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:

*IMAGESOURCE:ULSELF-TESTPLATFORMTRAININGDOCUMENTATION

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 associat-ed with the brand. Use the down-facing arrow to expand, and the up-facing arrow to collapse.


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:

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 de-pending on the result of the test. Green always indicates pass, red always indicates fail.

To run your tests, expand each test scenario in turn and follow the instructions in the Test Procedures section.

•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. •Downarrow/Uparrow expand or collapse the test details.

•Square: indicates that the test has not yet been run. •RedX: indicates that the test failed•Greencheck: indicates that the test passed


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\2017-04-24 08-56-25\

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 ex-ample). When finished selecting your file, click Upload File.


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.

The results of the file upload appear next to the validation steps.


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”.

If you wish to request a waiver for this test scenario, click the Re-quest Waiver button.

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,WHENAWAIVERISREQUESTED,AFLAGICONDISPLAYSNEXTTOTHETESTSTEP:

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.


MOVING YOUR PROJECT TO CERTIFICATIONOnce you have completed all sections in the Pre-Certification screen, you can move your project to the Cer-tification 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:

•NavigatetoDashboard/ProjectManagement,select“Certification”fromtheCurrentStepdrop-down,andthenchangetheCurrentStatedropdownto“Active”,andthenclickSave;or:

•ClicktheCertificationtaskontheStepList.TheCertificationscreendisplayswithawarninghigh-lightedinyellow.Clickthe“MovethisprojecttostepCertification”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:

NOTETHEGREENCHECKMARKONTHEPRE-CERTIFICATIONSTEPTODENOTETHATYOUHAVECOMPLETEDIT.

CERTIFICATIONThe Certification step is the last step in the certification process. However, some brands do not require Certifi-cation 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 Certi-fication process. See the chapter on Pre-Certification for descriptions of the test cases.


POST-CERTIFICATION REVIEWOnce 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 certifica-tion review.

AmericanExpress: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 Re-ceipts. 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) summa-ry 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 certi-fication 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.

Date post:	18-Jan-2022
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times