PCI Watch

Tracking changes across the Payment Card Industry

SB n° 275: EMV® 3-D Secure SDK Specification

v2.3.1.0 Specification Bulletins
3-D Secure

EMV® Specification Bulletin No. 275 August 2022 EMV® 3-D Secure SDK Specification version 2.3.1.0 This Specification Bulletin No. 275 provides updates, clarifications and errata incorporated since the September 2021 release of version 2.3.0.0.

Applicability

This Specification Bulletin applies to:

  • EMV® 3-D Secure SDK Specification, Version 2.3.1.0 Updates are provided in the order in which they appear in the specification. Deleted text is identified using strikethrough, and red font is used to identify changed text. Unedited text is provided only for context.

Related Documents

EMV® 3-D Secure SDK Specification, Version 2.3.0.0

Effective Date

  • August 2022 countries. Contents EMV® 3-D Secure SDK Specification version 2.3.1.0. 2.3. 3. 3.3. 4. countries. Throughout Specification
  • Revisions added to improve grammar, spelling, consistency, clarity and readability without any effect on the meaning or interpretation of the specification are not included in this bulletin.
  • For consistency and ease of reference, the EMV® 3-D Secure Protocol and Core Functions Specification is referred to as the Core Specification. countries. Chapter 2 EMV 3-D Secure Architecture and Flows Overview 2.3 UI Types for Challenge Flow 2.3.2 Challenge Flow Implemented Using HTML UI The last sentence in the section has been revised to refer to a different section of the Core Specification. For more information about the HTML UI, refer to Section 4.2.44.2.5 of the Core Specification. Chapter 3 Getting Started with the EMV 3-D Secure Default SDK 3.3 Authentication Flows 3.3.1 Frictionless Flow 13. In the getProgressView method call, the 3DS SDK returns an instance of Progress View (processing screen). Refer to [Req 141]–[Req 145144] in the Core Specification for additional detail. countries. Chapter 4 Code Elements of the EMV 3-D Secure Default SDK 4.11 Class ChallengeParameters Although no substantive revisions have been made to Table 4.75 in v2.3.1.0 of the specification, Table 4.75 is replicated below to correct a formatting error in v2.3.0.0 that caused it to display incorrectly. Table 4.75: ChallengeParameters Class Methods Method Description set3DSServerTransaction Sets the 3DS Server Transaction ID. ID setAcsTransactionID Sets the ACS Transaction ID. setAcsRefNumber Sets the ACS Reference Number. setAcsSignedContent Sets the ACS Signed Content. This data includes the ACS URL, ACS Ephemeral Public Key, and SDK Ephemeral Public Key. setThreeDSRequestorAppU Sets the 3DS Requestor App URL. RL get3DSServerTransaction Returns the 3DS Server Transaction ID. ID getAcsTransactionID Returns the ACS Transaction ID. getAcsRefNumber Returns the ACS Reference Number. getAcsSignedContent Returns the ACS Signed Content object. getThreeDSRequestorAppU Returns the 3DS Requestor App URL. RL countries.

Legal Notice

The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. 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 THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, knowhow, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications 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 these Specifications 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 the EMV® Specifications

countries.