Appendix G – Postman * ** Developers may want to test the protocol independent of their implementation by making use of Postman. When configuring Postman, the Headers must have an additional attribute added to set Content-Type to the value “application/json” as shown below. The Body should be set to the JSON as defined in this document to execute the command that is being tested as shown below: The result received in the response is displayed in the pane below the request. In this case the device 20605360 is not online so the result informs us of that.

This guide is dedicated to the explicit process of activating MauCAS for a merchant through iVeri's Administration Website. It assumes that the user performing the MauCAS activation for the merchant possesses prior knowledge of the take-on process (onboarding process). Which iVeri solution is MauCAS applicable to? PosPort *Note: The device utilized for MauCAS QR is the NewPOS 6210 & 7210. *

Authorisation * **

Automatic Billing Updater* **

Introduction *** Welcome to the PosPort Training Session, this session is aimed to provide details on the processes and procedures that need to be followed when onboarding and configuring a PosPort merchant. This process is important to ensure a merchant is accurately set up, so as the merchant can seamlessly process transaction as expected without any errors. Assumptions *** Actions assumed to be in place The Objectives of this learner guide are attainable on the assumption that the merchant profile already exist/captured on the Gateway Admin website by the acquiring bank. The Device/Terminal also needs to already be created and should exist on the gateway on request by the acquirer to None [1] assist@iveri.com . NEWPOS Devices have already been injected or loaded with the necessary key

* What is IYS? * Iveri has partnered with an eCommerce 3rd party that specializes in the creation of applications (i.e. mobile and website) that enable merchants to be able to display their goods and services they are selling in order to receive payments (i.e. online payments). Merchants will be able to do this through the use of an App that was created and renamed for iVeri, called IYS – Increase Your Sales. Utilizing the designated API, it provides merchants the ability to set up their online stores to be able to receive payments based on what they are actively selling, allowing them to categorise and display what they want to present to their end customers. *Co-partnership with iVeri* The eCommerce 3rd Party has partnered with iVeri to enable their merchants to be able to implement this

Application Identifiers: There are 2 application modes: Live and Test. To ensure updates and changes are configured for a merchant’s application, select the LIVE application. BackOffice Services: How to navigate to the BackOffice Services screen: Applications > Update > BackOffice Services 1. This is where BackOffice Services are created for the merchant. This is a mandatory step that would need to be updated in order to activate an application for a Merchant. b1 [1] 2. Under BackOffice Services, under ‘Local’, click on the dropdown and navigate your way to ‘FNB Back Office’. This update will provide the Merchant access to BackOffice. Once the user has captured the details under Local, click on the ‘Update’ tab. This following screen will now appear. b2.1 [2] 3. Under the ‘Update BackOffic

BackOffice User Guide * ** This document details the functionality available in Backoffice for merchants. The merchant interface (URL) to be accessed depends on the acquirer in which the merchant has an agreement with.

Batch is a payment solution that allows for bulk payment uploads using the iVeri system. It enables a merchant to create and process large volume, card not present transactions. Batch is a solution that facilitates collections from your customers' card accounts. It is an effective way to collect regular payments. Batch is aimed at merchants who accept cards and do not need to process transactions in real-time. Configure – Application *** Purpose *  – Configuring your application needs to take place before a user can create a batch. To capture the email address of the person to whom the confirmation email will be sent after the upload of a batch confirming either the successful upload or an error in the upload to the selected Application ID. Configure%20-%20Application%201 [1] Action * : T

* Batch Upload File XML Specification * **