Print Report – Batch Summary * ** Purpose -  *To View/Print the report of a processed batch in either PDF – Downloadable PDF View or XLS – Excel Spreadsheet formats. This function will produce a report summarizing the transactions by Result Description in the selected batch. Action: * From the main menu, the user will navigate to Batch - Print Report - Batch Summary*. Action: * The user will select the applicable Application ID. Action: * Determine the date range for the search criteria you wish to retrieve. Action: * Select the file format you wish to obtain from the drop down (either the default PDF, CSV or XLS) and then select the file from the list which you want to download and click on Print. This will bring up the following screen. The Print Button will start an automatic download t

Create Batch * ** Purpose * - To create and upload a batch file for processing in BackOffice, the system will automatically generate both the header and trailer records in compliance with iVeri standards. Action: * From the main menu, the user will navigate to: Batch - Create Batch.* Action: * The user will select the applicable Application ID. Action: * Select ' New transaction'* in order to start capturing your own batch entries. Action: * After capturing each transaction, select "Save." Repeat this process until all the transactions you want to process have been captured. NOTE: * Merchant Terminal *– The default is BATCH. If you want to sort your transactions in the Transaction Details Report, you can allocate your own terminal number for each transaction by deleting the word BATCH and

* Development phase * ** At this stage you will proceed with development based on the integration method [1] you have selected, and may reach out for your contact at the acquiring bank if you require support. [1] /knowsystem/general-requirements-10

View Batch * ** Purpose * - To view the status of batches that have been uploaded for processing and view any errors / failed transactions in a completed batch. Action: * From the main menu, the user will navigate to: Batch - View Batch.* Action: * The user will select the applicable Application ID. Action: * The user will select the date range for the Batch they would like to view. Action: * The user will now be able to view the Batch for the selected date range. To view any errors within the Batch or applicable to a specific transaction, the user can click on the "Errors".

Print Report – Batch Details * ** Purpose *- To view a list of all transactions performed for a selected Date or Period. Action: * In the menu bar, Select Batch - Print Report - Batch Details.  * Action: * The user will select the applicable application ID. Action: * The user will select the Date range and click on Search. This will bring up the list of ALL transactions performed for your selection. Action:  * Select the file format you wish to obtain from the drop down (either the default PDF, CSV or XLS) and then select the file from the list which you want to download and click on Print. This will bring up the following screen. The Print Button will start an automatic download to your PC.

3D secure transaction process flow * ** Cardholder is on the merchant’s checkout page, ready to pay for their order. They will input and submit their card details on the payment page hosted by the Gateway. The Gateway will proceed to check if the card in use is enrolled in 3DS by sending a request to the Directory Server. Directory Server will respond with enrollment status. Considering the response is positive and the card is enrolled for 3DS,  The Gateway will redirect to the issuer ACS for authentication The ACS will prompt the cardholder to insert and submit OTP/Password/credential(etc.) Considering the authentication was successful, the response is returned to the gateway to confirm successful authentication Gateway then forwards the transaction details to the acquirer for authorizati

*Registering as a merchant * ** Merchant account can be attained by registering with an acquiring bank, a list of which can be found on this page [1] [1] /knowsystem/distributors-contact-information-33

* iVeri Lite Process Flow * ** iVeri Lite requires very little integration and is aimed at Internet merchants who have limited technical resources. Lite transactions are processed on a web site and secured via an SSL certificate without the merchant having to buy SSL since iVeri lite takes care of it on their behalf. Although ideal for websites with small catalogs, iVeri Lite still provides a powerful processing engine. */ Process Flow /* This diagram illustrates the flow of events of an iVeri Lite transaction: /*Process Flow Description:*/ (1) The cardholder is at the point in the purchase process where the basket has already been selected and he is now on the brink of paying for it. The website thus knows the price of the basket, the Invoice Number (the merchant could also have iVeri Bac

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

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