7. Sandbox Testcases¶
The sandbox contains a list of test cases meant to assist you in implementation. More testcases can be added on demand.
It is also the intension that you can use the sandbox for automatic integration testing of your service. We will not modify individual test cases and will deprecate them with a sufficient grace period, if need be.
The 3-D Secure server sandbox validates input according to the specification.
7.1. Generic Tests¶
Test |
Trigger PAN |
What’s being tested in your system |
---|---|---|
Card not enrolled |
|
Handling not enrolled response. This test only involves the preauth call. |
7.2. Browser Tests¶
These tests involve deviceChannel: 02
. This must be set in all
authentication requests.
- For all these tests:
Perform the preauth call.
Execute the 3DS Method if available.
Perform a regular auth request. Use the same
acctNumber
as used in thepreauth
call.Fetch the challenge result using the postauth endpoint if relevant.
The /auth
browser example input is usable for all
cases. Just change the acctNumber
or purchaseAmount
where needed.
Message Version 2.1.0
¶
These tests have a preauth response with
acsEndProtocolVersion: 2.1.0
. This means your system should automatically
fall back to using verson 2.1.0
.
Sending messageVersion: 2.2.0
with these PANs will result in an error.
Testname |
Trigger PAN |
Success criteria |
What’s being tested in your system |
---|---|---|---|
3DS Method timeout |
|
|
The |
Frictionless 3DS Method |
|
|
Frictionless authentication with 3DS Method |
Frictionless no 3DS Method |
|
|
Frictionless authentication without 3DS Method |
Manual challenge |
|
|
Challenge authentication with 3DS method |
Automatic Challenge pass |
|
|
Successful challenge authentication with 3DS method The challenge will auto-submit using JavaScript |
Automatic Challenge fail |
|
|
Failed challenge authentication with 3DS Method The challenge will auto-submit using JavaScript |
Automatic Challenge pass |
|
|
Successful challenge authentication without 3DS method The challenge will auto-submit using JavaScript |
Frictionless |
|
|
Frictionless authentication failure |
Frictionless |
|
|
Frictionless authentication failure |
Frictionless |
|
|
Frictionless authentication failure |
Frictionless |
|
|
Frictionless authentication attempt |
Frictionless |
|
|
Correctly displaying |
DS Timeout |
|
|
Correct handling of DS timeout |
Message Version 2.2.0
¶
These tests have a preauth response with
acsEndProtocolVersion: 2.2.0
. If your system supports version 2.2.0
,
you can use these testcases to verify that your system automatically upgrades
to version 2.2.0
.
Sending messageVersion: 2.1.0
with these PANs will result in an error.
Testname |
Trigger PAN |
Success criteria |
What’s being tested in your system |
---|---|---|---|
3DS Method timeout |
|
|
The |
Frictionless 3DS Method |
|
|
Frictionless authentication with 3DS Method |
Frictionless no 3DS Method |
|
|
Frictionless authentication without 3DS Method |
Manual challenge |
|
|
Challenge authentication with 3DS method |
Automatic Challenge pass |
|
|
Successful challenge authentication with 3DS method The challenge will auto-submit using JavaScript |
Automatic Challenge fail |
|
|
Failed challenge authentication with 3DS Method The challenge will auto-submit using JavaScript |
Automatic Challenge pass |
|
|
Successful challenge authentication without 3DS method The challenge will auto-submit using JavaScript |
Frictionless |
|
|
Frictionless authentication failure |
Frictionless |
|
|
Frictionless authentication failure |
Frictionless |
|
|
Frictionless authentication failure |
Frictionless |
|
|
Frictionless authentication attempt |
Frictionless |
|
|
Correctly displaying |
DS Timeout |
|
|
Correct handling of DS timeout |
Scheme test PANs¶
To allow for integration testing with your authorization system, three different PANs exist in the sandbox.
These cards support versions 2.1.0
and 2.2.0
. You need to force
2.1.0
if your system automatically upgrades to 2.2.0
.
Testname |
Trigger PAN |
Trigger Amount |
Success criteria |
---|---|---|---|
Manual Challenge |
|
|
|
Frictionless |
|
|
|
Frictionless |
|
|
|
Frictionless |
|
|
|
Automatic challenge pass |
|
|
|
Automatic challenge fail |
|
|
|
7.3. 3RI Tests¶
These tests involve deviceChannel: 03
. This must be set in all
authentication requests.
The /auth
3RI example input is usable for all
cases. Just change the acctNumber
where needed.
For all these tests: Perform a regular auth request.
The /preauth
call is optional. Any threeDSServerTransID
received from
it will not be used in a final 3DS Requestor Initiated transaction.
Message Version 2.1.0
¶
Sending messageVersion: 2.2.0
with these PANs will result in an error.
Testname |
Trigger PAN |
Success criteria |
What’s being tested in your system |
---|---|---|---|
Frictionless |
|
|
Correctly sending a 3RI request |
Frictionless |
|
|
Correctly sending a 3RI request |
Frictionless |
|
|
Correctly sending a 3RI request |
Frictionless |
|
|
Correctly sending a 3RI request |
Message Version 2.2.0
¶
Sending messageVersion: 2.1.0
with these PANs will result in an error.
Testname |
Trigger PAN |
Success criteria |
What’s being tested in your system |
---|---|---|---|
Frictionless |
|
|
Correctly sending a 3RI request |
Frictionless |
|
|
Correctly sending a 3RI request |
Frictionless |
|
|
Correctly sending a 3RI request |
Frictionless |
|
|
Correctly sending a 3RI request |