EMV® 3-D Secure Approval – Test Harness for Split-SDK as System Under Test

EMV® 3-D Secure Approval Test Harness for Split-SDK as System Under Test Version 1.15 11 Jul 2025 © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Legal Notice Page iii 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 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. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page iv Version 1.0 1.1 1.2 Date 05 May 2022 10 Jun 2022 22 Jul 2022 Revision Log Description Initial version: mainly extracts from former [TEST_REQ_SDK] v2.5 and updates to manage ShellSDK and Browser-SDK Test Architecture:  Section “3. Communication Test Requirements for Split-SDK/Native and Shell as SUT” extracted from [TEST_REQ_SDK] v2.5 o Only editorial changes o Section is also applicable for Shell-SDK  New section “4. Communication Test Requirements for Split-SDK/Browser as SUT”  “5. API Specifications ” extracted from [TEST_REQ_SDK] v2.5 o Editorial changes o API description have been made more generic to manage also Shell-SDK and Browser-SDK Test Architecture. P3DS_TP-374: Clarifications / Typo corrections:  “5.2.3 – Tool.3DSSplitSdk_API.fetchTC” o Data elements: clarification, it may be defined upon TPP or SUT needs o Output parameters: clarification, it contains the visualEvidencePoint o RunTcId Presence: Not present in HTTP request, but returned in HTTP Response  “5.2.4.1 – pErq elements, Visual Evidence Endpoint” : clarifications on the manaqement of the reception of pErq Upgrade references to documents due to new 2.3.1 specifications © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page v Version 1.3 1.4 1.5 1.6 1.7 1.8 Date 23 Sept 2022 28 Oct 2022 25 Nov 2022 14 Dec 2022 27 Jan 2023 Description Upgrade version to referenced documents  [3DS_Core_2.3.1] / [3DS_SDK_Spec_2.3.1] / [3DS_Split_SDK_Spec_2.3.1]  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK]  New reference to [RFC_4122] Editorial changes to realign Split-SDK Variant terminology from 2.3.1 specifications. No content change. Only reformatting to latest EMVCo Template document Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] P3DS_TP-471 - Clarification of the fetchTC usage has been done in section 5.2.3 of the ‘Test Harness for SplitSDK’ specification. P3DS_TP-478 - Sections 3.1.4 and 4.1.2 have been corrected with the correct label i.e. TPP (3DS Server). In addition, the security related to the CReq/CRes functions has been specified in the new sections 3.1.5 and 4.1.3. P3DS_TP-480 - Clarification on visualEvidenceEndpoint and new visualEvidenceEndpointURL in section 5.2.3. P3DS_TP-484 : Reference of RFC 2388 has been replaced by the 7578 P3DS_TP-476 : Different header names used: RunTcId vs TCRunID 28 April 2023 Updated version of referred documents :  [TEST_REQ_SDK] Updated version of referred documents :  [TEST_REQ_SDK] © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page vi Version 1.9 1.10 1.11 1.12 1.13 1.14 1.15 Date 30 June 2023 21 July 2023 27 Oct 2023 26 Apr 2024 11 Oct 2024 30 Apr 2025 11 Jul 2025 Description Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] Update from EMV® Specification Bulletin No. 255 v4 July 2024 : 3DS 2.1.0 is sunsetted  All references to 3DS 2.1.0 are removed Updated version of referred documents :  [TEST_REQ_ALL_SUT]  [TEST_REQ_SDK] Updated version of referred document:  [TEST_REQ_SDK] Updated version of referred document:  [TEST_REQ_SDK] © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page vii Contents 1. References......................................................................................................... 9 2. Introduction ..................................................................................................... 10 3. Communication Test Requirements for Split-SDK/Native and Shell as SUT11 3.1. Security & network connection ................................................................. 11 3.1.1. 3.1.2. 3.1.3. 3.1.4. 3.1.5. Standards ..................................................................................... 11 User Authentication....................................................................... 11 Connection from the Test Client Agent to the Test Environment ... 12 Connection from the MiddleWare to the TPP (3DS Server)........... 13 Connection from the Split-SDK to the TPP (ACS Server).............. 13 3.2. Use cases ................................................................................................ 15 3.2.1. Nominal flow ................................................................................. 15 3.2.2. Error flow management................................................................. 16 3.2.2.1. Trigger transaction error from Test Client Agent to Split-SDK.... 16 3.2.2.1. Trigger transaction error from the MiddleWare to the Split-SDK 16 4. Communication Test Requirements for Split-SDK/Browser as SUT ........... 17 4.1. Security & network connection ................................................................. 17 4.1.1. 4.1.2. 4.1.3. 4.1.4. Connection from the MiddleWare to the Test Environment ........... 17 Connection from the MiddleWare to the TPP (3DS Server)........... 18 Connection from the Split-SDK to the TPP (ACS Server).............. 18 Connection between the Merchant Web Page and the MiddleWare19 4.2. Use cases ................................................................................................ 20 4.2.1. Nominal flow ................................................................................. 20 4.2.2. Error flow management................................................................. 21 4.2.2.1. Trigger transaction error from MiddleWare to Split-SDK/Browser21 5. API Specifications ........................................................................................... 22 5.1. RunTcId specific data element ................................................................. 22 5.2. Methods ................................................................................................... 23 5.2.1. Tool.3DSSplitSdk_API.pArq.......................................................... 23 5.2.2. Tool.3DSSplitSdk_API.pSrq.......................................................... 24 5.2.3. Tool.3DSSplitSdk_API.fetchTC..................................................... 24 5.2.4. Tool.3DSSplitSdk_API.pErq.......................................................... 25 5.2.4.1. pErq elements, Visual Evidence Endpoint ................................. 25 5.3. Error Cases .............................................................................................. 26 © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 9 / 27 1. References Short name [TEST_REQ_ALL_SUT] [TEST_REQ_SDK] [3DS_Core_2.2.0] [3DS_SDK_Spec_2.2.0] [3DS_Core_2.3.1] [3DS_SDK_Spec_2.3.1] [3DS_Split_SDK_Spec_2.3.1] [RFC_4122] Reference Document Test Requirements for all Systems Under Test Test Requirements for SUT Default SDK and Split SDK EMV® 3-D Secure Protocol and Core Functions Specification EMVCo EMV® 3-D Secure – SDK Specification EMVCo EMV® 3-D Secure Protocol and Core Functions Specification EMVCo EMV® 3-D Secure – SDK Specification EMVCo EMV® 3-D Secure – Split-SDK Specification EMVCo A Universally Unique IDentifier (UUID) URN Namespace. https://tools.ietf.org/html/rfc4122 Version / Date v2.14 / 11 Oct 2024 V2.21 / 11 Jul 2025 v2.2.0 / nov-2018 v2.2.0 / nov-2018 v2.3.1.1 / May-2023 v2.3.1.1 / May-2023 v2.3.1.1 / May-2023 - © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 10 / 27 2. Introduction This document describes communication test requirements between Test Environment and 3DS Split-SDK as System Under Test (SUT). It relies on the [TEST_REQ_SDK] document which describes the high-level requirements applicable for the Split-SDK testing. Communication test requirements may vary depending on the Split-SDK variants:  Split-SDK/Native and Split-SDK/Shell requirements are described in section 3  Split-SDK/Browser requirements are described in section 4 A test API has been designed especially for executing the Split-SDK test cases (see section 5). © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 11 / 27 3. Communication Test Requirements for Split-SDK/Native and Shell as SUT 3.1. Security & network connection 3.1.1. Standards To secure the exchanges between all components, the document specifies some standards for the transport layer to use: Transport layer Description Protocol HTTPS Confidentiality TLS ≥ 1.2 Integrity TLS ≥ 1.2 Authentication Server Authenticate / Mutual Authenticate Authority Private CA / Commercial CA X509 rfc5280 PKI Certificate and Certificate Revocation List (CRL) Profile TLS 1.3 rfc8446 TLS Protocol 1.3 Certificate Pinning If requested by the system under test The Test Environment can support the certificate Pining if requested by the SUT for the authentication. 3.1.2. User Authentication The different connections can use specific and additional user authentications. It is optional and depends on the system under test request. This user authentication should support a standard authentication method to assume the TPP has the capability to use. As the interface uses HTTP, the authentication methods should be based on this protocol. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 12 / 27 3.1.3. Connection from the Test Client Agent to the Test Environment NOTE: This connection is mainly used for exchanging the fetchTC, pErq and pSrq messages. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 3.1.4. Connection from the MiddleWare to the TPP (3DS Server) Page 13 / 27 NOTE: This connection is mainly used for exchanging the pArq/pArs messages. 3.1.5. Connection from the Split-SDK to the TPP (ACS Server) NOTE: This connection is mainly used for exchanging the cReq/cRes messages. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 14 / 27 © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 3.2. Use cases 3.2.1. Nominal flow Page 15 / 27 © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 16 / 27 3.2.2. Error flow management To indicate to the TPP that an issue is coming, whatever the issue, some error flows have been created. 3.2.2.1. Trigger transaction error from Test Client Agent to Split-SDK 3.2.2.1. Trigger transaction error from the MiddleWare to the Split-SDK © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 17 / 27 4. Communication Test Requirements for Split-SDK/Browser as SUT 4.1. Security & network connection Security standards and user authentications defined in sections 3.1.1 and 3.1.2 apply also for the Split-SDK/Browser. 4.1.1. Connection from the MiddleWare to the Test Environment NOTE: This connection is mainly used for exchanging the fetchTC, pErq and pSrq messages. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 4.1.2. Connection from the MiddleWare to the TPP (3DS Server) Page 18 / 27 NOTE: This connection is mainly used for exchanging the pArq/pArs messages. 4.1.3. Connection from the Split-SDK to the TPP (ACS Server) NOTE: This connection is mainly used for exchanging the cReq/cRes messages. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 19 / 27 4.1.4. Connection between the Merchant Web Page and the MiddleWare The connection between the Merchant Web Page and the MiddleWare remains Product Provider application dependent. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 4.2. Use cases 4.2.1. Nominal flow Page 20 / 27 © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 21 / 27 4.2.2. Error flow management To indicate to the TPP that an issue is coming, whatever the issue, some error flows have been created. 4.2.2.1. Trigger transaction error from MiddleWare to Split-SDK/Browser © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 22 / 27 5. API Specifications This section describes the specific API messages required for testing the Split-SDK whatever its variant. Service Name Protocol type Protocol reference Protocol Format Protocol Format reference Service Identifier API exchange HTTP (REST) rfc7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content JSON rfc7159 JSON Data Interchange Format Tool.3DSSplitSdk_API 5.1. RunTcId specific data element Some specific data elements can be requested by the TPP to execute a test session. TPP has to retrieve the test case running during a session for a specific System Under Test. To manage the same process for all SUT, this document specifies this identifier. The identifier is unique and dynamically generated by the TPP. This ID shall not be related to a specific test case identifier. And the SUT cannot anticipate the test case running based on this identifier. Only the TPP can synchronize this element. This dynamic run test case identifier shall not be predictive. This ID is named RunTcId. RunTcId is encoded in UUID4 format as specified in [RFC_4122]. This is a contextual element which shall be exchanged between TPP and SUT. As this is not a test plan element, this ID should not be present in the test plan messages. This ID shall be present in the HTTP Headers. The RunTcId shall be present in the following messages  pIni message  pArq message  pArs message  pSrq message  pErq message For the Split-SDK/Native and Split-SDK/Shell, the Test Client Agent has to share the RunTcId with the MiddleWare in order to be able for it to provide it in pArq (the way to share this information between Test Client Agent and Middleware implementation dependent). The Test environment makes the link between RunTcId and threeDSServerTransID while sending the pArs message. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 23 / 27 Regarding the CReq/CRes messages exchanged between Split-SDK Server and Test Environment, no RunTcId is transmitted neither in message, nor in HTTP header. From the CReq/CRes messages, the Test environment is able to synchronize them with the current test execution through the field ‘threeDSServerTransID’ At the end of the transaction, for the generation of pSrq and pErq messages, the Test Client Agent or the MiddleWare will do the reconciliation with RunTcId (it is implementation dependent) The Version 4 of UUID is a universally unique identifier that is generated using random numbers. The Version 4 UUIDs produced by the TPP shall be generated using a secure random number generator. TPP and SUT can manage this element as a non-standard HTTP Header field. Name Description Example Status RunTcId Dynamic and Unique identifier UUID4 format as specified in [RFC_4122] RunTcId: c2cd982a8a6e-472a-b77f6a8c089170b3 Permanent 5.2. Methods The content of messageType is described previously on this document, the API uses the same data structure as the test plan requires. 5.2.1. Tool.3DSSplitSdk_API.pArq Method Name pArq Description proprietary message Caller Middle Ware Protocol type HTTP (REST) Protocol method POST messageType pArq Data elements Section 3.2.1 a) of [TEST_REQ_SDK] Output parameters pArs messageType Section 3.2.1 b) of [TEST_REQ_SDK] RunTcId Presence yes © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 24 / 27 5.2.2. Tool.3DSSplitSdk_API.pSrq Method Name pSrq Description proprietary message Caller Test Client Agent or MiddleWare Protocol type HTTP (REST) Protocol method POST messageType pSrq Data elements Section 3.1.3 a) of [TEST_REQ_SDK] Output parameters (pSrs) None (Acknowledge, no data) RunTcId Presence yes 5.2.3. Tool.3DSSplitSdk_API.fetchTC Method Name Description Caller Protocol type Protocol method messageType Data elements Output parameters RunTcId Presence fetchTC polling request Test Client Agent or MiddleWare HTTP (REST) GET NA None by default (any specific input parameter may be added in accordance with the SUT and TPP providers if required) pIni messageType Section 3.1.1 of [TEST_REQ_SDK] Plus the ‘visualEvidenceEndpoint’ indicator if relevant Or None (Acknowledge, no data) if there is no test to be executed no (not present in the HTTP request but returned in the HTTP Response) The polling requests the TPP to send the pIni element of the current test case. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 25 / 27 The content of the output parameters of the fetchTC method may include some specific data elements for the TPP. The pIni element is described on the section 3.1.1 of the [TEST_REQ_SDK]. The message includes the challengeUserData as a table of Tool.3DSSplitSdk_API. In addition to those elements, the messageType pIni should include the elements below in case the SUT supports visual evidence extraction:  visualEvidenceEndpoint (pErq management) o Indicator for TPP to manage endpoint for the visual evidence. These evidences are managed with pErq messageType. In case there is no test to be executed, the TPP shall send back an empty body response with an HTTP 204 or 200 status code. In such case, the SUT may decide to stop polling the TPP. It is assumed that, in case a test case consists in executing several transactions, the SUT shall send as many fetchTC requests as transactions to be executed (i.e. one pIni per transaction). In such case, the TPP must use the same RunTcId in each pIni. When the visualEvidenceEndpoint indicator is set to ‘True’, the TPP may also provide its root URL implementing the pErq requests, so that the SUT may use it dynamically during the visual evidences sharing:  visualEvidenceURL (pErq management) o Root URL of the TPP server (named as [root_url_endpoint_path] in the [TEST_REQ_SDK]) managing the visual evidences storage. 5.2.4. Tool.3DSSplitSdk_API.pErq Method Name Description Caller Protocol type Protocol method messageType Data elements Output parameters (pErs) RunTcId Presence pErq proprietary message Test Client Agent or MiddleWare HTTP (REST) Post pErq Visual Evidence Endpoint RFC 7578 None (Acknowledge, no data) yes 5.2.4.1. pErq elements, Visual Evidence Endpoint If the pIni related to a specific test contains the visualEvidenceEndpoint indicator set to ‘true’, the SUT has to provide the endpoint element with a pErq messageType. © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 26 / 27 The 'visualEvidenceEndpoint’ is retrieved after a fetchTC request and the pErq content type is defined in rfc 7578 (Returning Values from Forms: multipart/form-data) as defined in section 3.1.4 of [TEST_REQ_SDK]. An extended time can be allowed to the SUT to send the pErq to the TPP after the pSrq (e.g. in minutes) in order to let the SUT uploading all visual evidences. Nevertheless, even if the pErq of a related test has not been received yet, it should not prevent the TPP to start a new test sequence. In addition, the TPP shall not wait the pErq message in case the ‘visualEvidenceEndpoint’ indicator was set to ‘false’. 5.3. Error Cases http code 400 401 403 404 405 408 Message Service not recognized Client not authenticated Client authenticated but not allowed to use this service Client authenticated but application not known Client authenticated but method not allowed for this application The request is no longer expected - delay (e.g. 15 min) reached since the pSrq © 2022-2025 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 Test Harness for Split-SDK as System Under Test v1.15 Page 27 / 27 *** END OF DOCUMENT *** © 2022-2025 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.