PCI Watch

Tracking changes across the Payment Card Industry

EMV® 3-D Secure SDK—Device Information v1.5 DRAFT Disposition of Comments

v1.0 Draft Specification
3-D Secure

Draft Specification & Bulletin Industry Feedback Form Company Name: Primary Contact Name: Working Group or Task Force: 3-D Secure Working Group Document: 3-D Secure Device Information v1.5 Draft Date: September 2021 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) D013 D029 ed The description mentions examples for Android and iOS on how to obtain the device information. Are these appropriate examples for this type of device parameters? te Is this device parameter only applicable for Split SDK? If so, maybe this should be mentioned in the Comments (compare e.g. D030 which is listed as Browser-SDK only). Proposed change Status (Accept, Reject, In progress) EMVCo Use Only EMVCo observations on each comment submitted Accept A clarification was added if the SDK is implemented on an Android or iOS device. Reject If the D029 or D030 are not available for a particular SDK, they will be listed in the DPNA list with reason RE02. 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. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 21-Sep-2021

of 3 Draft Specification & Bulletin Industry Feedback Form Company Name: Primary Contact Name: Working Group or Task Force: 3-D Secure Working Group Document: 3-D Secure Device Information v1.5 Draft Date: September 2021 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 SDKDevic eInfo

  • Table 1.2: Is the correct Protocol Version "2.3.0" or "2.3.0.0"?
  • D017: Do we need a comment indicating when challengeWindowSize is applicable? … vs D008
  • D031: Do we also want this value for Shell-SDK? (Similar to A137 on Android)
  • Were D021 and D022 intentionally removed?
  • Table 2.8 sample: C002 does not follow required format, C007 should be removed In DSB225, the Android sample was replicated, and the DV values not consistent for multiple rows. But these were correct in the actual full document. Platform Provider specific row had a C003 instead of a D003 field Accept The SDK Device Information document refers to the Specification Bulletin 255 for the Protocol version 2.3.0. D008 is the screen size, D017 is the challenge window size, these data elements are applicable for all SDK types. D031 is applicable to all SDK types, if not available it will be in the DPNA list D021, D022: This was an error, these 2 data elements are included in the final version of the SDK Device Information document. The C002 example in Table 2.8 is updated: "iPhone 5S" is replaced by a valid value "iPhone6,1". SB 225 has been updated. 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. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 21-Sep-2021 of 3 Draft Specification & Bulletin Industry Feedback Form Company Name: Primary Contact Name: Working Group or Task Force: 3-D Secure Working Group Document: 3-D Secure Device Information v1.5 Draft Date: September 2021 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 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. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 21-Sep-2021 of 3