Last Updated: 17 October 2024 | Change Log
Testing
Test your Payments integration in the Try environment using a combination of cardholder and card number test values. Send requests and see simulated responses.
As features such as 3DS, FraudSight or auto settlment can be enabled and disabled, the outcome of the scenarios below will change based on the configuration you have in place.
Tokens
If you're creating tokens containing the test card numbers, you must delete the token before creating another with the same PAN. You are prevented from creating another token using the same PAN. As an alternative, you can also change the tokenCreation.namespace used as part of the token creation.
| Test Scenario | Description | Cardholder Value | Card Values (3DS 2.1.0) | Card Values (3DS 2.2.0) | Outcomes |
|---|---|---|---|---|---|
| Successful frictionless 3DS Authorized Payment | Issuer assessment resulted in a frictionless 3DS authentication | AUTHORISED |
|
|
|
| Successful 3DS challenge Authorized Payment | Issuer prompts a challenge in authentication, customer responds successfully | AUTHORISED |
|
|
|
| Successful frictionless 3DS Sent for Cancellation | Successful, frictionless 3DS payment. Sent for cancellation due to mismatching CVC/AVS Only applicable if settlement.auto is true | AUTHORISED
|
|
|
|
| High Risk Fraud Assessment | Fraudsight flags the payment as highRisk and stops it from proceeding | fs-highRisk |
|
|
If fraud.silentMode is set to true, we return sentForSettlement or authorized ('settlement.auto' value dependant)
|
| Failed frictionless 3DS authentication | Issuer failed the 3DS authentication without offering a challenge | Any value e.g. Bob |
|
|
|
| Failed challenged 3DS authentication | Issuer prompts a challenge in authentication, customer responds with incorrect details (e.g. OTP, fingerprint etc) | Any value e.g. Bob |
|
|
|
| 3DS unavailable when attempting authentication | Initial 3DS authentication not available due to downstream system error | Any value e.g. Bob |
|
|
|
| 3DS unavailable when attempting verification (step after challenge) | The 3DS authentication details could not be retrieved following the challenge | Any value e.g. Bob |
|
|
|
| Refused Payment | The issuer refused the payment, if 3DS is used its frictionless | REFUSED |
|
|
|
Example device data form
The form below allows you to submit the 3DS device data details provided in the API response and receive the sessionId/collectionReference back for use in the /3dsDeviceData request. This is useful if using tools such as postman/insomnia to test your integration.
Example challenge form
The form below allows you to submit the 3DS challenge details provided in the API response and display the issuer challenge. This is useful if using tools such as postman/insomnia to test your integration.