Chip Card Testing and Approval Requirements V8.0
Chip Card Testing and Approval Requirements V8.0
Chip Card Testing and Approval Requirements V8.0
Requirements
Visa Approval Services
Version 8.0
April 2021
Visa Public
Important Information on Confidentiality and Copyright
Notice: The Visa Confidential label indicates that the information in this document is intended for use
by Visa employees, Visa clients, and other external persons and entities that are parties to an
applicable Confidentiality and Nondisclosure Agreement (NDA) with Visa. This information is not for
public release.
THIS DOCUMENT IS PROVIDED ON AN "AS IS,” “WHERE IS,” BASIS, “WITH ALL FAULTS” KNOWN AND
UNKNOWN. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VISA EXPLICITLY
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE LICENSED WORK AND TITLES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY , FITNESS FOR A PARTICULAR
PURPOSE, AND NON-INFRINGEMENT.
All brand names and logos are the property of their respective owners, are used for identification
purposes only and do not imply product endorsement or affiliation with Visa.
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
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.
Contents
Chip Card Testing & Approval Requirements
Contents
Tables
Figures
Introduction
The process and requirements described in this document applies to the following types of product
• Contact chip products supporting Visa Smart Debit/Credit (VSDC)
• Contactless chip products supporting MSD/qVSDC
• Dual interface chip products supporting VSDC and MSD/qVSDC
For the purpose of this document the term “card” shall be used to represent ID1 size cards, fobs, mini
cards, micro-tags, adhesive micro-tags (stickers), and inlays for non-card products with static
contactless chip.
Other form factors will be referred to as “non-card products with a static contactless chip”, one
example being a wearable product such as a wristband.
A product with a static contactless chip is defined as a payment product that cannot have its account
data provisioned or updated post issuance. In other words, the genuine account number, not a token,
is personalized to the product prior to issuance.
For information about the mobile product type approval process please refer to Visa Approval
Services Mobile Product Testing and Compliance Requirements document.
Audience
This document is intended for vendors submitting chip card products and non-card products with a
static contactless chip to Visa Approval Services for testing. It describes Visa’s product testing and
approval process.
Contact Information
Visa Approval Services is responsible for managing the accreditation and various other processes
described in this guide. They are the single point of contact within Visa for vendors seeking testing
and laboratories seeking accreditation. The vendor or the testing laboratory may contact Visa
Approval Services at any time.
Email: [email protected]
Websites: Visa Technology Partner
(https://technologypartner.visa.com)
Visa Digital Partner Services
(https://digitalpartnerservices.visaonline.com/ )
US Postal Address: Visa International Approval Services
For shipping non-card
•
900 Metro Center Boulevard
products and inlays with
static contactless chip Mail Stop M3-2NW
for interoperability and
performance testing Foster City, CA 94404
United States
• For shipping cards for Mailroom Contact : (650) 432-8822
archiving:
Process Overview
To reduce the duplication of testing for vendors, Visa’s type approval process utilizes testing and
certification programs offered by EMVCo and GlobalPlatform.
The applicability and scope of functional and security testing is dependent of the configuration of
product being submitted and the circumstance of the submission, i.e. whether it is a new product or a
derivative.
If the product successfully passes all required testing and requirements, Visa issues a Letter of
Approval (for card products) or Letter of Compliance (for stickers and non-card products). The
approval recognition applies internationally unless specified in the letter.
Note: The process described in this document does not approve vendors, it only approves products.
Approval is not transferrable from one product to another, or from one vendor to another.
Note: The issuance of a letter by Approval Services does not provide an allowance of the card
construction per ISO 7810 & 7811-6, or review against the Visa Product Brand Standards, as required
by Global Design & Innovation (Brand). Information regarding this separate and required qualification
process can be found on the Visa Product Brand Standards website or by contacting
[email protected].
The Visa Technology Partner website facilitates the vendor registration process. Information can be
found at https://technologypartner.visa.com/Registration. Vendors only need to register once.
Note: Vendors who are submitting a non-card product with a static contactless chip, e.g. a wearable
or an IOT product, are also required to enroll in the Visa Ready program. Please contact Visa Ready at
[email protected] or go to Visa Ready Portal at. https://partner.visa.com/site/programs/visa-
ready.html
Product manufacturers are responsible for developing products to supported Visa specifications and
requirements.
The Visa Technology Partner website facilitates the licensing of Visa’s Chip Specifications and Visa-
developed Software, which in turn allows access to additional documentation vendors will need:
• Visa Contactless Payment Specification
• Visa Integrated Circuit Card Specification
• Visa-developed Visa Smart Debit / Credit application software
• Visa Chip Security Program
• GlobalPlatform Requirements
• Visa Prepaid Specification
• Multi-Access for Visa Smart Debit/Credit Specification
• Test plans and personalization (see section 1.4)
• Visa Biometric Sensor-on-Card Specification
This list is not exhaustive of all specifications and requirements that may be used in the development
of a Visa-compliant payment product, for example EMVCo and GlobaPlatform. The vendor developing
a product is ultimately responsible for obtaining all specifications and requirements relevant to the
product it submits for testing and approval.
Information about licensing Visa technology can be found on the Visa Technology Partner website at
https://technologypartner.visa.com/Registration.
In addition to the license agreements, vendors intending to submit a product to Approval Services for
testing must execute an Approval Services Testing Agreement (ASTA). The ASTA is a standard
agreement that defines the terms and conditions governing the testing and approval of the vendor’s
product. The ASTA is made available to download from the Visa Technology Partner website after the
vendor has registered (see section 1.1). Please contact Approval Services if you have questions about
the ASTA.
Vendors who enroll in the Visa Ready program will also need to execute the Visa Ready Contract.
Please contact Visa Ready at [email protected].
Vendors will also need to enter into agreements with Visa-recognized testing laboratories that will test
their product. Visa does not get involved with agreements between laboratories and vendors. A
current list of Visa Recognized Testing Laboratories and their contacts can be found on the Visa
Technology Partner and Visa Digital Partner websites.
Test plans and commercial test tools with associated test scripts are available to assist vendors in
conducting quality assurance (QA) testing prior to submitting the product for official testing.
Successful completion of all the test scripts by the vendor does not imply approval, nor does it depict
Visa’s full testing process. Rather, it provides the vendor with insight into the product testing process.
Visa reserves the right to develop and run additional tests that are not part of the current test plan.
Visa testing may include subjecting the product to additional physical and situation-specific tests as
needed.
Vendors must sign the Approval Services Testing Agreement to gain access to test plans on the Visa
Technology Partner website.
Visa grants vendors who have signed the required agreements permission to use the test plans solely
for purposes of developing and testing products for a Visa application. Visa may revoke its permission
at any time. Possession and use of these materials is subject in all respects to the terms and the
continued effectiveness of the Approval Services Testing Agreement.
These materials are provided on an “as is” basis “with all faults.” Visa disclaims all warranties
pertaining to these materials, expressed or implied, including the implied warranties of
merchantability, fitness for purposes, or non-infringement.
Commercial test tools and test scripts are available from Test Tool Vendors. Test Tool Vendor contact
information is published on the Visa Technology Partner or Visa Digital Partner Service website.
Test plans and test scripts are subject to enhancements and modifications at any time. Unpublished
test plan revisions are made available through Approval Services’ knowledge base on the Visa
Technology Partner website or Visa Digital Partner Service (requires logging on to the site).
Test plan revisions will be accumulated and published as new test plans as determined by Visa. It is
the Vendor’s responsibility to ensure that they have the most current test plans and test scripts
available. Vendors should contact their tool supplier to obtain any test script updates. Test Plans are
accessible online via the Visa Technology Partner or Visa Digital Partner Services website for licensed
Vendors
The forms and process differs slightly between cards and non-card form factors with a static
contactless chip.
Vendor Completes
Vendor Updates
Non-Card Product Questionnaire for Vendor Submits Approval Services
Questionnaire Questionnaire and
with Static Wearable with Questionnaire to Reviews N
OK? Re-submits to
Contactless Chip Static Contactless Visa Ready Questionnaire
Approval Services
Chip
Approval Services
Vendor Completes
Vendor Submits Issues Visa
Approval Services
Card Form Factor Questionnaire to Reference Number
Chip Card
Approval Services and Determines
Questionnaire
Testing
Vendors must provide a Product Questionnaire for each product submitted for testing and approval.
The questionnaire is used to determine whether the product is acceptable and what testing is
required.
• If a product supports both T=0 and T=1 protocols, the product can be submitted
separately for each protocol or can be both protocols in one questionnaire. If submitted
with both protocols, the product will be evaluated in one testing scope.
• If a contactless product supports both Type A and Type B, the product must be
submitted separately for each contactless type and each will be tested independently.
• If a product supports multiple memory sizes, it shall be submitted with multiple memory
sizes declared in the same questionnaire. Approval Services assigns a single Visa
reference number. Visa’s approval extends to all chip models or memory sizes covered
by the EMVCo IC Certificate Number referenced in the approval letter.
The vendor and the laboratory(s) are responsible for scheduling testing once the vendor has received
confirmation of the testing requirements from Approval Services and testing is authorized. Visa does
not participate in and is not responsible for any scheduling between the Laboratories and Vendors.
Security testing can take longer than functional testing. It is the vendor’s choice when to start security
and functional testing.
A vendor has six months from the testing authorization date to complete all testing and submit test
results to Approval Services. If applicable , all test samples for Performance and Cross Testing must
be submitted within reasonable timeframe so that testing can be completed within the six months
from the testing authorization date.
It may be necessary to contact more than one laboratory, depending on the characteristics of the
product, the scope of testing, and the testing available at various laboratories. For a current list of
testing offered by a laboratory, go to the Approval Services section on Visa Technology Partner
website.
Note: If any problems occur during functional or security testing that would not allow the product to
successfully complete testing, the following will occur:
• Official testing will stop.
• The vendor is responsible for all costs incurred with the Laboratory(s).
• The problem is corrected and the product questionnaire resubmitted.
Laboratories performing functional testing may offer quality assurance (QA) testing that can be
completed prior to submitting a product for official testing. However, quality assurance testing is not
part of Visa’s official testing and approval process and QA test results are not accepted for review.
Note: Visa reserves the right to conduct additional testing on any products that have gone through
the testing and approval process.
Official testing shall not begin until the vendor has provided all necessary forms to the laboratory.
The Exhibit A and Request for Approval Forms are combined in a single file.
Table 2–1: Forms Required for Testing
Form Description
Exhibit A: Request for Establishes Visa’s right to review testing results submitted by the Vendor,
Testing Services following testing at a Laboratory.
+ An official request to release test reports to Visa so that Visa can begin
the review and approval process for a product tested at the Laboratory.
Request for Approval Form
Single Production Batch An attestation by the vendor that all samples submitted for testing (initial
Confirmation Form test samples or replacement samples), regardless of the Laboratory to
which they are being sent, are from the same production batch and
without modification.
Implementation A vendor must provide detailed information regarding the Visa payment
Conformance Statement application, platform, or interface.
(ICS)**
A separate ICS is needed for each type of functional testing performed.
** Visa accepts the equivalent forms used by EMVCo and GlobalPlatform, specifically:
• EMVCo Common Payment Application Level 1 & Level 2 ICS (for Contact Level1). The vendor only
needs to complete the section for Electrical and Protocol testing. The ICS must show the
hexadecimal values returned by the chip card in response to Answer to Reset (ATR), SELECT
command, and GET PROCESSING OPTIONS. Data provided by the Vendor is used to check the
data returned by the card during testing.
• EMVCo PICC Level 1 ICS (for Contactless Level1)
• GlobalPlatform Supported Configuration Options (SCO)
Forms must be submitted for each product submission. If a product fails testing, a new version of
each form must be provided when the product is resubmitted for testing.
Laboratories test various functions and applications supported by Visa. Such testing includes the
electrical aspects of the chip protocol and communications of the product, as well as functionality of
the applications.
Testing is dependent on the technology and applications supported by the product. A rough guide is
shown below.
Contact Product EMV Contact Level 1 (Electrical & Protocol) T=0 or T=1
Contactless Product EMV Contactless Level 1 (Analog & Digital) Type A or Type B
Visa Payment Application (MSD and/or qVSDC)
Cross Testing
Performance Testing
Visa Biometric Sensor on Card Specification Application (VBSS)
Visa Biometric Sensor Performance Testing
Dual Interface Product EMV Contact Level 1 (Electrical & Protocol) T=0 or T=1
Although testing of dynamic CVV2 functionality is out of scope of functional testing, if supported the
dCVV2 functionality shall be enabled for testing.
EMV Contact Level 1 ensures a level of interoperability for cards and acceptance devices. Testing is
comprised of electrical characteristics, transmission protocol T=0 or T=1, and Answer to Reset (ATR) 3
volt and 5 volt.
EMV Contactless Level 1 ensures a level of interoperability for contactless products and acceptance
devices. Testing is comprised of analog testing to ensure the magnetic field characteristics are able to
carry the communication, and digital testing to ensure the timing, anti-collision, and protocol
characteristics are able to carry the communication.
Visa Payment Application testing ensures that the application processes the transactions correctly,
in accordance with the relevant specifications. MSD and qVSDC application paths are for contactless
use only and shall not be used through a contact interface. VSDC application path is for contact use
only and shall not be used over a contactless interface. Multi-Access for VSDC and Prepaid application
testing are also included if declared to be supported by the product. VBSS application is for contact
and contactless interfaces.
Visa performs cross testing (also referred to as interoperability testing) to ensure that contactless
products and devices are interoperable with each other. Cross-Testing is a part of the official testing
process, and the performance during this testing will be part of final approval consideration. Products
that fail to communicate with multiple devices may not be eligible for approval.
Note: Visa is not permitted to disclose information about the terminals used for Cross-Testing to
Vendors. Samples cannot be shared for contactless level 1 and cross testing.
Performance testing: Effective September 1 2016, contactless and dual interface products are
required to support a minimum ICC key size of 1152 bits and still meet the contactless performance
requirement of ≤ 400 milliseconds. Please refer to Approval Services Announcement ASA20150801 on
the Visa Technology Partner website for details.
VBSS compliant products, template extraction and matching timing shall be <1 second.
GlobalPlatform manages the platform functional testing for GP platforms. Visa only accepts official
GP test results performed by a GP-qualified Laboratory. Self-testing results are not accepted as proof
of specification compliance. Vendors shall provide an SCO Form and Qualification Letter from GP to
Visa in support of their submission. Visa requires the SCO and Qualification Letter prior to issuing an
approval or compliance letter. More information about the GlobalPlatform compliance testing process
can be found on its website at http://www.globalplatform.org.
Vendors have the opportunity to leverage functional test reports from approved products. A product
that shares test results may be eligible for reduced testing.
If Visa discovers a defect in a product that other products have shared test results from, all Vendors
involved in the sharing agree that Visa can communicate all relevant information to each affected
Vendor and its customers, including an explanation of the nature of the defect and products at issue.
Shared test results are permitted only if:
All Vendors involved in the sharing have an ASTA.
The product being leveraged from has been tested and approved with no issues or
comments.
The product being leveraged from is not already sharing test results from another
product.
A product using shared results will be tied to the original approved product as follows:
The product will receive the same expiration date as the product from which the results
are shared.
If the original product is revoked, then all products sharing testing results will be
revoked.
If the original product is modified and/or updated, then all products sharing testing
results may require additional testing.
The questionnaire being submitted should indicate that the product is seeking to share
test results and provide the Visa Reference Number (VTF#) of the approved product.
Note: If a product is submitted for full testing, it will receive an independent approval, and its
expiration date is not tied to any other product.
Chip hardware is defined as the basic ‘Chip’ or ‘IC’ product without an operating system or
application. The security of the chip hardware is evaluated by EMVCo. The EMVCo IC security
evaluation process considers the security of chip products and aims to provide a high level of
assurance that the chip is designed to resist known attack methods. Visa leverages the EMVCo
process to minimize cost and time spent in performing evaluation work and to avoid duplication of
effort.
EMVCo issues an IC certificate with an IC Certificate Number (ICCN) when a chip has successfully
completed the EMVCo IC security evaluation process. EMVCo approved ‘IC’ products are listed on the
EMVCo website at www.emvco.com.
Requirement: Visa will only accept new products for security testing if the chip has successfully
completed the EMVCo IC security evaluation process and the chip is listed on the EMVCo approved
chips list.
For detailed information on the EMVCo ‘IC’ security evaluation process, please see EMV Security
Guidelines – EMVCo Security Evaluation Process available at www.emvco.com, or contact the EMVCo
Security Evaluation Secretariat at [email protected] with any questions.
For further information on how the EMVCo security evaluation process ties in with the Visa Chip
Security Program, please contact Approval Services.
Like functional testing, security testing is performed only on a product in its final configuration, as it
would be supplied to a Visa client. Security testing focuses on aspects of the product implementation
that may have a security impact. Security testing goes beyond the functional testing to see if the
product is vulnerable to known attacks, whether or not these are explicitly cited in the specification.
The Visa Chip Security Program (VCSP) seeks to minimize the cost and time spent in performing
evaluation work and to avoid duplication of effort. Security testing is not exhaustive and focuses on
the most likely vulnerabilities as revealed by previous testing, knowledge of the particular
application(s), and past experience with similar products.
The level of testing is continuously increasing to reflect ‘state-of-the-art’ attack potential.
Consequently, the introduction of new chip products should offer a higher level of protection against
the latest threats. However, no testing can anticipate all potential future attacks. Security, by
definition, is an ongoing process; as time progresses, attack and defense becomes a race.
All Visa chip-based payment products are required to go through VCSP security testing.
Visa Chip Security Program—Security Testing Process for Chip Cards provides detailed information
about the security evaluation program. The VCSP Initial Assessment Letter (IAL) requirements
document provides the requirements for submitting an IAL to Approval Services. These documents
are available at the Visa Technology Partner website.
Products exist in many variants and may sometimes have minor differences. A product with a “minor
change” is not required to undergo Visa security testing and will leverage the approval date and
comments of the original product.
A minor change is defined as:
• Verified bug fixes with no negative impact on security
• Functional changes that do not have an impact on security testing
• VSDC code changes that Visa has defined as minor
Vendors must obtain an initial assessment letter (IAL) from a Visa-recognized security laboratory prior
to Visa authorizing security testing to begin on a product. The Vendor must authorize the laboratory
to submit the IAL to Visa for products being submitted for security testing.
The review of the IAL will determine the amount of security testing that will need to be performed,
and Visa may decide that more or less testing is required based on product history and other factors.
The following summarizes different security testing scenarios:
• Full security testing – This will be required in the case of a new product that has not been
evaluated previously by the Laboratory under the VCSP program.
• Delta security testing – This will be performed in the case of product modification or
patch.
• No security testing – This may result in the instance that the product has been evaluated
before and the changes have no negative security impact (e.g., it is classified as a Minor
Change).
Laboratories will accept products for testing only in their final configuration as they will be supplied to
Visa clients. A product submitted for testing shall be in the state described below.
Requirement Description
Chip The chip must be embedded and bonded to the product’s body.
Commands Commands that can update the product must be in compliance with the
Visa specifications for the application(s) in the product.
Debugging code All debugging code must be removed from the product before it is
submitted for testing. Failure to remove this code may cause the product
to fail testing.
ATR values After the card is put into an initialized state, the Answer to Reset (ATR)
(contact only) values (except for historical bytes) cannot be changed.
A product may not contain both T=0 and T=1 protocols within the same
Answer to Reset (ATR).
ATS values For Type A contactless products, the Answer to Select (ATS) values on the
(contactless only) product submitted for testing must be those identified in the
Implementation Conformance Statement (ICS).
Answer to REQB For Type B contactless products, the values of bytes 10, 11, and 12 in the
Command “Answer to REQB Command” on the product submitted for testing must
be those identified in the Implementation Conformance Statement (ICS).
Antenna A schematic of the antenna must be provided for all contactless and dual
Schematic interface products.
(contactless only)
A product that supports more than one Visa payment application requires a full set of samples for
each Visa payment application. For dual interface products, a full set of samples must be provided for
each interface.
All personalization requirement documentations are published on the Visa Technology Partner or Visa
Digital Partner website.
Personalization of test data will differ for each Visa application being tested. The functionality of the
Visa application must not be affected by personalization.
Inlays for non card products are treated the same as the card for the purposes of this section
o Fob 22_1152_v1*
o Mini Card Performance 12 For VCPS 2.1.3 or less: Vendors are required to
o Inlay with Testing provide three samples of
21_1024_v2 each profile.
static
contactless 21_1152_v2 Send samples to
chip Singapore location
21_1408_v2
except Inlay, which goes
21_1920_v2 to Foster City.
22_1024_v1
22_1152_v1
22_1408_v1
22_1920_v1
22_1152_v1*
21_1920_v2
22_1024_v1
22_1152_v1
22_1408_v1
22_1920_v1
Card Contact Level Number depends on For VIS 1.5.4 or less: Card Image files are
1 test requirements. included in the VIS
Refer to test VSDC01, VSDC11,
laboratory for VSDC12 or VSDC13 test plan package
guidance
(VIS Card Images
Requirements v1.5.4b)
CT_L1
Any Contactless Level Number depends on For VCPS 2.1.3 or less: Card Image files are
1 test requirements. included in the VCPS test
Refer to test VCPS_1_000 or plan package
laboratory for VCPS_2_000
guidance
(VCPS Card Image Book
2 Part 1 v2.1.3b_R_01)
CTL_L1
(VCPS Contactless L1
Test v2.2 R01)
Non-card Cross Testing 3 For VCPS 2.1.3 or less: Send samples to Foster
product with City location.
static contactless 21_1152_v2*
chip Vendors may provide
For VCPS 2.2 or additional equipment for
higher: the purpose of holding
the product at its
22_1152_v1*
preferred angle for
testing, otherwise the
default presentment
shall be face down,
parallel to the terminal
landing plane.
21_1920_v2
22_1024_v1
22_1152_v1
22_1408_v1
22_1920_v1
Notes:
i. Vendors should always check and use the latest Card Images for Performance and Cross test provided in
Visa Technology Partner site. The current card image version for VCPS 2.1.x products is v2 and VCPS
2.2.x products is v1.
ii. Samples for card image 1920 is required if the product or its base product supports this key size. The
vendor shall indicate any limitations in the CCQ if the product cannot meet this requirement
The table below details the Information printing for functional testing samples.
This information is optional for the Performance and Cross Testing samples. Each Performance and
Cross Testing samples must include a QR Code label as described in next section.
.
Table 2–3: Printing for functional testing samples
Card Visa reference number (VTF number) Paste-on labels are not acceptable.
Chip model number
Test cards are not required to have a
Contactless interface type (Type A or Type B) magnetic stripe for the testing process.
if applicable
Transmission protocol (T=0 or T=1) if
applicable
Unique serial number per card
List of applications on the card (abbreviations
are acceptable)
Card Image Number – (not applicable for
Reduced Sample testing for GP cards
supporting VIS 1.6.1 and VCPS 2.2)
The QR code label requirement is applicable to all Cross Testing and Performance Testing samples for
the following product form factors: ID1 Card, Micro Tag, Sticker, Mini Card, ID1 Card (Metal) and ID1
Card (dCVV2). The printed information detailed in section 2.6.3 is optional for Cross Testing and
Performance testing samples.
Each individual QR code label will contain and display the following information:
Vendors will receive a QR code label package with two files upon testing authorization. The number of
labels in each file is dependent on the quantity required for the card product. The package includes
following:
• The PNG file contains .PNG image files that are customizable according to the Vendor’s in-house
label printer requirements.
• The PDF file is a ready-to-print 8.5” x 11” label template with 1”x1” QR code labels.
• A sample QR code label package is attached with this announcement. Vendors may use both file
formats that are included for trial runs at their respective printing facility.
Vendors shall comply with the following requirements when using the QR code labels:
• Print the QR code on durable white matte or semi-gloss adhesive labels.
• Alternatively, Vendors can also print the QR code label directly on each sample.
• Transparent labels are not acceptable.
• For ID1 size cards:
o Place the QR code label on the back of the card as shown in Figure 1. Ideally, its
position should be right in the center, but we can accept displacement of up to
10mm.
o The size of the QR code should be between 18mm x 18 mm to 25mm x 25mm
Vendors can optionally generate their own QR codes and not use the labels provided during test
authorization as long as the additional requirements below are met.
• QR codes are consistent with the product information declared in the questionnaire
• QR fields are separated by a semi-colon
• Example: “LBTEST02345A;001;22_1152_v1;XT;A”
• QR image resolution should be at least 200 dpi.
• Serial numbering of the samples should follow the format as shown in Table 2–4.
• Use Arial font for the text around the QR code. Please choose a font size that is easy and clear
enough to read.
Serial Number
• ID1 Card
• Micro Tag Cross Testing 001 to 055 001 to 055
• Sticker
• Mini Card Performance Testing 056 to 067 056 to 064
•
Performance Testing Only 001 to 012 001 to 009
• ID1 Card
(Metal) Cross Testing 001 to 005 001 to 005
• ID1 Card
(dCVV2) Performance Testing 006 to 009 006 to 008
Vendors and Laboratories should contact Approval Service if there are any question related to the
personation.
Current test plans and test tools provide the opportunity to reduce the number of test samples
needed for a GlobalPlaffom chip card product’s approval test cycle. This approach is called Reduced
Sample testing.
Following are the eligibility requirements for using Reduced Sample Testing
• Platform must be compliant to GlobalPlatform version 2.1.1
• Platform must support dynamic JavaCard with garbage collection.
• Product must use Visa-developed VSDC applet or vendor -developed applet that supports:
o EMV Card Personalization Specification version 1.1
o VSDC Personalization Specification version 2.1 ( for VIS 1.6 & VCPS 2.2)
• Product must be developed to the following specifications:
o VIS 1.6 UL1
o VCPS2.2
For the specification- related criteria listed above, the version referenced is a minimum requirements (
ie more recent versions also qualify for eligibility).
If the product meets all of the above criteria, then the Reduced Sample testing approach can be used.
Instead of submitting a test sample image for each test case and the test plan, the card vendor may
submit test samples as follows:
• Provide 90 samples to Visa-recognized test lab for testing
• The card samples must have the Visa payment applet loaded
• The card samples must be in OP_SECURED state
• The card samples must be labeled according to the Chip Card Submission Requirements
document
VIS 1.6 UL1 and/or VCPS 2.2 products that do not meet eligibility requirements for Reduced Sample
testing must continue to submit test sample images as specified by the test plan. However, these
types of products still benefit from the personalization image scripts that are provided in XML format
(that are easily imported into card vendor personalization tools).
Note that test plans for earlier version of VIS and VCPS (such as the VIS 1.5.4b and VCPS 2.1.3b) will
continue to use the existing document-based approach for specifying personalization test images
Vendor Provides
Approval Services Lab Performs Lab Provides
Request for Approval Services Approval Services
Authorizes Testing Testing & Provides Report to Approval Passes Testing? Y Product Approved
Approval Form to Reviews Reports Issues Letter
at Laboratories Report to Vendor Services
Lab
Vendor Provides
Vendor Initiates Samples to
Product Failed
Brand Review Approval Services
for Archive
When functional testing is complete, the Laboratory will provide the Vendor with a report outlining
the test results. There are two possible outcomes from functional testing, pass or fail.
In the instance where a product fails testing, the Laboratory will send a report to the Vendor
identifying the reasons for the failures. If the Vendor intends to resubmit the product, the Vendor
must do the following:
• Correct the discrepancies
• Submit a new questionnaire to Approval Services
• Prepare new versions of the forms
• Contact the Laboratories for a new test date
• Provide new samples for testing
When a product passes testing, the Laboratory sends a final report to the Vendor.
The Vendor determines whether it wishes to submit the results of application testing to Visa. If so, the
Vendor completes and signs the Request for Approval form and submits it to the Laboratory, thus
authorizing the Laboratory to send an electronic copy of the results to Approval Services for review.
Test results should be submitted to Approval Services for evaluation within six months after testing
authorization date. Please contact Approval Services if testing cannot be completed with reports
submitted within this timeframe.
Visa will consider issuing a letter only for products that have successfully passed all testing at a
Laboratory and that support Visa-defined applications.
Upon successful completion of official testing, the product will appear on the Visa Approved Products
List located on both the Visa Technology Partner and Visa Digital Partner Services websites, unless
the Vendor requests otherwise. Publication of non-card products with static contactless chip is
managed through the Visa Ready program on the Visa Digital Partner website.
Note: Vendors are required to submit ten (10) cards for archiving, whether testing was performed or a
paper approval. The sample quantity and personalization are detailed in the table below
*If product
supports both
VCPS 2.1.3 and earlier.
Contactless Only 5 contact T=0/1,
VCPS Image 2000.
we require one
set per
VCPS 2.2 and above:
protocol.
VCPS image
(1) 6_33_C09_001 or
(2) 6_33_C03_001.
contact T=0/1,
we require one
set per
protocol.
When a product successfully passes all required testing, Approval Services will issue a Letter of
Approval
A Letter of Approval for a product submitted through the Visa Ready Program will be provided to the
vendor once all requirements of the program have been met. Contact [email protected] to obtain
the letter.
The term “approval” is being used generically in this section to mean either the issuance of an
approval letter or the issuance of a compliance letter.
Visa’s approval only applies to products that are identical to the product tested by Visa or one of
Visa’s recognized laboratories. A product may not be considered approved by Visa, nor promoted as
approved, if any aspect of the product is different from that which was tested by a laboratory or by
Visa, even if the product conforms to the basic product description contained in the letter of approval
or letter of compliance. For example, even though a product contains applications or operating
systems that have the same name or model number as those tested by one of Visa’s recognized
laboratories or by Visa, but the product is not identical to the features previously tested by one of
Visa’s recognized laboratories or by Visa, the product should not be considered or promoted as
approved by Visa.
Visa’s approval is granted solely in connection with a specific product and to the submitting vendor.
Such approval may not be assigned, transferred or sublicensed, either directly or indirectly, by
operation of law or otherwise. Only vendor(s) that receive a Visa approval for a product may state that
they have the approval.
No product manufacturer, chip supplier, 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 in part, approved any
aspect of a manufacturer, or supplier, 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 a letter
of approval or letter of compliance provided by Approval Services. All other references to Visa
approval are strictly and actively prohibited by Visa.
When granted, Visa approval is provided by Visa to ensure certain security and operational
characteristics important to Visa’s systems as a whole, but does not, under any circumstances, include
any endorsement or warranty regarding the functionality, quality or performance of any particular
product or service. Visa does not warrant any products or services provided by third parties. Approval
does not, under any circumstances, include or imply any product warranties from Visa, including,
without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement,
all of which are expressly disclaimed by Visa. All rights and remedies regarding products and services
which have received Visa approval shall be provided by the party providing such products or services,
and not by Visa. Unless otherwise agreed in writing by Visa, all property and services contemplated in
this document, which Visa provides to any third parties, are provided on an “as-is” basis, “with all
faults” and with no warranties whatsoever. Visa specifically disclaims any implied warranties of
merchantability, fitness for purpose or non-infringement.
The issuance of a letter of approval or letter of compliance is conditioned upon the vendor having
executed all necessary agreements, including without limitation, the applicable license agreements
with Visa, and shall be of no force and effect unless such agreements have been executed
contemporaneously with or prior to the issuance of the letter.
Visa performs limited testing to ascertain a product’s compliance with any required specifications and
may perform interoperability testing with other approved products. Visa’s limited testing program is
not designed to establish the functionality of an approved product in all potential conditions in which
it may be used. Visa’s approval does not in any circumstances include or imply any guarantees,
assurances or warranties that the approved product will operate in all possible settings or in
connection with any other approved product. Approval granted by Visa does not supersede additional
testing requirements as may be imposed by national testing bodies, financial institutions, network
services providers, Visa Region Specific Requirements or other customers.
The issuance of an approval or compliance letter does not provide an allowance of the card
construction per ISO 7810 & 7811-6, or the Visa Product Brand Standards, as required by Global
Design & Innovation (Brand). Information regarding this separate and required qualification process
can be found on the Visa Product Brand Standards website or by contacting
[email protected].
This section describes the card lifecycle management policy for cards and non-card products with a
static contactless chip.
The card lifecycle management policy applies to all products except for products based on the EMVCo
Common Payment Application and products approved prior to 1 January 2016. Those products will
continue to be governed under the existing renewal policy (see section 0).
Upon approval, the usage date assigned on the product’s letter will be based on the issue date of the
underlying IC Certificate from EMVCo. The current approval period is replaced with a usage period
covering the entire life of the product in the field. The usage date is defined as the IC Certificate issue
date + 12 years. The vendor may sell the product at any time during its usage period. If the product is
submitted on a newly certified IC, then the maximum usage date can approach twelve years. For
products submitted on older IC’s, the usage date timeframe will be shorter.
Base and derivative product submissions may be submitted during the IC’s certification period.
Products submitted as a base product will receive the usage date based on the underlying IC
Certificate. Derivative products are tied to the parent product’s usage date.
When the usage date of a product has been reached, the product will be removed from the Visa
Approved Products List the month following the usage end date.
The issuance of a letter by Approval Services does not provide an allowance of the card construction
per ISO 7810 & 7811-6, or review against the Visa Product Brand Standards, as required by Global
Design & Innovation (Brand). Information regarding this separate and required qualification process
can be found on the Visa Product Brand Standards website or by contacting
[email protected].
6.9 October 2016 Addition of content related to non-card products and inlays with a
static contactless chip.
6.5 December 2015 Cross-Testing Cards: Updated cross-testing cards and mailing
address
Cross-Testing: Added the performance testing card profiles
Added the Card Lifecycle Management policy
This appendix lists the testing requirements for products. Products have been grouped into four
categories
• Static native platforms (including Javacard-S)
• GlobalPlatform
• Inlays for non-card products with static contactless chip
• Non-card products with static contactless chip
Vendors that have received a letter from Approval Services identifying issues in the specification
deviation / comments sections may not use this process to make changes to a product. Vendors must
correct the issue(s) identified in the Letter before submitting the next version of the product for
testing.
Following forms must be completed, signed and provided to Approval Services if the vendor has not
executed a version of the ASTA that is May 2018 or later:
• Request for Approval
• Exhibit A
Contact Only
2 Full Electrical (on N/A Full (on one N/A IAL Both contact
one protocol) protocol)) protocol
supported
Full Protocol (T=0 VIS Transaction (on
and T=1) the other protocol )
Contactless Only
Dual Interface
5 Full Electrical (on Full Full (On one Full IAL Both contact
one protocol) protocol)) protocol
supported
Full Protocol (T=0 VIS/VCPS Transaction
and T=1 (on the other
protocol )
Below is a list of acceptable changes for a Static Native Base Product. The list below is not exhaustive,
but provides examples of commonly submitted change requests. If a Vendor wants to make a change
that is not listed below, they should contact Approval Services to determine which process the Vendor
may utilize. Changes to the ROM mask are treated as a base product.
14 L1 Firmware Full Full Digital VIS and VCPS Selected IAL Dual interface L2
Protocol Transactions components not
affected
23 Add Contact Full Full Analog Full VIS None IAL* or *If contact interface
Plate None** was not in scope in
base product or if
any change in
firmware/software
**Otherwise, no
need for IAL
The list in this section defines the base product requirements for products submitted on a GP
platform. GlobalPlatform manages the platform functional testing for GP platforms. Visa no longer
offer testing for Visa GlobalPlatform. Refer to the GlobalPlatform web site to understand its process.
Contact Only
Contactless Only
Dual Interface
Below is a list of acceptable changes for a GP Base Product. The list below is not exhaustive, but
provides examples of commonly submitted change requests. If a Vendor wants to make a change that
is not listed below, it should contact Approval Services to determine which process the Vendor may
utilize. Changes to the ROM mask will require full functional testing.
15 Add Contact Full Full Analog VCPS None IAL** or *Full contact
Plate Transaction None*** platform testing
required.
VIS
Transaction **If contact
interface was
*Full VIS if
not in scope in
not Visa
base product or
applet
if any change in
firmware/softwa
re
***Otherwise, no
need for IAL
Below is a list of acceptable changes for an inlay. The list below is not exhaustive, but provides
examples of commonly submitted change requests. If a Vendor wants to make a change that is not
listed below, it should contact Approval Services to determine which process the Vendor may utilize.
Static Native or GlobalPlatform Platform, Contactless Only – leveraging from an approved card product
Below is a list of acceptable changes/derivatives to a base product. The list below is not exhaustive,
but provides examples of commonly submitted change requests. If a Vendor wants to make a change
that is not listed below, it should contact Approval Services to determine which process the Vendor
may utilize.
5 Size and/or Full Analog VCPS Full None Change impacts thickness
Shape of Transaction or distance of antenna
Product from surface.
Testing dependent on
differences.
Contact Only
Contactless Only
Dual Interface
This section defines the testing requirements for VBSS compliant products and it’s derivatives. The list
below is not exhaustive. If a Vendor wants to make a change that is not listed below, they should
contact Approval Services.
4 Contactless Full Full Digital Full VBSS ISO Analog IAL Dual interface
Type Protocol Timing product
Performance
5 Contactless None Full Digital Full VBSS ISO Analog IAL Contactless only
Type Timing product
Performance
7 VCPS None None Full VBSS ISO Analog IAL Level 1 components
Application Timing not affected
Change Performance
9 Contactless None Full Digital Full VBSS ISO Analog IAL Level 2 components
L1 Firmware Timing not affected.
Performance Contactless Only
10 L1 Firmware Full Full Digital Full VBSS ISO Analog IAL Dual interface L2
Protocol Timing components not
Performance affected
12 Antenna / None Full Analog Full VBSS * Sensor None size or shape,
Inlay characteristic material,
s on Card + connection
ISO Analog technology, layout
Timing changes
Performance.
Full if
noticeable
difference on
sensor
characteristic
on Card.
13 Chip None None* or Full Full VBSS * Sensor None Dual Interface
Module Analog characteristic product or
s on Card + Contactless only
ISO Analog product
Timing
*None if 8/6 pin
Performance.
change only
Full if
noticeable
difference on
sensor
characteristic.
17 Add Contact Full Full Analog Full VBSS Sensor IAL* or *If contact interface
Plate characteristic None** was not in scope in
s on Card> base product or if
Full if any change in
noticeable firmware/software
difference
**Otherwise, no
need for IAL
18 Add None Full Full VBSS Full VBSS IAL* or *If contactless
Antenna None** interface was not in
scope in base
product or if any
change in
firmware/software
**Otherwise, no
need for IAL
22 Sensor None None Full VBSS Full VBSS IAL* or *If with changes in
change or Sensor test None** any component
modification firmware/SW
(including
coating) **If purely physical
change
23 Enrollment None None Full VBSS Full VBSS IAL* or *If with changes in
Sensor (if Sensor test None** any component
different firmware/SW
from Sensor
from VBSS **If purely physical
product) change
Probably
not
accepted /
Tending to
disappear
due to lack
of
acceptance
and
potentially
poor results
24 Any None None Full VBSS Sensor IAL* or *If with changes in
Hardware characteristic None** any component
change of s on Card > firmware/SW
the card Full if
product not noticeable **If purely physical
listed difference change
previously
Product Manufacturer The entity that offers the final tested and
approved product to the financial institution.