This document details the functionality available in Backoffice for DiVert merchants. The merchant interface (URL) to be accessed depends on the acquirer in which the merchant has an agreement with.

*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

Transaction – Subsequent Transaction * ** Purpose * - To take further action on a transaction which has already been successfully processed. You can convert an Authorisation to a Sale or process a sale Refund. Image [1] Action: * Click on the appropriate Application ID in which you can view transactions that have been processed. Once the transactions details are displayed you, perform refunds, or do a debit Image [2] Action: * Select the Date on which the original transaction took place from the drop down menu or select a period if you are not sure of the exact date and click on Search. This will bring up a summary list of all the transactions which match your search selection. Image [3] Action:  * Scroll through the summary list until you find the transaction you want to take the action o

*Transaction – Subsequent Transaction* ** * Purpose * - Subsequent transactions allow a user with the correct permissions to further action a transaction that has been successfully processed. For example, a user can change the transaction type from an Authorisation to a Sale or from a Sale to a Refund. Action: * From the menu, select *Lite - Transactions - Subsequent Transactions.* * Action: * Click on the appropriate Application ID in which you can view transactions that have been processed. Once the transactions details are displayed you, perform refunds, or do a debit *Action:* Select the Date on which the original transaction took place from the drop down menu or select a period if you are not sure of the exact date and click on Search. This will bring up a summary list of all the tran

Transaction -View – Authorisations ** * Purpose * - To view the transactions for which you originally only obtained an Authorisation. This allows you to now use that Authorisation code to Debit the cardholder by doing a Subsequent Transaction [1]   to debit the cardholder and obtain the money in your bank account. * Action: * In the menu bar, Select Lite, Transactions, View Authorisation. Click on the Application ID you wish to view Authorisations. Select the Date or Date range and click on Search. A list of transactions will be displayed *Choose a date *and select *Search* * Action: * This will give you the below screen reflecting the details of the Authorisation for either viewing of the details or you can print this page for use at a later stage. [1] /knowsystem/subsequent-transactions-

* View – Transactions History * ** * Purpose *- To view a list of all transactions performed for a selected Date or Period. * Action: * In the menu bar, Mouse over mPress, Transactions, View, Transaction History. Click on the Application ID you wish to view Transactions. If you only have one Application ID, this page will NOT be displayed, and you will be automatically taken to the Choose Date/Period page. Select the Date or Date range and click on Search. This will bring up the list of ALL transactions performed for your selection. Choose a specific Application ID Choose a date range to start your Search * Action *: Allows you to get details pertaining to a specific transaction – available when clicking on the actual transaction detail. Once edit is selected click on submit to continue th

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

* Enterprise Introduction  *** The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd provides proven credit card payment solutions for businesses that have online or physical presence. The use of Enterprise API's is ideal for merchants that want complete control & flexibility of the payment page and transaction mechanisms supported. Enterprise API’s currently support the following Webservices REST SOAP */Merchant Requirements/* Merchants are required to enter into a “Agreement” with an authorised Acquiring Institution. Once there is a merchant agreement in place, a merchant profile can be created With Enterprise calls to the Gateway, the presence of a certificate ID is required, with the actual physical certificate available as optional means to authentica

Iveri Lite is a redirect hosted payment page solution, for card-not-present transactions, designed to facilitate secure and efficient e-commerce payments on merchant websites. A website developer in the iVeri Merchant BackOffice can configure the look and feel of the secure payment page that is hosted by the iVeri Payment Gateway.

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