NIBSS INSTANT PAYMENT · User Acceptance Test Document . UAT Script Test Steps: 1. Share Technical...

Testing Start Date: [Insert Start Date] Testing End Date:

Introduction The document is meant to guide the proposed integration of financial institutions to NIBSS NIP Platform.

The testing is conducted to enable us validate that the integration meets the agreed acceptance criteria.

Integration Information Name of Institution

[INSERT NAME OF CLIENT]

Client’s URL

[INSERT CLIENT URL]

Client’s Representative

[INSERT CONTACT PERSON FOR THE INTEGRATION]

Contact Email, Phone Number

[INSERT EMAIL AND PHONE NUMBER OF REPRESENTATIVE]

The following checklist's purpose is to ensure that the appropriate steps have been taken to execute a user acceptance test (UAT), to ensure proper documentation has been completed.

NIBSS INSTANT PAYMENT

User Acceptance Test Script

User Acceptance Test Document

UAT Script

Test Steps:

1. Share Technical Specification 2. Share UAT Script 3. Exchange Web Service URLs on both ends 4. Share SSM Package and exchange Public Keys 5. Exchange test parameters (such as test account number and Financial Institution) 6. Schedule integration time 7. Commence testing based on UAT Script 8. NIBSS sends summary test status at the end of each test session (preferably at end of day) 9. Upon completion of test, NIBSS Tester Officer runs tests based on the test script again end

to end (against the test environment of another Financial Institution). 10. Evidences of completed tests are collected in form of exchanged messages for both inward

and outwards transactions 11. Stress Test 12. Exchange of Sign off documents 13. Exchange of production parameters 14. Migration to production 15. Pilot run 16. Completion of pilot and migration for public use

Test Cases

Please note that the highlighted texts in “Yellow” signify new features in the most recent version of the

NIP Technical Specification

S/N

TEST

RESULT/COMMENTS

VERDICT

1. GENERAL CONFIRMATION

a The following functions should be exposed in the webservice that would be provided by Financial Institution

1. Name Enquiry – NESingleRequest & NESingleResponse

2. Fund Transfer (Direct Credit) - FTSingleCreditRequest & FTSingleCreditResponse

3. Fund Transfer (Direct Debit) - FTSingleDebitRequest & FTSingleDebitResponse

4. Transaction Status Query – TSQuerySingleRequest & TSQuerySingleResponse

5. Balance Enquiry – BalanceEnquiryRequest & BalanceEnquiryResponse

6. Fund Transfer Advice (Direct Credit) - FTAdviceCreditRequest & FTAdviceCreditResponse

7. Fund Transfer Advice (Direct Debit) - FTAdviceDebitRequest & FTAdviceDebitResponse

8. Amount Block – AmountBlockRequest & AmountBlockResponse

9. Amount Unblock – AmountUnblockRequest & AmountUnblockResponse

(Yes) (No)

10. Account Block – AccountBlockRequest &

AccountBlockResponse

11. Account unblock – AccountUnblockRequest & AccountUnblockResponse

12. Financialinstitutionlist – FinancialInstitutionListRequest & FinancialInstitutionListResponse

13. MandateAdvice – MandateAdviceRequest & MandateAdviceResponse

Call By Financial Institutions (OUTWARDS from Financial Institution)

Call by NIP Engine (INWARDS to Financial Institution)

NAME ENQUIRY FT ADVICE Debit

FT DIRECT Credit FT ADVICE CREDIT

TRANSACTION STATUS Query BALANCE ENQUIRY (BE)

ACCOUNT BLOCK

ACCOUNT UNBLOCK

AMOUNT BLOCK

AMOUNT UNBLOCK

FINANCIAL INSTITUTION LIST

MANDATE ADVICE

FT DIRECT DEBIT

b Confirm that 1. NIBSS is able to consume FI’s Web Service 2. FI is able to consume NIBSS’s Web Service

(Yes) (No)

INWARDS This list of functions will be called by NIBSS’s NIP to Financial institution’s (FI), Mobile Payment Operators (MPO) and Other Financial Institution’s (OFI) webservice. It is expected that the receiving institution would perform the required action and return appropriate response

1. NAME ENQUIRY

a

Ensure that response matches the format below

Name Enquiry Response: <?xml version="1.0" encoding="UTF-8" ?>

<NESingleResponse>

<SessionID>000001100913103301000000000001</SessionID>

<DestinationInstitutionCode>000002</DestinationInstitutionCode>

<ChannelCode>1</ChannelCode>

<AccountNumber>2222000000012345</AccountNumber>

<AccountName>Ajibade Oluwasegun</AccountName>

<BankVerificationNumber>1033000441</BankVerification

Number>

<KYCLevel>1</KYCLevel>

<ResponseCode>00</ResponseCode>

</NESingleResponse>

(Yes) (No)

b Special XML Character received or transmitted in

any of the tags should be properly escaped.

(Yes) (No)

Examples of these special characters include

(&,<,>,\)

c Double check to confirm that the following parameter values are returned in the response from institution

Account Name

BVN

KYC Level Account Name returned should be for accounts that

can receive NIP credit or debit.

KYC Level are usually categorized as 1, 2, 3 with 1

meaning low KYC, 2 meaning semi (medium) KYC

and 3 meaning full (high) KYC.

Bank Verification Number of the customer is

returned for Commercial Banks. For non-financial

institutions customer Phone Number is returned

in place of BVN

(Yes) (No)

d

Ensure that the response codes returned by Destination Bank are interpreted properly and matches with the appropriate response message as contained in the specification document.

(Yes) (No)

e

Response Time for Name Enquiry should not be longer than 50 secs. Response should be returned in industry average time of less than 20 seconds.

(Yes) (No)

2. BALANCE ENQUIRY

a

Confirm the response is in the format below: Balance Enquiry Response <?xml version="1.0" encoding="UTF-8" ?>

<BalanceEnquiryResponse>

<SessionID>000001100913103301000000000001</SessionID> <DestinationInstitutionCode>000002</DestinationInstitutionCode> <ChannelCode>7</ChannelCode> <AuthorizationCode>xxxxxxxxxxxxxxx</AuthorizationCode> <TargetAccountName>Ajibade Oluwasegun</TargetAccountName> <TargetBankVerificationNumber>1033000442</TargetBankVerificationNumber> <TargetAccountNumber>2222002345</TargetAccountNumber> <AvailableBalance>1000.00</AvailableBalance> <ResponseCode>00</ResponseCode>

</BalanceEnquiryResponse>

(Yes) (No)

b

Ensure that you reject it when Authorization Code being sent to you is INCORRECT. * Mandate Advice should have been done earlier in

order to have the Authorization Code that will

be sent for Balance Enquiry. This mandate can

come from NIBSS or from the Financial Institution.

(Yes) (No)

If from Financial Institution, it would have been

pre-created with CentralPay and if with NIBSS,

through CMMS or other solutions

c

Special XML Character received or transmitted in any of the tags should be properly escaped. Example of these special characters are &, <, >, and \

(Yes) (No)

3. MANDATE ADVICE

a Ensure that response matches the format below Mandate Advice Response <?xml version="1.0" encoding="UTF-8" ?>

<MandateAdviceResponse>




<MandateReferenceNumber>xxxxxxxxxxxxxxx</MandateRe

ferenceNumber>

<Amount>Ajibade Oluwasegun</Amount>

<DebitAccountName>Ajibade Oluwasegun</DebitAccountName>

<DebitAccountNumber>2222000000012345</DebitAccountNumber>

<DebitBankVerificationNumber>1033000442</DebitBankVerificatio

nNumber>

<DebitKYCLevel>1</DebitKYCLevel>

<BeneficiaryAccountName>Sarah Hassan

Emeka</BeneficiaryAccountName>

<BeneficiaryAccountNumber>2222002345</BeneficiaryAccountNum

ber><BeneficiaryBankVerificationNumber>1033000442</Beneficiar

yBankVerificationNumber>

<BeneficiaryKYCLevel>1</BeneficiaryKYCLevel>


</MandateAdviceResponse>

(Yes) (No)

b Confirm that the mandate reference number is unique and that the one supplied doesn’t exist before especially on that account. If it does, it should be rejected.

(Yes) (No)

4. FUNDS TRANSFER (DIRECT CREDIT)

a Ensure that response matches the format below

Fund Transfer Response (Direct Credit): <?xml version="1.0" encoding="UTF-8" ?> <FTSingleCreditResponse> <SessionID>000001100913103301000000000002</SessionID> <NameEnquiryRef>000001100913103301000000000001</NameEnquiryRef> <DestinationInstitutionCode>000002</DestinationInstitutionCode> <ChannelCode>1</ChannelCode> <BeneficiaryAccountName>Ajibade Oluwasegun</BeneficiaryAccountName> <BeneficiaryAccountNumber>2222002345</BeneficiaryAccountNumber> <BeneficiaryKYCLevel>1</BeneficiaryKYCLevel> <BeneficiaryBankVerificationNumber>1033000442</BeneficiaryBankVerificationNumber> <OriginatorAccountName >Adewale Hassan</OriginatorAccountName> <OriginatorAccountNumber>3333002345</OriginatorAccountNumber>

(Yes) (No)

<OriginatorBankVerificationNumber>1033000441</OriginatorBankVerificationNumber> <OriginatorKYCLevel>1</OriginatorKYCLevel> <TransactionLocation>6.4300747,3.4110715</TransactionLocation> <Narration>1000000001</Narration>

<PaymentReference>yyyyyyyyyyyyyy</PaymentReference>

<Amount>1000.00</Amount>


</FTSingleCreditResponse>

b Balance Enquiry will be done first to confirm

balance before an FT is done and will be repeated

afterwards to confirm if the FT impacted on the

account successfully.

1st Step: Call Balance Enquiry, note the balance as

BAL1

2nd Step: Do Funds transfer (direct credit) of

amount, AMT

3rd Step: Call Balance Enquiry, note the balance as

BAL2

Confirm that the Funds Transfer was executed

successfully, by checking that BAL2 shows that

BAL1 increased by AMT passed in amount tag.

c

Ensure that Amount is rejected if it is NOT in two decimal places. Or if any component of the amount value is non-number.

(Yes) (No)

d

Special XML Character received or transmitted in any of the tags should be properly escaped. Examples of these special characters include &, <, > and \

(Yes) (No)

5. FUNDS TRANSFER (DIRECT DEBIT)


Fund Transfer Response (Direct Debit): <?xml version="1.0" encoding="UTF-8" ?> <FTSingleDebitResponse> <SessionID>000001100913103301000000000002</SessionID> <NameEnquiryRef>000001100913103301000000000001</NameEnquiryRef> <DestinationInstitutionCode>000002</DestinationInstitutionCode> <ChannelCode>1</ChannelCode> <DebitAccountName>Ajibade Oluwasegun</DebitAccountName> <DebitAccountNumber>2222000000012345</DebitAccountNumber> <DebitBankVerificationNumber>1033000442</DebitBankVerificationNumber> <DebitKYCLevel>1</DebitKYCLevel> <BeneficiaryAccountName>Sarah Hassan Emeka</BeneficiaryAccountName> <BeneficiaryAccountNumber>2222002345</BeneficiaryAccountNumber> <BeneficiaryBankVerificationNumber>1033000442</BeneficiaryBankVerificationNumber> <BeneficiaryKYCLevel>1</BeneficiaryKYCLevel> <TransactionLocation>6.4300747,3.4110715</TransactionLocation> <Narration>Transfer from 000002 to 0YY</Narration>

<PaymentReference>1000000001</PaymentReference>

(Yes) (No)

<MandateReferenceNumber>xxxxxxxxxxxxxxxxxxx</MandateReferen

ceNumber>

<TransactionFee>0.00</TransactionFee>



</FTSingleDebitResponse>

b Mandate Advice should have been done initially

to send the Mandate Reference Number to

Institution before an FT (Direct Debit) is done.

Note down the mandate reference number as

MANDATE1.

Next Balance Enquiry (BE) will be done to

confirm balance before an FT (Direct Debit) is done

and will be repeated afterwards to confirm if the FT

impacted on the account successfully.

When sending BE supply the Mandate Reference

Number generated as the Authorization Code in

the request. Test with both invalid and valid code.


BAL1

2nd Step: Do FT (Direct Debit) of amount, AMT

while specifying an INVALID mandate reference

number to confirm if it goes through. It shouldn’t be

successful, appropriate response code should be

returned.

3rd Step: Do FT (Direct Debit) of amount, AMT

while specifying a VALID mandate reference

number to confirm if it goes through. It should be

successful, appropriate response code should be

returned.

4th Step: If successful, Call Balance Enquiry, note

the balance as BAL2

Confirm that the Funds Transfer was executed successfully by checking that BAL2 has decreased by the amount specified in the amount tag.

(Yes) (No)

c Ensure that Amount is rejected if it is NOT in two decimal places. Or if any component of the amount value is non-number.

(Yes) (No)

d Special XML Character received or transmitted in any of the tags should be properly escaped e.g. of these special characters include (&,<,>,\)

(Yes) (No)

6. FUNDS TRANSFER ADVICE (DIRECT CREDIT)

a


Fund Transfer Advice Response (Direct Credit): <?xml version="1.0" encoding="UTF-8" ?>

<FTAdviceCreditResponse> <SessionID>000001100913103301000000000002</SessionID>

<NameEnquiryRef>000001100913103301000000000001</NameEn

(Yes) (No)

quiryRef>

<DestinationInstitutionCode>000002</DestinationInstitutionCode


<BeneficiaryAccountName>Ajibade

Oluwasegun</BeneficiaryAccountName>

<BeneficiaryAccountNumber>2222002345</BeneficiaryAcc

ountNumber>

<BeneficiaryBankVerificationNumber>1033000442</Benefi

ciaryBankVerificationNumber>


<OriginatorAccountName >Adewale

Hassan</OriginatorAccountName>

<OriginatorAccountNumber>3333002345</OriginatorAcco

untNumber>

<OriginatorBankVerificationNumber>1033000441</Origin

atorBankVerificationNumber>

<OriginatorKYCLevel>1</OriginatorKYCLevel>

<TransactionLocation>6.4300747,3.4110715</TransactionL

ocation>

<Narration>Transfer from 000002 to 0YY</Narration>




</FTAdviceCreditResponse>

b If response is not received in 50 seconds after call to FT Direct Credit request, advice will be sent and appropriate response should be returned.

(Yes) (No)

c If advice is received and there is credit impact to beneficiary account, impact should be reversed, and response still returned.

(Yes) (No)

d If advice is received and there is no credit impact to beneficiary account, no further action should be taken, response should just be returned.

(Yes) (No)

e If there is no response to an advice, three (3) extra advices will be sent consecutively until there is response. Only one of the advices should be acted on if there is credit impact otherwise no further action should be taken.

(Yes) (No)

7. FUNDS TRANSFER ADVICE (DIRECT DEBIT)


Fund Transfer Advice Response (Direct Debit): <?xml version="1.0" encoding="UTF-8" ?>

<FTAdviceDebitResponse> <SessionID>000001100913103301000000000002</SessionID>

<NameEnquiryRef>000001100913103301000000000001</NameEn

quiryRef>



<DebitAccountName>Ajibade

Oluwasegun</DebitAccountName>

<DebitAccountNumber>2222000000012345</DebitAccount

Number>

<DebitBankVerificationNumber>1033000442</DebitBankV

erificationNumber>

<DebitKYCLevel>1</DebitKYCLevel>

<BeneficiaryAccountName>Sarah Hassan

Emeka</BeneficiaryAccountName>

<BeneficiaryAccountNumber>2222002345</BeneficiaryAcc

(Yes) (No)

ountNumber>

<BeneficiaryBankVerificationNumber>1033000442</Benefi

ciaryBankVerificationNumber>


<TransactionLocation>6.4300747,3.4110715</TransactionL

ocation>



<MandateReferenceNumber>xxxxxxxxxxxxxxxxxxx</MandateReferen

ceNumber>

<TransactionFee>0.00</TransactionFee>



</FTAdviceDebitResponse>

b If response is not received in 50 seconds after call to FT Direct Credit request, advice will be sent and appropriate response should be returned.

(Yes) (No)

c If advice is received and there is debit impact to the target account, impact should be reversed, and response still returned.

(Yes) (No)

d If advice is received and there is no debit impact to target account, no further action should be taken, response should just be returned.

(Yes) (No)

e If there is no response to an advice, three (3) extra advices will be sent consecutively until there is response. Only one of the advices should be acted on if there is debit impact otherwise no further action should be taken.

(Yes) (No)

8. AMOUNT BLOCK


Amount Block Response <?xml version="1.0" encoding="UTF-8" ?>

<AmountBlockResponse>




<ReferenceCode>xxxxxxxxxxxxxxx</ReferenceCode>

<TargetAccountName>Ajibade Oluwasegun</TargetAccountName>

<TargetBankVerificationNumber>1033000442</TargetBankVerificat

ionNumber>

<TargetAccountNumber>2222002345</TargetAccountNumber>

<ReasonCode>0001</ReasonCode>




</AmountBlockResponse>

(Yes) (No)

b Confirm that ReferenceCode generated is unique and within the limit (Maximum 30 in length) and reject if it exceeds the limit with appropriate response

(Yes) (No)

c Confirm that one cannot do AmountBlock that is less than or equal to zero (0) naira.

(Yes) (No)

d Confirm that after AmountBlock, a lien is put on

that amount. Confirm this by sending BalanceEnquiry before and after AmountBlock to be sure it’s working. Balance Enquiry will be done first to confirm

balance before an AmountBlock is done and will

be repeated afterwards to confirm if it impacted on

the amount successfully.


BAL1

2nd Step: Do AmountBlock of amount, AMT


BAL2

Confirm that the AmountBlock was executed successfully by checking the AvailableBalance after the block reduces by the value in the amount tag.

(Yes) (No)

9. AMOUNT UNBLOCK


Amount Unblock Response <?xml version=”1.0” encoding=”UTF-8” ?>

<AmountUnblockResponse>

<SessionID>000001100913103301000000000001</SessionID> <DestinationInstitutionCode>000002</DestinationInstitutionCode> <ChannelCode>7</ChannelCode> <ReferenceCode>xxxxxxxxxxxxxxx</ReferenceCode> <TargetAccountName>Ajibade Oluwasegun</TargetAccountName> <TargetBankVerificationNumber>1033000442</TargetBankVerificationNumber> <TargetAccountNumber>2222002345</TargetAccountNumber> <ReasonCode>0001</ReasonCode> <Narration>Transfer from 000002 to 0YY</Narration> <Amount>1000.00</Amount> <ResponseCode>00</ResponseCode>

</AmountUnblockResponse>

(Yes) (No)

b Confirm that only the ReferenceCode used to Unblock Amount can be used to Unblock. When another ReferenceCode is used, it shouldn’t unblock the amount blocked.

(Yes) (No)

c Confirm that after AmountUnblock, the amount is removed from lien and by sending BalanceEnquiry the complete value in amount tag is available in account. Balance Enquiry will be done first to confirm

balance before an AmountUnBlock is done and

will be repeated afterwards to confirm if the

AccountUnblock impacted on the amount

successfully.


BAL1

2nd Step: Do AmountUnBlock of amount, AMT

(Yes) (No)


BAL2

Confirm that BAL2 shows that the balance in the

account has increased by the unblocked amount.

d Confirm that one cannot do AmountUnBlock that

is less than or equal to zero (0) naira and not more than the amount initially blocked.

(Yes) (No)

e Test for Partial Unblock: Confirm that one can do an amount unblock of amount greater than zero (0) but less than the amount initially unblocked.

(Yes) (No)

10. ACCOUNT BLOCK


Account Block Response <?xml version="1.0" encoding="UTF-8" ?>

<AccountBlockResponse>

<SessionID>000001100913103301000000000001</SessionID> <DestinationInstitutionCode>000002</DestinationInstitutionCode> <ChannelCode>7</ChannelCode> <ReferenceCode>xxxxxxxxxxxxxxx</ReferenceCode> <TargetAccountName>Ajibade Oluwasegun</TargetAccountName> <TargetBankVerificationNumber>1033000442</TargetBankVerificationNumber> <TargetAccountNumber>2222002345</TargetAccountNumber> <ReasonCode>0001</ReasonCode> <Narration>Transfer from 000002 to 0YY</Narration> <ResponseCode>00</ResponseCode>

</AccountBlockResponse>

(Yes) (No)

b Confirm that ReferenceCode generated is unique and within the limit (Maximum 30 in length) and reject if it exceeds the limit with appropriate response

(Yes) (No)

c Confirm that after AccountBlock, a lien is put on that amount. Confirm this by sending FundsTransfer (Direct Credit) and (FundsTransfer (Direct Debit) before and after AccountBlock to be sure it’s working.

(Yes) (No)

11. ACCOUNT UNBLOCK


Account Unblock Response <?xml version=”1.0” encoding=”UTF-8” ?>

<AccountUnblockResponse>




<ReferenceCode>xxxxxxxxxxxxxxx</ReferenceCode>

<TargetAccountName>Ajibade Oluwasegun</TargetAccountName>

<TargetBankVerificationNumber>1033000442</TargetBankVerificat

ionNumber>

(Yes) (No)

<TargetAccountNumber>2222002345</TargetAccountNumber>

<ReasonCode>0001</ReasonCode>



</AccountUnblockResponse>

b Confirm that only the ReferenceCode used to

Block Account can be used to Unblock. Testing using an invalid ReferenceCode and confirm if it goes through.

(Yes) (No)

c Confirm that after AccountUnblock, the account is actually unblocked. Confirm by sending FundsTransfer (Direct Credit and Direct Debit) to the account to see if it goes through.

(Yes) (No)

12. FINANCIAL INSTITUTION LIST REQUEST


Financial Institution List Response <?xml version="1.0" encoding="UTF-8" ?>

<FinancialInstitutionListResponse>

<BatchNumber>000001100911000000000001</BatchNumber>



<NumberOfRecords>5</NumberOfRecords>


</FinancialInstitutionListResponse>

(Yes) (No)

b Institution should successfully receive, store and respond with acknowledgment

(Yes) (No)

OUTWARDS These list of functions available on NIP Web Service which will be called by Institutions.

1. NAME ENQUIRY

a Ensure that request matches the format below

Name Enquiry Request: <?xml version="1.0" encoding="UTF-8" ?>

<NESingleRequest>




<AccountNumber>2222000000012345</AccountNumber>

</NESingleRequest>

(Yes) (No)

b Confirm that these parameters contained in each of the request/response is as below

Session ID (in Single Item) and RecID (in Bulk items)

(Yes) (No)

Numbers are 30 characters in length and will follow the format below: Char 1 – 6: Senders Financial Institution’s code Char 7 – 18: Date and time (in the format yymmddHHmmss – HH is 24 hour clock) Char 19 – 30: 12 – character unique number (either serial # or random number)

c Ensure that the Channel codes specified matches with the appropriate response message. See Below

Codes Channel Names

1 Bank Teller 2 Internet Banking 3 Mobile Phones 4 POS Terminals 5 ATM 6 Vendor/Merchant Web Portal 7 Third – Party Payment Platform 8 Other Channels

(Yes) (No)

2. FT DIRECT CREDIT

a Ensure that request matches the format below

Fund Transfer Request (Direct Credit): <?xml version="1.0" encoding="UTF-8" ?> <FTSingleCreditRequest> <SessionID>000001100913103301000000000002</SessionID> <NameEnquiryRef>000001100913103301000000000001</NameEnquiryRef> <DestinationInstitutionCode>000002</DestinationInstitutionCode> <ChannelCode>1</ChannelCode> <BeneficiaryAccountName>Ajibade Oluwasegun</BeneficiaryAccountName> <BeneficiaryAccountNumber>2222002345</BeneficiaryAccountNumber> <BeneficiaryBankVerificationNumber>1033000442</BeneficiaryBankVerificationNumber> <BeneficiaryKYCLevel>1</BeneficiaryKYCLevel> <OriginatorAccountName>Adewale Hassan</OriginatorAccountName> <OriginatorAccountNumber>3333002345</OriginatorAccountNumber> <OriginatorBankVerificationNumber>1033000441</OriginatorBankVerificationNumber> <OriginatorKYCLevel>1</OriginatorKYCLevel> <TransactionLocation>6.4300747,3.4110715</TransactionLocation> <Narration>1000000001</Narration>

<PaymentReference>yyyyyyyyyyyyyy</PaymentReference>


</FTSingleCreditRequest>

(Yes) (No)

b Confirm that these parameters contained in the request is as below

Session ID (in Single Item) and RecID (in Bulk items) Numbers are 30 characters in length and will follow the format below: Char 1 – 6: Senders Financial Institution’s code Char 7 – 18: Date and time (in the format yymmddHHmmss – HH is 24 hour clock) Char 19 – 30: 12 – character unique number (either serial # or random number) Amount is the exact figure in two decimal places and without comma to separate thousands.

(Yes) (No)

Narration is a maximum of hundred (100) character in length.

c Confirm that when “00 - approved” is received, original

debit transaction should not be reversed.

(Yes) (No)

d Confirm that when an error code is received other than

“00”, original debit transaction should be reversed

immediately.

(Yes) (No)

e When a timeout response is received, transaction

should be reversed immediately.

(Yes) (No)

f When no response is received, original transaction

should not be reversed. Query should be sent, and when

there is no response to query, settlement report should

be used as basis for final status of transaction.

(Yes) (No)

g Ensure amount being sent is in two decimal places

ONLY without non-number characters.

(Yes) (No)

h Confirm that the name enquiry reference being sent in

FT Direct Credit is same as the one used during Name

Enquiry

(Yes) (No)

3. TRANSACTION STATUS QUERY [TSQ]

a


Transaction Status Query Request (Single

Transaction)

<?xml version="1.0" encoding="UTF-8" ?>

<TSQuerySingleRequest>




</TSQuerySingleRequest>

(Yes) (No)

b

Confirm that NIBSS returns current status of

transaction successfully with appropriate response

codes, number of records, channel code, destination

Financial Institution Code and Batch Number

(Yes) (No)

c

Confirm that appropriate ChannelCode has been

specified.

(Yes) (No)

UAT SIGN-OFF Please note that the authorized signatory of Client should be two namely Tester and Supervisor.

AUTHORIZED SIGNATURE: AUTHORIZED SIGNATURE:

______________________ _______________________________

[INSERT NAME OF INSTITUTION] Nigeria Inter-Bank Settlement System Plc.

NAME: NAME:

DESIGNATION: DESIGNATION:

DATE: DATE:

AUTHORIZED SIGNATURE: AUTHORIZED SIGNATURE:

______________________ _______________________________

[INSERT NAME OF INSTITUTION] Nigeria Inter-Bank Settlement System Plc.

NAME: NAME:

DESIGNATION: DESIGNATION:

DATE: DATE:

*This document should be filled, signed and sent back in two copies to [email protected] by

Financial Institution, upon complete integration and testing. It is also expected that each page of the

document will be signed and scanned back ONLY at the time of Test Closure.

mailto:[email protected]

NIBSS INSTANT PAYMENT · User Acceptance Test Document . UAT Script Test Steps: 1. Share Technical...

Documents

Transcript of NIBSS INSTANT PAYMENT · User Acceptance Test Document . UAT Script Test Steps: 1. Share Technical...