EMV® Secure Remote Commerce Specifications -JavaScript SDK - DRAFT: Disposition of Comments

Draft Specification & Bulletin Industry Feedback Form Company Name: Consolidated Feedback Primary Contact Name: Working Group or Task Force: Secure Remote Commerce Working Group Document: EMV Secure Remote Commerce Specifications – JavaScript SDK v1.6 DRAFT Date: September 2026 EMVCo Use Only EA/Sub 1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of com- ment 2 Comment (justification for change) Proposed change Status (Accept, Acknowledge, Reject, In progress) 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: https://www.emvco.com/contact/ to submit feedback. 13-Aug-2026

of 1 EA Revision Log + Sections 2.4.1 Tables 2.4.1 + 2.4.2 te In the Revision Log it is indicated for section 2.4: “Optional additionalSources of type List<AdditionalSource> added to request parameters" + In the ‘getSrcProfile’ example in table 2.4.1, it is indicated “optional List<AdditionalSource> additionalSources”. + In table 2.4.2 ‘Request Parameters’, the ‘additionalSources’ list is defined as Conditional (“Only one of additionalSourceId and additionalSources can be provided”). It seems that the ‘additionalSources’ data element should be defined as ‘Conditional’ in the Revision Log and in the example in table 2.4.1 (as it is the case in the main definition of the data element in table 2.4.1). Accept Adjusted to reflect ‘Conditional’