Test Conditions
For getPaymentURL, the predefined test conditions are based on transaction_amount value.
For example, to test a declined payment, set transaction_amount to 3001. This response will contain payment_url and a predefined value for process_no. On launch of payment_url, a page similar to below will be displayed. It shows the test condition, process number, transaction id and redirect url from getPaymentURL request.

The process number (3000 in this example) can be used to getPaymentStatus, which will return Declined status.
For each test condition a predefined process_no is returned.
| Transaction_Amount | Test Condition | Process_no |
|---|---|---|
| 3001 | Declined (01) | 3000 |
| 4001 | In progress (02) | 4000 |
| 5001 | Error (03) | 5000 |
| 6001 | Cancel (04) | 6000 |
| 7001 | Invalid Product Codes | N/A |
| 9998 | System Error | N/A |
| Any Other Value | Approved (00) | 2000 |
Test Conditions - getPaymentStatus
For getPaymentStatus, the predefined test conditions are based on process_no value.
| Process_no | Test Condition |
|---|---|
| 2000 | Approved (00) |
| 3000 | Declined (01) |
| 4000 | In Progress (02) |
| 5000 | Error (03) |
| 6000 | Cancel (04) |
| 9998 | System Error |
| 9999 | Not Valid |
Test Conditions - createPaymentRefund
For createPaymentRefund, the predefined test conditions are based on merchant_transaction_id value.
| Merchant_transaction_id | Test Condition |
|---|---|
| 2000 | Approved |
| 3000 | Not Valid |
| 4000 | Invalid amount |
| 9998 | System Error |
Updated about 21 hours ago