Divert Backoffice User Guide - Payment Technology · Purpose - To log in to the secure BackOffice...

Divert Merchants

a

Divert Backoffice User Guide

p. 1

DivertBackofficeUserGuide

www.iveri.com iVeri – At the Heart of Transactions

Table of Contents

1 Overview .......................................................................................................................................................................... 5

1.1 Merchant URLS by Acquirer .................................................................................................................................. 5

1.2 Requirements for using Divert .............................................................................................................................. 5

1.3 Customising the Divert Payment Page .................................................................................................................. 5

2. Merchant Interface functionality .................................................................................................................................... 6

2.1 Login .......................................................................................................................................................................... 6

2.1.1 Reset Password .................................................................................................................................................. 6

3. Welcome Page ................................................................................................................................................................ 7

4. User Manager ................................................................................................................................................................. 8

4.1 Add User ............................................................................................................................................................... 8

4.2 Edit User ................................................................................................................................................................ 9

5. Divert ............................................................................................................................................................................ 17

5.1 Transactions – Create Transaction Request........................................................................................................ 17

5.2 Transactions – View – Pending ........................................................................................................................... 19

5.3 Transactions – View - Successful ........................................................................................................................ 20

5.4 Transaction -View – Authorisations .................................................................................................................... 22

5.5 Transactions - View – All Transactions ................................................................................................................ 23

5.6 Transactions – Reports – DiVert Trading ............................................................................................................ 25

5.7 Transaction – Subsequent Transaction ............................................................................................................... 25

5.8 Divert – Batch- Upload File ................................................................................................................................. 28

5.9 Divert – Batch – Download File ........................................................................................................................... 28

5.10 Divert- Batch-View Batch .................................................................................................................................. 30

5.11 Configure Application ....................................................................................................................................... 31

5.12 Customise Transaction Form ............................................................................................................................ 33

6. Reconciliation ............................................................................................................................................................... 35

6.1 Print Report ........................................................................................................................................................ 35

6.2. Download Reconciliation ................................................................................................................................... 36

7. Black Card List ............................................................................................................................................................... 38

8. View .............................................................................................................................................................................. 40

8.1 Transaction Lookup ............................................................................................................................................. 40

8.2 Transaction History ............................................................................................................................................. 41

8.3 Info ...................................................................................................................................................................... 42

p. 2



9. Security ......................................................................................................................................................................... 43

9.1 Change Password ................................................................................................................................................ 43

9.2 Logout ................................................................................................................................................................. 44

p. 3



Version History

Version Description

19-10- 2016 Added VisaCheckOut as payment method and for merchants to register

for Visa Checkout in 5.11 “Configure Application” section

19-10-2016 Added functionality that allows merchants to choose a preferred “Default

Payment Method in 5.11 “Configure Application”

26-01-2017 Added MasterPass as a payment method in Divert in 5.11 “Configure

Application”

20-03-2017 Updated the document to include DivertBatch functionality

13-04-2018 Added notes that relate to an email address that can be captured for a user

to receive confirmation emails when a payment is received from the

cardholder – page 31

20-05-2019 Included additional options for customising the payment page

Added the Requirements for using Divert

Added the Backoffice portal URL for CIM merchants

31-07-2019 Added I&M merchant URL

p. 4



p. 5



1 Overview

This document details the functionality available in Backoffice for Divert merchants. The merchant portal (URL) to be

accessed depends on the acquirer in which the merchant has an agreement with.

1.1 Merchant URLS by Acquirer Nedbank Merchants: https://backoffice.nedsecure.co.za

CSC Merchants: https://backoffice.cscacquiring.com

CBZ Merchants: https://backoffice.host.iveri.com

I&M Merchants: https://backoffice.host.iveri.com

CIM Merchants https://backoffice.merchant.cim.mu

1.2 Requirements for using Divert

1.2.1 Configuration of the Application ID

Before creating a payment request to your clients, the LIVE Application ID must be configured with following

information: The configuration of the Application ID is discussed from page 31.

o Email address of the merchant in which transaction confirmation emails will be delivered into

o Association logos to be displayed on the Divert Payment Page must be selected

o Configuring the content that will be on the Divert Payment request mailer

1.3 Customising the Divert Payment Page Merchants have the capability to customise the payment page to the likeliness of their Brand or CI. The options that are

available to the merchant are as follows, instructions on how to customise are discussed on page 32

• Uploading a Logo

• Choosing their Color Scheme for the following

• Background Color

• Font Color

• Buttons Background colour

• Font type

https://backoffice.nedsecure.co.za/

https://backoffice.cscacquiring.com/

https://backoffice.host.iveri.com/

https://backoffice.host.iveri.com/

https://backoffice.merchant.cim.mu/

p. 6



2. Merchant Interface functionality

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

2.1.1 Reset Password The above details are for Administrator access. Once in BackOffice, the Administrator is able to allocate User

Names and Passwords to additional users by making use of the User Manager function described later in this

guide.

Please follow the steps below to reset your password.

• Click on Forgot your password? "This is a link found under the "Login" button "

• Enter your User Group & User Name.

• Click on Submit

If everything is entered correctly, you will receive an email with link for you to reset your password.

• Open your email

• Click on the link (this will then redirect you to a password reset page )

• Enter your new password (twice).

• Click on Submit

• Now go to Backoffice URL and login with the new password

NB: Should you have tried more than 3 times to login with your old password (prior to resetting your password) then

your user name might be suspended and you will be required to wait for 30 minutes before the system can allow you to

login

p. 7



3. Welcome Page

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

p. 8



4. User Manager

4.1 Add User Purpose - To add/capture the details for a new user

Action:

Mouse over User Manager, Add User. The following screen will appear. Fill in all the mandatory fields (marked X)

and click on Add User. A resultant message will be displayed

p. 9



4.2 Edit User

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

BackOffice

Action:

Mouse over User Manager, Add User. Click on the name of the user you want to edit. Make the required change(s)

and click on Save. The success message: “The user was successfully updated” will be displayed.

p. 10



4.2.2 Service Functions Purpose - To allocate the functions within BackOffice which you (the Administrator) want to allow the new user to

have access to.

Action:

Mouse over User Manager, Edit User, Service Functions. Click on the name of the user you want to allocate function

to. Tick the appropriate functions allocated to the user and click Save. The success message: “The service functions

were successfully updated for the user” will be displayed.

p. 11



4.2.3 Service Parameters Purpose - To allocate the Application ID and or Card Acceptor ID to which the selected user will have access for

processing transactions and viewing reports etc. in relation to the selected Service Functions.

Action:

Mouse over User Manager, Edit User, Service Parameters.

Action:

Mouse over User Manager, Edit User, Parameters. Click on the name of the user you want to allocate parameters to.

p. 12



Action:

Click on the Application ID/s you need to allocate to the user. Highlight your allocation and click on Save. The success

message: “The service parameters were successfully updated for the user” will be displayed

4.2.4 Application Parameters Purpose - To allocate the Application ID and or Card Acceptor ID to which the selected user will have access for

processing transactions and viewing reports etc. in relation to the selected Service Functions.

Action:

Mouse over User Manager, Edit User, Application Parameters. Click on the name of the user you want to allocate

parameters to as well as the application ID. Tick the appropriate functions allocated to the user and click Save

p. 13



Action:

Click on the name of the user you want to allocate parameters to. Click on the relevant Parameter (Default is No) and

click on Save. The success message: “The service parameters were successfully updated for the user” will be displayed

p. 14



4.2.5 Security Configuration 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

p. 15



NOTE:

• Strong Password: The default is No. This means that the password can be anything as long as it is not less

than the default minimum length. If you change the default to Yes, then the users 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 as long as 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 of time. 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.

p. 16



p. 17



5. Divert

5.1 Transactions – 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, mouse over DiVert, Transactions and click on Create Transaction Request.

Action:

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

p. 18



Action:

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

NOTE: Fields marked with an X are mandatory and must be completed.

p. 19



5.2 Transactions – View – Pending Purpose - view the list of Pending Orders 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, Mouse over DiVert, Transactions, View Pending. Click on the Application ID you wish to view

Successful Orders for. 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 following pages for viewing.

p. 20



Action:

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

5.3 Transactions – View - Successful Purpose - To view the list of Successful Orders 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, Mouse over DiVert, Transactions, View Successful. Click on the Application ID you wish to view

Successful Orders for. 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 following pages for viewing.

p. 21



Action: If you want to print out a copy of a particular order for your records or just view the full details of an order, click on the

order you wish to Print/View full details. This will display the following page, which you can then print or view.

p. 22



5.4 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 (see 8.4) to debit the cardholder

and obtain the money in your bank account.

Action:

In the menu bar, Mouse over DiVert, Transactions, View Authorisation. Click on the Application ID you wish to

view Authorisations. 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. A list of

transactions will be displayed

p. 23



5.5 Transactions - View – All Transactions

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

Action:

In the menu bar, Mouse over DiVert, Transactions, View All Authorisation. 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

bringup the list of ALL transactions performed for your selection.

p. 24



Action: You can now print out the above details for your records.

p. 25



5.6 Transactions – Reports – DiVert Trading Purpose - This function allows you to download reports in PDF, XLS or CSV formats

Action: In the menu bar, Mouse over DiVert, Transactions, Reports and click on Divert Trading. Click on the

Application ID you wish to download 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. Click on Search

Action: Choose format for download and click on Go

5.7 Transaction – Subsequent Transaction Purpose - To take further action on a transaction which has already been successfully processed. You are able to

p. 26



convert an 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. If

satisfied, go back to the previous page and click on the transaction on which you want to take further action. This will

bring up a page with the Order Details/Transaction Details and Further Transaction section at the bottom. Fill/Change

p. 27



the relevant fields and click on Submit

p. 28



5.8 Divert – Batch- Upload File

Purpose - Used by merchants to upload DivertBatch payment requests to be sent to cardholders. An XML file based

specification on how to create DivertBatch can be downloaded from http://forum.iveri.com.

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

Action: Click on Choose File to select the file saved on your directory to be uploaded and Click Submit

5.9 Divert – Batch – Download File

Purpose - Used by merchants upload the Result file of the Divert Batch uploaded in 5.8. The result file can be

downloaded either by application ID or by File name.

5.9.1 Download By application ID

Action: On the main menu go to DiVert – Batch – Download File – By Application. Click on the

Application ID (test or live) used during the creation of the Divertbatch file

http://forum.iveri.com/

p. 29



Action: Select the Date period in which the file was uploaded in, Click “Search”

Action: A list of Result files by Application ID will be will displayed, click on “Download”

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

p. 30



5.10 Divert- Batch-View Batch Purpose: Merchants can view all DivertBatch files that have been uploaded

Action: On the main menu go to Divert-Batch- View Batch

Action: Click on the relevant Application ID used on the DivertBatch file

Action: Select the date range and click Search. All the Batch Uploaded will be displays with the status (errors, or

successfully uploaded or processed message)

p. 31



5.11 Configure Application Purpose - In order to receive e-mail confirmations after processing successful transactions and to set-up your

transaction viewing options, you will now need to set up your choice of transaction configuration.

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.

p. 32



NOTE: The above image only reflects a portion of the complete list which you are able to select from.

• The Administrator can add specific user email addresses to receive confirmation emails when payments

are made by the cardholders

o Select whether to send email confirmation “to user that created the request”. This will allow

the user created by the Administrator to receive transaction confirmation emails

o Alternately, provide a different email address on the text field below

o Select whether to send email confirmation to Cardholder and if so, type in the address to send

from

• Customise content sent to or displayed to cardholder. DO NOT change content that is between $ sign

• For merchants that have more than one payment method, they can select a preferred default Payment

Method from the list– Visa CheckOut, MasterPass or Card Payments

Visa Checkout Merchant Take-On

Merchants can also register for Visa Checkout in order 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 populate 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

VisaCheckout.

p. 33



5.12 Customise Transaction Form

Purpose - Customise the payment page that cardholder interacts with

Action: On the main menu go to DiVert – Customise Transaction Form

Action: Click on the Application ID you want to customise, i.e. either the Test or the Live. Make the relevant

changes and click on Submit.

p. 34



NOTE:

• Under settings, you can upload a company logo and amend the font colours, fonts and background colour

NOTE:


NOTE:


p. 35



6. Reconciliation

6.1 Print Report Purpose - To View/Print/Save reconciliation file for a specific acquirer cycle/settlement period in either:

• PDF

• XLS format

• CSV format.

Action: Mouse over the menu function Reconciliation then click on Print Report.

Action: If you have only one Merchant Card Acceptor ID simply click on Submit. If you however have

more than one, then click on the drop down and select the Card Acceptor ID for which you want the report

before you click on Submit. The following screens and points highlight the various parameters that need to

be selected before viewing the report

Action:Select the required Output format – either PDF or XLS. Find the acquirer cycle number you

want to view and click on the actual cycle number. You can now choose to either Save the report or

to open it in a new

p. 36



NOTE: If your file contains more than 10000 records then the time in the message above will show 20 minutes. It is

recommended that you click on the words Click Here and you will receive an email when your file is ready for retrieval.

6.2. Download Reconciliation Purpose - To download and save the selected reconciliation file in XML format.

Action: Mouse over the menu function Reconciliation then click on Download File. This will bring up the

following form.

Action: If you have only one merchant Card Acceptor ID simply click on Submit. If you however have more than

one, then click on the drop down and select the Card Acceptor ID number for which you want the report before you

click on Submit. Select the cycle you wish to view

p. 37



NOTE: If your file contains more than 10000 records then the time in the message above will show 20 minutes. It is

recommended that you click on the words Click Here and you will receive an email when your file is ready for retrieval.

p. 38



7. Black Card List

Purpose - This is used to create a list of credit card numbers that you do not want to accept. The iVeri gateway will

always check your list before sending the transaction to the bank for processing. If the card number is on your list, the

transaction will be rejected immediately. The reasons for putting card numbers into this list are at the discretion of each

individual merchant and will only be rejected by your business.

Action: Click on Configure, BlackCardList. This will bring up the following screen

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.

p. 39



Action: Capture the credit card number you want to add to your Black Card List and click on Add. This will put the

card number into your list. If you have more than one number to add, put in the next number and click on Add again. To

save your entries, click on Submit. You can also search for a number by typing it in and clicking on Search to see if a

card that is being rejected is on your list. If the number is on your list, it will be highlighted. To remove a number from

your list, enter the number, click on Search and when it is highlighted, click on Remove and then click on Submit to

save your change (removal)

p. 40



8. View

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

p. 41



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.

8.2 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

Action: To view Transaction history, .click on the appropriate Application ID, Live or Test

p. 42



Action: Make your selection of period/time in the above form by manually changing the default dates or using the

calendar icons next to each date. Also select file format i.e. XML or CSV. Once done click on Search. Your file will be

open or downloaded to selected folder

8.3 Info Purpose - To reset your home page back to the welcome page if you have previously set it to a different page by using

the Set Home Page button on the main menu at the bottom left of your screen. The Set Home Page function is described

in the section 12 GENERAL after Security below.

Action: Click on View then click on Info. This will bring up your Welcome page which contains the details of the

person who is logged in

p. 43



9. Security

9.1 Change Password Purpose - To allow the user who is currently logged in to change his/her password.

Action: Click on Security, Change Password

Action: Complete all the required fields and click on Change Password. A success message will be

displayed

p. 44



9.2 Logout Purpose - To log out of iVeri BackOffie

Action: Click on Security in the Main Menu, scroll across and down to Logout and click your mouse when Logout is

highlighted in blue. You will be logged out.

Date post:	11-Sep-2020
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times

Divert Backoffice User Guide - Payment Technology · Purpose - To log in to the secure BackOffice...

Documents