UAT SIGN-OFF DOCUMENT

TEST DOCUMENTATION

REMITA E-COLLECTION UAT SIGN-OFF DOCUMENT

Component Name Remita e-Collection UAT Sign-Off Document

General Description This is an acknowledgement of integration project

implementation and certification of all functions as
agreed between SystemSpecs and the Merchant
Target Audience Merchants

Merchant Name, Signature & Date.

Copyright SYSTEMSPECS LIMITED
This document, a property of the SystemSpecs Limited, cannot be reproduced nor communicated without written authorization.
 Remita e-Collection Integration

User Acceptance Test Sign-off Document

Merchant Name

Merchant Technical Contact Name

Merchant Technical Contact Phone

Number

Merchant Technical Contact Email

Merchant Business Contact Name

Merchant Business Contact Phone

Number

Merchant Business Contact Email

Merchants Product/Services

Merchants Website URL

Remita Certification Officer

Merchants Sign Off (Name,

Signature & Date)

Test Date

Merchant Name, Signature & Date.

2
Copyright SYSTEMSPECS LIMITED
This document, a property of the SystemSpecs Limited, cannot be reproduced nor communicated without written authorization.
 Remita e-Collection Integration

S/ CHECKLIST DESCRIPTION SAMPLE SCREENSHOT

N
1 You must have the Remita logo on your site to (Yes) (No) (Not Applicable)
differentiate our payment services from any other
ones you might have.

2 Is the customer aware of the total amount he/she (Yes) (No) (Not Applicable)
will be debited of before loading the payment
page? Always inform the customer duly.

3 Are customers on your website registered? If no, (Yes) (No) (Not Applicable)
then you need to communicate their transaction
reference number to them before they make
payment so that they will have a reference value
in case they have issues with their transactions.

You should send a mail, text or you could print

these details for them on the website with an
eye-catching prompt to notify them.

4 When the payment page loads up, confirm that (Yes) (No)
the amount displayed is correct.

Merchant Name, Signature & Date.

3
Copyright SYSTEMSPECS LIMITED
This document, a property of the SystemSpecs Limited, cannot be reproduced nor communicated without written authorization.
 Remita e-Collection Integration

5 After a transaction had been processed, certain (Yes) (No) (Not Applicable)
information needs to be displayed to the
customer. They include the following
The transaction reference number which
you sent to Remita for that transaction.
The payment reference which is
generated and returned by Remita.

6 There are various response codes that can be (Yes) (No) (Not Applicable)
returned by Remita along with their different
descriptions. The objective here is to ensure that
the customer gets the same description as sent
by Remita. The website should NEVER customize
Remita responses displayed to the customer.

Successful transactions

Successful transaction display

Failed transactions

Failed transaction display

7 It is expected that you have a log of all (Yes) (No) (Not Applicable)
transaction attempts on your website.
When transaction IDs are generated, you are to
log the transaction on that table and update when
the responses returned.
That way, you will be able to determine
transactions status. For transactions that were

Merchant Name, Signature & Date.

4
Copyright SYSTEMSPECS LIMITED
This document, a property of the SystemSpecs Limited, cannot be reproduced nor communicated without written authorization.
 Remita e-Collection Integration

described as pending, you need to have the

means of confirming their status on Remita.
You are to use the Webservice query to do that.

8 It is expected you have a Payment Notification (Yes) (No) (Not Applicable)

Listener URL, which will receive Payment
Notifications sent by Remita. The URL will be http://www.example.com/RemitaPayment
Configured on your Remita profile. Notifications.reg

Merchant Name, Signature & Date.

5
Copyright SYSTEMSPECS LIMITED
This document, a property of the SystemSpecs Limited, cannot be reproduced nor communicated without written authorization.