Last Updated: 19 March 2024 | Change Log
The Payments API is for preview only and will be released soon.
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 | Cardholder Test Values | Card Number Test Values | Outcomes |
|---|---|---|---|
| Successful frictionless 3DS payment | AUTHORISED | Card number:
|
|
| Successful payment with 3DS challenge | AUTHORISED | Card number:
|
|
| Successful, frictionless 3DS payment. Sent for cancellation due to mismatching CVC/AVS | AUTHORISED | Card number:
|
|
| High risk fraud outcome | fs-highRisk | Card number:
|
If merchant.fraud is set to fraudSightSilentMode, we return sentForSettlement |
| Failed frictionless 3DS authentication | Any value | Card number:
|
|
| Failed challenged 3DS authentication | Any value | Card number:
|
|
| 3DS unavailable when attempting authentication | Any value | Card number:
|
|
| 3DS unavailable when attempting verification | Any value | Card number:
|
|
| Refused payment with frictionless 3DS | REFUSED | Card number:
|
|