ℹ️
Tracked metadata: Sourced from EMVCo's public document index. PCI Watch records each document's details and its extracted text so changes can be tracked over time; the document PDF itself is hosted by EMVCo.
View on EMVCo.com →

3DSA Bulletin nº 28: Activation of the Approval Testing Process

v2.0 Type Approval Bulletins
3-D Secure
Extracted document text

EMVCo's index flattens the document's layout, so this text is best used for searching and comparing versions rather than reading end-to-end.

EMV® 3-D Secure Approval Bulletin No. 28 Second Edition March 2026 Activation of the Approval Testing Process for Split-SDK Native & Split-SDK Shell Applicability This approval bulletin applies to the approval process for the EMV® 3-D Secure (3DS) Products. Related Documents • EMV 3-D Secure Protocol and Core Functions Specification version 2.3.1.1 • EMV 3-D Secure SDK Specification version 2.3.1.1 • EMV 3-D Secure Split-SDK Specification version 2.3.1.0 • EMV 3-D Secure Test Harness for Split-SDK as System Under Test – latest version • EMV 3-D Secure Test Requirements for 3DS Default SDK and Split-SDK – latest version • EMV 3-D Secure Approval – Administrative Process version 1.5 • EMV 3-D Secure Approval Bulletin No 01 6th Edition Effective Date April 1st, 2026 Description The 3DS approval process is updated to support the testing of EMV 3-D Secure Split-SDK Native & Split-SDK Shell. The Split-SDK functions much like 3DS Default-SDK, but 3-D Secure Split-SDK divides the client functionalities between Split-SDK Client and Split-SDK Server. For the Split-SDK Native, the client functionality is implemented using native platform code embedded within a 3DS Requestor App. For Split-SDK Shell, the Client functionality is implemented using JavaScript running in a secured WebView opened by the Split-SDK Shell that is embedded in the 3DS Requestor App. Standard approval process applies and the Product Provider shall fill the relevant sections in the ICSform. Product Provider shall either prepare the Merchant Web Page including the Test Client Agent and the Middleware, or request support from the Test Platform Provider in obtaining these. Upon successful compliance testing and payment of the 3-D Secure Approval fee, the Product Provider will obtain an LOA for the product. General Rules Please reach out to your Test Platform Provider and Testing Laboratory on their readiness to support the testing of Split-SDK Native & Split-SDK Shell. For additional information on the changes made to the 3-D Secure Approval process, please contact EMVCo 3DS Secretariat. © 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. Page 1 Legal Notice This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document. © 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. Page 2