* View – Authorisations * * */ Purpose /*- To view the transactions for which you originally only obtained an Authorisation. This allows you to now use that Authorisation code to Debit the cardholder by doing a Subsequent Transaction [1] to debit the cardholder and obtain the money in your bank account. */ Action: /* In the menu bar, Select DiVert, Transactions, View Authorisation. Click on the Application ID you wish to view Authorisations. Select the Date or Date range and click on Search. A list of transactions will be displayed View%20-%20Authorisations%201 [2] View%20-%20Authorisations%202 [3] Choose a date and select Search View%20-%20Authorisations%203 [4] View%20-%20Authorisations%204 [5] [1] http://www.iveri.co.za/knowsystem/subsequent-transaction-151?enable_editor [2] /web/image/

* General Requirements * ** iVeri Lite implementation consists of doing a submission of a form post to the Gateway endpoint while including all required/mandatory parameters. Applicable Parameters to be passed in the request are common to all the integration methods supported on iVeri Lite, and elaborated in this documentation. The list of applicable parameters can be found None [1] here [1] /knowsystem/parameters-14

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.

Authentication - Manage client certificate* ** Certificate Expiry and Dependency on Intermediate CA: Certificate Expiry and Dependency on Intermediate CA: Server Certificate Expiry: A server certificate has a specific validity period, typically ranging from one to two years. This expiry date is hard-coded into the certificate at the time of issuance by the Intermediate CA. When the server certificate reaches its expiry date, it is no longer considered valid, and a new certificate must be issued to maintain secure connections. Dependency on Intermediate CA: The server certificate's validity also depends on the validity of the Intermediate CA that issued it. If the Intermediate CA's certificate expires before the server certificate, the server certificate will no longer be trusted, even i

Transaction – Subsequent Transaction * ** Purpose - * To take further action on a transaction which has already been successfully processed. You can convert an Authorisation to a Sale or process a sale Refund. Action: * Click on the appropriate Application ID in which you can view transactions that have been processed. Once the transactions details are displayed you, perform refunds, or do a debit Action: * Select the Date on which the original transaction took place from the drop down menu or select a period if you are not sure of the exact date and click on Search. This will bring up a summary list of all the transactions which match your search selection. Action:  * Scroll through the summary list until you find the transaction you want to take the action on. To make sure that it is the

* Enterprise Introduction  *** The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd 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 */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 authentica

V4.139 7/2/2024 ** Release Notes Overview The release notes provided in V1 of this document serve as an initial preview of the changes expected in the upcoming production release scheduled for November 12th, 2023, on the Hosted Gateway. The definitive release notes for deployment in production will be included in V2 of this document. Summary The Gateway release notes will contain information related to the new iVeri software release. The release notes will include the impact of software release to the intended target audience. The release notes will adopt the format outlined below, as applicable: Compliance - Refers to the adherence of the software to specific industry standards, regulations, or internal policies. This includes ensuring that the software meets legal and regulatory requirem

Gateway Release Notes V 4.130 * ** / Hosted Gateway: /* Date: 21/05/2023 Start Time: 20:00 UCT +2 Duration: 2-4hrs Expected Downtime: 5-10mins. / Nedbank Gateway:  /* Date: 11/06/2023 Start Time: 20:00 UCT +2 Duration: 2-4hrs Expected Downtime: 5-10mins. Enhancements * Compliance – Mastercard Edits* MCI: Edit 7 - TermPOS The Terminal Operating Environment value in POSDATA element has been updated from value “5” to “0” for instances where POSEntryMode is set to “01 Amendments have been made on DE 123 for MasterPass Pin authenticated transactions. Backoffice 2 * The inclusion of the "View All" option for Batch users together with the ability to view transactions performed under specific users has been introduced. With this change it is now possible for users to view and do subsequent actions

3DS 2 Parameters * ** Request Parameters * Parameter * Description * Merchant ReturnUrl Mandatory: The URL which the Gateway will post return response parameters to ApplicationID Mandatory: Merchant Application ID generated upon the creation of the merchant profile on the iVeri Gateway MerchantReference Mandatory: A merchant generated identifier that is unique within a specified time that identifies a transaction sequence. Amount Mandatory: The total value of the transaction in the smallest unit of the currency specified (eg in cents) Currency Mandatory: The ISO 4217 currency code of the value of the transaction. e.g., USD or ZAR or GBP PAN Mandatory: Card number used for transaction ExpiryDate Mandatory: The last month of the validity period of the card, formatted as MMYY or   MMYYYY Card

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