3-D Secure ICS Form - Instruction Manual

EMV® 3-D Secure Approval ICS Form - Instruction Manual Version 1.12 May 2026 © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Legal Notice Page ii / viii This document is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or noninfringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Revision Log – Version 1.12 Page iii / viii The following changes have been made to the document since the publication of Version 1.11. Some of the numbering and cross references in this version have been updated to reflect changes introduced by the published bulletins. The numbering of existing requirements did not change, unless explicitly stated otherwise. Incorporated changes described in the following Document Updates: • Support of ICS 1.12. Other editorial changes: • Editorial updates. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Contents Page iv / viii 1 INTRODUCTION................................................................................................................... 1 Purpose..................................................................................................................... 1 Audience ................................................................................................................... 1 Background ............................................................................................................... 1 Normative References ............................................................................................... 2 Definitions ................................................................................................................. 3 Notational Conventions ............................................................................................. 5 Abbreviations................................................................................................. 5 Terminology and Conventions ....................................................................... 5 2 PART I - ADMINISTRATIVE .................................................................................................. 6 Product Provider Identification ................................................................................... 6 Product Provider - Company Legal Name ..................................................... 6 Product Provider – EMVCo Registration Number .......................................... 6 Laboratory Identification ............................................................................................ 7 Laboratory – Company Legal Name .............................................................. 7 Laboratory – EMVCo Registration Number.................................................... 7 ICS Submission Type ................................................................................................ 8 ICS Submission Type .................................................................................... 8 EMVCo Letter of Approval ............................................................................. 8 ICS Replacement .......................................................................................... 8 ICS Replacement – Previous ICS reference Number .................................... 9 ICS Replacement – Reason for ICS Replacement ........................................ 9 ICS Replacement – ICS Replacement Details ............................................... 9 3 PART II - SUBMITTED COMPONENT AND SPECIFICATION VERSION ...................................... 10 3DS Component Type ............................................................................................. 10 Letter of Approval Requested (3DS Protocol Version) ............................................. 11 Specification Bulletins Supported by the Product..................................................... 11 Device Information Supported ................................................................................. 12 Laboratory Reserved Section .................................................................................. 12 Product Provider Details .......................................................................................... 12 Product Provider Details – Person Name .................................................... 12 Product Provider Details - Comments.......................................................... 12 4 PART IIIA – 3DS SDK COMPONENT ................................................................................. 13 3DS SDK Component Identification ......................................................................... 13 3DS SDK Name .......................................................................................... 13 © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page v / viii 3DS SDK Version ........................................................................................ 13 3DS SDK Build Number .............................................................................. 13 3DS SDK Operating System........................................................................ 14 3DS SDK Operating System Version Tested ............................................... 14 3DS SDK Supported Operating System Versions........................................ 14 Eligibility for Regression Testing on Protocol 2.2.0 ...................................... 15 Eligibility for Regression Testing on Protocol 2.3.1 ...................................... 15 Reference Number of the expiring 3DS SDK LOA ....................................... 17 3DS SDK Reference/Requestor Application Usage ..................................... 17 3DS SDK Reference/Requestor Application Change................................... 17 3DS SDK Reference/Requestor Application Change Details ....................... 17 3DS SDK Component Features............................................................................... 18 Platform Provider Specific ........................................................................... 18 Trust List Implementation ............................................................................ 18 3DS SDK Component Options ................................................................................ 19 Supported Device User Interface Mode(s) ................................................... 19 Type of Device Parameters ......................................................................... 19 5 PART IIIB – SPLIT-SDK COMPONENT ............................................................................... 20 Split-SDK Component Identification......................................................................... 20 Split-SDK Name .......................................................................................... 20 Split-SDK Version........................................................................................ 20 Split-SDK Client Component Identification............................................................... 20 Split-SDK Client Version.............................................................................. 20 Split-SDK Client Build Number .................................................................... 20 Split-SDK Client Operating System ............................................................. 21 Split-SDK Client Operating System Version Tested..................................... 21 Split-SDK Client Supported Operating System Versions ............................. 21 Eligibility for Regression Testing on Protocol 2.2.0 ...................................... 22 Eligibility for Regression Testing on Protocol 2.3.1 ...................................... 22 Reference Number of the expiring 3DS Split-SDK LOA............................... 24 Split-SDK Client Reference/Requestor Application Usage........................... 24 Split-SDK Client Reference/Requestor Application Change......................... 24 Split-SDK Client Reference/Requestor Application Change Details ............. 25 Split-SDK Client Component Features..................................................................... 25 Platform Provider Specific ........................................................................... 25 Trust List Implementation ............................................................................ 26 Split-SDK Client Component Options ...................................................................... 26 © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page vi / viii Supported Device User Interface Mode(s) ................................................... 26 Type of Device Parameters ......................................................................... 26 Split-SDK Server Component Identification ............................................................. 26 Split-SDK Server Version ............................................................................ 26 Split-SDK Server Build Number ................................................................... 27 Split-SDK Server Operating System Name or Virtual Machine Name .......... 27 Split-SDK Server Operating System Version or Virtual Machine Version Tested 27 Name of the Underlying Operating System.................................................. 27 6 PART IIIC – 3DS SERVER COMPONENT ............................................................................ 28 3DS Server Component Identification...................................................................... 28 3DS Server Name ....................................................................................... 28 3DS Server Version..................................................................................... 28 3DS Server Build Number ........................................................................... 28 3DS Server Operating System Name or Virtual Machine Name .................. 29 3DS Server Operating System Version or Virtual Machine Version Tested . 29 Name of the Underlying Operating System.................................................. 29 Eligibility for Regression Testing on Protocol 2.2.0 ...................................... 30 Eligibility for Regression Testing on Protocol 2.3.1 ...................................... 30 Reference Number of the expiring 3DS Server LOA.................................... 31 7 PART IIID – DIRECTORY SERVER COMPONENT ................................................................. 32 Directory Server Component Identification .............................................................. 32 Directory Server Name ................................................................................ 32 Directory Server Version ............................................................................. 32 Directory Server Build Number .................................................................... 32 Directory Server Operating System or Virtual Machine ................................ 33 Directory Server Operating System Version or Virtual Machine Version Tested 33 Name of the Underlying Operating System.................................................. 33 Eligibility for Regression Testing on Protocol 2.2.0 ...................................... 34 Eligibility for Regression Testing on Protocol 2.3.1 ...................................... 34 Reference Number of the expiring Directory Server LOA ............................ 35 Directory Server Component Options ...................................................................... 35 Card Range Data File Download ................................................................. 35 Partial Cache Update .................................................................................. 36 Card Security Code ..................................................................................... 36 DS able to Create the ARes Message on the ACS’s Behalf......................... 36 © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page vii / viii Split-SDK Server Signature algorithm supported ......................................... 37 OReq/Ores Messages supported ................................................................ 37 8 PART IIIE – ACCESS CONTROL SERVER COMPONENT ....................................................... 38 Access Control Server Component Identification ..................................................... 38 Access Control Server Name ...................................................................... 38 Access Control Server Version .................................................................... 38 Access Control Server Build Number .......................................................... 38 Access Control Server Operating System or Virtual Machine ...................... 39 Access Control Server Operating System Version or Virtual Machine Version Tested 39 Name of the underlying Operating System .................................................. 39 Eligibility for Regression Testing on Protocol 2.2.0 ...................................... 40 Eligibility for Regression Testing on Protocol 2.3.1 ...................................... 40 Reference Number of the expiring ACS LOA............................................... 41 Access Control Server Component Options ............................................................ 42 Native UI Fields ........................................................................................... 42 HTML UI Fields ........................................................................................... 42 9 PART IV – MESSAGE EXTENSIONS TO TEST...................................................................... 43 Bridging Message Extension 2.0 ................................................................. 43 10 PART V – DIGITAL SIGNATURES ....................................................................................... 44 Digital Signature ...................................................................................................... 44 Test Laboratory Comments ......................................................................... 44 Test Laboratory Signature ........................................................................... 44 EMVCo Signature........................................................................................ 44 © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Tables Page viii / viii Table 1.1: 3-D Secure Specifications ................................................................................... 2 Table 1.2: 3-D Secure Approval Documents ........................................................................ 2 Table 1.3: 3-D Secure Approval Forms ................................................................................ 2 Table 1.4: Definitions ........................................................................................................... 3 Table 1.5: Abbreviations ....................................................................................................... 5 © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 1 Introduction Page 1 / 38 Purpose According to the 3DS Approval Process, a completed Implementation Conformance Statement (ICS) or ICS data has to be provided by a 3DS Product Provider to its Test Laboratory to enter the Compliance Testing phase. This manual has to be used in conjunction with the 3-D Secure ICS Version 1.12 Note: In case a new ICS version is released without update of this manual, then the changes in the ICS take precedence over the information in this document. Audience The audience for this manual is the 3DS Product Providers who will use it when filling the ICS form. Background • The ICS is a form that is presented in PDF format (.pdf). • Compliance Testing shall not begin until the ICS is approved by EMVCo. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Normative References Page 2 / 38 Ref. [PCF 3DS] [SDK 3DS] [SPL 3DS] [3DS BME] [SB 3DS] [SB 3DS 255] [DEV 3DS] [VER 3DS] Table 1.1: 3-D Secure Specifications Document Title Version EMV® 3-D Secure Protocol and Core All active Functions Specification versions EMV® 3-D Secure SDK Specification All active versions EMV® 3-D Specification Secure Split-SDK Latest available EMV® 3-D Secure Bridging Message 2.0 or higher Extension EMV® 3-D Secure Specification All Bulletins (SB Bulletins) EMV® 3-D Secure Bulletin 255 – 3DS Version Configuration Specification Specification Latest available EMV® 3-D Secure SDK Device All active Information versions EMV® 3DS Version Number Management - Protocol Version 2.3.0 & above Latest available Distribution Publicly available Publicly available Publicly available Publicly available Publicly available Publicly available Publicly available Publicly available Ref. [AP 3DS] Table 1.2: 3-D Secure Approval Documents Document Title Version EMV® 3-D Secure Approval - Latest available Administrative Process Distribution Publicly available Ref. [ICS 3DS] Table 1.3: 3-D Secure Approval Forms Document Title Version 3-D Secure - Implementation 1.9b Conformance Statement Distribution Publicly available © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Definitions Table 1.4 defines selected terms used in this document. Page 3 / 38 Table 1.4: Definitions Term 3DS Component Active Protocol Compliance Testing Definition A 3-D Secure Component that will be approved. There are four 3DS components: • 3DS SDK or Default-SDK • 3DS Server • Directory Server (DS) • Access Control Server (ACS) The list of the active Protocol Versions is provided in the latest 3DS Specification Bulletin 255 [SB 3DS 255]. The execution by a Test Platform of a defined set of tests against requirements described in a specification to determine official compliance with that specification. EMVCo The organization that manages the EMV Specifications and their related testing processes. EMVCo Recognised Laboratory (or Test Laboratory or Laboratory) An independent, impartial entity that has been audited by an EMVCo Qualified Auditor for compliance with the requirements outlined in this document and has received a Letter of Recognition from EMVCo, entitling it to perform 3-D testing and test report validation. EMVCo 3DS Approval Secretariat The EMVCo entity that manages the 3-D Secure Approval process defined in [AP 3DS] and related documents. Contact: 3ds_approval@emvco.com. Major Refactoring Significant software update to the product while supporting the same functional features. It can be for instance porting the software to another development language or using new libraries to implement the same functionalities. If you have questions as to whether a change constitutes Major Refactoring, please contact the EMVCo 3DS Secretariat at 3ds_approval@emvco.com. Multi-Protocol Version Support 3DS components are required to support all active protocol versions as defined in [PCF 3DS] Requirement 311 and in the latest 3DS Specification Bulletin 255 [SB 3DS 255]. This rule is applied in Compliance testing to include the highest protocol version selected and all lessor active protocol versions. Pre-Compliance testing An approval process test phase where Product Providers can access the same defined set of Compliance tests allowing debug, analysis and review of the compliance with that specification. Product A 3-D Secure component submitted for approval © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 4 / 38 Term Product Provider Protocol Version Specification Bulletin System Under Test Test Case Test Plan Test Platform (or 3DS Test Platform) Test Platform Provider Definition Entity submitting a 3-D Secure component for approval. Protocol Version defines the interoperability between the 3DS Secure components. Protocol Version format is MAJOR.MINOR.PATCH and it is defined in [VER 3DS] Notification released to communicate updates to the EMV specifications. The 3-D Secure Component (may include hardware with identified Operating System) that is being evaluated for its compliance with EMVCo specification and for receipt of LOA. A description of the actions required to achieve a specific test objective. Specification describing all Test Cases that have to be run to verify the compliance of a 3DS component to a version of 3DS Secure protocol and Core Functions Specification and 3DS Secure SDK Specification. An online test system that has been EMVCo recognised for 3DS testing. The Test Platform executes 3-D Secure test plans and test cases which SUTs use for 3DS compliance approval. Entity developing and hosting the Test Platform, in accordance with EMV Test requirements. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Notational Conventions Abbreviations The abbreviations listed in Table 1.5 are used in this document. Abbreviation 3DS ACS BME ICS LOA OS SDK UI Table 1.5: Abbreviations Description EMV® 3-D Secure Access Control Server Bridging Message Extension Implementation Conformance Statement Letter Of Approval Operating System Software Development Kit User Interface Page 5 / 38 Terminology and Conventions • Fields marked “M” are mandatory and must be provided in the ICS form. • Fields marked “C” are conditional and should be completed per the instructions provided. • Fields marked “O” are optional and may be completed. For each field of the ICS form described in this document, the section Instructions indicates how the field shall be completed. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 6 / 38 2 PART I - Administrative Usage Part I is completed by the Product Provider except the section related to the Laboratory Identification (section 2.2 hereafter). Product Provider Identification Product Provider - Company Legal Name M Company Legal Name Instructions • The Product Provider indicates its company name. It must be identical to the company name that is registered with EMVCo and linked to the issued EMVCo registration number. • If the company name has changed, the Product Provider must submit a formal change of name request to the EMVCo 3DS Approval Secretariat (3DS_approval@emvco.com). Product Provider – EMVCo Registration Number M EMVCo Registration Number Instructions • The Product Provider indicates its EMVCo Registration Number that is issued by EMVCo at the time the Product Provider registered for 3DS. • If the Product Provider is not registered yet, it has to do so by filling and sending a completed 3DS Registration Form to the EMVCo 3DS Approval Secretariat. • The form is available on the EMVCo website (https://www.emvco.com/product-providerregistration/) © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 7 / 38 Laboratory Identification Laboratory – Company Legal Name M Company Legal Name Instructions • The Test Laboratory shall fill Company Legal Name. The name provided must be identical to the Laboratory name that is registered with EMVCo and linked to the issued EMVCo Laboratory Registration Number. Laboratory – EMVCo Registration Number M EMVCo Registration Number . Instructions • The Test Laboratory shall fill EMVCo Registration Number and the number provided must be identical to the Registration Number issued by EMVCo at the time Laboratory registered for 3DS Laboratory recognition. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 8 / 38 ICS Submission Type ICS Submission Type M Select submission type “Initial” or “Add Message Extension” Instructions The Product Provider can select “Initial” or “Add Message Extension” in this version of ICS. • “Initial” applies when: o It is the first time the Product is submitted for approval and does not have an LOA yet. o The LOA of a Product has expired and a new version of the Product has to be submitted for approval. o A Product Provider wants to make major change(s) to an existing Product with LOA. • “Add Message Extension” applies when a Product Provider requests a LOA update to add testing of the Bridging Message Extension (BME) to a Product that already has a valid LOA. EMVCo Letter of Approval C For any submission except “Initial”, please provide the EMVCo Letter of Approval reference number of the previously approved product: Instructions • This field shall only be completed if “Submission Type” = “Add Message Extension”. • The Product Provider indicates the LOA Reference number of the approved LOA that will be updated to indicate the testing BME. ICS Replacement M Is this ICS a replacement of a previously “Yes” or “No” accepted ICS? Instructions • The Product Provider selects “No”, if this is the first submission of the ICS to EMVCo for this Product. • The Product Provider selects “Yes”, if an ICS for this Product has already been submitted and approved by EMVCo (ICS replacement). See Section 2.5.3 in 3DS Approval Administrative Process document. NOTE: ICS replacement can be used for both administrative or functional updates. See Section 2.5.3 in 3DS Approval Administrative Process document. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 9 / 38 ICS Replacement – Previous ICS reference Number C Previous ICS Reference number Instructions • This field shall only be completed if “Replacement” = “Yes”. • The Product Provider indicates the ICS Reference number of the previously approved ICS. ICS Replacement – Reason for ICS Replacement C Reason for ICS replacement “Administrative” or “Functional” Instructions • This field shall only be completed if “Replacement” = “Yes”. • The Product Provider selects “ADMINISTRATIVE” if the replacement is due to an administrative change like the name of the Product or a typo in one of the different fields in the ICS. • The Product Provider selects “FUNCTIONAL”, if the replacement is due to a change made on the Product or the system under test resulting in updated feature and new Product build number or Product version. ICS Replacement – ICS Replacement Details C ICS replacement details Instructions • This field shall only be completed if “Replacement” = “Yes”. • The Product Provider provides detailed information on the reason why the ICS had to be replaced. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 10 / 38 3 PART II - Submitted Component and Specification Version Usage Part II is completed by the Product Provider except for the Laboratory reserved section Identification (section 3.5 hereafter). 3DS Component Type M 3DS SDK (applicable for 3DS Specification “Yes” or “No” 2.2.0) or Default-SDK (applicable for 3DS Specification 2.3.1.x) M Split-SDK/Native (applicable for 3DS Standard Limited Specification 2.3.1.x): “Yes” or “Yes” or “No” “No” M Split-SDK/Shell (applicable for 3DS “Yes” or “No” Specification 2.3.1.x): M Split-SDK/Browser (applicable for 3DS “Yes” or “No” Specification 2.3.1.x): M 3DS Server (3DSS) “Yes” or “No” M Directory Server (DS) “Yes” or “No” M Access Control Server (ACS) “Yes” or “No” Instructions: • The Product Provider selects “Yes“ in the row indicating the component submitted for Compliance Testing. • For all the other rows, the Product Provider selects “No”. • For Split-SDK/Native variant, the Product Provider also selects if it is a Standard implementation or a Limited implementation (only one applies). NOTE: an ICS can only document one single 3DS Component at a time. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 11 / 38 Letter of Approval Requested (3DS Protocol Version) M Select version of LOA: “2.2.0” or “2.3.1” Instructions: • The Product Provider shall select the 3DS Protocol Version for which he wants to obtain a LOA for its Product. For this version of ICS, LOA 2.2.0 and LOA 2.3.1 can be requested. • The Product Provider shall verify with its Laboratory or Test Platform Provider that the requested Protocol Version is activated on the Test Platform for the selected component. NOTE: • Per the 3DS requirement, o a Product that obtains a LOA for 3DS Protocol Version 2.3.1, shall also comply with 3DS Protocol Versions 2.2.0. Specification Bulletins Supported by the Product M Specification Bulletin(s) and Version(s) • Example supported: Note: to be completed whatever LOA Bulletin Version version is requested 214 3 222 1 Instructions: • The Product Provider indicates all 3DS specification bulletins supported by the Product. • Only one bulletin and version shall be listed per row. • Any 3DS component submitted for approval 2.2.0 or 2.3.1 (including 3DS SDK or DefaultSDK component) shall comply with all active specification bulletins (except if the specification bulletin is associated to a Product option that is not supported or is specific to a component that is not the one submitted. In this case, the specification bulletin does not have to be listed). NOTES: • Specification bulletin version numbers are assumed to incorporate or supersede all prior bulletin versions, unless explicitly stated otherwise. Consequently, only the latest applicable version needs to be listed. • There can be more than one specification bulletin active at a given time for the Core specification or the 3DS SDK specification. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 12 / 38 Device Information Supported C Supported Data Version Number(s) • Example 1.1 1.3 1.4 1.5 1.6 Instructions: • This field shall only be completed if 3DS SDK component, Default-SDK component, SplitSDK component or ACS component is selected (see section 3.1 – Component Type). • If the Product is an ACS, the Product Provider indicates all active Data Version Numbers supported by the Product. • If the Product is a 3DS SDK, a Default-SDK or a Split-SDK, the Product Provider indicates the Data Version Number supported by the Product. Only Data Version Number(s) defined as “active” in the latest 3DS Specification Bulletin 255 [SB 3DS 255] shall be listed. Laboratory Reserved Section O Project ID Instructions: • This field may be used by the Test Laboratory to document its internal project reference. Product Provider Details Product Provider Details – Person Name M Contact name of the person who completed the ICS Instructions: • The Product Provider indicates the First Name and Last Name of the person who completed the ICS. Product Provider Details - Comments O Comments Instructions: • The Product Provider or the Test Laboratory may use this field to provide additional information. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 13 / 38 4 PART IIIa – 3DS SDK Component Usage • The Part IIIa is completed by the Product Provider. • It shall only be completed if the selected Component is a 3DS SDK or a Default-SDK (First Component in Section 3.1 is ticked). If not, the Product Provider leaves this part empty. 3DS SDK Component Identification 3DS SDK Name C 3DS SDK Name: Instructions: • The Product Provider indicates the commercial name of its 3DS SDK or Default-SDK product. • This name will be published on the EMVCo web site and documented in the LOA (It is recommended to include the target OS in the 3DS SDK or Default-SDK Name so that a clear distinction can be made on the web site between 3DS SDKs) 3DS SDK Version C 3DS SDK Version: Instructions: • The Product Provider indicates the version of its 3DS SDK or Default-SDK Product. • This version will be published on the EMVCo web site and documented in the LOA. 3DS SDK Build Number C 3DS SDK Build Number Instructions: • The Product Provider indicates the Build Number of its tested 3DS SDK or Default-SDK Product. • Format of the build number is at the discretion of the Product Provider. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 14 / 38 3DS SDK Operating System C Name of the Operating System used for testing the 3DS SDK: Instructions: • The Product Provider indicates the name of the Operating System used for testing the 3DS SDK or Default-SDK Product. • This Operating System Name will be documented in the LOA. • Only one OS Name shall be listed. If several OS are supported by the 3DS SDK or DefaultSDK Product, different ICS shall be submitted and distinct LOAs will be granted. 3DS SDK Operating System Version Tested C Version of the Operating System used for testing the 3DS SDK: Instructions: • The Product Provider indicates the version of the Operating System used for testing the 3DS SDK or Default-SDK Product (only the OS Version used for testing shall be listed). • This Operating System Version will be documented in the LOA. 3DS SDK Supported Operating System Versions C Operating System Version(s) able to support the 3DS SDK: Instructions: • The Product Provider lists all versions of the tested Operating System supported by the 3DS SDK or Default-SDK Product. • At minimum the OS version tested during the Compliance Testing shall be listed. • All supported versions shall be separated by a space character. For example: o For a SDK supporting iOS10, iOS11, iOS12, iOS13, iOS14, iOS15, iOS16 and iOS17 the field will be completed with: “10 11 12 13 14 15 16 17”. o For a SDK supporting Android 5, Android 6, Android 7, Android 8, Android 9, Android 10, Android 11 and Android 12 the field will be completed with: “5 6 7 8 9 10 11 12”. • All supported versions of the Operating System will be documented in the LOA. NOTE: Only one version of the Operating System is tested. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 15 / 38 Eligibility for Regression Testing on Protocol 2.2.0 C Is a previous version of this 3DS SDK product “Yes” or “No” already approved (i.e. expiring LOA) - for 2.2.0 or 2.3.1 protocol, - for the same Operating System, - for the same or lower Operating System Version, - for the same 3DS SDK Component options and features, - and for the same Message Extensions tested (if supported)? Instructions: • The Product Provider shall not complete this field if the submission type of this ICS is “Add Message Extension” (See section 2.3.1) or if the Protocol Version is not 2.3.1 (See section 3.2) • The Product Provider selects “Yes“ if o The submission type of this ICS is “Initial” (See section 2.3.1), o The Protocol Version is 2.3.1 (See section 3.2), o A previous version of this 3DS SDK component has already been approved for 2.2.0 or 2.3.1 protocol, o The LOA of the previous 3DS SDK component has not expired yet, o The previously approved 3DS SDK component supported the same Operating System (See Section 4.1.4), o The previously approved 3DS SDK component supported the same Operating System Version or lower (See Section 4.1.5), o The previously approved 3DS SDK component supported the same 3DS SDK Component options and features (See Sections 4.2 and 4.3), o The previously approved 3DS SDK component was tested for the same Message Extensions (if supported). See section 9. • The Product Provider selects “No“ otherwise. Eligibility for Regression Testing on Protocol 2.3.1 C Is “Yes” or “No” - answer to previous question =Yes? - expiring SDK supporting protocol version 2.3.1? - UI implementation the same as in the expiring SDK? - do you confirm that submitted SDK has not undergone any Major Refactoring? © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 16 / 38 Note: If the response to this question is Yes and the product provider wants to benefit from the regression testing on protocol 2.3.1 for its SDK, an attestation that the UI implementation has not changed and that the SDK did not undergo any Major Refactoring has to be signed and provided to EMVCo no later than RFA submission. Attestation template can be downloaded from EMVCo website. Instructions: • The Product Provider shall not complete this field if the submission type of this ICS is “Add Message Extension” (See section 2.3.1) or if the Protocol Version is not 2.3.1 (See section 3.2) • The Product Provider selects “Yes“ if o The submission type of this ICS is “Initial” (See section 2.3.1), o The Protocol Version is 2.3.1 (See section 3.2), o A previous version of this 3DS SDK component has already been approved for 2.3.1 protocol, • UI implementation has not changed compared to previous 3DS SDK component. Note that changes made on font, colour, size or boldness of text or on size or shape of logos are not considered as UI implementation changes in the context of this bulletin. For more details on acceptable UI changes, please contact EMVCo 3DS Secretariat at 3DS_approval@emvco.com, o The SDK has not undergone any Major Refactoring, o The LOA of the previous 3DS SDK component has not expired yet, o The previously approved 3DS SDK component supported the same Operating System (See Section 4.1.4), o The previously approved 3DS SDK component supported the same Operating System Version or lower (See Section 4.1.5), o The previously approved 3DS SDK component supported the same 3DS SDK Component options and features (See Sections 4.2 and 4.3), o The previously approved 3DS SDK component was tested for the same Message Extensions (if supported). See section 9. If the response to this question is “Yes“, an attestation that the UI implementation has not changed and that and that the SDK did not undergo any Major Refactoring has to be signed and provided to EMVCo. Attestation template can be downloaded from EMVCo website or requested to EMVCo 3DS Secretariat at 3DS_approval@emvco.com. • The Product Provider selects “No“ otherwise. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 17 / 38 Reference Number of the expiring 3DS SDK LOA C What is the Reference Number of the expiring 3DS SDK LOA? Instructions • If the response to the question 4.1.7 and/or 4.1.8 is “Yes”, please document the (expiring) LOA Reference number of the approved product that is being re-approved. 3DS SDK Reference/Requestor Application Usage C Are you using the Reference/Requestor “Yes” or “No” Application provided by the Test Platform Provider for the 3DS SDK testing? Instructions: • The Product Provider indicates if it is using the Reference/Requestor Application provided by the Test Platform Provider for the 3DS SDK or Default-SDK testing. • If the Product Provider is not using the Test Platform Provider Reference/Requestor Application (the response to question 4.1.10 is “No”), o Before entering the Compliance phase, the Product Provider shall provide an attestation to the Test Laboratory that the Reference/Requestor Application used does not impact the functional compliance as described in the applicable 3DS specifications. o EMVCo reserves the right to request code review of the Reference/Requestor Application 3DS SDK Reference/Requestor Application Change C In case you are using the Test Platform “Yes” or “No” Provider Reference/Requestor Application, did you make any change to this Application? Instructions: • If the answer to previous question 4.1.9 is “Yes”, the Product Provider indicates if he has modified the Test Platform Provider Reference/Requestor Application. • If the Product Provider has modified the Test Platform Provider Reference/Requestor Application (the response to question 4.1.10 is “Yes”), o Before entering the Compliance phase, the Product Provider shall provide an attestation to the Test Laboratory that the Reference/Requestor Application used does not impact the functional compliance as described in the applicable 3DS specifications. o EMVCo reserves the right to request code review of the Reference/Requestor Application. 3DS SDK Reference/Requestor Application Change Details C If yes is answered at the previous question, please provide high level description of the changes © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 18 / 38 Instructions: • If the Product Provider has modified the Test Platform Provider Reference/Requestor Application (the response to question 4.1.10 is “Yes”), the Product Provider documents the changes made to the Test Platform Provider Reference/Requestor Application (high level description). 3DS SDK Component Features Platform Provider Specific C 3DS SDK is Platform Provider specific (e.g. “Yes” or “No” gaming console, set top box, e-reader,…) Instructions: • The Product Provider indicates if the 3DS SDK or Default-SDK is Platform Provider specific (e.g. gaming console, set top box, e-reader, …). NOTE: Platform Provider specific refers to the 3DS SDKs or Default-SDKs that utilize the Platform Provider-specific Parameters. 4.2.1.1 OOB Authentication App on the Same Device as the Merchant App C Does the platform support an OOB “Yes” or “No” authentication app on the same device as the merchant app? Instructions: • If the answer to previous question 4.2.1 is “Yes”, the Product Provider indicates if the platform supports an OOB authentication app on the same device as the merchant app. 4.2.1.2 Cancel Action Implemented as a Controller Function C Is Cancel Action implemented as a function on “Yes” or “No” an external controller for the platform (e.g. gaming console controller, TV remote controller,…)? Instructions: • If the answer to question 4.2.1 is “Yes”, the Product Provider indicates if Cancel Action implemented as a function on an external controller for the platform. Trust List Implementation C Trust List implementation Instructions: • The Product Provider describes his Trust List implementation for the 3DS SDK or DefaultSDK Product. For example it may be a “CheckBox” or a “Toggle” or other implementation. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 19 / 38 3DS SDK Component Options Supported Device User Interface Mode(s) C Supported Device User Interface Mode(s) (of  Portrait the target merchant application):  Landscape Instructions: • The Product Provider indicates which Device User Interface Mode(s) are supported by the target merchant application. NOTE: For rotatable devices like mobile phones, both orientation options shall be selected in the ICS and each orientation will be tested. Type of Device Parameters C Type of Device Parameters included in the “Android“ or “iOS“ or “Platform Device Information Provider (e.g. OS for gaming consoles)” Instructions: • The Product Provider indicates which type of Device Parameter is supported by the 3DS SDK or Default-SDK Product. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 20 / 38 5 PART IIIb – Split-SDK Component Usage • The Part IIIb is completed by the Product Provider. • It shall only be completed if the selected Component is a Split-SDK (Second, Third or Fourth Component in Section 3.1 is ticked). If not, the Product Provider leaves this part empty. Split-SDK Component Identification Split-SDK Name C Split-SDK Name: Instructions: • The Product Provider indicates the commercial name of its Split-SDK Product. • This name will be published on the EMVCo web site and documented in the LOA Split-SDK Version C Split-SDK Version: Instructions: • The Product Provider indicates the version of its Split-SDK Product. • This version will be published on the EMVCo web site and documented in the LOA Split-SDK Client Component Identification Split-SDK Client Version C Split-SDK Client Version: Instructions: • The Product Provider indicates the version of its Split-SDK Client. • If there is not a specific versioning for the client part, the Split-SDK Version (see 5.1.2) can be duplicated in this cell. Split-SDK Client Build Number C Split-SDK Client Build Number Instructions: • The Product Provider indicates the Build Number of its tested Split-SDK Client. • Format of the build number is at the discretion of the Product Provider. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 21 / 38 Split-SDK Client Operating System C Name of the Operating System used for testing the Split-SDK Client: Instructions: • The Product Provider indicates the name of the Operating System used for testing the Split-SDK Client. • This Operating System Name will be documented in the LOA. • Only one OS Name shall be listed. If several OS are supported by the Split-SDK Client, different ICS shall be submitted and distinct LOAs will be granted. Split-SDK Client Operating System Version Tested C Version of the Operating System used for testing the Split-SDK Client: Instructions: • The Product Provider indicates the version of the Operating System used for testing the Split-SDK Client (only the OS Version used for testing shall be listed). • This Operating System Version will be documented in the LOA. Split-SDK Client Supported Operating System Versions C Operating System Version(s) able to support the Split-SDK Client: Instructions: • The Product Provider lists all versions of the tested Operating System supported by the Split-SDK Client. • At minimum the OS version tested during the Compliance Testing shall be listed. • All supported versions shall be separated by a space character. For example: o For a Split-SDK Client supporting iOS10, iOS11, iOS12, iOS13, iOS14, iOS15, iOS16 and iOS17 the field will be completed with: “10 11 12 13 14 15 16 17”. o For a Split-SDK Client supporting Android 5, Android 6, Android 7, Android 8, Android 9, Android 10, Android 11 and Android 12 the field will be completed with: “5 6 7 8 9 10 11 12”. • All supported versions of the Operating System will be documented in the LOA. NOTE: Only one version of the Operating System is tested. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 22 / 38 Eligibility for Regression Testing on Protocol 2.2.0 C Is a previous version of this 3DS Split-SDK “Yes” or “No” product already approved (i.e. expiring LOA) - for 2.3.1 protocol, - for the same Operating System, - for the same or lower Operating System Version - for the same 3DS Split-SDK client Component options and features, - and for the same Message Extensions tested (if supported)? Instructions: • The Product Provider shall not complete this field if the submission type of this ICS is “Add Message Extension” (See section 2.3.1) or if the Protocol Version is not 2.3.1 (See section 3.2) • The Product Provider selects “Yes“ if: o The Submission type of this ICS is “Initial” (See section 2.3.1) o The Protocol Version is 2.3.1 (See section 3.2) o A previous version of this 3DS Split-SDK component has already been approved for 2.2 or 2.3.1 protocol, o The LOA of the previous 3DS Split-SDK component has not expired yet. o The previously approved 3DS Split-SDK component supported the same Operating System (See Section 5.2.3). o The previously approved 3DS Split-SDK component supported the same Operating System Version or lower (See Section 5.2.4), o The previously approved 3DS Split-SDK component supported the same 3DS SplitSDK Component options and features (See Sections 5.3 and 5.4). o The previously approved 3DS Split-SDK component was tested for the same Message Extensions tested (if supported). See section 9. • The Product Provider selects “No“ otherwise. Eligibility for Regression Testing on Protocol 2.3.1 C Is “Yes” or “No” - answer to previous question = Yes? - UI implementation the same as in the expiring Split-SDK? - Do you confirm that submitted Split- SDK has not undergone any Major Refactoring? Note: If the response to this question is Yes and the product provider wants to benefit from the regression testing on protocol 2.3.1 for its Split-SDK, an attestation that the UI implementation has not changed and that the © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 23 / 38 Split-SDK did not undergo any Major Refactoring has to be signed and provided to EMVCo no later than RFA submission. Attestation template can be downloaded from EMVCo website. Instructions: • The Product Provider shall not complete this field if the submission type of this ICS is “Add Message Extension” (See section 2.3.1) or if the Protocol Version is not 2.3.1 (See section 3.2) • The Product Provider selects “Yes“ if o The submission type of this ICS is “Initial” (See section 2.3.1), o The Protocol Version is 2.3.1 (See section 3.2), o A previous version of this 3DS Split-SDK component has already been approved for 2.3.1 protocol, o UI implementation has not changed compared to previous 3DS Split-SDK component. Note that changes made on font, colour, size or boldness of text or on size or shape of logos are not considered as UI implementation changes in the context of this bulletin. For more details on acceptable UI changes, please contact EMVCo 3DS Secretariat at 3DS_approval@emvco.com, o The Split-SDK has not undergone any Major Refactoring, o The LOA of the previous 3DS Split-SDK component has not expired yet, o The previously approved 3DS Split-SDK component supported the same Operating System (See Section 5.2.3), o The previously approved 3DS Split-SDK component supported the same Operating System Version or lower (See Section 5.2.4), o The previously approved 3DS Split-SDK component supported the same 3DS SplitSDK Component options and features (See Sections 5.3 and 5.4). o The previously approved 3DS Split-SDK component was tested for the same Message Extensions tested (if supported). See section 9. If the response to this question is “Yes“, an attestation that the UI implementation has not changed and that and that the Split-SDK did not undergo any Major Refactoring has to be signed and provided to EMVCo. Attestation template can be downloaded from EMVCo website or requested to EMVCo 3DS Secretariat at 3DS_approval@emvco.com. • The Product Provider selects “No“ otherwise. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 24 / 38 Reference Number of the expiring 3DS Split-SDK LOA C What is the Reference Number of the expiring 3DS Split-SDK LOA? Instructions • If the response to the question 0 and/or 5.2.7 is “Yes”, please document the (expiring) LOA Reference number of the approved product that is being re-approved. Split-SDK Client Reference/Requestor Application Usage C Are you using the Reference/Requestor “Yes” or “No” Application provided by the Test Platform Provider for the Split-SDK Client testing? Instructions: • The Product Provider indicates if it is using the Reference/Requestor Application provided by the Test Platform Provider for the Split-SDK Client. • If the Product Provider is not using the Test Platform Provider Reference/Requestor Application (the response to question 5.2.9 is “No”), o Before entering the Compliance phase, the Product Provider shall provide an attestation to the Test Laboratory that the Reference/Requestor Application used does not impact the functional compliance as described in the applicable 3DS specifications. o EMVCo reserves the right to request code review of the Reference/Requestor Application Split-SDK Client Reference/Requestor Application Change C If you are using the Test Platform Provider “Yes” or “No” Reference/Requestor Application, did you make any change to this Application? Instructions: • If the answer to previous question 5.2.8 is “Yes”, the Product Provider indicates if he has modified the Test Platform Provider Reference/Requestor Application. • If the Product Provider has modified the Test Platform Provider Reference/Requestor Application (the response to question 5.2.9 is “Yes”), o Before entering the Compliance phase, the Product Provider shall provide an attestation to the Test Laboratory that the Reference/Requestor Application used does not impact the functional compliance as described in the applicable 3DS specifications. o EMVCo reserves the right to request code review of the Reference/Requestor Application. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 25 / 38 Split-SDK Client Reference/Requestor Application Change Details C If at the answer to the previous question is yes, please provide high level description of the changes Instructions: • If the Product Provider has modified the Test Platform Provider Reference/Requestor Application (the response to question 5.2.9 is “Yes”), the Product Provider documents the changes made to the Test Platform Provider Reference/Requestor Application (high level description). Split-SDK Client Component Features Platform Provider Specific C Split-SDK Client is Platform Provider specific “Yes” or “No” (e.g. gaming console, set top box, e- reader,…) Instructions: • The Product Provider indicates if the Split-SDK Client is Platform Provider specific (e.g. gaming console, set top box, e-reader, …). 5.3.1.1 OOB Authentication App on the Same Device as the Merchant App C Does the platform support an OOB “Yes” or “No” authentication app on the same device as the merchant app? Instructions: • If the answer to previous question 5.3.1 is “Yes”, the Product Provider indicates if the platform supports an OOB authentication app on the same device as the merchant app. 5.3.1.2 Cancel Action Implemented as a Controller Function C Is Cancel Action implemented as a function on “Yes” or “No” an external controller for the platform (e.g. gaming console controller, TV remote controller,…)? Instructions: • If the answer to question 5.3.1 is “Yes”, the Product Provider indicates if Cancel Action implemented as a function on an external controller for the platform. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Trust List Implementation C Trust List implementation Page 26 / 38 Instructions: • The Product Provider describes his Trust List implementation for the Split-SDK Client. For example it may be a “CheckBox” or a “Toggle” or other implementation. Split-SDK Client Component Options Supported Device User Interface Mode(s) C Supported Device User Interface Mode(s) (of  Portrait the target merchant application):  Landscape  Voice Instructions: • The Product Provider indicates which Device User Interface Mode(s) are supported by the target merchant application. NOTE: For rotatable devices, both Portrait and Landscape orientation options shall be selected in the ICS and each orientation will be tested. Type of Device Parameters M Type of Device Parameters included in the “Platform Provider Device Device Information Parameters” Instructions: • Split-SDK Client shall always use the Platform Provider Device Parameters so this cell shall be set. Split-SDK Server Component Identification Split-SDK Server Version C Split-SDK Server Version: Instructions: • The Product Provider indicates the version of its Split-SDK Server. • If there is not a specific versioning for the server part, the Split-SDK Version (see 5.1.2) can be duplicated in this cell. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Split-SDK Server Build Number C Split-SDK Server Build Number Page 27 / 38 Instructions: • The Product Provider indicates the Build Number of its tested Split-SDK Server. • Format of the build number is at the discretion of the Product Provider. Split-SDK Server Operating System Name or Virtual Machine Name C Operating System Name or Virtual Machine Name used for testing the Split-SDK Server: Instructions: • The Product Provider indicates the Operating System Name or Virtual Machine Name used for testing the Split-SDK Server. • This Operating System Name or Virtual Machine Name will be documented in the LOA. • Only one OS Name (or Virtual Machine Name) shall be listed. If several OS (or Virtual Machine) are supported by the Split-SDK Server, different ICS shall be submitted and distinct LOAs will be granted (unless this is the same application code that is used across different Operating Systems in which case the Product Provider may decide to use the same LOA for different Operating Systems). Split-SDK Server Operating System Version or Virtual Machine Version Tested C Operating System Version or Virtual Machine Version used for testing the Split-SDK Server: Instructions: • The Product Provider indicates the Operating System Version or Virtual Machine Version used for testing the Split-SDK Server (only the OS Version or Virtual Machine Version used for testing shall be listed). • This Operating System Version or Virtual Machine Version will be documented in the LOA. Name of the Underlying Operating System C In case of Virtual Machine used for testing the Split-SDK Server, Name of the underlying Operating System used for testing the Split- SDK Server: Instructions: • It shall only be completed if the Split-SDK Server is tested over a Virtual Machine • The Product Provider indicates the name of the underlying Operating System (below the Virtual Machine) used for testing the Split-SDK Server. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 28 / 38 6 PART IIIc – 3DS Server Component Usage • The Part IIIc is completed by the Product Provider. • It shall only be completed if the selected Component is 3DS Server (Fifth Component in Section 3.1 is ticked). If not, the Product Provider leaves this part empty. 3DS Server Component Identification 3DS Server Name C 3DS Server Name: Instructions: • The Product Provider indicates the commercial name of its 3DS Server Product. • This name will be published on the EMVCo web site and documented in the LOA. 3DS Server Version C 3DS Server Version: Instructions: • The Product Provider indicates the version of its 3DS Server Product. • This version will be published on the EMVCo web site and documented in the LOA. 3DS Server Build Number C 3DS Server Build Number Instructions: • The Product Provider indicates the Build Number of its tested 3DS Server Product. • Format of the build number is at the discretion of the Product Provider. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 29 / 38 3DS Server Operating System Name or Virtual Machine Name C Operating System Name or Virtual Machine Name used for testing the 3DS Server: Instructions: • The Product Provider indicates the Operating System Name or Virtual Machine Name used for testing the 3DS Server Product. • This Operating System Name or Virtual Machine Name will be documented in the LOA. • Only one OS Name (or Virtual Machine Name) shall be listed. If several OS (or Virtual Machine) are supported by the 3DS Server Product, different ICS shall be submitted and distinct LOAs will be granted (unless this is the same application code that is used across different Operating Systems in which case the Product Provider may decide to use the same LOA for different Operating Systems). 3DS Server Operating System Version or Virtual Machine Version Tested C Operating System Version or Virtual Machine Version used for testing the 3DS Server: Instructions: • The Product Provider indicates the Operating System Version or Virtual Machine Version used for testing the 3DS Server Product (only the OS Version or Virtual Machine Version used for testing shall be listed). • This Operating System Version or Virtual Machine Version will be documented in the LOA. Name of the Underlying Operating System C In case of Virtual Machine used for testing the 3DS Server, Name of the underlying Operating System used for testing the 3DS Server: Instructions: • It shall only be completed if the 3DS Server is tested over a Virtual Machine • The Product Provider indicates the name of the underlying Operating System (below the Virtual Machine) used for testing the 3DS Server Product. © 2020-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® 3-D Secure Approval ICS Form - Instruction Manual v1.12 Page 30 / 38 Eligibility for Regression Testing on Protocol 2.2.0 C Is a previous version of this 3DS Server “Yes” or “No” product already approved (i.e. expiring LOA) - for 2.2.0 or 2.3.1 protocol, - for the same Operating System, - for the same or lower Operating System Version - and for the same Message Extensions tested (if supported)? Instructions: • The Product Provider shall not complete this field if the submission type of this ICS is “Add Message Extension” (See section 2.3.1) or if the Protocol Version is not 2.3.1 (See section 3.2) • The Product Provider selects “Yes“ if o The submission type of this ICS is “Initial” (See section 2.3.1) o The Protocol Version is 2.3.1 (See section 3.2) o A previous version of this 3DS Server component has already been approved for 2.2.0 or 2.3.1 protocol, o The LOA of the previous 3DS Server component has not expired yet. o The previously approved 3DS Server component supported the same Operating System (See Section 6.1.4) and same or lower Operatin