Appendix B – QA Environment for Development and Certification * ** During the development and certification phases of an integration project the Indigo server will be located within iVeri's QA environment and a Merchant Profile for the Integrator performing the integration must be created on iVeri's QA Gateway as well as on the iVeri QA Indigo Server and the resulting credentials distributed to the Integrator. This must be performed by iVeri Support who can be contacted at assist@iveri.com. Please make sure in all communication with Support that they must deal with QA Indigo and the QA Gateway. Network wise, the Integrator must ensure that the POS/Till system which will be communicating to the Indigo server using the Generic POS Channel protocol has outbound internet access to the iVeri QA

Appendix C – Test Plan * ** The purpose of the following section is to validate the implementation of the Generic POS Channel protocol for the transaction sets chosen by the Integrator. An Integrator may choose to only implement a subset of all the Test Cases (1, 2, 3, 4 and 5) below but, having chosen a Test Case, all sub Test Cases and the transaction types applicable to these Test Case must be performed. By way of example, if an Integrator only wants to perform Debits then only Test Case 3 comprising 3.0, 3.1, 3.2, 3.3 and 3.4 need to be tested and logs for these submitted. In this case logs for 3.0a, 3.1a, 3.1b, 3.2a, 3.3a, 3.3b, and 3.4a would need to be submitted. Integrators should keep logs of all requests sent to the Indigo Server as well as the responses received and the data and

Appendix D – Receipt Requirements * ** At the conclusion of each transaction a customer receipt for the cardholder to keep as a record of the transaction needs to be printed. In addition, a merchant receipt for the merchant to keep as a record of the transaction needs to be printed as well. Not all fields are returned for every transaction depending on the type of transaction, the result and other circumstances so, in the event that a field is not returned in the Response then it is not required that it be printed on the receipts. Data Element Source Customer Receipt Merchant Receipt Notes AcquirerReference Response Y Y If available Address Merchant Y* Y* ApplicationIdentifier Response Y* Y* If available ApplicationLabel Response Y* Y* If available AuthorisationCode Response Y Y If availab

Appendix F – Reconciliation * ** The Indigo Server as well as the iVeri Gateway operates in Host Settlement rather than Terminal Settlement mode which means that a transaction is settled in the cycle that the Host is in when a transaction arrives at the Host. The cycle into which a transaction’s settlement will fall is allocated at the time of the transaction and returned in the AcquirerReference number which is a composite field consisting of the Settlement Cycle Number and the Transaction Trace assigned by the Acquirer. For the Integrator to be able to generate statements which match the bank statement the integrator needs to produce reports based on the Settlement Cycle number received from Indigo at the time of the transaction. By doing this the value of the settlement deposited into t

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