* Merchant URLS by Acquirer * ** Nedbank Merchants [1] CSC Merchants [2] CBZ Merchants [3] I&M Merchants [4] CIM Merchants [5] [1] https://backoffice.nedsecure.co.za/ [2] https://backoffice.cscacquiring.com/ [3] https://backoffice.host.iveri.com/ [4] https://backoffice.host.iveri.com/ [5] https://backoffice.merchant.cim.mu/

* Settlement * ** /* Purpose - */ This detail information provides the merchant the view based on what they will be settled on based on processed transactions. It also provides a breakdown on what could have been retained by the acquiring bank and what is due to them as the merchant. iVeri will then settle the merchant once the acquirer settles the funds to iVeri. */ Action: /* After the user clicks on settlement, select the date range for the settled transaction. (The image attached should follow on from the image where the user clicks on the ‘settlement’ tab).

Advanced Settings * ** This section documents functionality within the iVeri Gateway that is not enabled by default. Contact your local distributor should you wish to activate one of these settings for your ApplicationIDMerchant Reference validity period See “Duplicate Transactions” (section 7.3.2) for a discussion of this option. Recurring transaction checking * See“Duplicate Transactions” (section 7.3.3) for a discussion of this option. Recon Reference extraction * ReconReference extraction setting is only available for the Nedbank https://distributor.an/ 8 digit ReconReference is sent from iVeri to the acquirer to uniquely identify a transaction. This number is used to query transaction information with the acquirer, and it may appear on the merchant reconciliation statement. By default

Divert – Batch- Upload File * ** / Purpose /* - Used by merchants to upload Divert Batch payment requests to be sent to cardholders. An XML file based specification on how to create Divert Batch can be downloaded from http://forum.iveri.com. / Action: */ On the main menu go to DiVert – Batch – Upload File /Action:/ * Click on Choose File to select the file saved on your directory to be uploaded and Click Submit. This is the message indicate that the file is uploaded.

Network Topology

Network Topology** The generic solution is premised on the following network topologies and depends on whether or not the Indigo Server and/or the POS Server, if it exists, are located inside or outside of the merchant’s location. At the point that a payment by the customer must be made the POS Till or POS Server will, using the protocol described in this document, contact the Indigo Server which will control the appropriate device to prompt for payment from the cardholder. Once the required card details have been collected on the device the Indigo server will process the transaction to the iVeri Gateway before returning a response to the POS Till or POS Server which will then be able to close the invoice created and indicate to the cashier at the POS Till that the invoice has been paid. I

REST API

* REST Endpoints * ** On all endpoints the following applies: Method: Only GET, POST methods are supported Format: JSON Submission of transactions to the correct Gateway endpoint relates to the acquiring bank that holds the merchant agreement. To submit transactions to the iVeri Gateway, merchants can connect to following end points. *Nedbank Merchants:* None [1] https://portal.nedsecure.co.za/ *CSC acquiring bank merchants* None [2] https://portal.cscacquiring.com/ *CBZ Bank merchants:* https:// None [3] portal.host.iveri.com/ *I&M Bank merchants:* https:// None [4] portal.host.iveri.com/ *CIM Merchants* None [5] https://portal.merchant.cim.mu [1] https://portal.nedsecure.co.za/ [2] https://portal.cscacquiring.com/ [3] https://portal.host.iveri.com/ [4] https://portal.host.iveri.com/

Profile Parameters

* Purpose - * To set the Security Parameters for all users in terms of their passwords, validity, suspension, and login notifications. These parameters can only be set by the Back Office Administrator. * Action:  * In the menu bar, click on User Manager, scroll to, and click on Security Configuration. This will bring up the following form on which you can now change the system defaults to suit your own requirements. Please remember that changes made to the defaults will apply to ALL users that you have given BackOffice access to */ Note: /* Strong Password: The default is No. This means that the password can be anything if it is not less than the default minimum length. If you change the default to Yes, then the user’s password must be a combination of alpha/numeric and special characters

Parameter description

* * * Parameter description *** Command * Authorisation * Debit * Credit * AutohorisationReversal * Void* GetData* Cancel* GetHMAC* GetSystemInfo* Parameter* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* Description* AcquirerCode O O O O O The Acquirer ISO code returned for this transaction.  Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription.  This is only made available as extra information and may not exist in all response. AcquirerDescription O O O O O The Acquirer ISO description returned for this transaction.  Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription

Automatic Billing Updater

Automatic Billing Updater* **

User Manager

* Manger the user on your back office Edit User * ** Edit – General details / Purpose /* - To edit/change any of the user information previously captured, or to suspend a user from having access to BackOffice / Action /*: Hover over the users’ profile and select on the user’s icon. Edit%20User%201 [1] Select the Edit button MicrosoftTeams-image%20%282%29 [2] Make the changes on the Users profile and click Save Changes to action the change. MicrosoftTeams-image%20%283%29 [3] Please Note: * To change Password of the user to a new one, select either Change Password or reset Password You can make changes to the Users existing profile. To suspend / disable an users access to BackOffice, navigate to the ‘Enabled’ tab and click on the Radio button. This will suspend / disable the users access. Cl