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

3D Secure * ** 3D secure is an XML-based security protocol for online credit and debit card transactions. 3D Secure adds an authentication step for online payments, making it possible for cardholders to authenticate their online transactions with their card issuers, using a password or OTP. Benefits of using 3D secure * Reduces fraudulent debit & credit card transactions processed through online platforms Gives the merchants and acquiring bank liability protection 3D secure providers * CyberSource Bankserve 3D secure with iVeri * High: 3D secure – If a merchant is deemed high risk, the acquiring bank can set merchants on this level. Merchants that want lowest possible risk can also opt for this level. Medium: 3D secure/attempted- This option gives merchants a broader reach in the cards the

* Sign Up Process * Need the sign up detail process. Where can a merchant access the IYS URL to sign up for a subscription. In order to view and compare the IYS packages, user would need to scroll down to ‘Subscription solutions’. The merchant is able to compare and select a solution that is fit for purpose. For this example, we have selected the Unlimited option by clicking the ‘sign up now’ tab. The billing details screen will appear. The blue fields are mandatory fields that would need to be completed by the merchant. The merchant would need to insert their personal details and setup their credentials to login to their IYS store. Note: When setting up a password, enter a strong password that is at least twelve characters long and contains a combination of upper case, lower case, numeric

* Payment Method Configuration – Back End Interface * 1.User to use the left adjusted Menu Items, navigate to Payments – To set up your payment provider. Select iVeri as a Payment Processor. This is done so that iVeri becomes the payment provider. The radio button will be on the disabled state until the merchant sign’s in. Scroll up and enable iVeri as the payment process here as well. Select the Enable radio button to allow iVeri as the payment provider 1. Turn the Radio button on. Select Actions then Edit 2. The system will update the page. 3.Insert your iVeri Provided store credentials. These are the merchants BackOffice account details that you would have already received. 4.This screen indicates a successful log in and link of the merchants’ store Profile with their iVeri merchant Pro

*How to Configure Shipping & Pick Up* 1.Use the left adjusted Menu Items, navigate to Shipping & Pickup – To set up your Shipping methods. Choose your providers you will use to courier or ship the goods based on the aggreement you have with your partner.

* Connecting your IYS store via Social Media * In this process, we will look at configuring a Merchant’s online store via a Social Media Platform. For this example, we will be setting up an iVeri Demo store via Facebook. 1. From the menu, the Merchant would need to select which social media platform they would like to configure. Click on the tab ‘Connect to get your Facebook Shop’. Note: In order to link your account your Social media page requires a Business Manager account as well as a catalogue of products. 2. The next step would be to use your social media login credentials to connect to your selected Social media platform. Click on ‘Continue’. Note: It is important that you have a Business Account / Profile setup on your social media platform. Click on ‘continue as’ (this would appear

** The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd ( www.iveri.com) [1]  provides proven credit card payment solutions for businesses that have online or physical presence. The use of Enterprise API's is ideal for merchants that want complete control & flexibility of the payment page and transaction mechanisms supported. Enterprise API’s currently support the following Webservices. REST   SOAP [2]   Merchant Requirements * Merchants are required to enter into a “Agreement” with an authorised Acquiring Institution. Once there is a merchant agreement in place, a merchant profile can be created With Enterprise calls to the Gateway, the presence of a certificate ID is required, with the actual physical certificate available as optional means to

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.

* Core Parameters * * Parameter Node Type Data Type Min Length Max Length Description ApplicationID Attribute parameter GUid 38 38 Identification of the merchant’s configuration within the iVeri Gateway CertificateID property 38 38 The iVeri CertificateID installed on the server communicating with the iVeri Gateway CertificatePath Property A Valid Path to directory where the KeyStoreFile or CertificateFile exists on the filesystem CertificateFile Property A Existing certificate file CertificatePassword Property A Password of the certificate Gateway Property A The name of the gateway connecting to. If not explicitly set, the default gateway is used. RequestID Attribute 38 38 A unique identifier generated by the iVeri Gateway for this request Mode Attribute parameter 4 4 The mode of the corr

* Ecommerce, Card Not Present * * * M Mandatory O Optional C Conditional blank not relevant * Context * * Parameter * * Debit with PAN * * Debit with TransactionIndex * * Void * * Credit with PAN * * Credit with TransactionIndex * * Authorisation with PAN * * AuthorisationReversal with TransactionIndex * * Additional Authorisation with TransactionIndex * Core ApplicationID * M * * M * * M * * M * * M * * M * * M * * M * Core Category * M * * M * * M * * M * * M * * M * * M * * M * Core CertificateID * M * * M * * M * * M * * M * * M * * M * * M * Core Gateway * O * * O * * O * * O * * O * * O * * O * * O * Core Command * M * * M * * M * * M * * M * * M * * M * * M * Core Mode * M * * M * * M * * M * * M * * M * * M * * M * Common Amount *  M * *  M * *   * *  M * *  M * *  M * *  O * *   *