PCI Watch

Tracking changes across the Payment Card Industry

EMV® 3-D Secure SB nº 223 SDK—Device Information Data Updates, Clarifications and Errata

v1.0 Specification Bulletins
3-D Secure

EMV<sup>®</sup> Specification Bulletin No. 223 v1 October 2019 EMV 3-D Secure SDK—Device Information Data Version 1.4 Updates, Clarifications and Errata This Specification Bulletin No. 223 v1 provides updates, clarifications and errata incorporated into 3-D Secure—Device Information Data Version 1.4

Applicability

This Specification Bulletin applies to:

  • EMV 3-D Secure—Device Information Data Version 1.4 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.

Effective Date

October 2019

countries.

Contents EMV 3-D Secure SDK—Device Information Data Version 1. EMV 3-D Secure SDK—Device Information Data Version 1.1 1.4. Table 1. 2. 2. Table 2. 2. Table 2. 2. Table 2. 2. Table 2. 2. 2. Table 2. 2.

countries.

EMV 3-D Secure SDK—Device Information Data Version 1.1 1.4 Chapter 1 Introduction 1.5 Data Version Number Table 1.2 Data Version Numbers Data Version Number Protocol Version 1.3

  • 2.1.0
  • 2.2.0
  • 2.3.0 1.4
  • 2.1.0
  • 2.2.0
  • 2.3.0 Status
  • Active Chapter 2 Device Information Parameters 2.1 Data Version The device identification parameters that are described in this document constitute Data Version 1.34.

2.2 Minimum Supported Platform Versions Table 2.1 Minimum Supported Platform Versions Platform Minimum Version Android KitKat 4.4 (API version 19) Android 5 (API version 21) iOS 8 10 Note: Note: The SDK can elect to support older versions of the OS if the versions are supported by OS providers.

2.4 Common Device Identification Parameters Available in All Platforms Note: If the value returned for a particular parameter is null, then the string value "null" shall be added for the parameter in the DD block. All parameters shall be encoded as String or Array of String. See Table 2.8 for examples.

countries.

Table 2.2 Common Parameters Available in Android, iOS and Windows 10 Platforms

Description

Permissions The unique package name/bundle identifier of the application in which the 3DS SDK is embedded. No permissions required. C014 SDK App ID Universally unique ID that is created for each installation of the 3DS Requestor App on a Consumer Device. Note: This should be the same ID that is passed to the Requestor App in the AuthenticationRequestParamete rs object (refer to Section 4.12.1 in the EMV 3DS SDK Specification). No permissions required. C015 SDK Version 3DS SDK version as applied by the implementer and stored securely in the SDK (refer to Req 58 in the EMV 3DS SDK Specification). No permissions required.

2.5 Android-specific Device Parameters Note: If the value returned for a particular parameter is null, then the string value "null" shall be added for the parameter in the DD block. Table 2.3 Android-specific Parameters A070 DATA_ROAMING and A072 DEVICE_PROVISIONED were moved to the Settings Global group in Table 2.3. 2.6 iOS-specific Device Parameters Note: If the value returned for a particular parameter is null, then the string value "null" shall be added for the parameter in the DD block.

countries.

Table 2.4 iOS-specific Parameters Group or Identifier Attribute NSBundle I014 appStoreReceiptURL Description A representation of the code and resources stored in a bundle directory on disk. The file URL for the bundle’s App Store receipt. https://developer.apple.com/documentation/foun dation/nsbundle/1407276-appstorereceipturl This bundle property can be used to locate the receipt for an application purchased from the Apple App store. Indirectly, this property can be used to identify whether the App has been installed from the Apple App store.

2.7 Windows 10 specific Device Parameters Note: If the value returned for a particular parameter is null, then the string value "null" shall be added for the parameter in the DD block.

2.9 Reasons for Device Parameters Unavailability Table 2.7 Device Parameter Unavailability Reasons Group or Identifier Description RE04 Parameter value returned is null or blank.

2.10 Device Information JSON Data If DD, DPNA, or SW is empty, the field shall not be present in the Device Information; meaning to be present, DD, DPNA, or SW shall contain at least one element.

countries.

Legal Notice

The EMV<sup>®</sup> 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 NON-INFRINGEMENT, 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<sup>®</sup> Specifications 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 the EMV<sup>®</sup> 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<sup>®</sup> Specifications

countries.