search

clearhaus / 3DSv2-api-documentation

Clearhaus 3D Secure v2 Server API documentation
4 stars 3 forks source link

Update sandbox documentation - allow all pan #24

Closed Lassejoe closed 10 months ago

Lassejoe commented 10 months ago

Update the documentation after allowing all PANs https://github.com/clearhaus/edss-go/pull/267.

The new trigger is the last 4 in PAN which is documented here. I have also updated some of the text to make it bit more readable.

There is a section with examples that tries to help out integrators getting started.

Lassejoe commented 10 months ago
  1. Are the first column necessary in the tables?

I personally think it improves the readability, but maybe it is a personal preference and if so, I'm not against to remove it.

  1. What happens if one is to provide a digit not specified? Should we add a catch all/default in the bottom of all the tables, and what should this then be?

They will receive an error where the description is the following: "Unknown test, see valid tests here https://docs.3dsecure.io/3dsv2/sandbox.html"

  1. In the ARes table the 4th digit is set to 3 on most of the test cases this seems to collide with the rest of the changes? I would have expected an X at this point.

This was necessary when creating the test cases. So if it is a frictionless flow the 4th digit has to be 3.

cbobach commented 10 months ago

I personally think it improves the readability, but maybe it is a personal preference and if so, I'm not against to remove it.

It's fine by me :smile:

They will receive an error where the description is the following: "Unknown test, see valid tests here https://docs.3dsecure.io/3dsv2/sandbox.html"

Should we state this somewhere on the page?

This was necessary when creating the test cases. So if it is a frictionless flow the 4th digit has to be 3.

I would probably have flipped the 3th and 4th then such that the 3th digit determined the flow type friction-less or challenge, and then transStatus as the 4th :shrug:

Something in the line off:

Challenge type

Third digit PAN last 4 Description Requirements
0 xx0x Friction-less transaction status is required
7 xx7x Challenge invocation of /postauth is required

Transaction status

Fourth digit PAN last 4 Description Requirements
0 xxx0 transStatus Y
1 xxx1 transStatus N
2 xxx2 transStatus A [^1]
3 xxx3 transStatus R [^1]
4 xxx4 transStatus I [^1] [^2]
5 xxx5 transStatus U [^1]
6 xxx6 DS timeout [^1]
7 xxx7 Manual challange with transStatus Y or N [^3]

Just a thought :shrug:

[^1]: Only applicable for challenge type: Friction-less, last 4: xx0x. [^2]: Only supported with messageVersion 2.2. [^3]: Only applicable for challenge type: Challenge, last 4: xx7x.

Lassejoe commented 10 months ago

Should we state this somewhere on the page?

We can write something a la this: If the last four digits do not match any of the given test cases above, an error will be given

Lassejoe commented 10 months ago

I would probably have flipped the 3th and 4th then such that the 3th digit determined the flow type friction-less or challenge, and then transStatus as the 4th 🤷

I see your point but not all of the transStatus matches if it is a challenge flow. So it will become messy, IMO.

cbobach commented 10 months ago

We can write something a la this: If the last four digits do not match any of the given test cases above, an error will be given

I think that would be nice :bow: