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)


Administrator Password Reset


Administrator Password Reset


Purpose – This is used when an Administrator would like to reset their existing password.

Action:
From the menu, select the Administrator area and choose the option to change password.
It is recommended that you use Alphanumeric and Special characters to ensure the password strength meter indicates a strong password.

Save Changes once completed




 


Add User


 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.



Subsequent Transaction


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

Once edit is selected click on submit to continue the refund on the particular transaction. As you can see the transaction automatically goes to refund.

If this was an Authorisation transaction, under transaction type, you could also use this subsequent transaction option to authorize (Bank) the Authorized transaction by selecting Authorize Sale under Transaction Type




Application Parameters


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.


View – Authorisations


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




Choose a date and select Search


Create Transaction Request


Create Transaction Request

 
Purpose - This function allows you to create a request for payment to be sent to cardholder

Action:
On the main menu bar, select the DiVert menu, Select Transactions and click on Create Transaction Request. 

 
Action:
Select the relevant Application ID. A Capture Transaction screen will be displayed



Action:
Complete the details on the capture page and click Submit. A resultant page will then be displayed.



Once completed the Submit button is selected and the below Pop up screen will be displayed.





Service Functions


Service Functions


Purpose – Based on the functions that the user has been granted on a particular product these parameters determine the functions to be made available pertaining to the product access a user has.

Action:
Tick on the relevant functions a user is enabled to perform within Backoffice for a particular product.

Save Changes once completed.


Report – DiVert Trading


Report – DiVert Trading

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

Action:
In the menu bar, select DiVert, Transactions, View All Authorisation. Click on the Application ID you wish to view Transactions. This will bring up the list of ALL transactions performed for your selection.
Purpose - To print a report of processed transactions on a specific Application ID. 

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



Choose a date and from the user tab, please select from the dropdown ‘All’. This will ensure that the report extracted will include all users who have created transactions.


Choose the applicable form to download the  Trading’ report on a particular Application ID




Dashboard


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.


Service Parameters


Service Parameters


Purpose - To allocate the functions within BackOffice in which you (the Administrator) want to allow the new user to have or not have access to


Action:
Select Users, select a particular user, and then select Service Parameters, based on the products used by the merchant choose Yes or No to a particular access rights and limits.
Save Changes once done.



DiVert


DiVert 


DiVert is an instant remote payment solution for Merchants processing Card Not Present transaction requests to cardholders that utilise their services.

How does DiVert work?

A client receives an e-mail request with a link. When clicked, the client is redirected to a secure payment page where a payment is made.


Welcome Page


Welcome Page


Purpose - Reflects who is logged in and provides the menu options which the logged in user is able to access or use.




Edit User


Edit User


Edit – General details 

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

Action:
Hover over the users’ profile and select on the user’s icon. 

Select the Edit button


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


Please Note: 
To change Password of the user to a new one, select either Change Password or reset Password 
You can make changes to the Users existing profile. To suspend / disable an users access to BackOffice, navigate to the ‘Enabled’ tab and click on the Radio button. This will suspend / disable the users access. Click on the Save Changes to action the changes.


Merchant URLS by Acquirer



View – Pending


View – Pending


Purpose - view the list of Pending transactions for a selected Date or Period in order to check these against your confirmation emails or to view ALL details related to individual transactions.

Pending Transactions may result, where a transaction request was created, but payment has not yet been actioned by the cardholder. 
The user is able to view pending transactions as a means to follow up with a cardholder.

Action:
In the menu bar, select DiVert, View, and then select Pending.


Choose an Application ID



Choose a Date Criteria and select Search


Action:
Click on Cancel to delete the transaction or Edit to change the cardholder email address.


View - Successful


View - Successful

 
Purpose - To view the list of Successful Transactions’ for a selected Date or Period in order to check these against your confirmation emails or to view ALL details related to individual transactions.

Action:
In the menu bar, Select DiVert, Transactions, View Successful. Click on the Application ID you wish to view Successful Orders for. Select the Date or Date range and click on Search. This will bring up the following pages for viewing.



Choose a date and select Search

The Administrator or users who have been granted the necessary access will be able to view all successful transactions for ALL users.


Action:

If a user wants to view the details (above) of the transaction, edit is selected to see more information pertaining the transactions




Login


Login

Purpose - To log in to the secure BackOffice Website, login credentials are emailed to the merchant during taken on process by the acquirer.


 
Action:

  • User Group - enter your Billing Details ID
  • User Name - type in Administrator
  • Password - this is the Administrator password sent to you with the Billing Details ID by email. Copy and paste it from the email.


View – All 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 DiVert, 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.


 


Download by File


Download by File

Action:
On the main menu go to DiVert – Batch – Download File – By File 




Action:
Select the Date range, click “Search”; Click on the File name, the file will start downloading

 


Profile Parameters


Profile Parameters

 
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.


Transactions


Transactions

 



The below section allows the merchant to configure their website URL Link that holds the terms and conditions. When the merchants URL Link is configured, the terms and conditions can be viewed by the client on the payment page and must be accepted before submitting the payment.


 
NOTE: Once the client reads through the terms and conditions, they would be required to select a tick box on the payment page and acknowledge before completing a payment online.


Merchant Interface Functionality


Merchant Interface Functionality

 


Reset Password


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.



Reconciliation


Reconcilation

 



Visa Checkout


Visa Checkout

 

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.


 



Settlement


Settlement

Purpose - This detail information provides the merchant the view based on what they will be settled on based on processed transactions. It also provides a breakdown on what could have been retained by the acquiring bank and what is due to them as the merchant. iVeri will then settle the merchant once the acquirer settles the funds to iVeri.


Action:
After the user clicks on settlement, select the date range for the settled transaction. (The image attached should follow on from the image where the user clicks on the ‘settlement’ tab).




Configure Application


Configure Application

Purpose - TConfiguring your application is important. Configuring your application needs to take place before a user is able to create a transaction request. The user would need to configure: 

  • If E-mail confirmations can be sent to a cardholder. 
  • Confirm the E-mail address confirmations are sent to and from.
  • Receive a copy of the payment request that has been sent to the cardholder.
  • Customise the message on payment page.
  • Customise the message on payment request e-mail.
  • Link Merchants Terms and Conditions
  • Show Associated Logos

To make the relevant changes, click on Save Changes.

Action:
On the main menu go to DiVert – 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.


 



Transaction Lookup


Transaction Lookup

 
Purpose - To lookup the details of a single transaction based on specific search criteria.

Action:
Click on View then Transaction Lookup


Action:
Click on the Application ID on which you want to do the lookup e.g., Live or Test



Action:

Select the Date on which the transaction took place by changing the default date or by clicking on the calendar icon next to the date. If you are not 100% sure of the date, you are able to search in a range of up to + or – 2 days of the date you have selected by changing the 0 default to 1 or 2 in the +/- Days drop down next to the date. 

You then need to enter either the Transaction Index or the Merchant Reference number. If you do not have either of these numbers you are able to enter either the full credit card number or a partial (first four numbers …….. last four numbers) AND the amount. Click on search.


The result/s (summary) will be displayed on screen. Click on the summary of the transaction to obtain all the details pertaining to the selected transaction.


DiVert BackOffice User Guide


DiVert BackOffice User Guide

 
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.


Transaction History


Transaction History

Purpose -To obtain a list of transactions for a selected calendar period reflecting all the result details for each in XML format.


Action:
Click on View then Transaction History