- To test 3-D Secure authentication, please use the card numbers and OTPs listed below to obtain any expected authentication result (combinations such as authentication/frictionless, success/failure, etc.)
- After authentication, authorization occurs.
While your MID is in TEST-mode:
- For testing 3-D Secure authentication please use the card numbers and OTPs listed below to get any expected authentication result (combinations like challenge/frictionless, successful/failed, ...)
- After authentication the authorization takes place. Here please use "
OrderDesc=Test:<nnnn>" (e.g. "OrderDesc=Test:0000" or "OrderDesc=Test:0305") to get any expected authorization result
Once your MID is in PROD-mode:
- Testing of 3-D Secure authentication is not possible any more because your configuration is working with live 3-D Secure servers.
- However, "
OrderDesc=Test:<nnnn>" is still possible to simulate authorization.
Cartes
One-time Passwords (OTPs)
For strong authentication, please confirm the one-time password with a mouse click instead of the Enter key, as otherwise the "Cancel" button is selected and the authentication is completed.
transStatus
| transStatus | Description |
|---|---|
Y | Authentication Verification Successful |
N | Not Authenticated /Account Not Verified; Transaction denied |
U | Authentication/ Account Verification Could Not Be Performed; Technical or other problem, as indicated in ARes or RReq |
A | Attempts Processing Performed; Not Authenticated/Verified, but a proof of attempted authentication/verification is provided |
C | Challenge Required; Additional authentication is required using the CReq/CRes |
D | Challenge Required; Decoupled Authentication confirmed |
R | Authentication/ Account Verification Rejected; Issuer is rejecting authentication/verification and request that authorisation not be attempted |
I | Informational Only; 3DS Requestor challenge preference acknowledged |
transStatusReason
Please refer to 3D Secure - transStatusReason Codes (EN)
Simulation – always possible
The simulation mode is initiated by the "OrderDesc" parameter with the value "Test: <nnnn>", which also defines the result of the payment process.
The simulation mode is always available – but also requires card numbers that pass the so-called LUHN test. There is a short table below for this; You can also use real credit cards.
| Scheme | Card number | Value OrderDesc | Response | Description |
|---|---|---|---|---|
| VISA | 4111111111111111 | Test:<nnnn> | <nnnn> | see: A4 Error codes |
| MasterCard | 5555555555554444 | Test:<nnnn> | <nnnn> | see: A4 Error codes |
Testing with Bancontact - 3DS flow only (not QR code flow)
- Simulation mode needs to be activated
"simulationMode": "test:0000"
- Acquirer BIN : 777777
Bancontact 3DS:
Brand | PAN | Expiry Date | Test Scenario |
Bancontact | 67033790000009015 | 12/2028 | Successfuly authenticated browser challenge |
Bancontact | 6060055600000000900 | 12/2028 | Successfuly authenticated browser frictionless |
Bancontact | 6060050800000009019 | 12/2028 | Not authenticated browser frictionless |