Test Amounts
Before going live you will first complete a number of test card transactions on our test environment. We have provided a range of amounts that you can use to check all the transactional statuses. Using the below amounts will produce specific responses in order for you to test different scenarios.
Please be aware that all the possible statuses of the transactions that are returned in responses are based on the values assigned in the Amount field.
If you want to obtain a specific status, simply enter a specific amount as the transaction amount. Below you will find different amounts to simulate certain situations and statuses.
The amount’s last two digits represent the decimal part (11.54 will be sent 1154).
| Test Amounts | ||
|---|---|---|
| Value | Status | Description |
| 1 – 10000 | Captured / Authorized | For this amount range all the actions will be successful: payment authorization, capture action, cancel action, refund action. |
| 10001 | Failed | All the transactions having this amount will fail. |
| 10002 | QueuedForCapturing |
If you set capture flag to true it will return status QueuedForCapturing with return code: 5288: “Capture failed but will retry again later”. If you set capture flag to false it will return status Authorized. Then if you sent a capture request it will receive status QueuedForCapturing with return code: 5288: “Capture failed but will retry again later”. |
| 10003 | CaptureRequested |
If you set capture flag to true it will return status CaptureRequested. If you set capture flag to false it will return status Authorized. Then if you sent a capture request it will receive status CaptureRequested. |
| 10004 | Transaction: Captured; Refund: Open | If this amount will be used for a transaction it will be captured but the refund will remain Open. |
| 10005 | Failed | Capture failed with timelimit reached. The timelimit for capture action is overdue. |
| 10006 | QueuedForCanceling | If you set capture flag to false it will return status Authorized. Then if you sent a cancel request it will receive status QueuedForCanceling with return code: 5289: “Cancel failed but will retry again later”. |
| 10201 – 10299 | Transaction: Captured; Refund: Failed | If any of the amounts in this range limit are used for a transaction it will be Captured but the refund will fail. |
| 20001 – 30000 | Failed | If any of the amounts in this range limit are used for a transaction it will fail and it will receive status Failed with return code: 5291: “Security code (CVV2/CVC2) is incorrect”. |
| 30001 – 30200 | Captured / Authorized | For this amount range all the actions will be successful: payment authorization, capture action, cancel action, refund action. For the initial request there is a delay in seconds according to the last 3 digits (from 1 – 200 seconds). |
Test Credit Card Numbers
For testing purposes, please use the following credit card numbers:
| Test Credit Card Numbers | |
|---|---|
| Credit Card Name | Credit Card Number |
| Visa: | 4111111111111111 |
| 4024007189870784 | |
| 4548812049400004 | |
| Mastercard: | 5148196509775860 |
| 5443066050671259 | |
| Discover: | 6011087785272940 |
| 6011235328768235 | |
| UnionPay: | 6226388000000095 |
| 6216261000000000018 | |
| Visa Electron: | 5443066050671259 |
| 4917300800000000 | |
| American Express: | 345364891980314 |
| 372986503275489 | |
| Diners Club: | 30120905411096 |
| 38341714925074 | |
| Hipercard: | 6062825624254001 |
| JCB: | 3158178601355868 |
| 210076836080396 | |
| InstaPayment: | 6385756289989351 |
| 6390524121376333 | |
For testing purposes, please use only the credit card numbers from the above list! If any other credit card number is used for a test transaction it will fail and it will receive status Failed with return code: 5287: “Invalid card for test transaction”.