CDET User Guide v2 3
CDET User Guide v2 3
User Guide
Version 2.3 – Revision A
02 February 2018
Important Information on Confidentiality and Copyright
Notice: This information is proprietary and CONFIDENTIAL to Visa. It is distributed to Visa participants
for use exclusively in managing their Visa programs. It must not be duplicated, published, distributed
or disclosed, in whole or in part, to merchants, cardholders or any other person without prior written
permission from Visa.
The trademarks, logos, trade names and service marks, whether registered or unregistered (collectively
the “Trademarks”) are Trademarks owned by Visa. All other trademarks not attributed to Visa are the
property of their respective owners.
Note: This document is not part of the Visa Rules. In the event of any conflict between any
content in this document, any document referenced herein, any exhibit to this document, or any
communications concerning this document, and any content in the Visa Rules, the Visa Rules shall
govern and control.
Contents
Contactless Device Evaluation Toolkit - User Guide (Version 2.3 - Revision A)
Contents
1 Contactless Device Evaluation Toolkit (CDET) User Guide Introduction................................................ 6
1.1 Introduction ...................................................................................................................................................................... 6
1.2 Contact Information ...................................................................................................................................................... 7
1.2.1 General Information and Support..................................................................................................................... 7
1.2.2 Obtaining Toolkits .................................................................................................................................................. 7
1.3 Summary of Changes Introduced in this Version ............................................................................................... 7
1.4 CDET Support Documentation .................................................................................................................................. 8
1.5 Disclaimer ........................................................................................................................................................................ 10
2 Contactless Device Evaluation Toolkit - User Guide Overview ................................................................ 11
2.1 Objective .......................................................................................................................................................................... 11
2.1.1 Visa Contactless Transit Terminal Testing ................................................................................................... 11
2.2 Audience .......................................................................................................................................................................... 12
2.3 Document Organization............................................................................................................................................. 12
2.4 CDET Components ....................................................................................................................................................... 14
2.5 Related Documents ..................................................................................................................................................... 14
2.6 CDET Usage .................................................................................................................................................................... 14
2.6.1 CDET Usage Guidelines....................................................................................................................................... 15
2.7 New CDET Versions ..................................................................................................................................................... 16
2.8 Scope of CDET Testing ............................................................................................................................................... 16
2.9 EMVCo Level 3 Framework Compliance .............................................................................................................. 17
2.9.1 Provision of CDET Test Card Images to Test Tool Vendors .................................................................. 17
3 Test Case Introduction ....................................................................................................................................... 19
3.1 Pre-requisites ................................................................................................................................................................. 19
3.1.1 Reader Capabilities ............................................................................................................................................... 19
3.1.2 Visa CA Test Public Keys ..................................................................................................................................... 19
3.1.3 Configured for Operational Use ...................................................................................................................... 20
3.1.4 Testing and Approval .......................................................................................................................................... 20
3.2 Instructions...................................................................................................................................................................... 20
4.17 Test Case 17: Card supporting qVSDC Online Transit SDA, but SDA fails, and a non-compliant
T2ED ............................................................................................................................................................................................. 64
A Visa CA Test Public Key for qVSDC Offline and transit............................................................................. 67
A.1 1408 Bit VSDC TEST Key ............................................................................................................................................. 67
A.2 1536 Bit VSDC TEST Key ............................................................................................................................................. 68
B Acronyms and Glossary..................................................................................................................................... 70
Tables
Table 1: CDET Support Documentation ......................................................................................................... 8
Table 1–1: Document Organization .................................................................................................................... 12
Table 1–2: Scope of CDET Testing ...................................................................................................................... 16
Table 2–1: Test Case Summary ........................................................................................................................... 24
Table A–1: 1408 Bit VSDC Test Key .................................................................................................................... 68
Table B–1: Acronyms ............................................................................................................................................. 70
Table B–2: Glossary ................................................................................................................................................ 72
1.1 Introduction
The Visa Contactless Payment Specification (VCPS) was developed as a platform to support globally
interoperable contactless chip programs. It facilitates the creation of payment technologies that provide
Visa Contactless issuing clients with the flexibility to customize their contactless chip programs to meet
local market needs while gaining the benefits of global interoperability. The specification also provides
additional security options and enables enhanced performance for faster transaction processing.
To ensure that Visa Contactless acceptance devices deployed by acquiring clients do not contribute to
interoperability issues, Visa has developed the Visa Contactless Device Evaluation Toolkit (CDET) - a set
of test card images, an accompanying user guide (“this document”) and a card profile definitions
document. CDET is designed to allow Visa Contactless acquiring clients and their technical support
providers to validate correct configuration of their Visa Contactless acceptance devices. The Toolkit may
also be used to assist Visa Contactless reader developers and systems integrators with development
and Level 3 integration testing and to ensure that Visa requirements for card acceptance devices are
being met.
Oftentimes, cards issued in one country or region may experience acceptance problems when used in
other countries and regions, even though both the card and reader were fully tested and approved by
the payment scheme’s accredited testing laboratory. These issues may be the result of incorrect device
configuration, inadequate Level 3 integration testing or misunderstandings about payment scheme’s
rules and requirements.
In addition to ensuring Visa Contactless card acceptance globally, the CDET also enables user interface
testing of payment terminals. This step is necessary to confirm that correct user prompts, error
messages, application selection menus and PIN Entry messaging are being appropriately applied and
readily comprehensible to the cardholder and merchant.
Users of the CDET that require general information on the tool or with support needs should contact
Visa at [email protected].
Toolkits supporting the latest CDET test cases may be obtained by contacting the third-party test tool
suppliers directly. Visa publishes an ongoing list of confirmed suppliers that support both the card and
host simulation of the CDET. This list is available by visiting the following link:
https://technologypartner.visa.com/Toolkits/#orderlist
In a Visa Business News article published on 6 August 2016, Visa announced the release of a new
Android-based mobile app, as an alternative and convenient option for performing the latest CDET
testing requirements. An updated version of the Visa Mobile CDET App supporting CDET Version 2.3
requirements can be downloaded from the Google Play Store.
Please note: since the release of the Visa Mobile CDET app, physical test cards for CDET are no longer
available from the Visa fulfillment service (XPressDocs).
This section provides an overview of the changes made in this document since its last publication.
Section 3.3 (Test Case Summary) Deleted Delete the following: (VCPS 2.1.x baseline) Online-only
– Table 3-1 – Test Case Number card using the 1536-bit CA key
16
Section 4.16 (Test Case 16) Corrections Made the following corrections:
and - Section heading: Online-only Card using the
updates 1536-bit CA key
- Objective: To ensure correct Reader behavior for
an Online-only card using the 1536-bit CA key.
- Pre-requisite: Reader supports Online with ODA,
or an offline-only transit terminal
- Pass Criteria/User Validation:
1. If Transaction Amount is zero (e.g. from an MTT
Transit Terminal):
2. SODA successfully performed (SODA data
returned by the card)
3. Transit Gate access permitted
4. If Transaction Amount is non-zero (e.g. from an
KFT Transit Terminal):
5. SODA successfully performed (SOSDA data
returned by the card)
Transit Gate access permitted
Section 4.17: Test Case 17 Updated Updated to include a non-compliant Track 2 Equivalent
Data (T2ED)
CDET support documentation now consists of two documents: a Card Profiles document and a User
Guide (this document).
Visa Contactless Device This document provides the This document is intended for
Evaluation Toolkit (CDET) Card details required to personalize personalization bureaus and chip
Profiles each of the CDET test cards. tool vendors responsible for
developing CDET test cards or
simulated/scripted equivalents.
1.5 Disclaimer
The Visa Contactless Device Evaluation Toolkit provides a means for a Visa Contactless acquiring client
(or agent) implementing a contactless chip program to test its card acceptance device prior to
deployment. The Visa Contactless Device Evaluation Toolkit described herein includes test card images,
a User Guide and a Card Profiles document, specifically for use with Visa Contactless readers that are
compliant to the Visa Contactless Payment Specifications (VCPS). The Toolkit is designed to assist Visa
Contactless acquiring clients and their merchants perform tests that help to minimize card acceptance
problems. Systems Integrators and Visa Contactless device vendors can also benefit from the use of the
Toolkit, as it provides a tool to assist them during development or integration of VCPS-compliant
readers.
The tests prescribed in the user guide do not supersede the requirement for readers to undergo type
approval testing at a Visa accredited laboratory. Visa reserves the right to add or remove tests and test
requirements in the Toolkit at any time and in its sole discretion.
Visa does not warrant the Toolkit or any Toolkit test results for any purpose whatsoever, and expressly
disclaims any and all warranties of merchantability, fitness for purposes, or non-infringement of third
party intellectual property rights. No vendor or other third party may refer to a product, service or
facility as “Visa-approved”, nor otherwise state or imply that Visa has, in whole or part, approved any
aspect of a vendor or its products, services or facilities, except to the extent and subject to the terms
and restrictions expressly set forth in a written agreement with Visa or in an approval letter provided by
Visa. All other references to “Visa approval” are strictly prohibited by Visa.
All references to Visa operating regulations in this document are deemed to be references to both Visa
International Operating Regulations and/or Visa Europe Operating Regulations, as appropriate.
2.1 Objective
The objective of this document and its corresponding test cases is to provide Visa Contactless
acquiring clients, merchants, system integrators and vendors with a Toolkit to confirm that their reader
can accept Visa Contactless cards during the reader development, deployment and update stages of
the program.
With the recent definition of requirements, general guidance and recommendations for the
deployment of Visa Contactless acceptance devices on transit systems, this document will assist transit
agencies and equipment vendors with the testing of systems, developed to accept Visa Contactless
payment transactions directly at the point of entry to their transit networks.
These include systems where the fare is known at the point of entry (‘Known Fare Transaction’) and
those where the amount to be paid is determined after the travel has taken place (‘Mass Transit
Transaction).
Important This document assumes that Offline Data Authentication will be the method used to allow
access to the transit network; that is, the ODA data provided by the card must be positively
authenticated by the transit terminal before the consumer is allowed to travel.
Important The test cases within this document are only relevant to transit readers operating one of the
following implementations:
Known Fare Transaction (KFT): an implementation in which a contactless payment is
made at the point of entry to the transit network (for example, at a bus ticket machine,
where the fare amount is typically known)
Mass Transit Transaction (MTT): an implementation in which a contactless card to be
used subsequently to pay for the travel is authenticated at point of entry to the transit
network).
Note: Kiosks and ticket machines operating in a retail mode at which a transit ticket may be
purchased using a contactless / contact card for subsequent presentation and entry to the
transit network are not in scope.
2.2 Audience
This document should not be shared with or distributed to any other parties.
Chapter Description
1 - CDET User Guide Introduction This chapter provides background information on this CDET User
Guide. It also includes:
Chapter Description
2 - CDET User Guide Overview This chapter provides the following information:
Details on the objectives of the document
The audience to which the document applies
A description of how the document is organized
A description of the CDET components
List of Related Documents
CDET usage criteria
Policy with respect to the introduction of new versions
Scope of CDET testing
Comments on future enhancements
Relevance to the EMVCo Terminal Integration Taskforce
Framework
3 - Test Case Introduction This chapter introduces the CDET test cases. It includes pre-requisite
information for testing, including instructions for each test case and a
summary of all test cases included in this version of the toolkit.
4 - Test Case Details This chapter outlines each CDET test case, providing details on:
Test Case Number
Test Case Name
Objective
Regional Requirement
Business Justification
Pre-requisite
Applicable Terminal Device Type
Applicable Terminal Interface
Test Card used
Test Evidence to be submitted
Document Reference
Pass Criteria/User Validation
A - Visa CA Test Public Key for Provides the value of the currently active 1408-bitsand 1536-bits Visa
qVSDC Offline CA Test Public Key, used for Offline Data Authentication.
B - Acronyms and Glossary Provide a list of commonly used Acronyms and a Glossary of
commonly used terms.
This section lists documents that may be read and/or referred to in conjunction with this document:
Visa Contactless Payment Specifications, (latest version)
Visa International Operating Regulations (latest version)
Visa Europe Operating Regulations (latest version)
Transaction Acceptance Device Requirements (TADR)—Requirements (latest version)
Transaction Acceptance Device Guide (TADG)—Requirements and Best Practices (latest version)
CDET should be utilized to ensure that Visa Contactless readers being deployed have been correctly
configured. It is expected that each applicable test case will be performed to gain the full benefits of
the Toolkit.
If a CDET test result does not meet the expected outcome of the test, it is anticipated that the acquirer
will work with their reader supplier or system integrator to resolve the issue. The acquirer must
continue to work with their technical support service provider until the issue is resolved and the result
complies with the expected outcome.
The following guidelines are intended to provide specific use cases that may govern the use of CDET.
Note that this list is not exhaustive. If a situation arises that is not currently listed, the Acquirer should
contact their Visa representative for guidance.
Prior to deployment of a new Visa Contactless reader for a new or existing Visa Contactless
program
Following significant software of hardware modification or reconfiguration of an existing Visa
Contactless Reader. This includes but is not limited to changes to the following:
o The approved Kernel
o The payment component of the terminal application, affecting Visa Contactless
processing
o The Cardholder Verification Method (CVM) capabilities
o Language Support
o The telecommunications method (e.g. upgrade from dial-up to high-speed)
o Supported Currency Code/Country Code
Introduction of a new model of device hardware.
Note: It is possible to have “families” of devices, which are identical from a payment’s perspective.
Here a new “model” is taken to mean a change, which may affect card acceptance. This includes the
user interface presented to either the cardholder or merchant.
Changes to a merchant or acquirer’s network infrastructure. For example, in a case where a
merchant has switched acquirers, even though their terminal configuration might remain the
same.
A strong suspicion by Visa or other stakeholders of the presence of an acceptance or
interoperability problem affecting the Visa Contactless acceptance device or its connectivity to
VisaNet.
Following upgrades or modifications to the reader to terminal interface or acquirer host systems,
which could affect the transmission of chip data.
Addition of a new peripheral device requiring changes to the existing code, e.g. a new printer or
cash dispenser module.
Change to the terminal-to-host protocol, which does affect authorization messages.
The Contactless Device Evaluation Toolkit may be expanded in the future to include additional device
and/or online transaction processing tests.
On release of a new version of the Toolkit, a six-month grace period will be granted to users prior the
requirement to upgrade to the latest version. During this grace period, testing will still be allowed with
the CDET version just prior to the new release. However, on expiration of the grace period, users will
be required to upgrade to the latest version. In cases where CDET use is mandated, results from earlier
versions of the Toolkit will no longer be accepted.
Device vendors are also recommended to use the Toolkit during the reader development phase. This
will help to ensure that these devices are capable of accepting a selection of diversely configured Visa
Contactless cards.
Table 2–2: Scope of CDET Testing
Device testing Acquirer host The Toolkit focuses on helping to ensure devices
certification deployed in the field are configured in a way that
promotes the best potential for acceptance of Visa
contactless cards.
While some of the cards in this Toolkit are to be used for
online testing, this Toolkit is not specifically designated
as a host certification Toolkit. Acquirers will continue to
perform host system certification using the current set of
test cards and scripts. Please see your Visa regional
representative to obtain the test kit for acquirer host
testing.
Visa, along with the five other EMVCo member Payment Networks, embarked on a series of Level 3
process alignment initiatives that started back in September 2013. Under the leadership of the EMVCo
Level 3 Testing Group (L3TG), various payment networks’ testing processes for the integration of EMV
contact and contactless acceptance devices are currently being standardized. Recent L3TG efforts have
led to the publication of the EMV Level 3 Testing Framework – Process Enhancements and the EMV Level
3 Testing Framework – Implementation Guidelines definition documents, both of which collectively
define standardized methods for L3 test tool development, qualification and usage.
The main impacts of these initiatives on Visa’s CDET processes will be on:
The standardized format in which the CDET Test Cases are being provided to Level 3 test tool
suppliers
The L3 Card Simulator used by clients to perform CDET testing – these tools are being enhanced
with a standardized L3 platform, as defined by EMVCo. This approach enables the standardized:
- Provision of Payment Networks’ test requirements in a machine-readable format
- Presentation of an L3 Test Selection Engine (TSE) where clients define their EMV terminal
configuration details. This in turn enables the Card Simulator to systematically determine and
present the applicable test cases for execution
- Determination of the L3 Pass/Fail Results in an automated way, following test case execution,
and subsequently the reporting of those results in a standardized format along with the
supporting Transaction Logs.
For more information on EMVCo’s L3TG efforts, or to download any of the relevant documentation,
please visit the EMVCo website at the following link: http://www.emvco.com/approvals.aspx?id=272
In compliance with the EMVCo Level 3 requirements, Visa is now providing its CDET test card images
to Level 3 test tool suppliers in the standardized XML format defined by the EMVCo Level 3 Testing
Group (L3TG). These images, representing each of the CDET card profiles and expected behaviors, are
intended for use in conjunction with EMVCo-qualified test card simulators.
3.1 Pre-requisites
Prior to running the CDET test cases, acquirers must ensure that the prerequisites in this section are
fulfilled.
Before beginning any of the tests, it is important to understand the capabilities of your contactless
reader. This will help you ensure you are performing the tests correctly for your specific device.
Authorization Capability—Determine if the reader will be Offline-only, Online only or
Offline/Online capable. Note that while qVSDC may support offline and/or online transactions,
MSD transactions are online only.
Cardholder Verification Methods—Determine the cardholder verification methods that the
reader supports
Note: Online PIN, CDCVM, and Signature are the only CVMs that may be supported for Visa
Contactless.
Offline Data Authentication—Determine if the reader supports Offline Data Authentication.
The capabilities of the contactless acceptance device are indicated within the Terminal Transaction
Qualifier (TTQ) data element, which it sends to the card.
Readers that support Offline Data Authentication must be configured with the Visa CA Test Public Key
while the Toolkit is being used. Details of this test key are located in Appendix A: Visa CA Test Public
Keys for qVSDC Offline.
Note: Prior to production deployment of Visa Contactless readers, the Visa CA Test Public Key must
be removed from readers and replaced with the production Visa CA Public Keys.
With an exception for the use of the Visa test CA keys as described above, the reader under test must
be configured for as close to operational use as possible. For example, readers should include the Visa
AIDs, correct terminal country code, correct date/time, and floor limits, etc.
In accordance with the Visa Operating Regulations, all Visa Contactless acceptance devices must be
successfully tested by a Visa-accredited laboratory and receive a formal Visa approval, prior to
deployment.
3.2 Instructions
In the first instance, the CDET is a self-administered tool. Users must work to fix any problems on their
own or work with their technical support teams for resolution. Visa assistance should only be
requested for queries related to Visa Contactless acceptance policy, rules or best practices or to
provide consultation on the interpreting results.
For readers being initially deployed, the intent is for acquirers to run each applicable test and make
modifications to the reader configuration until the reader meets the expected outcome of the test.
Acquirers should run these tests on each reader type as well as each reader hardware and/or software
configuration. After running all tests and making the appropriate reader configuration modifications,
acquirers in regions where CDET is mandated should submit their results to Visa.
If Visa or the acquiring client suspects a Visa Contactless acceptance problem at a reader that has
already been deployed, it is recommended that all applicable tests specified in the CDET be performed
to assist with analysis.
If changes are made the configuration of an already deployed reader, it is recommended that the
acquiring client re-run all applicable CDET tests, to provide a level of confidence in the changes made.
There is a difference between a declined transaction response and an error message. In some
situations, a declined response on the reader may be acceptable to a test case. However, error
message responses, where the reader is unable to complete the transaction, are generally
unacceptable and can indicate a problem with the reader or its setting/configuration. Testers should
not necessarily be alarmed by a declined response (as long as a declined response is acceptable in the
Expected Results section of the test case). However, error messages (such as “Card Not Read” or the
equivalent) must be investigated.
Users must execute the test cases using the available test card images. For simplicity, a single test card
image represents a single test case, and in all cases the test card image number corresponds with the
test case number (e.g., for Test Case 1, the tester will use Test Card Image 1).
3.2.7.1 General
In the Test Cases section, tests are now designated as Online Applicable. When an Online transaction
is performed, the transaction must be sent online to VCMS or a Visa-confirmed, third party supplied
host simulator for validation of the Authorization Request Cryptogram (ARQC) and/or the CVV (dCVV
or iCVV) data.
Visa Acquirers are required to perform online testing by connecting their reader/terminal to their test
host system and generating transactions through to the VisaNet Certification Management Service
(VCMS), or a Visa-confirmed third party supplied test host, which mimics VCMS. Each test card is
configured with test Data Encryption Standard (DES) keys that is also set up within VCMS, allowing it
to validate and generate the online cryptograms. Successful validation of the cryptogram by VCMS
helps to ensure that all the components involved in the online transaction are correctly coded and
integrated.
For the online tests, card authentication (the validation of the Authorization Request Cryptogram or
dCVV/iCVV) shall be performed and must be successful (unless otherwise noted in the test case).
NOTE: Access to the VisaNet Certification Management Service is provided to Visa Clients only.
Visa provides a web-based solution, the Chip Compliance Reporting Tool (CCRT) that enables
acquirers to report their CDET results online. Once results are submitted, they will be reviewed by Visa
and the acquirer contacted if necessary.
The Chip Compliance Reporting Tool (CCRT) was developed by Visa to provide acquirers with a more
convenient means of completing their compliance requirements, such as the submission of CDET
results following testing. As a web-based, user-friendly solution, CCRT was designed as an improved
alternative to the manual methods previously used for submission of Toolkit test results. With CCRT,
chip acquirers or their designated processors can complete and submit the mandatory compliance
reports via a globally automated online system.
Hosted on the Visa Online (VOL) web portal, CCRT is designed in accordance with Visa’s three-tier
architectural requirements, which provides a high-level of application and data security.
Reducing potential for errors in manual entry by guiding users to choose from applicable
options and providing mandatory information requirements
Allowing the "re-use" of reports as a starting point for new reporting, reducing time spent
completing the reports
Supporting online status review and automated management of reports submitted to Visa,
expediting communication between Visa and clients
Enables the direct importation of CDET validation results performed with PC-based card
simulators
Acquiring clients already enrolled for VOL services may request entitlement to CCRT from their VOL
support representative. Those not yet enrolled, must first request VOL enrollment before being able to
be entitled to CCRT access.
For more details on CCRT, please contact your local Visa Representative.
This section provides a brief description of each test case currently included in this version of the Toolkit. The table below includes
the following information:
Mandatory or Conditional: whether the test case is mandatory to all devices or conditional on the features supported by
the device.
Device Capability: depending on the capability of the device, the test case may either be considered “Applicable (A)” – i.e.
should therefore be performed, or “Non-applicable (N/A)” and should not be performed.
o Online only: generally implies either (a) an acceptance device with a Floor Limit permanently set to zero, or (b) an
acceptance device not supporting a Floor Limit. Such devices also typically support Offline Data Authentication (ODA)
o Offline Capable: an acceptance device with the capability to perform Offline Data Authentication to enable Offline
transaction processing.
o Transit: an acceptance device operating in a Transit environment. This is generally limited to devices that are capable of
performing ODA on a Visa contactless card to enable access into the Transit network.
Test Case Test Case Description Mandatory (M) or Online Offline Transit
Number Conditional (C ) Only Capable
Test Case Test Case Description Mandatory (M) or Online Offline Transit
Number Conditional (C ) Only Capable
5 Card that: M A A A
returns additional data in its SELECT PPSE Response
returns the AIP for an MSD transaction
does not include a PVKI or PVV in Track 2 Equivalent Data
(on device
supporting the
Electron AID)
(on device
supporting the
Interlink AID)
Test Case Test Case Description Mandatory (M) or Online Offline Transit
Number Conditional (C ) Only Capable
9 VMPA Card containing “00” and “FF” Padding in the GPO and a M A A A
Read Record Responses respectively.
15 (VCPS 2.1.x baseline) Card supporting qVSDC Online Transit SDA C N/A N/A A
16 (VCPS 2.1.x baseline) Card using the 1536-bit CA key C N/A N/A A
Test Case Test Case Description Mandatory (M) or Online Offline Transit
Number Conditional (C ) Only Capable
Online, i.e. Transit
Gates)
17 (VCPS 2.1.x baseline) Card supporting qVSDC Online Transit SDA, C N/A N/A A
but SDA fails, and a non-compliant T2ED (on devices
supporting ODA
Online, i.e. Transit
Gates)
M (on all other
devices)
Please refer to the Acronyms Glossary in Section B for the definition and usage of the Floor Limit,
Reader Contactless Floor Limit and Terminal Floor Limit.
Offline Test Cases 1b, 2b, 3b, 4b, 5b, 6b, 7b, 8b, 9b, 12b, 13b and 14b do not apply if either of the
following conditions exists:
- The Reader Contactless Floor Limit is equal to zero
- The Reader Contactless Floor Limit is not present, and the Terminal Floor Limit is set to zero
Additionally, for Test Cases 2b, 3b, 4b, 6b, 7b, 8b, 12b. 13a, 13b and 14b to apply, the following
Terminal Transaction Qualifier (TTQ) bit should not be set:
- TTQ (9F66) Byte 2 – bit 6 = 0 ((Contact Chip) Offline PIN support not supported)
- 1c, 2c, 3c, 4c, 5c, 6c, 7c, 8c, 9c, 10c, 12c, 13c, 14c, 15c, 16c, 17c
Important: Prior to beginning the tests, be sure to read the following sections:
Section 3.1: Pre-requisites
Section 3.2: Instructions (specifically Section 3.2.7: Online Testing)
These sections contain critical information.
Document Reference—References to the specification or rule that acquirers may refer to for
background information on the test. This information is especially important in the event that the
test fails.
Pass Criteria/User Validation—the success criteria expected for the test case.
a. Perform an Online transaction at POS, ATMs & MPOS with online capability
b. Perform an Offline transaction at POS & MPOS with offline capability
c. If applicable, perform transaction at a Transit Terminal (for MTT or KFT) for ODA
Test Case 1/Test Card 1 (Mandatory and both Online and Offline Applicable)
Test Case Number: 1
Test Case Name: VCPS 2.0.2 Baseline Card
Objective:
To ensure acceptance of a VCPS v2.0.2-compliant Visa Contactless card, supporting the
specific features described below.
Support of VSDC Applet Version: 2.7.1
Dual Interface
o MSD supports:
Legacy with dCVV
CVN 17
o qVSDC supports:
Online without ODA (CVN = 17)
Offline with ODA (fDDA)
o VSDC (contact) supports:
DDA
CVN = 10
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a commonly configured Visa Contactless
Justification: card, compliant to VCPS 2.0.2.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only MSD dCVV
MSD 2.x only MSD CVN 17
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Terminal Device
Type:
Applicable ☐Contact ☒Contactless
Terminal Interface:
Test Card: 1
Test Evidence to ☒Receipt (where possible) ☒Card-to-Terminal Interaction Log ☒Host Simulator Log (if
be Submitted: Note: A receipt may be scanned (if available) applicable)
and submitted as a .pdf file.
Document Visa Contactless Payment Specifications – Version 2.0.2 including published updates
Reference:
Test Case 1/Test Card 1 (Mandatory and both Online and Offline Applicable)
Pass Criteria/User Test Online-only Devices: Offline-capable Devices:
Validation Case:
a The transaction should be completed Perform an ‘above Floor Limit’ transaction.
online and be approved by the
The transaction should be completed
VCMS
online and be approved by the
VCMS
Online ODA not performed (ODA data not returned by the card)
Test Case 2/Test Card 2 (Mandatory and both Online and Offline Applicable)
Test Case Number: 2
Test Case Name: VCPS 2.2 Baseline Card
Objective:
To ensure acceptance of a VCPS v2.2-compliant Visa Contactless card, supporting the
specific features described below.
Support of VSDC Applet Version: 2.9
Dual Interface
o MSD not supported
o qVSDC supports:
Online without ODA (CVN = ‘22’)
Online with ODA (fDDA)
Offline with ODA (fDDA)
Valid for domestic and international cash transactions
Valid for domestic cashback
o VSDC (contact) supports:
DDA
CVN = ‘22’
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a commonly configured Visa Contactless
Justification: card, compliant to VCPS 2.2.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only No transaction – path not
supported
MSD 2.x only No transaction – path not
supported
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 2
Test Evidence to be ☒Receipt (where possible) ☒Card-to-Terminal Interaction ☒Host Simulator Log (if
Submitted: Note: A receipt may be scanned Log (if available) applicable)
and submitted as a .pdf file.
Document Visa Contactless Payment Specifications – Version 2.2
Reference:
Test Case 2/Test Card 2 (Mandatory and both Online and Offline Applicable)
Pass Criteria/User
Validation Test Online-only Devices: Offline-capable Devices:
Case:
a The transaction should be Perform an ‘above Floor Limit’ transaction.
completed online and be approved
The transaction should be
by the VCMS
completed online and be approved
by the VCMS
4.3 Test Case 3: Card with a 16-byte ADF Name and other Features
Test Case 3/Test Card 3 (Mandatory and both Online and Offline Applicable)
Test Case Number: 3
Test Case Name: Card with a 16-byte ADF Name and other Features
Objective:
To ensure acceptance of a card with a 16-byte ADF Name, and the following additional
features.
Support of VSDC Applet Version: 2.8.1F1
Dual Interface card
PDOL requests a 2-byte TTQ
No Application PAN Sequence Number (PSN) on the card
Cardholder Name has a minimum value of “ /” (space and forward slash)
Service Code = 621
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a Visa Contactless card, compliant to the
Justification: most recent version of the VCPS specifications and with various unique features included.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only MSD dCVV
MSD 2.x only MSD CVN 17
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 3
Test Evidence to be ☒Receipt (where possible) ☒Card-to-Terminal ☒Host Simulator Log (if
Submitted: Note: A receipt may be scanned Interaction Log (if available) applicable)
and submitted as a .pdf file.
Document Visa Contactless Payment Specifications – Version 2.1 including published updates
Reference:
Test Case 3/Test Card 3 (Mandatory and both Online and Offline Applicable)
Pass Criteria/User Card is personalized with the Application Currency Code ‘0840’ (US Dollars)
Validation
Domestic transaction is a transaction processed by US acquirer
International transaction is a transaction processed by non-US acquirer
Test Online-only Devices: Offline-capable Devices:
Case:
a The transaction should be Perform an ‘above Floor Limit’ transaction.
completed online and be approved
The transaction should be
by the VCMS
completed online and be approved
by the VCMS
b N/A Perform a ‘below Floor Limit’ transaction.
4.4 Test Case 4: Card with additional Data in the GPO Response and
with no Cardholder Name
Test Case 4/Test Card 4 (Mandatory and both Online and Offline Applicable)
Test Case Number: 4
Test Case Name: Multi-application card with additional data in the GPO Response and with no Cardholder
Name
Objective:
To ensure acceptance of a Multi-application card with additional data in the GPO Response
and No Cardholder Name. Card features include:
Support of VSDC Applet Version: 2.8.1F1
Dual Interface card
o MSD supports:
Legacy with dCVV
CVN 17
o qVSDC supports:
Online without ODA (CVN = 10)
Online with ODA (fDDA)
Offline with ODA (fDDA)
o VSDC (contact) supports:
DDA
CVN = 10
Multi-application card, with:
o Visa Credit = A0 00 00 00 03 10 10 01
Application Priority Indicator = 81
o Visa Debit = A0 00 00 00 03 10 10 02
Application Priority Indicator = 82
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a Visa Contactless card, compliant to the
Justification: most recent version of the VCPS specifications and with some unique features included.
With the card containing two applications (Visa Credit and Visa Debit), both requiring
Cardholder Confirmation, and Visa Contactless Readers not supporting this feature, the
intent of this test case is to ensure that the Reader correctly disregards these settings.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only MSD dCVV
MSD 2.x only MSD CVN 17
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 4
Test Case 4/Test Card 4 (Mandatory and both Online and Offline Applicable)
Test Evidence to be ☒Receipt (where possible) ☒Card-to-Terminal ☒Host Simulator Log (if
Submitted: Note: A receipt may be scanned Interaction Log (if available) applicable)
and submitted as a .pdf file.
Document Visa Contactless Payment Specifications – Version 2.1 including published updates
Reference:
Pass Criteria/User
Validation Test Online-only Devices: Offline-capable Devices:
Case:
a Applications shall not be displayed Perform an ‘above Floor Limit’ transaction.
to the cardholder for confirmation.
Applications shall not be displayed
The Visa Credit application shall be to the cardholder for confirmation.
selected for processing.
The Visa Credit application shall be
The transaction should be selected for processing.
completed online and be approved
The transaction should be
by the VCMS
completed online and be approved
by the VCMS
b N/A Perform a ‘below Floor Limit’ transaction.
Applications shall not be displayed
to the cardholder for confirmation.
The Visa Credit application shall be
selected for processing.
The transaction should be approved
Offline by the reader (qVSDC only).
4.5 Test Case 5: Card that returns additional Data in the Select PPSE
Response and containing other unique features.
Test Case 5/Test Card 5 (Mandatory and both Online and Offline Applicable)
Test Case Number: 5
Test Case Name: Card that returns additional Data in the Select PPSE Response and containing other unique
features.
Objective:
To ensure acceptance of a card that has the following features:
Returns additional data in the Select PPSE Response: Language Preference, Kernel
ID, Issuer Identification Number, Issuer Country Code (alpha 2), and Extended
Selection.
The incorrect AIP for MSD (91 81)
PVKI and PVV are not personalized in the Track 2 Equivalent Data (T2ED)
The card also features:
Support of VSDC Applet Version: 2.7.1
Dual Interface card
o MSD supports:
Legacy with dCVV
CVN 17
o qVSDC supports:
Online without ODA (CVN = 17)
Offline with ODA (fDDA)
o VSDC (contact) supports:
DDA
CVN = 10
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a Visa Contactless card, compliant to the
Justification: most recent version of the VCPS specifications and with specific features included.
This test case is intended for readers which are not supporting Extended Selection.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only MSD dCVV
MSD 2.x only MSD CVN 17
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 5
Test Case 5/Test Card 5 (Mandatory and both Online and Offline Applicable)
Test Evidence to be ☒Receipt (where possible) ☒Card-to-Terminal ☒Host Simulator Log (if
Submitted: Note: A receipt may be scanned Interaction Log (if available) applicable)
and submitted as a .pdf file.
Document Visa Contactless Payment Specifications – Version 2.0.2 including published updates
Reference:
Pass Criteria/User
Validation Test Online-only Devices: Offline-capable Devices:
Case:
a The transaction should be Perform an ‘above Floor Limit’ transaction.
completed online and be approved
The transaction should be
by the VCMS
completed online and be approved
by the VCMS
b N/A Perform a ‘below Floor Limit’ transaction.
The transaction should be approved
Offline by the reader (qVSDC only).
Note: iCVV verification is expected to fail since PVKI and PVV are not personalized in the
Track 2 Equivalent Data.
4.6 Test Case 6: qVSDC-only card with 19-digit PAN and CVN 18
Test Case 6/Test Card 6 (Mandatory and both Online and Offline Applicable)
Test Case Number: 6
Test Case Name: qVSDC-only card with 19-digit PAN and CVN 18
Objective:
To ensure acceptance of a qVSDC-only card with 19-digit PAN and CVN 18.
Support of VSDC Applet Version: 2.8.1F1
Dual Interface card
o qVSDC supports:
Online without ODA (CVN = 18)
Online with ODA (fDDA)
Offline with ODA (fDDA)
o VSDC (contact) supports:
DDA
CVN = 18
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a Visa Contactless card, compliant to the
Justification: most recent version of the VCPS specifications and with specific features included.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only No transaction – MSD not
on the card
MSD 2.x only No transaction – MSD not
on the card
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 6
Test Evidence to be ☒Receipt (where possible) ☒Card-to-Terminal ☒Host Simulator Log (if
Submitted: Note: A receipt may be scanned Interaction Log (if available) applicable)
and submitted as a .pdf file.
Document Visa Contactless Payment Specifications – Version 2.1 including published updates
Reference:
Test Case 6/Test Card 6 (Mandatory and both Online and Offline Applicable)
Pass Criteria/User
Validation Test Online-only Devices: Offline-capable Devices:
Case:
a The transaction should be Perform an ‘above Floor Limit’ transaction.
completed online and be approved
The transaction should be
by the VCMS
completed online and be approved
by the VCMS
4.9 Test Case 9: VMPA Card containing “00” and “FF” Padding in the
GPO and a Read Record Response Respectively
4.10 Test Case 10: Card with an IAD length of 23-bytes and an
Unrecognized CVN
Please note: this card image is personalized to return 16 bytes of Issuer Discretionary Data
(IDD), following the 7 bytes of Issuer Application Data (IAD). The IDD consists of the
following:
Byte 8 = length of IDD (0F)
Byte 9 = option ID (03)
Bytes 10 - 14 = VLP Available Funds (variable)
Bytes 15 - 19 = CTTA (variable)
Bytes 20 – 23 = MAC (variable)
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business This card is provided to validate acceptance of a Visa Contactless card, compliant to the
Justification: most recent version of the VCPS specifications and with specific features included.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only MSD dCVV
MSD 2.x only MSD CVN 17
qVSDC only qVSDC
Both qVSDC and MSD 2.x qVSDC
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 10
b N/A N/A
Note: Card Authentication Method (CAM) result will not be provided by Visa in the Field 44.8
due to CVN not supported by the VCMS.
4.11 Test Case 11: Card with a VMPA Applet that causes a Pre-tap
Test Case 11/Test Card 11 (Mandatory and Applicable to both Online Only and Offline-capable
devices)
Test Case Number: 11
Test Case Name: Card with a VMPA Applet that causes a Pre-tap
Objective:
To ensure the Reader displays the correct response message and performs the correct
behavior when presented with a card containing the VMPA Applet that causes a Pre-tap.
Support of VMPA Applet Version: 1.4.1.5 (VMPA 1415 Core 12 121214 00.cap)
Dual Interface card
o MSD supports:
Legacy with dCVV
CVN 17
o qVSDC supports:
Online without ODA (CVN = 10)
o VIS – not supported
Regional Mandatory in Regions where CDET use has been mandated
Requirement:
Business Although a standard qVSDC transaction is typically completed with a single “tap” of the
Justification: contactless payment card, the concept of a “Pre-Tap” is introduced for Mobile consumer
devices. Pre-Tap is defined as the first presentation of the Mobile consumer device to the
contactless payment reader in a situation where some consumer interaction is required to
complete the transaction (e.g. consumer device CVM), and the cardholder has not
completed that interaction prior to presenting the consumer device for payment. After the
consumer interaction has been completed, the consumer device can be re-presented to the
contactless payment reader to perform a “1st Tap” payment transaction.
Although the VMPA applet is presented here in ID-1 card form, its intent is to emulate a
consumer device that has experienced an exception condition (i.e. CDCVM is required but
not performed). The intent of this test case is to ensure that the Reader displays the
correct response message to this condition and performs the correct behavior.
Pre-requisite: For Readers supporting: Resulting Tx should be:
MSD 1.4.2 only Pre-tap
MSD 2.x only Pre-tap
qVSDC only Pre-tap
Both qVSDC and MSD 2.x Pre-tap
Applicable Terminal ☒POS ☒ATM ☒MPOS ☒Transit Terminal
Device Type:
Applicable Terminal ☐Contact ☒Contactless
Interface:
Test Card: 11
Test Evidence to be ☒Receipt (where possible) ☒Card-to-Terminal ☐Host Simulator Log (if
Submitted: Note: A receipt may be scanned Interaction Log (if available) applicable)
and submitted as a .pdf file.
Test Case 11/Test Card 11 (Mandatory and Applicable to both Online Only and Offline-capable
devices)
Document For the Reader: Visa Contactless Payment Specifications – Version 2.1 including
Reference: published updates
For the Card: Visa Mobile Contactless Payment Specification (VMCPS) 1.4.1
Pass Criteria/User
Validation Test Online-only Devices: Offline-capable Devices:
Case:
a The Reader should display a The Reader regardless of the Reader
message to the cardholder Contactless Floor Limit or the
instructing them to ‘refer to their Terminal Floor Limit should display a
payment device for further message to the cardholder
instructions’, briefly power down the instructing them to ‘refer to their
contactless interface before payment device for further
returning to Discovery Processing. instructions’, briefly power down the
contactless interface before
returning to Discovery Processing.
Test Case is considered successfully
completed if the Reader displays the
correct response message (like “Please Test Case is considered successfully
refer to you mobile device”) and briefly completed if the Reader displays the
power down the contactless interface correct response message (like “Please
before returning to Discovery Processing. refer to you mobile device”) and briefly
power down the contactless interface
before returning to Discovery Processing.
b N/A N/A
c N/A
4.12 Test Case 12: Card with a CTQ indicating an issuer preference to
switch to contact interface on ODA failure.
ODA fails
Transit Gate access not permitted
Note: This test case does not applicable to devices supporting ODA for Online Authorizations.
4.15 Test Case 15: Card supporting qVSDC Online Transit SDA
b N/A N/A
b N/A N/A
4.17 Test Case 17: Card supporting qVSDC Online Transit SDA, but
SDA fails, and a non-compliant T2ED
SDA fails
Transit Gate access not permitted
Note: An expiration date has not been defined for test CA Public Key, and it should not be assumed
that a test key has the same expiry date as the live key of the same length. If your Terminal
Management System requires expiry dates to be provided for CAPKs then please set the expiry date
to 31 December 2025 for this test key.
Important: Prior to deployment, this test key must be removed from the terminal and replaced with
the Visa CA production keys.
Component Value
Registered Application A0 00 00 00 03
Provider Identifier (RID)
Index 92
Modulus 99 6A F5 6F 56 91 87 D0 92 93 C1 48 10 45 0E D8 EE 33 57 39 7B 18 A2 45 8E
FA A9 2D A3 B6 DF 65 14 EC 06 01 95 31 8F D4 3B E9 B8 F0 CC 66 9E 3F 84 40
57 CB DD F8 BD A1 91 BB 64 47 3B C8 DC 9A 73 0D B8 F6 B4 ED E3 92 41 86
FF D9 B8 C7 73 57 89 C2 3A 36 BA 0B 8A F6 53 72 EB 57 EA 5D 89 E7 D1 4E
9C 7B 6B 55 74 60 F1 08 85 DA 16 AC 92 3F 15 AF 37 58 F0 F0 3E BD 3C 5C 2C
94 9C BA 30 6D B4 4E 6A 2C 07 6C 5F 67 E2 81 D7 EF 56 78 5D C4 D7 59 45
E4 91 F0 19 18 80 0A 9E 2D C6 6F 60 08 05 66 CE 0D AF 8D 17 EA D4 6A D8
E3 0A 24 7C 9F
Exponent 03
Secure Hash Algorithm-1 42 9C 95 4A 38 59 CE F9 12 95 F6 63 C9 63 E5 82 ED 6E B2 53
Hash
Comments: The expiration date for certificates issued using Visa’s 1408-bit Test CA public
key is December 31, 2019.
Component Value
Registered Application A0 00 00 00 03
Provider Identifier (RID)
Index 89
Modulus E5 E1 95 70 5C E6 1A 06 72 B8 36 7E 7A 51 71 39 27 A0 42 89 EA 30 83 28 FA
D2 80 71 EC EA E8 89 B3 C4 F2 9A C3 BD E4 67 72 B0 0D 42 FD 05 F2 72 28 82
0F 26 93 99 0F 81 B0 F6 92 8E 24 0D 95 7E C4 48 43 54 CD 5E 5C A9 09 2B 44
47 41 A0 39 4D 34 76 65 12 32 47 4A 9B 87 A9 61 DA 8D D9 6D 90 F0 36 E9 B3
C5 2F B0 97 66 BD A4 D6 BC 3B DA DB C8 91 22 B7 40 68 F8 FA 04 02 6C 5F
A8 EF 39 8B C3 AB 39 92 A8 7F 6A 78 5C C7 79 BA 99 F1 70 95 66 23 D6 7A 18
EB 83 24 26 3D 62 6B E8 5B FF 77 B8 B9 81 C0 A3 F7 84 9C 4F 3D 8E 20 54 29
55 D1 91 28 19 85 47 B4 7A E3 4D F6 7F 28 BE 43 3F 33
Exponent 03
Secure Hash Algorithm-1 71 70 85 0B 97 F8 39 52 04 5C F9 CA 8B 76 12 DF EB 69 E9 EF
Hash
Comments: The expiration date for certificates issued using Visa’s 1536-bit Test CA public
key is December 31, 2023.
Acronym Meaning
a alpha
AAC Application Authentication Cryptogram
AAR Application Authentication Referral
ADA Application Default Action
ADF Application Definition File
ADVT Acquirer Device Validation Toolkit
AEF Application Elementary File
AFL Application File Locator
AID Application Identifier
AIP Application Interchange Profile
an alphanumeric
ans alphanumeric special
APDU Application Protocol Data Unit
API Application Priority Identifier
ARPC Application Response Cryptogram
ARQC Application Request Cryptogram
ATC Application Transaction Counter
ATM Automated Teller Machine
AUC Application Usage Control
b binary
BIN Bank Identification Number
CA Certificate Authority
CAM Card Authentication Method
CAT Cardholder Activated Device
CDA Combined Dynamic Data Authentication
CDOL Card Risk Management Data Object List
CID Cryptogram Information Data
cn compressed numeric
CSV Comma-Separated Values
CVK Card Verification Key
CVM Cardholder Verification Method
CVR Card Verification Result
CVV Card Verification Value
DDA Dynamic Data Authentication
DDF Directory Definition File
DDOL Dynamic Data Authentication Data Object List
Acronym Meaning
DEA Data Encryption Algorithm
DES Data Encryption Standard
DGI Data Group Identifier (used by the Card Personalizer only)
DKI Derivation Key Index
EMV Europay, MasterCard & Visa
FCI File Control Information
GPO Get Processing Options
hex. Hexadecimal
IAC Issuer Action Code
ICVV Alternate Card Verification Value
IFM Interface Module
KFT Known Fare Transaction
L3TG Level 3 Testing Group
MCC Merchant Category Code
MDK Master Derivation Key
MPOS Mobile Point of Sale Device
MTT Mass Transit Transaction
N/A Not Applicable
n numeric
PAN Primary Account Number
PDOL Processing Options Data Object List
PIN Personal Identification Number
PIX Proprietary Application Identifier Extension
PK Public Key
PKI Public Key Infrastructure
PKI Public Key Index
POS Point of Sale
PSE Payment Systems Environment
PSTN Public Switched Telephone Network
PVK PIN Verification Key
PVV PIN Verification Value
RFU Reserved For Future Use
RID Registered Application Provider Identifier
RSA Rivest, Shamir, Adleman
RRN Retrieval Reference Number
SAD Signed Static Application Data
SAM Secure Access Module
SDA Static Data Authentication
STIP Stand-In Processing
TAC Terminal Action Code
TC Transaction Certificate
TDOL Transaction Certificate Data Object List
TITF Terminal Integration Task Force
Acronym Meaning
TLV Tag-Length-Value
TSI Transaction Status Information
TVR Terminal Verification Result
UAT Unattended Acceptance Device
UCAT Unattended Cardholder Acceptance Device
UDK Unique Derived Key
var. variable
VCMS Visa Certification Management Service
VIP VisaNet Integrated Payment
VLP Visa Low-value Payment
VMTS Visa Member Test System
VSDC Visa Smart Debit/Credit
VTS VisaNet Test System
XML Extensible Mark-up Language
XSD XML Schema Definition
For terminals, this describes the state in which the terminal has already been
equipped with a chip reader/writer and has been configured with Brand-specific
data and is ready for use in accepting chip cards.
Term Definition
Comma-Separated A format that stores tabular data (numbers and text) in plain-text form (i.e. a
Values (CSV) 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 An interaction between a chip application and a device using the radio frequency
Transaction wireless interface, as defined in [EMV CL].
Customer Activated See “Cardholder Activated Device.”
Terminal (CAT)
EMVCo LLC (EMVCo) Industry organization that manages, maintains, and enhances the EMV
Specifications. Current Members are American Express, JCB International,
MasterCard Worldwide, UnionPay, and Visa Inc.
EMV Specifications Technical specifications developed and maintained by EMVCo to create standards
and ensure global interoperability for use of chip technology in the payment
industry. In order to support EMV, cards and terminals must also meet the
requirements described in the bulletins available on the EMVCo website.
Floor Limit A currency amount that Visa has established for single transactions at specific types
of merchants, above which online authorization is required.
Host Authorization A description of the transaction message initiated from the device and sent online
Message via the acquirer and network to the issuer, processor, or Brand for transaction
authorization.
Host Authorization A Test Plan-defined description of the requirements for elements and content of
Message Validation the Host Authorization Message to be validated during standalone or terminal
integration testing.
Implement To make a card, application, or device capable of performing a functionality.
Functionality that is implemented may also need to be enabled (see Chip-enabled).
Interoperability The ability of all card acceptance devices to accept and read all chip cards that are
properly coded and personalized.
Kernel EMV definition for the set of functions required to be present on every terminal
implementing a specific interpreter. The kernel contains device drivers, interface
routines, security and control functions, and the software for translating from the
virtual machine language to the language used by the real machine. In other words,
the kernel is the implementation of the virtual machine on the real machine.
Known Fare Transit implementation in which a contactless payment is made at the point of
Transaction (KFT) entry to the transit network, using a contactless payment card.
Level 3 Testing Group EMVCo testing group into which the Terminal Integration Task Force (TITF) evolved
in January 2017. Responsible for managing all aspects of the Level 3 testing
initiatives and processes.
Limited Amount An unattended device that has data capture-only capability, and accepts payment
Device for items such as parking garage fees, road tolls, etc.
Mass Transit Transit implementation in which a contactless card to be used subsequently to pay
Transaction (MTT) for the travel, is authenticated at the point of entry to the transit network.
Term Definition
Mobile Point of Sale A smartphone, tablet, or dedicated wireless device that performs the functions of a
(MPOS) cash register or electronic point of sale terminal (POS terminal).
Offline-Capable A transaction acceptance device that has the ability to process the transaction
offline for card authentication and authorizations.
Offline-Only A transaction acceptance device that is only able to process the transaction offline
for card authentication and authorizations.
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.
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 field that describes an expected result for a successful outcome
or conclusion of a test case.
Pass Criteria File The file (in CSV format) that embeds the Brand-defined pass criteria for each test
case.
Personalization For chip cards, the process of applying both cardholder and Brand-specific data to
the card in preparation for its use.
Point of Sale The physical location where a merchant or acquirer in a face-to-face environment
or an unattended device completes a transaction.
Point-of-Sale Device A device used at the POS to process transactions, including chip devices,
automated dispensing machines, self-service devices, and ATMs.
Reader Contactless Indicates the contactless floor limit of the reader for Visa applications. If the
Floor Limit transaction amount is greater than the Reader Contactless Floor Limit, then the
reader requires online processing for the transaction.
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 A description of the features and parameters on the acceptance device under test.
Configuration For example, it might include the EMV-defined terminal types, supported interfaces,
etc.
Terminal Floor Limit Indicates the floor limit in the terminal.
Terminal compares Amount, Authorized with the applicable Terminal Floor Limit if
the Reader Contactless Floor Limit is not present.
Terminal Integration A process implemented and managed by the respective Brands, aimed at providing
Testing a level of assurance that Brand-specific requirements and recommendations are
being implemented in contact or contactless chip acceptance devices that will
accept a Brand’s products.
Terminal Integration Task Force established by EMVCo in 2013 with the purpose of examining each of
Task Force (TITF) the Brand’s terminal integration processes, in order to determine the possibilities of
aligning key elements of these processes.
The TITF was renamed the Level 3 Testing Group (L3TG) in January 2017
Test Card Image An electronic representation of a physical card.
Test Case A Test Plan-defined description of a test scenario, defined by a Payment Brand for
execution of terminal integration or host message testing.
Term Definition
Test Case Name A Test Plan-defined description of the name associated with a specific test case.
Test Case Number A Test Plan-defined unique test case identifier.
Test Case Objective A Test Plan-defined description of the objective of performing a given test case.
Test Plan A Brand-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
textual document or a machine-readable file.
Test Procedure A Test Plan-defined description of the steps required in order to execute a specific
test case.
Test Tool The process undertaken by each Brand to provide themselves, tool vendors, and
Confirmation clients will a level of assurance that the tools being used by clients to execute
terminal integration testing will do so in compliance with Brand requirements.
Process is also referred to as “Test Tool Qualification.”
Test Tool The process undertaken by each Brand to provide themselves, tool vendors, and
Qualification clients will a level of assurance that the tools being used by clients to execute
terminal integration testing will do so in compliance with Brand requirements.
Process is also referred to as “Test Tool Confirmation.”
Transaction An EMV definition for the successful closing of transaction processing. The
Completion completion function is always the last function in transaction processing and must
occur unless the transaction is terminated prematurely by error processing.
Transit Terminal Refers to the combination of equipment at the entrance to a transit network (for
example, a metro gate) or vehicle (for example, a bus) that is collectively used to
accept Visa contactless cards for transit network access. This equipment may be a
single integrated piece of equipment or a number of separate physical components
(for example, bus ticket machine, display and reader) that together form the card
acceptance device.
Unattended A cardholder-operated device that reads, captures, and transmits card information
Cardholder Activated in an unattended environment.
Terminal (UCAT) Also known as “Customer Activated Terminal (CAT)” or “Unattended Acceptance
Device (UAT).”
User Validation A Test Plan-defined description of the requirements for the user/tester to validate
responses from the device under test.
Extensible Mark-up A mark-up language that defines a set of rules for encoding documents in a format
Language (XML) that is both human-readable and machine-readable.