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

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-

* *This section explains how to implement a follow up/subsequent transaction using the TransactionIndex returned from an initial/previous transaction processed successfully. Merchants that wish to accept payments from regular customers without worrying about PCI DSS burdens of storing or retaining the card number have an option of submitting a unique identifier associated with the customers card number from a previously successfully processed transaction. In iVeri's realm, the identifier which the merchant can pass on subsequent transactions is called the “TransactionIndex”. This variable is an iVeri Gateway generated identifier commonly found in Gateway responses to the merchant.

*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

* 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

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. 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 transactions which match your search selection. Action:  * Scroll through the summary list until you find the transaction you want to take the action on. To make sure that it is the

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

* Subsequent Transaction * * / Purpose /* - Subsequent transactions allows a user with the correct permissions to further action a transaction that has been successfully processed. You can change the transaction type to Authorisation to a Sale or a Sale to a Refund. / 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 transactions which match your search selection. */ Action:  /* Scroll through the summary list until you find the tran

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.

* 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 DiVert, 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 View%20-%20Authorisations%201 [2] View%20-%20Authorisations%202 [3] Choose a date and select Search View%20-%20Authorisations%203 [4] View%20-%20Authorisations%204 [5] [1] http://www.iveri.co.za/knowsystem/subsequent-transaction-151?enable_editor [2] /web/image/