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)

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

Enterprise

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.

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 .
 
 

Enterprise BackOffice User Guide

 
Corporate Strength APIs

Enterprise consists of two APIs which are intended for businesses that need the flexibility to integrate and customise a transaction processing engine to their own unique business requirements. This solution provides businesses with the ultimate control to manage their card processing requirements.

iVeri Enterprise APIs also allow for central processing of multichannel card payments. Payments received from the internet, the call centre and from the physical point of sale or kiosk can all be processed using the power and versatility of IVeri Enterprise.

Developers can chose between the Rest or SOAP versions of iVeri Enterprise API.

Transactions – View- Transaction History

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

Action: In the menu bar, Select Enterprise, 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.

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.

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.

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

Users – Certificates - Manage server certificates

Purpose – This certificate is auto generated and is used as an internal iVeri certificate. 

View

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 

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 Download. Your file will be open or downloaded to selected folder

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

Billing

Purpose - This feature shows the Billing that is in place for this merchants’ transactions. The list of transaction and what is being charged to the merchant, this will appear here.
Note: the plus sign provides details as to how this amount is calculated.

Action:
Click on Billing 

Action:
Choose a date to search for transactions processed at a certain period.

Transaction will appear 

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.

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.

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.

Print Report

Purpose - To View/Print/Save reconciliation file for a specific acquirer cycle/settlement period in either:
PDF
XLS format
CSV format

Action:
Select 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

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

User Manager

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 

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.
  
  

Reconcilation

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, Black card List. 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.

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)