You are on page 1of 34

EMV®

Level 3 (L3) Testing Framework

Process Enhancements

Version 1.1
October 2016

© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
Legal Notice
This document summarizes EMVCo’s present plans for evaluation services and related
policies and is subject to change by EMVCo at any time. This document does not create
any binding obligations upon EMVCo or any third party regarding the subject matter of this
document, which obligations will exist, if at all, only to the extent set forth in separate written
agreements executed by EMVCo or such third parties. In the absence of such a written
agreement, no product provider, test laboratory or any other third party should rely on this
document, and EMVCo shall not be liable for any such reliance.
No product provider, test laboratory or other third party may refer to a product, service or
facility as EMVCo approved, in form or in substance, nor otherwise state or imply that
EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test
laboratory or other third party or its products, services, or facilities, except to the extent and
subject to the terms, conditions and restrictions expressly set forth in a written agreement
with EMVCo, or in an approval letter, compliance certificate or similar document issued by
EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo.
Under no circumstances should EMVCo approvals, when granted, be construed to imply any
endorsement or warranty regarding the security, functionality, quality, or performance of any
particular product or service, and no party shall state or imply anything to the contrary.
EMVCo specifically disclaims any and all representations and warranties with respect to
products that have received evaluations or approvals, and to the evaluation process
generally, including, without limitation, any implied warranties of merchantability, fitness for
purpose or non-infringement. All warranties, rights and remedies relating to products and
services that have undergone evaluation by EMVCo are provided solely by the parties
selling or otherwise providing such products or services, and not by EMVCo, and EMVCo
will have no liability whatsoever in connection with such products and services.
This document is provided "AS IS" without warranties of any kind, and EMVCo neither
assumes nor accepts any liability for any errors or omissions contained in this document.
EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-
INFRINGEMENT, AS TO THIS DOCUMENT.
EMVCo makes no representations or warranties with respect to intellectual property rights of
any third parties in or in relation to this document. EMVCo undertakes no responsibility to
determine whether any implementation of this document may violate, infringe, or otherwise
exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual
property rights of third parties, and thus any person who implements any part of this
document should consult an intellectual property attorney before any such implementation.
Without limiting the foregoing, this document may provide for the use of public key
encryption and other technology, which may be the subject matter of patents in several
countries. Any party seeking to implement this document is solely responsible for
determining whether its activities require a license to any such technology, including for
patents on public key encryption technology. EMVCo shall not be liable under any theory for
any party's infringement of any intellectual property rights in connection with this document.

© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
Revision Log – Version 1.1
The following changes have been made to the document since the publication of
Version 1.0.

Version Date Description


V1.0 November 1, 2014 First release of Framework document

V1.1 Draft August 7, 2015 – CS - Includes initial updates based on vendor


feedback
August 28, 2015 – DoD - A9 - Add Online Message format
October, 22, 2015 – JCO - A4-Replace Transaction log by Card
Terminal log
- Replace “Brand” by “Payment system”
- A7-Update Terminal families with Andy’s
inputs
- A9-Update Online message format with
Acquirer System’s inputs
October, 26, 2015 – JCO
- A6-Update Common terminologies with
Andy’s input
- A5- Add Test Card PAN, Transaction
amount and Host simulator behaviour in
Test report template
- A4- Add Timestamp element as optional
February, 25, 2016 – JCO - A9 - Correct discrepancies in format
description vs XML and XSD definition
- A3 – Align with FIG content (e.g. Non ISO
message)
March, 5, 2016 – CS - Mostly changes of ‘Terminal Integration’
reference to ‘Level 3’ and updates to
Phase II timeline chart and related
sections.
- Compliance with EMVCo documentation
April 26, 2016 – CS
requirements
- A3 – Complete PS directives for Non ISO
June, 1st, 2016 – JCO
message
- Final draft version (Cleaned up)

Oct, 11th, 2016 Move A1 A2 A3 A4 & A9 to Implementation


Guidelines [L3FIG]
Move A6 to [L3FRAME] section 1.4 Glossary
Move A5 & A8 to Client facing document
Move A7 to EMVCo Bulletin

© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
Add Document references table in section
1.3

© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 5 / 34

Contents
1 Background ................................................................................................................... 7
1.1 Audience ................................................................................................................ 7
1.2 Document Organization .......................................................................................... 8
1.3 EMVCo L3 related documents ................................................................................ 8
1.4 Glossary ................................................................................................................. 8
2 L3 Testing Overview ................................................................................................... 16
2.1 Objectives ............................................................................................................ 16
2.2 Scope ................................................................................................................... 17
2.3 Current Payment system Processes ..................................................................... 18
2.3.1 Process References............................................................................... 18
2.3.2 Test Execution Tools ............................................................................. 18
2.3.2.1 Tool Qualification and Availability to Users .............................. 19
2.3.3 Testing Process Steps ........................................................................... 20
3 EMVCo Process Enhancements (Phase I) ................................................................. 23
3.1 Test Tool Developments and Automation ............................................................. 23
3.1.1 Machine-readable Test Card Images ..................................................... 23
3.1.1.1 Key Stakeholder Benefits ........................................................ 24
3.1.2 Test Case Pass/Fail Criteria .................................................................. 24
3.1.2.1 Key Stakeholder Benefits ........................................................ 25
3.1.3 Common Card Terminal log Format ....................................................... 25
3.1.3.1 Key Stakeholder Benefits ........................................................ 26
3.1.3.2 Other Benefits.......................................................................... 26
3.1.4 Common Online Message Format ......................................................... 26
3.1.4.1 Key Stakeholder Benefits ........................................................ 27
3.1.4.2 Other Benefits.......................................................................... 27
3.2 Test Execution...................................................................................................... 27
3.2.1 L3 Test Plan Template ........................................................................... 27
3.2.1.1 Key Stakeholder Benefits: ....................................................... 28
3.2.2 Common Terminology Glossary ............................................................. 28
3.2.2.1 Key Stakeholder Benefits ........................................................ 29
3.2.3 L3 Testing/Retesting Criteria .................................................................. 29
3.2.3.1 Key Stakeholder Benefits: ....................................................... 30
3.3 Test Results Submission and Validation ............................................................... 30
3.3.1 Test Report Guidelines .......................................................................... 30
3.3.1.1 Key Stakeholder Benefits: ....................................................... 31
4 Further EMVCo Efforts (Phase II) ............................................................................... 32
4.1 EMVCo Technical and Administrative Support ..................................................... 32
October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 6 / 34

4.1.1 Infrastructure Support ............................................................................ 32


4.1.2 Technical Support .................................................................................. 33
4.2 Estimated Phase II Timelines ............................................................................... 33

Figures
Figure 2-1: Chip Tool Development Life Cycle ........................................................ 19
Figure 2-2: Payment system Process Models ......................................................... 22

Tables
Table 2-1: Type Approval vs Terminal Integration Testing ...................................... 17
Table 2-2: Payment system References.................................................................. 18
Table 3-1: Machine-readable Card Image Benefits ................................................. 24
Table 3-2: L3 Test Case Criteria Benefits................................................................ 25
Table 3-3: Common Card to Terminal Log Format Benefits .................................... 26
Table 3-3: Common Online Message Log Format Benefits ..................................... 27
Table 3-4: L3 Test Plan Template Benefits ............................................................. 28
Table 3-5: Common Terminology Glossary Benefits ............................................... 29
Table 3-6: L3 Testing Criteria Benefits .................................................................... 30
Table 3-7: Common Report Requirements Benefits ................................................ 31

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 7 / 34

1 Background
The Terminal Integration Task Force (TITF) was established by EMVCo in September 2013,
to examine the Payment Systems’ testing processes for the integration of EMV contact and
contactless acceptance devices into their payment environments. The task force’s mission
was to determine the feasibility of standardizing key elements of these individual processes,
thereby delivering a more streamlined integration testing experience to Chip acquirers and
acquirer processors (Testers) that support multiple Payment Systems.
The charter defined by EMVCo for the task force required a detailed review of the various
processes that Testers encounter to meet individual Payment Systems’ requirements for a
terminal that has been approved by EMVCo and is ready for deployment in the field. The task
was to determine the possibilities of creating standardized, consolidated processes,
leveraging the EMVCo infrastructure as necessary. If opportunities were identified, the task
force would present a proposal to the EMVCo Board for approval to implement as necessary.

The task force’s initial efforts concluded that many elements of the individual processes could
indeed be standardized for better efficiencies. This document, re-released as the EMVCo
Level 3 Testing Framework – Process Enhancements – v1.1:
• Outlines the initial findings on synergies and differences across the various processes.
• Describes the intended standardization areas, as identified by the six participating
Payment Systems that are members of EMVCo.
• Provides details of the next steps that would need be taken by the TITF to achieve a
more standardized L3 testing process.
• Provides a timeline estimate on stages related to delivery of the Phase II initiatives.

Note: Details on specific Payment System’s testing policies and requirements remain out
of scope of the task force’s assignment and are not included in this Framework document.
Policy areas will remain the responsibility of the respective Payment Systems to define,
apply and manage as necessary.

1.1 Audience
This document is intended as a reference for all participants and stakeholders in the EMV L3
Testing Processes, which includes Merchants, Acquirers, Payment Systems, Payment
Processors and third-party test tool and service providers.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 8 / 34

1.2 Document Organization


This document is organized as follows:
Chapter 1: Background – contains general information intended to provide context for the
TITF’s work effort, and to help the reader understand the purposes behind the task force’s
efforts and ultimately this Framework document.
Chapter 2: L3 Testing Overview – provides an overview of the L3 testing processes
currently in place with each of the six Payment Systems that are members of EMVCo.
Chapter 3: New EMVCo Process Enhancements (Phase I) – describes EMVCo’s recent
and planned enhancements to accomplish standardization across the L3 testing processes
of the Payment Systems.
Chapter 4: Further EMVCo Efforts (Phase II) – describes the areas for further
standardization activities planned by the TITF.

1.3 EMVCo L3 related documents


Bookmark Publication Name Version

[L3FIG] EMV Level 3 (L3) Testing Framework – Latest available


Implementation Guidelines

[L3CLIENT] EMV Level 3 (L3) Testing Framework – Client Under


Usage Guideline development

[L3BULL A7] Level 3 (L3) Testing Framework – Bulletin Under


Testing/Retesting criteria & Terminal family development

1.4 Glossary
Below is a working glossary of common L3 testing process terms and abbreviations.

A
A Alpha
AAC Application Authentication Cryptogram
Acquirer Financial institution which passes on transaction data from
merchant to payment system.
ADA Application Default Action
ADF Application Definition File
ADVT Acquirer Device Validation Toolkit. The Visa Inc and Visa Europe
terminal integration testing process.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 9 / 34

AEF Application Elementary File


AEIPS American Express ICC Payment Specification. The Amex
implementation of EMV.
AFD Automated Fuel Dispenser
AFL Application File Locator
AID Application Identifier
AIP Application Interchange Profile
an alphanumeric
ans alphanumeric special
Application Protocol The communication format used between the chip card and the
Data Unit (APDU) payment application on a card acceptance device. This format is
defined in ISO specification 7816-4.
ARPC Application Response Cryptogram
ARQC Application Request Cryptogram
ATC Application Transaction Counter
ATM Automated Teller Machine. An unattended device that has
electronic capability to send transactions online for authorization,
accepts PINs, and disburses currency.
AUC Application Usage Control
B
b Binary

C
CAM Card Authentication Method

Card Acceptor Terminal See “Terminal”


Card/Terminal Log A capture of the data exchanged between the card/card
simulator and the acceptance device. Typically provided in
Application Protocol Data Unit (APDU) format (presently ISO
7816-3 and ISO 14443).
Card/Terminal Log A description of the requirements for validating the elements and
Validation content of the Card/Terminal Log during terminal integration
testing. It is defined by a Test Session files.
Cardholder Activated An unattended device, such as an automated dispensing
Device machine, self-service device, or limited amount device that is not
an ATM. See also: UAT, Cardholder Activated Terminal.
CAT Customer Activated Terminal
CDA Combined Dynamic Data Authentication
CDOL Card Risk Management Data Object List

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 10 / 34

Certification Validation that the format, function and content of authorization


messages executed from a defined test plan adheres to a
provided specification and set of business rules.
CID Cryptogram Information Data
cn Compressed numeric (also known as BCD)
Comma-separated A format that stores tabular data (numbers and text) in plain-text
Values (CSV) form (i.e. a sequence of characters, with no data that has to be
interpreted instead, as binary numbers). A CSV file consists of
any number of records, separated by line breaks of some kind;
each record consists of fields, separated by some other
character or string, most commonly a literal comma or tab.
Usually, all records have an identical sequence of fields.
Contact transaction An interaction between a chip application and a device using the
physical electrical interface, as defined in [EMV Book 1].
Contactless IC Terminal The JCB contactless IC terminal integration testing process.
Check for
Implementation (TCI-
CL)
Contactless transaction An interaction between a chip application and a device using the
radio frequency wireless interface, as defined in [EMV CL].
Customer Activated See ‘Cardholder Activated Device’
Terminal (CAT)
CVM Cardholder Verification Method
CVR Cardholder Verification Result
D
DDA Dynamic Data Authentication
DDF Directory Definition File
DDOL Dynamic Data Authentication Data Object List
DES Data Encryption Standard
DGI Data Group Identifier (used by the Card Personalizer only)
D-PAS Acquirer Terminal integration testing process for Discover.
Terminal E2E
DKI Derivation Key Index
D-PAS Discover Payment Application Specification
E
EMV A term referring to certain technical specifications developed and
maintained by EMVCo and/or technologies conforming to such
specifications.
EMVCo LLC (EMVCo) The limited liability company that manages, maintains, and
enhances the EMV Specifications. Current Members of EMVCo
are American Express, Discover, JCB, Mastercard, UnionPay
and Visa.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 11 / 34

EMV Specifications Technical specifications developed and maintained by EMVCo to


facilitate worldwide interoperability and acceptance of secure
payment transactions, including the requirements described in
the bulletins available on the EMVCo website.
F
FCI File Control Indicator
G
GPO Get Processing Options
H
Hex. Hexadecimal
Host Authorization The transaction message initiated from the device and sent
Message online via the acquirer and network to the issuer, processor or
Payment system for transaction authorization and back to the
device. This is a series of message formats, currently
implemented by more than one protocol.
I
IAC Issuer Action Code
Interoperability The ability of all card acceptance devices to accept and read all
chip cards that are properly coded and personalized.
ISO International Organization for Standardization
Issuer A financial institution which makes a card or other payment
method available to a consumer or business and which controls
the account to which the card or payment method is linked.
K
Kernel A piece of software implementing the set of functions required to
support the EMV specifications. The kernel may contain device
drivers, interface routines and security and control functions. The
kernel has to be sufficiently separable from the other software
elements constituting the complete terminal application that it
can have its own digital signature and be tested separately from
any specific deployed version of the terminal implementation.
L
Limited Amount Device An unattended device that has data capture-only capability, and
accepts payment for items such as parking garage fees, road
tolls, etc.
L3 CTT L3 Consolidated Test Tool – a L3 tool, qualified by EMVCo, for
inclusion of the following L3 tool components; L3 Test Selection
Engine (L3 TSE), L3 Test Tool (L3 TT), L3 Card Simulator (L3
CS)
L3 LoQ L3 Letter of Qualification – a formal letter issued to a L3 Test
Tool provider by EMVCo, on successful completion of the L3
qualification process.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 12 / 34

L3 QSP L3 Test Tool qualification service provider – entity accredited by


EMVCo to perform the qualification services on L3 test tools
submitted by third-party vendors for qualification.
M
Mobile Point-of- A smartphone, tablet or dedicated wireless device that performs
Sale/Mobile Point-of- the functions of a cash register or electronic point of sale terminal
Service (MPOS or (POS terminal), usually in conjunction with a card reader and PIN
mPOS) device pad device which can encrypt transaction data
M-TIP Mastercard Terminal Integration Process. The MasterCard
terminal integration testing process.
O
Offline-capable A transaction acceptance device that has the ability to process
transactions offline, making use of the EMV offline authorization
functionality.
Offline-only A transaction acceptance device that is only able to process
transactions offline. For example, low value POS or road toll
terminals.
Online-capable A transaction acceptance device that is able to send transactions
to the issuer or processor for authorizations.
Online-only A transaction acceptance device that requires that all
transactions be sent online for authorization. For example, ATM.
P
PA-DSS Payment Application Data Security Standard. The PCI SSC
standard relating to secure storage of transaction data.
PAN Primary Account Number
PAN Key Entry A manual procedure in which the merchant uses a device key
pad to enter the PAN embossed on a card in order to process a
transaction.
Pass Criteria A Test Plan-defined description of an expected result for a
successful outcome or conclusion of a test case.
Pass Criteria File The file (in CSV format) that embeds the Payment system-
defined pass criteria for each test case.
PCI SSC Payment Card Industry Security Standards Council.
PDOL Processing Options Data Object List
Personalization For Chip cards, the process of applying both cardholder and
Payment system-specific data to the card in preparation for its
use.
PIN Personal Identification Number
PIX Proprietary Application Identifier Extension
PK Public Key
PKI Public Key Infrastructure

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 13 / 34

Point of Sale/Point of The physical location where a merchant or acquirer in a face-to-


Service (POS) face environment or an unattended device completes a
transaction.
Point-of-sale Device A card accepting device used to process sale transactions.
Point-of-service Device A card accepting device used to process transactions. Can be
any type of transaction.
PSE Payment Systems Environment
R
RFU Reserved For Future Use
RID Registered Application Provider Identifier
S
SDA Static Data Authentication
T
TAC Terminal Action Code
TAD Transaction Acceptance Device. Another word for card
acceptance device or terminal. Applies to POS devices and
ATMs.
TC Transaction Certificate
TDOL Transaction Certificate Data Object List
Terminal The device used in conjunction with the Chip card at the point of
transaction to perform a financial transaction. The terminal
incorporates the interface device and may also include other
components and interfaces such as host communications.
Terminal Check for The JCB terminal integration testing process.
Implementation (TCI)
Terminal configuration A description of the features and parameters on the acceptance
device under test. For example, it might include the EMV-defined
terminal types, supported interfaces , etc.
Terminal integration A process implemented and managed by the respective
testing Payment systems, aimed at providing a level of assurance that
Payment system-specific requirements and recommendations
are being implemented in contact or contactless chip acceptance
device designed to interoperate with the Payment system’s
networks.
Terminal Integration Task Force established by EMVCo in 2013 with the purpose of
Task Force (TITF) examining each of the Payment system’s terminal integration
processes, in order to determine the possibilities of aligning key
elements of these processes.
Test Card Image An electronic representation of the data on a physical card
Test Case A single test scenario of a Test Plan, corresponding to one action
by the tester. It is defined by a Payment System for execution of
terminal integration or Host message testing.
Test Case Name The name associated with a specific test case.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 14 / 34

Test Case Number A unique test case identifier.


Test Case Objective A description of the reasons for a given test case. This is based
on Payment System rules.
Test Plan A Payment system-developed and managed set of test criteria
that defines the requirement for Terminal Integration or Host
Message testing. This may either take the form of a text
document, or a machine-readable file.
Test Procedure A description of the steps required in order to execute a specific
test case.
Test Tool Qualification The process undertaken by each Payment system to provide
themselves, tool vendors and clients with a level of assurance
that the tools being used by clients to execute terminal
integration testing, will do so in compliance with Payment system
requirements.
Third Party Processor A party which is appointed by a merchant or financial institution
to provide payment transaction processing services. In this
capacity they are not acting as a merchant, acquirer, issuer or
payment system.
TLV Tag-Length-Value

Transaction Completion An EMV definition for the successful closing of transaction


processing. The completion function is always the last function in
transaction processing, and must occur unless the transaction is
terminated prematurely by error processing.
TSI Transaction Status Information
TVR Terminal Verification Result
U
Unattended Acceptance A cardholder-operated device that reads, captures, and transmits
Device (UAT) card information in an unattended environment.
Also known as ‘Customer Activated Terminal’ (CAT) or
“Cardholder Activated Device”
UnionPay IC Card Test The terminal integration testing process for UnionPay.
Guide for Acquirers
User Validation A Test Plan-defined description of the requirements for the
user/tester to validate responses from the device under test.
V
var. Variable
VAR Value-added Reseller
X
Extensible Mark-up A markup language that defines a set of rules for encoding
Language (XML) documents in a format that is both human-readable and
machine-readable.
XSD XML Schema Definition

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 15 / 34

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 16 / 34

2 L3 Testing Overview
EMV Terminal Integration Testing (now referred to as L3 Testing) encompasses all the testing
activities and processes required of Testers by each of the respective Payment Systems. It is
a prerequisite to the deployment of any chip acceptance device that will accept payment
products associated with those Payment Systems. This section provides a:
• General overview of the current process, including its scope and objectives.
• High level overview of each of the respective Payment Systems’ current processes.

2.1 Objectives
Although elements of each of the respective Payment Systems’ L3 testing processes may
differ, the overall objectives are largely consistent and all include requirements to:
• Validate the terminal’s ability to process Chip data, specifically for products designed to
interoperate with the Payment Systems’ networks.
• Apply pre-emptive steps to identify and resolve terminal misconfiguration cases prior to
deployment, which if uncorrected, could ultimately lead to interoperability issues.
• Ensure, in many cases, end-to-end validation of online transaction request and response
messages, specifically related to the transportation of Chip data.
• Enable validation of compliance with each Payment System’s terminal configuration
rules, requirements and recommendations.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 17 / 34

2.2 Scope
As EMVCo currently administers Type Approval processes for testing and approval of
terminals in accordance with both the EMV Level 1 and Level 2 specification requirements, it
is important to delineate these processes from the L3 terminal integration processes described
in this framework document.
The table below provides this delineation:

Table 2-1: Type Approval vs Terminal Integration Testing

EMVCo Terminal Type Approval Payment System-managed


Testing Terminal Integration Testing
Objective: Ensure terminal fully complies with Ensure Payment System-specific
EMV Level 1 and Level 2 requirements and
specification requirements. recommendations are being
applied to terminal configuration.
Administration/ EMVCo Type Approval Working Each individual Payment System
Operation: Group (TAWG) though the use of manages, through a specific
accredited laboratories. selection or combination of lab-
based, self-serve or third-party
enabled.
Applies to: Terminal manufacturers Financial Institution clients of
Payment Systems and their
processors.

When On completion of product Prior to field deployment of a new


Performed: development. or upgraded device, that has
already successfully completed
EMV Type Approval testing.

Other • Applies to EMV Level 1 and • Applies to payment application


Differences: Level 2 (Kernel)
• May include end-to-end
• Limited to terminal-chip card testing requirements (online)
interface

Common • Same test tools/suppliers often used in both processes


Areas:
• Intent is to ensure global interoperability of EMV terminal – chip card
interaction

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 18 / 34

2.3 Current Payment System Processes


This section provides specific details on each of the respective Payment system’s L3 testing
processes.

2.3.1 Process References


Each Payment system uses a different definition for their L3 testing processes. The table
below provides current references for each of the major Payment systems’ processes as
applied to contact and contactless testing.

Table 2-2: Payment system References

Payment system Description


American Express 1. American Express ICC Payments Specification (AEIPS)
2. American Express Expresspay Contactless Specification
Discover Financial Discover Contact and Contactless D-PAS Acquirer-Terminal
Services End-to-End
JCB 1. Terminal Check for Implementation (TCI)
2. Contactless IC Terminal Check for Implementation (TCI-CL)
Mastercard Mastercard Terminal Integration Process (M-TIP)
UnionPay UnionPay Terminal Validation Toolkit (UTVT)
Visa 1. Acquirer Device Validation Toolkit
2. Contactless Device Evaluation Toolkit
3. quick Visa Smart Debit & Credit (qVSDC) Device Module
4. Visa payWave Test Tool (VpTT) (Visa Europe only)

2.3.2 Test Execution Tools


For execution of L3 testing, Payment Systems currently either allow clients to use a set of
physical test cards or a test card simulator tool capable of generating scripted card images. In
either case, test card images need to be created by the Payment Systems for use in producing
the physical test card plastics, or to enable the third-party chip tool vendors to develop
simulated test cards.
All Payment Systems have processes in place to offer development support to the third-party
vendors during the tool development cycle and ultimately to conduct qualification/confirmation
of those tools once development has been completed.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 19 / 34

The chart below illustrates the Chip Tool development and readiness cycle.

Figure 2-1: Chip Tool Development Life Cycle

(1) Payment Systems


Requirements Provision to
Tool Vendors

(4) Tool Availability to (2) Tool Development by


Clients Vendors

(3) Tool
Qualification/Confirmation
by Brands

2.3.2.1 Tool Qualification and Availability to Users


Prior to making their L3 test tools available to client users, vendors must first submit them for
formal qualification to the respective Payment Systems. A high level overview of the
qualification process is as follows:
1. L3 test tool vendor contacts the Payment System to arrange for formal qualification of
the tool.
2. At the agreed time, vendor provides its L3 test tool to the Payment System for
qualification.
3. Payment System either executes qualification process in-house or outsources it to an
external Laboratory to ensure its requirements are correctly implemented on the L3 test
tool. During the process, the following could occur:
 Implementation errors were found during a qualification test cycle requiring the vendor
to resolve them and resubmit an updated version of the tool for continuation or
completion of the qualification process.
 No implementation errors were found, or any found were resolved in an updated
version of the tool. In this case, the Payment System will inform the L3 test tool vendor
of the successful outcome of the tool qualification process.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 20 / 34

Once the Payment Systems have successfully completed their qualification/confirmation of a


third-party provided tool and informed the vendor, it is the vendor’s responsibility to publicly
announce its availability to potential clients. Such announcements are typically made through
vendor-prepared press releases that may require pre-approval by the Payment Systems, if
they are being mentioned. Vendors typically also post details of their Payment System-
qualified tools on their respective web sites.

Some Payment Systems may post a list of card simulator tools confirmed or qualified in
accordance with their requirements on their web sites.

Note: Periodically, Payment Systems will release updates to their L3 Requirements. In


some cases, this may impact the implementation of a L3 test tool. If this is the case, once
the Requirements are provided to a test tool vendor, they will need to enhance their tool to
support the new requirements and go through the qualification process with the Payment
System again.

2.3.3 Testing Process Steps


At a high level, there are generally four key steps involved in the L3 testing process. These
steps are:
1. Setup/Execution of test: Testers are required to obtain a Payment System-defined
test plan and a Payment System-qualified test tool, then determine and execute the
relevant test cases. In some Payment System’s processes, determining the required
test cases is automated through completion of a system-driven Implementation
Conformance Statement (ICS), while in other cases determination may be a more
manual and analytical process.
2. Submission of Results: Requires compliance with Payment System-defined policies
on how and where results must be submitted for review following testing, and to enable
subsequent validation and sign-off, prior to terminal activation.
3. Validation of Results: Process whereby the results of L3 testing are reviewed and
acknowledged either directly by the Payment Systems, or by a designated third-party
Service Provider on behalf of the Payment Systems.
4. Results Sign-off: This final step in the L3 testing process provides clients with the
go/no-go decision of the Payment Systems for terminal activation into the production
payment environment.
For the entities completing the above steps, each Payment system may apply a different
model and may use either one of the following exclusively or a combination of various models:
• Acquirer/Processor Self-Service: The acquirer/acquirer processor takes full ownership
of the specific process step. Although they may decide to engage a third-party service
provider to assist, the obligation on delivery remains with the acquirer/processor.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 21 / 34

• Client Service Provider: Some Payment systems are beginning to establish a third-party
service provider model. Acquirers/processors can enlist the services of a Payment system-
accredited third-party to assist with the required test execution and results submission
steps. This option is considered very valuable to acquirers/processors that may not have
the necessary technical expertise in-house to complete the required tasks.
• Payment Systems Service Provider: A number of Payment System-enlisted service
providers are available globally that have extended their services to accommodate some
of the L3 testing requirements of the Payment systems. These include, but are not limited
to, services such as the validation of test results on behalf of the Payment systems’.
• Payment system-provided service: Some Payment systems have established internal
support teams for the purposes of assisting clients and processors in each of the required
L3 testing steps.
Note: Similar to the L3 test tool qualification process, Payment Systems generally have in
place a Service Provider accreditation process for entities wishing to offer L3 supports
services to either clients or to the Payment Systems themselves. This generally entails a
demonstration by the prospective Service Provider their ability to perform the services
desired by the Payment System.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 22 / 34

The chart below provides an illustration of the models currently adopted by each of the six
studied Payment systems for each of the respective process steps.

Figure 2-2: Payment system Process Models

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 23 / 34

3 EMVCo Process Enhancements (Phase I)


Through the recent Phase I efforts of the TITF, EMVCo has been working on defining and
implementing a set of L3 initiatives that will bring standardization to the areas of tool
development and automation, test execution, results submission and validation. This section:
• Describes the specific efforts that are currently being undertaken by EMVCo for L3
testing and being implemented in the coming months.
• Provides a description of the benefits to be gained by stakeholders from each of the
respective efforts.

3.1 Test Tool Developments and Automation


In support of a more streamlined and consistent approach to enabling development, improving
automation and subsequent qualification of the third-party provided L3 test tools used by Client
Testers, EMVCo has established standardization of the following:
• Machine-readable L3 test card images, representing the expected card behaviour for
each of these images.
• A machine-readable syntax for defining each test case’s pass/fail result criteria.
• A common Card Terminal log format to assist with determining each test case’s pass/fail
result.
• A common Network Message log format to assist with determining the integrity and
accuracy of Chip-related data being sent from the terminal to the processing network.

3.1.1 Machine-readable Test Card Images


Any Payment System wanting to follow the EMVCo L3 testing and approval process will adopt
the use of a standardized, machine-readable format for providing its defined test card images
to the chip tool vendors. The format used is the Extensible Mark-up Language (XML), largely
due to its openness and wide adoption across the industry.
[L3FIG] section 3.5 provides the definition of the machine-readable test card images.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 24 / 34

3.1.1.1 Key Stakeholder Benefits


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-1: Machine-readable Card Image Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

A reduction in the development and qualification


timeline of chip tools, resulting in timelier delivery of √ √ √
qualified L3 test tools for Client Testers.
A reduction in developmental support demands on
Payment Systems during the test tool development √
cycle.
Elimination of the need for requirements conversion
from textual source documents to machine-readable
formats. This will equate to time savings on tool √ √ √
development as well as a significant mitigation in the
potential for conversion/implementation errors.

3.1.2 Test Case Pass/Fail Criteria


The EMVCo L3 testing and approval process is based on standardized principles and
guidelines for defining the pass/fail criteria for test cases associated with the L3 testing
processes. This effort consists of defining two components:
1. Principles for defining pass/fail criteria that will be applied to each test case.
2. A definition of a standardized, machine-readable syntax, in an open format such as
the Extensible Mark-up Language (XML) that will include the required fields for
applying the pass/fail criteria.
[L3FIG] section 3.3 provides the principles for the test case pass/fail criteria and includes a
template that defines the machine-readable syntax for the test case pass/fail criteria.
Both the guidelines document and the defined machine-readable syntax format will be shared
by entities supporting the EMVCo L3 testing process with the test tool vendors to enable tool
development and improved automation.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 25 / 34

3.1.2.1 Key Stakeholder Benefits


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-2: L3 Test Case Criteria Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

Clear and consistent definitions of pass and fail


criteria will help to eliminate any uncertainties √ √ √
among all L3 stakeholders.
Help reduce the number of technical queries and
√ √
clarification requests from chip tool vendors.
Improves the ability to automate determination of
test case results, which will help to increase the √ √
value and usability of L3 test tools.

3.1.3 Common Card Terminal log Format


EMVCo has defined a set of requirements that will enable chip tool vendors to develop a
common Card Terminal log format on their solutions for each of the L3 test cases. Since
submission of these logs may be required by some Payment Systems, developing them in a
standardized way will result in a simplified and consistent effort for the chip tool vendors.

[L3FIG] section 3.6 provides details of the standardized Card Terminal log format defined by
EMVCo.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 26 / 34

3.1.3.1 Key Stakeholder Benefits


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-3: Common Card to Terminal Log Format Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

Client Testers will be able to utilize a consistent method


of providing the necessary evidence of test case results √ √
to Payment Systems and their service providers.
This approach improves the ability all stakeholders to
√ √
quickly and consistently verify transaction outcomes.
Standardization simplifies and streamlines

development efforts for tool vendors.

3.1.3.2 Other Benefits


In addition to the benefits this initiative will provide during the tool development phase, use of
a standardized Card Terminal log format will also significantly benefit clients during the Test
Execution and Results Validation phases of the process. It will allow clients to provide tangible
evidence in a more consistent way that the tests have been successfully executed and
completed.

3.1.4 Common Online Message Format


Similar to the Common Card Terminal log Format described above, EMVCo has also defined
requirements for a common log format dedicated to online message.

As submission of these online message logs is a requirement for some results submission
processes, developing a dedicated log for online messages will result in a simplified and
consistent development effort for the chip tool vendors.
[L3FIG] section 3.7 provides details of the standardized online message log format.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 27 / 34

3.1.4.1 Key Stakeholder Benefits


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-4: Common Online Message Log Format Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

Client Testers will be able to utilize a consistent method


of providing the necessary online transaction data √ √
results.
This approach improves stakeholders’ ability to quickly
√ √
verify online transaction outcomes.
Standardization of this Online Message Log format
simplifies and streamlines development efforts for tool √
vendors.

3.1.4.2 Other Benefits


In addition to the benefits this initiative will provide during the tool development phase, use of
a standardized Online Message log format will also significantly benefit clients during the Test
Execution and Results Validation phases of the process. It will allow clients to provide tangible
evidence in a more consistent way that the tests have been successfully executed.

3.2 Test Execution


In support of an approach of enabling the execution of L3 testing by Client Testers, EMVCo
is working on the following process improvement initiatives:
• Development and use of a standardized Test Plan template
• Development and use a common terminology glossary
• The use of common Testing/Retesting Criteria

3.2.1 L3 Test Plan Template


For text-based L3 test plans, a standardized template will be used as a guide for future test
plan development. The template is provided in [L3CLIENT].

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 28 / 34

3.2.1.1 Key Stakeholder Benefits:


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-5: L3 Test Plan Template Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

A standardized format for all Test Plans will be


beneficial to acquirers and processors, as it will

bring consistency to testing efforts across the
multiple applications
A consistent test plan will mean less potential
confusion to Client Testers, with the net benefit of a √ √
reduction in Client support needs.

3.2.2 Common Terminology Glossary


Each entity adopting the EMVCo L3 Testing Framework guidelines would utilize a Common
Terminology Glossary within their test plans and other documentation related to their L3
testing processes.

A copy of the Common Terminology Glossary can also be found in section1.4.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 29 / 34

3.2.2.1 Key Stakeholder Benefits


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-6: Common Terminology Glossary Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

Consistent L3 testing process terminologies will


significantly reduce potential confusion among

clients and processors when executing the
process.
A reduction in client and processor confusion
during the test execution phase will also benefit

Payment Systems and other support entities
through a potential reduction in support calls.

3.2.3 L3 Testing/Retesting Criteria


For clarity and consistency, each entity adopting EMVCo L3 Testing Framework guidelines
will begin to utilize standardized criteria that define the conditions under which a terminal must
undergo L3 testing and re-testing. The criteria can be found in [L3BULL A7].

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 30 / 34

3.2.3.1 Key Stakeholder Benefits:


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-7: L3 Testing Criteria Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

Clear and consistent definitions related to the


L3 testing criteria will help to eliminate any
uncertainties among acquirers and √
processors conducting these tests across for
different payment applications
With more clarity and consistency around
these conditions, Payment Systems and other

support entities will benefit from an elimination
of potential conflicts in the L3 testing criteria.

3.3 Test Results Submission and Validation


Some of the initiatives described previously in the Chip Tool Development and Automation
section will equally enable an efficient and consistent approach to the test results submission
and validation phases of the process. These include:
• L3 Test Case Pass/Fail Criteria
• Common Transaction Log Format

3.3.1 Test Report Guidelines


When a formal test report with test results is required as part of the L3 testing process, a set
of Test Report Guidelines have been defined to enable the reporting of test results in a
consistent way following L3 testing.
[L3CLIENT] provides the Test Report Guidelines.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 31 / 34

3.3.1.1 Key Stakeholder Benefits:


The table below identifies some of the significant benefits that will result from this initiative
and identifies the key beneficiaries:

Table 3-8: Common Report Requirements Benefits

Benefits Key Beneficiaries


Client Payment Tool
Testers systems Vendors

Client Testers will be able to utilize a defined √ √


method of reporting their test case results.

This approach improves stakeholders’ ability to √ √


quickly verify transaction outcomes.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 32 / 34

4 Further EMVCo Efforts (Phase II)


The EMVCo Terminal Integration Task Force (TITF) has agreed on an additional set of
deliverables, being presented here as its Phase II initiatives. These initiatives have largely
been motivated by findings from an exploration into how EMVCo could play a greater role in
improving the efficiencies of the L3 testing processes.
Currently underway are efforts to:
• Define standardized requirements that L3 test tool vendors can use to develop a
common L3 Test Selection Engine (L3 TSE) within their environments or on their tools.
This would enable clients that accept Chip payment products from multiple Payment
Systems to be able to apply a single L3 Implementation Conformance Statement (ICS)
that will help to identify relevant test cases from all Payment Systems in a single effort.
• Establish, implement and operate a centralized L3 Test Tool qualification service
within EMVCo.
• Extend a L3 Informational web portal, within EMVCo.com, to enable the sharing of
relevant, process-related information to various L3 target audiences (client, processors,
networks, service providers, test tool providers, etc.), as a one-stop convenient service.
Other considerations for the future may include services to:
• Accredit service providers to allow them to be able to offer a full range of L3 support
services to Client Testers, including test execution, results analysis and validation.
• Enable submission of L3 test results into a centralized, EMVCo-hosted repository for
analysis and LOA processing.

4.1 EMVCo Technical and Administrative Support


In support of its Phase II L3 initiatives, the TITF will continue to leverage EMVCo existing
processes for delivery of both infrastructure and technical support.

4.1.1 Infrastructure Support


EMVCo will provide infrastructure support by facilitating the establishment and provision of a
centralized, web-based portal for collection and dissemination of all L3-related documentation,
templates, etc. Access to this portal will be available to entities who wish engage in the
development and delivery of solutions and services related to the L3 testing processes, as
well as clients needing information related to the process.

Use of a centralized portal will ensure information consistency and that stakeholders have
access to the latest documents, templates and guidelines for their respective requirements or
processes.

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 33 / 34

4.1.2 Technical Support


EMVCo will provide technical support to entities who want to use the EMVCo L3 terminal
integration process by facilitating access to any of its relevant working groups for the purposes
of consultation. For example, work activities within the Type Approval Working Group (TAWG)
may also benefit the L3 testing process. Also, the EMVCo Associates Program may provide a
valuable sounding board for some of the L3 initiatives.

4.2 Estimated Phase II Timelines


The chart below provides a timeline estimate on stages related to delivery of the Phase II
initiatives:

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.
EMV® Level 3 Testing Framework
Process Enhancements v1.1 Page 34 / 34

Page left intentionally blank

October 2016
© 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to
the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark
of EMVCo, LLC in the United States and other countries.