mPress Backoffice User Guide

For merchants who want to accept payments with their Mobile Device.

mPress is the first live mPOS EMV ‘CHIP & PIN’ certified mobile point-of-sale (PoS) solution in Africa. Businesses are able to process debit and credit card transactions by using their mobile device connected to a secure card reader.

mPress is suitable for any business that wishes to accept card payments securely without access to a fixed data or telephone line. mPress is more cost effective then the traditional PoS device.

The PoS device is small, with a secure PIN pad. The merchant is required to capture an email address into their smartphone application. On acceptance of the transaction amount, a digital receipt is sent to the captured email address.

The mPress merchant solution compromises of three distinct components: an Application on a mobile device, an mPoS Terminal and the iVeri Gateway which is integrated.

The Application is fully branded with your name, colours and logo. It is available from the Apple iOS and Android App stores.

Once the Application is downloaded and the merchant has been activated, they would pair with their mobile device via Bluetooth, and start accepting payments.

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)

Merchant Interface Functionality

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

Action:

User Group - enter your Billing Details ID
User Name - type in Administrator if you are the administrator or the username for the profile that was created.
Password - this is the Administrator password sent to you with the Billing Details ID by email. Copy and paste it from the email.

Welcome Page

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.

User Manager

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.

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.

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.

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.

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

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.

mPress

View – Transactions History

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

Action: In the menu bar, Mouse over mPress, 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.

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

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.

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.

Reconciliation

Print Report

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

Action:
From the main menu the user will navigate to: Reconciliations - 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:
The user can select their preferred Recon Layout and Recon format.

Find the acquirer cycle number you want to view and click on the actual cycle number. It will download automatically for you 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.

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.

Black Card List

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

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.

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.

View

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.

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

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

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