The merchant portal Backoffice allows for the following core functions: Management of User Creation of users Transaction Types allowed per user created Backoffice functionality views allowed Applications permitted on a user created Transaction Reports & Listing & Lookups Reconciliation  Reports Blacklisting of cards Customise payment request page with Merchant’s Corporate Identity. Create Transaction Requests Process Subsequent Transactions (Refunds)

Additional Variables * ** Note: *These are form variables that are not part of the iVeri Lite specification but may be required by the merchant. These form variables (if used) will be returned to the website together with all the iVeri Lite form variables. For added security, to prevent possible fraud by someone obtaining the websites return URL and parameters, we highly recommend that you submit an additional form variable of arbitrary name chosen by the merchant and random value which changes from transaction to transaction. This will be returned to the website along with all the iVeri Lite form variables and all you need to do is check for the existence of the form variable and that the value thereof is the same as that generated and used during the submission of the iVeri Lite page

Initial Transaction * ** When a merchant sends a transaction request(POST) to the iVeri Gateway, the response returned to the merchant generally contains a number of variables, some of which are important when performing subsequent transactions, in order for the merchant to implement subsequent transactions the following variables must be stored on the merchants database. Lite_TransactionIndex Ecom_Payment_Card_Number  Ecom_Payment_Card_ExpDate_Month  Ecom_Payment_Card_ExpDate_Year

Delete Code * ** Function: Delete a code that has been created Delete Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be deleted Response Parameter Description MasterPassAction The action that was performed Delete Code – REST Sample * Request Response { "Version" :  "2.0" , "CertificateID" :  "{xxxxxxxx-71dd-4044-802d-xxxxxxxxxxxx}" , "ProductType" :  "Enterprise" , "Direction" :  "Request" , "Enquiry" : { "ApplicationID" :  "{xxxxxxxx-68e0-42eb-aba9-xxxxxxxxxxxx}" , "Mode" :  "Live" , "command" : "MasterPassQuickResponseCode" , "MasterPassMerchantID" :  "xxxxx" , "MasterPassAction" :  "DeleteCode" , "MerchantRefer

* Full Redirect – Hosted Payment Page *** An example is available online on None [1] this link [1] https://examples.iveri.net/Example/Setup

* *Below is the contact information per distributor for registering billing and banking details with iVeri. An iVeri Distributor markets the services of the iVeri Gateway and products within a locality. Nedbank South Africa * *Location*: South Africa *Telephone*: 0860 114 966 *Websites*:  http://www.iveri.co.za/ [1]    |  http://www.nedbank.co.za/ [2] *Email*: ·        Technical Assistance  operations@iveri.com [3] ·        Non-technical requests/questions (e.g. costs, agreements, product information etc):  info@iveri.co.za [4] Nedbank Namibia * Location*: Namibia Websites*:  http://www.iveri.co.za/ [5]    |  http://www.nedbank.co.za/ [6] Email*: ·        Technical Assistance  operations@iveri.com [7] ·        Non-technical requests/questions (e.g. costs, agreements, product information et

The dashboard offers merchants a comprehensive overview* of their sales, transactions, and transaction statuses within a specified time frame. It serves as a real-time snapshot* of business performance, enabling merchants to quickly assess key metrics and trends. To cater to different business needs, the dashboard is fully customizable*. Merchants can drag and drop* various widgets to tailor the layout, ensuring that the most relevant data is easily accessible. This flexibility allows merchants to focus on the insights that matter most to their operations, such as daily sales trends, payment success rates, or transaction volume breakdowns. Dashboard [1] [1] /web/image/326767-f761d26c/Dashboard.png?access_token=da5ebf47-b586-4a1d-bbda-0b5c23a585a3

DiVert Functionality * ** The Divert API has a parameter “CreateTransactionUrl” that can be set to either “True or “False”. The value set determines how the Gateway handles and processes the message request. Scenario 1 * If CreateTransactionUrl” is set to“True” - the Gateway generates a transaction URL and makes a callback to the merchant with the URL. The merchant can then construct and format their own message, including the URL (returned by the Gateway) and distribute the message to their cardholder using either SMS|Email When the cardholder receives the messages, it will have all the particulars of the merchant, the cardholder can then click on the URL, and be redirected to a payment page wherein they can make a payment to the merchant Scenario 2* If CreateTransactionUrl is set to “Fal

Acquiring Bank * Gateway Address* Nedbank Merchants https://portal.nedsecure.co.za/ [1] CSC acquiring bank merchants https://portal.cscacquiring.com/ [2] CBZ Bank merchants https://portal.host.iveri.com/ [3] I&M Bank merchants https://portal.host.iveri.com/ [4] CIM Merchants https://portal.merchant.cim.mu [5] [1] https://portal.nedsecure.co.za/ [2] https://portal.cscacquiring.com/ [3] https://portal.host.iveri.com/ [4] https://portal.host.iveri.com/ [5] https://portal.merchant.cim.mu/

Subsequent Transactions implementation * ** On the request to the Gateway, the merchant developer has to pass all the required variables that pertain to a subsequent transaction so as to make sure that the iVeri Gateway handles the request appropriately. Variables that should be present in the request to the iVeri Gateway are as follows: The Lite_PanFormat must be set to TransactionIndex  Set the Lite_TransactionIndex to the actual TransactionIndex value e.g {000000-000000- 000-0000 0000000}  Set the Ecom_Payment_Card_Number to the Dotted PAN value Note:* These variables are defined in 8.2 iVeri specification. In addition to these the merchant will still need to pass all the other required variables.