* Application Parameters * ** */ Purpose /* – This function is used to allocate application ID(s) that a User is only allowed to have access to. This application refers to specific product and what a merchant uses to process transactions through iVeri. Example below indicates that when you select a particular Application ID an Administrator can configure what functions can this user perform in a particular Application ID. If no function is associated to an Application ID, no access is granted to that user. Administrator can configure what Transaction Types a user can perform on a specific Application ID. If no Transaction Types are configured for a user, the user will be unable to process transactions for any of the Application IDs. */ Action /*: Select the product and Live Application IDs

Transaction Lookup * ** / Purpose /* - To lookup the details of a single transaction based on specific search criteria. / Action: /* Click on View then Transaction Lookup / Action: /* Click on the Application ID on which you want to do the lookup e.g., Live or Test / Action: /* Select the Date on which the transaction took place by changing the default date or by clicking on the calendar icon next to the date. If you are not 100% sure of the date, you are able to search in a range of up to + or – 2 days of the date you have selected by changing the 0 default to 1 or 2 in the +/- Days drop down next to the date. You then need to enter either the Transaction Index or the Merchant Reference number. If you do not have either of these numbers you are able to enter either the full credit card nu

DiVert Batch Result File Data Elements * ** The result file data elements described in this section are returned to the merchant when the <CreateTransactionURL> in the “DivertUpload” file is set to “True”. Merchants can use the returned data elements to create and format their own payment request messages and send the requests to their cardholder using their own delivery method i.e. SMS|EMAIL The Divert Batch has the following logic: The <Divert> element can occur multiple times The <DivertItem> element can occur multiple times under a <Divert> element Divert Attributes * Tag Name Length Data Type Format Description Amount <=12 Numeric The sum of the Amount sub-element values of all the <DivertItem> sub-elements Count <=6 Number The number of <DivertItem> sub-elements Divert sub-elements *

Login * ** Purpose * - To log in to the secure BackOffice Website, login credentials are emailed to the merchant during taken on process by the acquirer. Action: * User Group - enter your Billing Details ID User Name - type in Administrator Password - this is the Administrator password sent to you with the Billing Details ID by email. Copy and paste it from the email.

Print Report * ** / Purpose /*- To View/Print/Save reconciliation file for a specific acquirer cycle/settlement period in either: PDF XLS format CSV format / Action: /* Select the menu function Reconciliation then click on Print Report. / Action: /* If you have only one Merchant Card Acceptor ID, simply click on Submit. If you however have more than one, then click on the drop down and select the Card Acceptor ID for which you want the report before you click on Submit. The following screens and points highlight the various parameters that need to be selected before viewing the report. Action: * Select the required Output format – either PDF or XLS. Find the acquirer cycle number you want to view and click on the actual cycle number. You can now choose to either Save the report or to open

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).

How Automatic Billing Updater works * ** Below is a high-level visual representation of how Automatic Billing Updater works:

*iVeri needs to:* Provide 1st line support to the merchant. Provide support on the Back End Admin enquiries . Inform eCommerce 3rd Party on merchants to be onboarded. Onboard the merchant on the Admin Gateway & Cardinal for IYS. Provider merchant with credentials in order for them to add iVeri as their payment processor on their IYS Backend System. * eCommerce 3rd Party needs to: * Set up and Create the merchant on the IYS Platform (Store ID). Provide 2nd line support. Address technical queries that the merchant may have. * Merchant needs to: * Sign in and Set up their Online Store Configure and enable iVeri as the Payment processor using the iVeri provided store credentials Send iVeri their Store ID in order for iVeri to complete the onboarding