* 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/
Add User * **
/ Purpose /* - To add/capture the details for a new user
/ Action /*:
Hover over to Users. The following screen will appear.
Select “Add New User” Fill in all the mandatory fields (marked [*]) and click on “Save changes”. A resultant message will be displayed.
Add User * **
/ Purpose /* - To add/capture the details for a new user.
/ Action /*:
Hover over to Users. The following screen will appear.
Select “Add New User”. Fill in all the mandatory fields (marked [*]) and click on “Save changes”. A resultant message will be displayed.
*Authentication - Manage client certificate*
**
* Purpose * – This is important so that the iVeri gateway uses this certificate to authenticate the merchant processed transactions.
* Action: * In the menu bar, Select
Authentication
, Manage Client Certificates.
Select New Certificate, once the merchant has captured their own client certificate it should appear as indicated.
Complete your merchant details on the screen below and select Submit.
Download the certificate and save it into your local environment, by clicking the "Download" tab.
*Please Note: *
After a period of time the certificate would need to be renewed as it will expire, after which the merchant must select Renew in this menu item .
Add User * **
/ Purpose /* - To add/capture the details for a new user
/ Action /*:
Hover over to Users. The following screen will appear.
Select “Add New User” Fill in all the mandatory fields (marked [*]) and click on “Save changes”. A resultant message will be displayed.
Core Functions in Backoffice*
**
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 Recon Reports Blacklisting of cards Customise payment request page with Merchant’s Corporate Identity. Create Transaction Requests Process Subsequent Transactions (Refunds)
* LiteBox Hosted Payment Page *
**
The LiteBox hosted payment page is an e-commerce solution that allows merchants to connect, send payment requests to the iVeri Payment Gateway without redirecting the cardholder away from their website. When implemented, the LiteBox pops up and sits in-front of the merchant’s website. From a merchant/cardholder point of view the LiteBox solution provides a more seamless checkout experience.
An example is available online on None [1] this link . To simulate the LiteBox behaviour, click on “Modal”.
Merchants’ developers can download the JavaScript library that handles the events to generate the button. The library can be found on the following URLs:
For Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland: https://p
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
Airline addendum data
**
Airline addendum data is additional transaction data which appear on a card holder's statement when buying a ticket from an airline merchant who include this data in a transaction request. Airline addendum data is currently only available for Nedbank. In addition, the airline addendum data is currently only supported for follow-up debit (pre-authorised debit) transactions.
Coding for Airline addendum data *
The following is a code snippet in C#:
enterprise.openElement("AirlineData");
enterprise.setTag("PassengerName", passengerName);
enterprise.setTag("PrimaryTicketNumber", primaryTicketNumber);
enterprise.setTag("FirstDepartureLocationCode", firstDepartureLocationCode);
enterprise.setTag("FirstArrivalLocationCode", firstArrivalLocationCode);
enterprise.setTag("PNR