Usage in CRes
Selection information that will be presented to the Cardholder if the option is single- or multi-select. The variables will be sent in a JSON Array and parsed by the 3DS SDK for display in the user interface. Example: " challengeSelectInfo " :[ {"phon":"Mobile **** **** 321" }, {"mail":"Email a*******g**@g***.com "} ]
Conditional inclusion — source text
See Table A.20 for presence conditions.
Format and scope
Type: Array
Source components: ACS. Channels: 01-APP. Categories: 01-PA, 02-NPA.
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 241
Scoped FAQ qualifications
- FAQ 26 — 2.2.0
App-based CRes, selected native UI template
Table A.1 optionality does not override the UI elements required by Table A.18. Challenge Information Label must be present for the templates discussed; it may contain a single space.
Related FAQ notes
- v2.2.0 requires total key length ≤45 characters across all options (keys are comma-joined in challengeDataEntry). v2.3.1.1 allows max 8 options with 4-char keys and 45-char values. — FAQ 62 (EMVCo FAQ)
Transaction context
This reference covers the published source edition. Use the explorer to inspect this field and any applicable transaction conditions. Scheme programme requirements are not inferred from the protocol edition.
Sources and related references
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 241
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b