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.

Merchant URLS by Acquirer

 Nedbank Merchants

CSC Merchants

CBZ Merchants

I&M Merchants

CIM Merchants

Purpose - The 'Active Session' tab reflects who is logged in and provides the menu options which the logged in user is able to access or use.

 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.

Edit User

Purpose - To edit/change any of the user information previously captured, or to suspend a user from having access to BackOffice

Action:
From the main menu the user will navigate to "User". Hover over the users’ profile you would like to edit and select the user’s icon. 

Action:

Select the "Edit" button. 

Please Note: 
To change Password of the user to a new one, select either "Change Password" or "Reset Password".

Make the changes on the Users profile and click Save Changes to action the change.

Please note:
User profiles cannot be deleted but can be disabled by the Administrator. To do this, the Administrator needs to click on the "Enabled" radio button, which will change the status to disabled.

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 you as an Administrator would like a user to access and configure per product, the Transaction types a user can access by ticking the applicable box under Transaction Types.

Save Changes once complete.

Reset Password

Should a user have forgot their login password to BackOffice, navigate to the ‘Forgot your password?’ link.

The system will request you to enter your User Group / Merchant Profile ID and Username.

Once the user clicks on submit, a notification will appear that the user will receive an e-mail notification. The e-mail notification will contain a link that the user will access to change their password.

Now that the user has clicked on the link, they will be redirected to the BackOffice Reset Password page. Enter and confirm the new password. Lastly to action the new password change, click on Reset Password tab.

The following notification will appear on a successful password change.

Dashboard

Purpose – The dashboard provides the Merchant with a summary or snapshot of Sales, Transactions and Transaction statuses within a set period of time. Depending on the needs of the Merchant, the dashboard is customisable by dragging and dropping the relevant widgets on the dashboard.

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

Transaction -View – PayPal & Interbank Transactions

Should the merchant be processing the following transactions these tabs are also available for the merchant to view and search these transactions.

Transactions - View – All Transactions

Purpose - To view a list of all transactions performed for a selected Date or Period. 

Action:
In the menu bar, select Lite, Transactions, View, All Transactions . Click on the Application ID you wish to view Transactions. This will bring up the list of ALL transactions performed for your selection.

Report – Lite Trading

Purpose - To print a report of processed transactions on a specific Application ID. 
Action:
In the menu bar, select Lite - Transactions - Reports - Trading Report. Click on the Application ID you wish to view Transactions. 

Choose a date and select Search. This will bring up the list of ALL transactions performed for your selection.
Transactions details for the last 6 months are available.

Choose the applicable file format to download the trading report on a particular Application ID

Transaction – Payment

Purpose - This function allows you to pass a credit to any card without having a previous debit transaction. There is a limit to the amount that you can process a credit transaction for. Please speak to your Acquirer to obtain this limit.
Action:
On the main menu bar, Click on Lite – Transactions – Payments , select the relevant Application ID. A Capture Transaction screen will be displayed.

Once the an application ID is selected, the system will allow you to manually capture and do the transaction, however this would require all the card details to be inputted and the set limits to be adhered to.

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 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 correct transaction, click on the Details button on the right to bring up the full details of the transaction. To complete the subsequent transaction process click on the 'Do Subsequent' tab.

Action: 

The subsequent transactions form pop-up will appear. As you can see the transaction automatically changes the transaction to refund. The user can click on the 'order basket' tab. 

Action:

The user would now select the line item they would like to refund, by ticking the checkbox. Click on the 'Confirm' tab once the selection has been made.

Action:

The 'Transaction Details' pop window will appear. To complete the subsequent transaction, the user will click on the 'Do Transaction' tab.

The following result page will appear confirming that the subsequent transaction was successful.

Configure Application

Purpose - To receive e-mail confirmations after processing successful transactions and to set-up your transaction viewing preferences, you will now need to set up your choice of transaction configuration.

Action:
On the main menu go to Lite – Configure Application.

Action:
Click on the Application you want to configure, i.e., either the Test or the Live. Make the relevant changes and click on Submit

Below are some of the details a user would need to configure under Application settings:

• E-mail confirmations can be sent to a cardholder. 
• Confirm the E-mail address confirmations are sent to and from.
• Customise the message on the payment page.
• Customise the message on payment request e-mail.
• Copy or Link Merchants Terms and Conditions
• Show Associated Logos
  

To make the relevant changes, click on Save Changes.

NOTE: 

The Administrator can configure specific user email addresses to receive confirmation emails when payments are made by cardholders. Here’s how:

Send Email Confirmation to the User Who Created the Request: Enable this option to allow the user created by the Administrator to receive transaction confirmation emails.
Send Email Confirmation to a Different Address: Alternatively, enter a different email address in the provided text field to receive transaction confirmation emails.
Send Email Confirmation to the Cardholder: Enter the email address where the cardholder's transaction confirmation emails should be sent.
Customizing Payment Request Messages

Customize the payment request message sent to the cardholder. Ensure not to alter the content between the $ signs.

Preferred Payment Method Selection

Merchants with multiple payment methods can select a default option from the list, such as Visa Checkout, MasterPass, or Card Payments.

Registering for Visa Checkout

To start accepting e-wallet payments via Visa Checkout, follow these steps:

Navigate to the “Transaction Viewing Layout” section.
Click on the “Reset Transaction Viewing Layout” dropdown.
Select “Visa Checkout Management.”
Click the “Submit” button.
A new page will display, where you can fill in the required fields and submit the form.

Important Note:
Merchants must notify their Acquiring Bank to enable Visa Checkout. This step is crucial for the activation process.

Linking Terms and Conditions: 
The merchant can now be able to configure terms and conditions to be set and agreed by the cardholder upon making a payment. This is done by inserting a URL link where the merchants’ terms and conditions are found or type out the Terms and conditions.

Customize Details

Purpose:
Configuring your application is important. Configuring your application needs to take place before a user can process transactions. Lite users need to configure and customise the details pertaining to:

• Order Basket
• Card Holder details
• Transaction Details 
• Billing and shipping details
  

Note:The fields that are ticked and greyed out are mandatory fields that cannot be configured. 

The merchant can configure the fields that they feel are applicable  and determine whether the fields require a prompt for input for the cardholder, appear on the invoice and/or show on the order details.

How you want the basket details to look like on the payment page.

Purpose - This configuration allows you to compile a list of credit card numbers that you wish to decline. Before forwarding any transaction to the bank for processing, the iVeri gateway will check this list. If a card number matches one on your list, the transaction will be instantly rejected. The reasons for adding card numbers to this list are determined by each merchant individually and will only result in rejections by your business.

Action: 
from the main menu, navigate to: Configure - Black card List.

Action:
If you have more than one Application ID and want to capture the card number to be blocked for all your applications, click on Go next to All Applications at the top. If not, then click on the Application ID in the bottom section and the next page will be displayed.

Action:

Enter the credit card number you wish to add to your Black Card List and click "Add." This will include the card number in your list. If you have multiple numbers to add, input each one and click "Add" after each entry. Once finished, click "Submit" to save your entries.

To search for a number, type it in and click "Search" to check if it’s already on your list. If the number is found, it will be highlighted. To remove a number from your list, enter the number, click "Search," and when it is highlighted, click "Remove." Then, click "Submit" to save the change (removal).

Purpose - To set the Security Parameters for all users in terms of their passwords, validity, suspension, and login notifications. These parameters can only be set by the Back Office Administrator. 

Action: 
In the menu bar, click on User Manager, scroll to, and click on Security Configuration. This will bring up the following form on which you can now change the system defaults to suit your own requirements. Please remember that changes made to the defaults will apply to ALL users that you have given BackOffice access to

 
Note:

• Strong Password: The default is No. This means that the password can be anything if it is not less than the default minimum length. If you change the default to Yes, then the user’s password must be a combination of alpha/numeric and special characters also not less than the default minimum length.
• Minimum Password Length: The default is 6. You can change it to any higher number. If you do then this number will apply to ALL users.
• Strong Username: The default is No. This means that the username can be anything if it is not less than the default minimum length. If you change the default to Yes, then the username must be a combination of alpha/numeric and special characters also not less than the default minimum length.
• Minimum Username Length: The default is 4. You can change it to any higher number. If you do then this number will apply to ALL users.
• Enforce Password Change: The default is No. This means that users will never be forced to change their passwords. If you change the default to Yes, then all users will have to change their passwords in accordance with the Password Change Frequency that you set next.
• Password Change Frequency (days): The default is 60 days. This default is only valid if you change the Enforce Password Change default to Yes. If you do this then you can also change this number of days default to a longer period.
• Auto Suspend Users: This is used to automatically suspend a user from accessing Back Office after a set period. The default is No. If you want to suspend ALL, the users after a certain period of time then change the default to Yes.
• Auto Suspend After Period (days): The default is 60 days. This default is only valid if you change the Auto Suspend Users default to Yes. If you do this then you can also change this number of days default to a longer period.
• Login Notification to Administrator: This is used if the Administrator wants to know every time a user logs in to Back Office. The default is No. Simply change this to Yes and the Administrator will be notified by email every time a user logs in to Back Office.
• Keep Password Unique: This is used to set the period after which a user can use the same password again. The default is One Time. What this means is that when a user’s password expires after the default period of 60 days or the new period set by the Administrator, the user will have to enter a new password in accordance with the relevant settings above. They can then use their original password again after this period has expired. If you want the period longer before a previous password can be used again, select one from the drop down If you select Always, then the user will have to choose a new password every time their password expires.
• After changing any of the default settings above, click on Save to effect your changes. The Administrator can change any of the above at any time.
  
  

Visa Checkout Merchant Take-On 
Merchants can also register for Visa Checkout to start accepting e-wallet payments from cardholders. To register merchants can mouse to the “Transaction Viewing Layout” section click on the “Reset Transaction Viewing layout dropdown, select “Visa Checkout Management” click the “Submit” button. A new page will be display and the merchant can be populating all the fields displayed on the below screen and Submit. 

NB: The merchant will also need to notify the Acquiring bank that they need to be enabled for Visa Checkout.