3 - Test Environment
3.1 - URLs
Valitor Payment Service can be tested here: https://paymentservice.uat.valitor.com/greidslugatt.asmx
3.2 - Test access
Input | Example |
---|---|
Notandanafn | visatest |
Lykilord | visatest123 |
PosiId | 1 |
3.2.1 - Test card
Please use the following card information when testing using the test environment.
Field | Value |
---|---|
Card Number | 9999999999999999 |
Expiry | 1114 |
Card Verification Code | 123 |
Tip
If a "500 - Operation timeout" error code is returned, please contact Valitor by phone on +354-525-2000.
The following test card numbers can be used when testing the Audkenning (3dSecure) endpoint, expiration date can be any date greater than current month and card verification code can be 123. - They can also be used for authorizations in test environment.
CardNumber | MdStatus (For 3dSecure authentication) | MdStaus description (For 3dSecure authentication) |
---|---|---|
2223000010275433 | 0 | Authentication failed, do not continue |
2223000010246699 | 1 | Fully authenticated, continue with authorization |
2223000010181581 | 2 | Authentication attempt, continue with authorization |
2223000010275466 | 4 | Authentication attempt, continue with authorization |
2223000010275474 | 5 | Gray area, do not continue |
2223000010275482 | 6 | Issuer error, do not continue |
2223000010275490 | 7 | Acquirer error, do not continue |
2223000010275508 | 8 | Possible fraud, do not continue |
2223000010275516 | 9 | Authentication pending, do not continue |
- MdStatus is a value returned back to merchant success url when 3dSecure authentication is finished.
3.3 - Production access
A merchant agreement needs to be completed prior to gaining access to production environment.
Contact Valitor for further information.