Authenticated Collections ** Authenticated collections are intended to enable a merchant who wants to make regular direct debits to a customer’s account to authenticate the customer. This has two benefits: The merchant has proved that the customer has consented to these regular debits  The customer has verified themselves by way of a pin validation so there is a higher level of comfort that the customer's account is a valid account and does belong to the customer. Authenticated Collections is currently only available from Nedbank. In addition, the Authenticated Collections provider parameter must be enabled otherwise the transaction will be declined. Coding for Authenticated Collection data The following is a code snippet in C#: enterprise.openElement("AuthenticatedCollectionData"); enterp

/ Nedbank Gateway /* – Applicable for Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland Website * URL * Port * BackOffice *   [1] https://backoffice.nedsecure.co.za/   443 * Lite   [2] https://portal.nedsecure.co.za/Lite/Authorise.aspx   Authorization Information   [3] https://portal.nedsecure.co.za/Lite/AuthoriseInfo.aspx   / CIM Hosted Gateway /* – Applicable for merchants acquired by CIM Finance in Mauritius Website * URL * Port * BackOffice *   [4] https://backoffice.merchant.cim.mu/   443 * Lite   [5] https://portal.merchant.cim.mu/Lite/Authorise.aspx   Authorization Information   [6] https://portal.merchant.cim.mu/Lite/AuthoriseInfo.aspx   / CSC Hosted Gateway */– Applicable for merchants that acquired by banks af

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

* Authorisation Reversal * * Unreserve the funds previously reserved on the cardholder’s account.

Gateway Release Notes * ** The release notes contained in this document will be applied on the Hosted Gateway and Nedbank Gateway Notes

Administrator Password Reset * ** / Purpose /* – This is used when an Administrator would like to reset their existing password. / Action: /* From the menu, select the Administrator area and choose the option to change password. It is recommended that you use Alphanumeric and Special characters to ensure the password strength meter indicates a strong password. Save Changes once completed

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

Fleet card transactions ** Fleet cards facilitate the tracking of costs and managing statistical information of a fleet of vehicles. A Fleet transaction refer to special processing for a Fleet card.  Fleet transactions are currently only available within distributor Nedbank.  If a fleet card is received with other distributors, then the fleet specific parameters are ignored.  Coding for Fleetcards  * The following optional input parameters are Fleet specific per transaction: CustomerReferenceIdentifier The following optional input parameters are Fleet specific per Line item: ProductCode  Quantity  QuantityDecimalPlaces  UnitCost The latest available values of the ProductCode field are obtained via the “Inventory” download command (See section 22). Only use the ProductCodes with Type='Fle

Authorisation Header * ** The authorisation header must be recalculated and sent on ever request. If the token calculated server side does not match the token sent, the client will receive “HTTP Error 401 Unauthorised”. Authorisation Header: Authorisation: Basic usergroup=””, username=””, timestamp=””, token=””* Usergroup = Backoffice credentials used to login to the backoffice website UserName = Backoffice credentials used to login to the backoffice website Timestamp = UTC date time in the format of “yyyyMMddHHmmssfff”(in java this would be “yyyyMMddHHmmssSSS”) Token =Base64 value, calculation shown below Calculating the authorisation token: c#* MD5 md5Hash = MD5.Create(); SHA256 sha256 = SHA256.Create(); string formattedDateTime = DateTime.UtcNow.ToString("yyyyMMddHHmmssfff"); [1] byte[]

* Shopping Carts * ** iVeri Lite plug-in is available for download for the following Shopping Cart platforms: WooCommerce: https://www.iveri.co.za/docs/woocommerce-6 [1] OpenCart: https://www.iveri.co.za/docs/opencart-14 [2] VirtueMart: https://www.iveri.co.za/docs/virtuemart-15 [3] [1] https://www.iveri.co.za/docs/woocommerce-6 [2] /docs/opencart-14 [3] https://www.iveri.co.za/docs/virtuemart-15