JSON Request ** { "Command": "Credit", "DeviceSerialNumber": "81546628", "MerchantReference": "Roland20190212.3", "Currency”: “ZAR”, "Amount": 1003, "Terminal" : "Roland" }

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

In order to list iVeri as your payment method option, merchants would need to select this from the Apps menu, the iVeri payments application, in order to receive card payments. *Below are the steps to setup iVeri as your payment method option:* The Merchant is able to access the iVeri payment application by navigating: From the menu, under Configuration > select Payment Scroll down to ‘Payment alternatives’ menu. Here the user Would need to select iVeri as their payment provider. Click on the ‘Choose payment processor’ dropdown. Scroll down to locate IYS as your payment provider: The Merchant is able to access the iVeri payment application by navigating: From the menu, under Configuration > select Payment Insert your iVeri provided store credentials. These are the merchants BackOffice acco

Pre-Requisites * ** Acquirer Collaboration for ABU Implementation: Establish an agreement with the Acquirer regarding the submission process for the Merchant Registration file. Follow the necessary steps to conclude the project with MasterCard, including customization, testing, and obtaining final approval. Acquirer Configuration on Admin Portal: Input the provided ICA value from the Acquirer under "System > Distributor > Parameters" on the Admin portal. Merchant Eligibility Requirements: Merchants must be actively processing Card Not Present (CNP) transactions using any of the following platforms: Lite, Enterprise, DiVert, Batch, or Link. Mastercard Transaction Processing: Merchants should be actively processing transactions with Mastercard.

Appendix A * ** The prompts are specific to devices so depending on which devices are attached to the Indigo server will determine which prompts are used. These prompts are, in general, loaded onto the device at initialisation so if this has not been done then prompts will not be supported. There is a hardcoded default prompt so that if the Index used from the list below does not happen to be loaded on the device or does not exist on the device then this prompt will be used as a generic request for data to be entered.

Introduction ** This content is called the Shopify Merchant Take on Guide. This Learner guide provides an overview of the Merchant onboarding process on the Gateway as well as the Shopify Merchant interface and how merchants would navigate the platform to configure iVeri as their payment provider through their Shopify store. The Guide covers the iVeri Admin Portal used by the Acquirer to onboard a Merchant and the Shopify Back end used by the Merchant to configure iVeri as their payment provider. Objectives ** The Objective of this user guide is to outline the actions on the iVeri Admin Portal and Shopify Back End interface through the use of step by step screen representations. The user guide explains in detail how the merchant interface works and the related functionalities available wit

Ingenico RA1 based devices *** Index Prompt Description 01 Amount 02 Please enter new total 03 Total 04 amount again 05 Please enter 06 Add 07 Input 09 Balance 10 Tip 11 Gratuity 12 Service 13 Donation 20 Waiter ID 21 Waiter logon 22 Table number 23 Bill number 24 Location reference 25 Tab Number 26 Operator ID 37 Split by 38 number of parties 39 to pay 3A Auth code 3B Cashback 3C Due 3D Maximum 3E Minimum 3F Multiples of 40 Format 41 Date 42 Incorrect 43 ID incorrect 44 Number incorrect 45 Bill not found 46 Cash 47 Card 48 Cheque 49 Voucher 4A Payment 4B Refund 4C Voucher number 4D Identity code 4E Kilometers 4F Car number 50 Product code 51 Number of items 52 Room number 53 Plu number Default Input

Followup * **

IYS Implementation Guide **

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