V2.3.1 docs update #27
Conversation
source/versioning.rst
Outdated
| 3-D Secure version determination | ||
| ================================ | ||
|
|
||
| There are currently three 3-D Secure versions, ``1.0.2``, ``2.1.0`` and ``2.2.0``. | ||
| There are currently three 3-D Secure versions, ``2.1.0``, ``2.2.0`` and ``2.3.1.1``. | ||
|
|
||
| 1. If the :ref:`preauth call <preauth-usage>` returns a :ref:`not_enrolled`, continue with 3DSv1. | ||
| 2. If ``acsInfoInd`` (`2.1.0 | ||
| <specification_210.html#attr-cardRangeData-acsInfoInd>`_, `2.2.0 | ||
| <specification_220.html#attr-cardRangeData-acsInfoInd>`_) is included, this | ||
| indicates if ACS supports challenges or only attempts. | ||
| 2. If ``acsInfoInd`` | ||
| (`2.1.0 <specification_210.html#attr-CRD-acsInfoInd>`_, | ||
| `2.2.0 <specification_220.html#attr-CRD-acsInfoInd>`_, | ||
| `2.3.1.1 <specification_2311.html#attr-CRD-acsInfoInd>`_) | ||
| is included, this indicates if ACS supports challenges or only attempts. | ||
|
|
||
| To select between ``2.1.0`` and ``2.2.0``, we suggest using the highest version | ||
| To select between ``2.1.0``, ``2.2.0`` and ``2.3.1.1``, we suggest using the highest version | ||
| that all parties support, including your implementation. Exemplified: | ||
|
|
||
| - If ``dsEndProtocolVersion: 2.2.0`` and ``acsEndProtocolVersion: 2.1.0``, then the ACS |
There was a problem hiding this comment.
We also need to reconsider this part a bit.
Depends on how the preauth response will be.
I believe @kbadk and I will have a talk about the preauth response.
There was a problem hiding this comment.
Do we really want to specify 2.3.1.1? Wouldn't 2.3.1 be sufficient?
|
@thejspr wrt. to the comments about the AReq remember the links shall also be changed. |
|
@thejspr I don't have much more than my comments above :) |
Co-authored-by: Lasse Johansen <[email protected]>
|
@Lassejoe the links to specific specs was manually edited and is quite a chore to do and will get overwritten when we generate the docs. |
| } | ||
| ] | ||
| } | ||
|
|
There was a problem hiding this comment.
Note to self @thejspr : Update once settle on a final structure.
| @@ -17,7 +17,7 @@ If `3DS Method URL`_ is included in the :ref:`preauth-usage` response, the | |||
| 3DS method *must* be invoked as explained in this guide. | |||
|
|
|||
| If ``threeDSMethodURL`` *is not* included in the ``/preauth`` response (ref. | |||
| :ref:`2.1.0 <preauth-response-210>`, :ref:`2.1.0 <preauth-response-220>`), | |||
| :ref:`2.1.0 <preauth-response-210>`, :ref:`2.2.0 <preauth-response-220>`, :ref:`2.3.1 <preauth-response-231>`), | |||
There was a problem hiding this comment.
Should probably omit 2.1.0 since it will be gone by the time this documentation is released?
There was a problem hiding this comment.
Given the size of this PR, i think it will make sense to remove 2.1 in a separate PR
Co-authored-by: Bror <[email protected]>
source/_staticis formatting and indentation.Status 09-10-2024: Awaiting 2.3.1 certification with major schemes before merging. ETA unknown.