This page presents all the requirements your service must meet.
| ID # | Description | Steps To Execute | Expected Results | Pass | Fail | Retest Date | Defect/Comments | |
| 1 | BookonHold Amount check(BookonHold ONLY) | Client sends amount in kobo | Amount is logged in Client System as kobo | N/A | ||||
| 2 | Customer Validation: Merchant reference is expected in response (CUSTOMER VALIDATION ONLY) | Merchant reference is manipulated in request | Merchant reference in the request is returned in your resposne. | N/A | ||||
| 3 | Customer Validation:Invalid Customer Scenario
(CUSTOMER VALIDATION ONLY) |
Wrong Customer number is supplied | Status of 1 is returned and XML conforms to API | N/A | ||||
| 4 | Customer Validation:Valid Customer Scenario(CUSTOMER VALIDATION ONLY) | Valid Customer number is supplied | Status of 0 is returned and XML conforms to API | N/A | ||||
| 5 | Customer Validation:Expired Customer Scenario
(CUSTOMER VALIDATION ONLY) |
Expired Customer number is supplied | Status of 2 is returned and XML conforms to API | N/A | ||||
| 6 | Customer Validation:XML conformance Check in Client’s Response
(CUSTOMER VALIDATION ONLY) |
Check for special characters at the beginning and end of XML document | No special character should be at the beginning and end of XML response from client system | N/A | ||||
| 7 | Payment Notification: Amount check (BookonHold ONLY) | Send Amount in naira | Amount is logged in Client System as Naira | N/A | ||||
| 8 | Payment Notification: Payment Log Id is expected in response
(BOTH SCENARIOS) |
Send Payment Notification to Client URL | Payment Log Id is returned | N/A | ||||
| 9 | Payment Notification: Valid Payment Notification Scenario
(BOTH SCENARIOS) |
Send Payment Notification to Client URL | Status of 0 is returned and XML conforms to API | N/A | ||||
| 10 | Payment Notification: Invalid Payment Notification Scenario
(BOTH SCENARIOS) |
Send Payment Notification to Client URL | Status of 1 is returned and XML conforms to API | N/A | ||||
| 11 | Payment Notification: Duplicate Payment Notification Scenario
(BOTH SCENARIOS) |
Send a Payment multiple times to Client URL | Status of 0 is returned and XML conforms to API | N/A | ||||
| 12 | Payment Notification: XML conformance Check in Client’s Response
(BOTH SCENARIOS) |
Check for special characters at the beginning and end of XML document | No special character should be at the beginning and end of XML response from client system | N/A | ||||
| 13 | Payment Notification: Unauthorized Interswitch IP is used to place call to Client system
(BOTH SCENARIOS) |
Interswitch IP has been configured on client system | No response is received from Client System | N/A | ||||
| 14 | Payment Notification: Authorized Interswitch IP is used to place call to Client system
(BOTH SCENARIOS) |
Interswitch IP has been configured on client system | Response is received from Client System | N/A | ||||
| 15 | Reversal Notification
(BOTH SCENARIOS) |
Send amount as -ve and IsReversal tag sent to True;using same Payment Log id | Status of 0 is returned | N/A | ||||
| 16 | Duplicate Reversal Notification
(BOTH SCENARIOS) |
Send amount as -ve and IsReversal tag sent to True ; with same PaymentLogID | Status of 0 is returned with effecting reversal on customer’s account | N/A | ||||
NB: Click on the below link to download the UAT Generic Test Scripts.
Generic Bill Payment Interface Test Scripts v2
NB: Click on the below link to download the UAT Postman Collection and Environment
Paydirect UAT Postman Collection
Paydirect Environment.postman_environment
