EMV® 3-D Secure SDK Device Information Data Version 1.6 - DRAFT - Disposition of Comments

Draft Specification & Bulletin Industry Feedback Form Working Group or Task Force: 3-D Secure Working Group Document: EMV® 3-D Secure SDK—Device Information Data Version 1.6 – Draft Date: May 2023 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA EA 2.8 D006 D008 ed Some examples in DV 1.6 are not compatible with latest updates. Update the examples to match the data definition and requirements Accept • Tag C002: Example: “samsung SM-G960U1” - missing “||” • Android: "C002":"HTC One_M8" missing “||” • iOS: "C006":"+360" : + sign not allowed • D004 does not exist in DV 1.6 ed Conflicting description of resolution Better explain that the value sent is the Accept Pixel width and pixel height. format nnn X yyy resulting in integer concatenation of the X and Y nnnyyy. Developers by encode as resolutions. JSON Data Type: String “nnnxyyy” instead of “nnnyyy” Length: Variable, maximum 13 characters Value accepted: Both width and height are integers in the range of 0 to 999999. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. © 2023 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. Draft Specification & Bulletin Industry Feedback Form Working Group or Task Force: 3-D Secure Working Group Document: EMV® 3-D Secure SDK—Device Information Data Version 1.6 – Draft Date: May 2023 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change EA A076 te, A076 does not need any permission, Note to clarify the need for run time major but canRequestPackageInstalls() permission and A076 listed in DPNA if actually need prompt for permission is needed android.permission.REQUEST_INST ALL_PACKAGES EA A143 te, A143 isMultiSimSupported() needs Add Run-time permissions major android.permission.READ_PHONE_S TATE EA A039, te, A039, A040, A0149, and C009 all Add Run-time permissions A040, major need a new run-time permission, A0149, android.permission.BLUETOOTH_CO and C009 NNECT, on top of the old android.permission.BLUETOOTH Status (Accept, Reject, In progress) EMVCo Use Only EMVCo observations on each comment submitted Accept Expressed as width x height, for example: “1080x1920”. Android update Accept Android update Accept Android update EA A028 te, Value will be an RE04 for Android 11+ Add Note: not available for API level 31 Accept Android update major due to the following: or higher. Set to RE04. https://developer.android.com/training/ articles/user-data-ids#mac-11-plus 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. © 2023 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. Draft Specification & Bulletin Industry Feedback Form Working Group or Task Force: 3-D Secure Working Group Document: EMV® 3-D Secure SDK—Device Information Data Version 1.6 – Draft Date: May 2023 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA ge In reviewing “SDK – Device Review and harmonize wording in Accept Table xx lists the Information” spec, we’ve come across section 2, 2.5, 2.6, 2.7 and 2.8 Common/Platform- some unclear verbiage parameters, specific/Platform Provider- what is defined to be the specific parameters that the difference between parameters 3DS SDK shall collect from … “collected” and parameters that are passed down to the ACS? Does “provided” mean the same as collected? EA ge 2.4 explicitly stating “Device ID Review wording and move to section 2 Accept General statement “The ACS validation and risk analysis” versus all uses the Device Information for other sections that only state “risk device identification and risk analysis” analysis.” Other occurrences have been deleted. EA ge Can you provide clarification to help Review and harmonize wording in Accept Clarification in the parameters us understand how to implement on section 2, 2.5, 2.6, 2.7 and 2.8 to provide in Section 2. the 3 seemingly contradictory The 3DS SDK shall collect statements across the different either: sections 2.5, 2.6 and 2.7? • for the Default-SDK – the Common parameters (see 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. © 2023 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. Draft Specification & Bulletin Industry Feedback Form Working Group or Task Force: 3-D Secure Working Group Document: EMV® 3-D Secure SDK—Device Information Data Version 1.6 – Draft Date: May 2023 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, In progress) EMVCo Use Only EMVCo observations on each comment submitted Section 2.5) and one set of Platform-specific parameters (see Section 2.6 for Android and Section 2.7 for iOS), OR • for the Split-SDK – the Platform Provider-specific parameters (see Section 2.8). 2.5 - Table 2.2 lists the Common parameters that the 3DS SDK shall collect from all Android and iOS device platforms. 2.6 - Table 2.3 lists the Platform-specific parameters that the 3DS SDK shall collect from the Android device platform. 2.7 - Table 2.4 lists the Platform-specific parameters 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. © 2023 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. Draft Specification & Bulletin Industry Feedback Form Working Group or Task Force: 3-D Secure Working Group Document: EMV® 3-D Secure SDK—Device Information Data Version 1.6 – Draft Date: May 2023 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, In progress) EMVCo Use Only EMVCo observations on each comment submitted that the 3DS SDK shall collect from the iOS device platform. 2.8 - Table 2.5 lists the Platform Provider-specific parameters that the 3DS SDK shall collect from the Platform Providerspecific platform. If providing Platform Provider-specific parameters, the parameters defined in Sections 2.5, 2.6 and 2.7 shall not be provided. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. © 2023 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.