Below we will look at the step-by-step process of enabling a merchant for MauCAS via the Administration Website. Navigation Path: To navigate to this screen, Select Applications > Update > Provider Specific. 1. Click on the ‘Common Provider’ expansion tab. 2. Navigate to the ‘Third Party’ parameter and click on the expansion tab. 3. Navigate to the ‘MauCAS enabled’ parameter. This parameter defaults to ‘No’. 4. To enable MauCAS, untick the default value. 5. From the dropdown, select ‘Yes’. 6. The next parameter that needs to be populated is the ‘MauCAS Merchant ID’. This parameter needs to be populated with the Merchant ID. The Merchant ID is provided / supplied by the Acquirer. 7. Untick the default value and enter the MauCAS Merchant ID. 8. Lastly, save the changes that you have captured

Enabling Merchants for Recurring transactions * ** Merchants that process recurring transactions need to be enabled as such via the Admin Portal. In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions. We will have a look at how to enable a merchant for recurring transactions via the Admin Portal. Navigation Path to this screen: Applications > Update > Provider Specific. Navigate and expand on the ‘Processing’ parameter. Scroll down to the ‘Cardholder Presence default’ parameter. The parameter is defaulted to ‘no’ Untick the default value. From the dropdown menu, select ‘Recurring transaction’ The next parameter that ne

Below is the process of how to enable MOTO transactions for a merchant on the Admin Website: Navigation Path: Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab as illustrated. 1. Navigate to the ‘Processing’ parameter and click on the expansion button. moto1 [1] 2. Navigate your way to the ‘Cardholder Presence Default’ Parameter. This parameter will be defaulted to ‘Not specified’. moto2 [2] 3. Untick the ‘Use Default’ tab. From the drop down, select ‘Mail/Telephone Order (single transaction)’. moto3 [3] 4. Lastly, to ensure the change has been saved, click on the ‘Update Parameters’ tab. moto4 [4] [1] /web/image/351226-55085015/moto1.png?access_token=a03576b8-fe21-4b94-b4c7-b2fe65ec31f6 [2] /web/image/351227-0b632be4/moto2.png?access_token=8d6f6399-44

Merchants that process recurring transactions need to be enabled as such via the Admin Portal. In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions. We will have a look at how to enable a merchant for recurring transactions via the Administration Website: Navigation Path: Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab as illustrated. 1. Navigate to the ‘Processing’ parameter and click on the expansion button. me1 [1] 2. Navigate your way to the ‘Cardholder Presence Default’ Parameter. This parameter will be defaulted to ‘Not specified’. me2 [2] 3. Untick the ‘Use Default’ tab. F

Transaction integrity can be seen as ensuring that all players within an individual iVeri transaction agree on its outcome. When a Card Holder gets his statement from his Issuer, it must correspond to his instruction to the merchant for a corresponding transaction. When transaction integrity is compromised either willfully (fraud) or unintentionally, it can result in a disputed transaction with legal impacts. Individual transactions *** Void* A Void of a previous transaction request is a command to ignore (i.e. cancel the effects of) a previous (recently submitted) transaction request. When a merchant receives a successful response for a transaction request, and thereafter “something goes wrong”, then the Merchant has the option to “void” the transaction. Examples of “something goes wrong”

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. image%20%2812%29 [1] Choose a specific Application ID image%20%2810%29 [2] Choose a date range to start your Search image%20%2811%29 [3] Action: * Allows you to get details pertaining to a specific transaction – available when clicking on the a

The error codes below can be resolved without returning a device back to Touchpoint Payments Error Code* Error * Solution * 100 Transaction declined by bank / blocked card Try another card 109 Merchant ID / Terminal ID / Serial number mismatch Please validate these settings on the iVeri server 399 Incorrect date and time on POS – Please update POS parameters [ FUNC + 1] 902 Device deactivated on server Please forward serial number to us to activate 921 Invalid data authentication Please insert the card and process PIN based transaction 908 Unknown host Please insert the card and process PIN based transaction 909 Various errors Please try PIN based transaction. If still fails please call Touchpoint to further investigate before shipping back to us No terminal params Please download terminal

Example Message Format * **

Field and Reply Codes * ** Result Status Code * Result Status Code ResultDescription 0 N/A (Approved) -1 Timeout waiting for response. Try again -3 Hot card -4 Denied -5 Please call -6 Card Address Failure -7 Card Security Code Failure -8 Card Type not accepted -9 Unable to process the transaction -11 Invalid Amount -12 Invalid Budget Period -14 Invalid Card Number -15 Invalid Track2 -16 Invalid Expiry Date/Card Period -18 Invalid Authorisation code -255 * Unknown Error * Recon Status * * VALUE* * DESCRIPTION* "-1" Unreconciled - The reconciliation process for this transaction has not taken place yet. "0" Reconciliation has taken place and the result code accurately depicts the status of the transaction "1" Reconciliation has taken place and the transaction could not be found. "2" Reconcil

Field and Reply Codes * ** Bank Code * * VALUE* * DESCRIPTION* "01" All Banks Transaction Code * * VALUE* * DESCRIPTION* "01" Sale "02" Refund “03” Authorisation “04” Authorisation Reversal “05” Recurring Sale Transaction Status * Transaction Status ResultDescription 0 N/A (Approved) 1 Timeout waiting for response. Try again 3 Hot card 4 Denied 5 Please call 6 Card Address Failure 7 Card Security Code Failure 8 Card Type not accepted 9 Unable to process the transaction 11 Invalid Amount 12 Invalid Budget Period 14 Invalid Card Number 15 Invalid Track2 16 Invalid Expiry Date/Card Period 18 Invalid Authorisation code 255 * Unknown Error * Reconciliation Status * * VALUE* * DESCRIPTION* "00000" Unreconciled - The reconciliation process for this transaction has not taken place yet. "10000" Rec