The release notes contained in this document are available in iVeri’ s repository in production and can be installed on any Cardinal and or indigo installation on a case-by-case bases as agreed with Customers and or Integrators. Nedbank *** What’s New* IndiGo * Self4000 Led light on card reader slot: Introduced Enablement of the green LED on card reader slot of Ingenico Self4000 devices.  * CIM *** What’s New* IndiGo (ARPED)* IndiGo Till-Initiated Cancel Instruction for MauCas Transaction: A new cancel instruction has been introduced for MauCas transactions, enabling IndiGo integrators to cancel an initiated or in-progress MauCas transaction from their till system. Once cancelled, the device will be ready to accept a different transaction. The cancel action is handled locally and is not

* Parameters * ** The following parameters are expected in the form submitted to the Gateway at step 3 of the iVeri Lite None [1] process flow and/or returned by the Gateway in the response at step 6 to the cardholder via the merchant's website. Note: Not all of the fields in this specification are mandatory.The list of parameters below has been split to reflect mandatory and optional data. You can simulate a test form post, using data corresponding to your request, on None [2] this link *Mandatory Parameters:* * Name * *General Description* *Length* * Notes * Lite_Merchant_ApplicationId iVeri Application id 36 Allocated to the Merchant during registration Lite_Order_Amount Amount to authorize 10 The total amount for the order including tax in cents. This must be equal to the sum of the

Subsequent Transactions implementation * ** On the request to the Gateway, the merchant developer has to pass all the required variables that pertain to a subsequent transaction so as to make sure that the iVeri Gateway handles the request appropriately. Variables that should be present in the request to the iVeri Gateway are as follows: The Lite_PanFormat must be set to TransactionIndex  Set the Lite_TransactionIndex to the actual TransactionIndex value e.g {000000-000000- 000-0000 0000000}  Set the Ecom_Payment_Card_Number to the Dotted PAN value Note:* These variables are defined in 8.2 iVeri specification. In addition to these the merchant will still need to pass all the other required variables.

* Development phase * ** At this stage you will proceed with development based on the integration method [1] you have selected, and may reach out for your contact at the acquiring bank if you require support. [1] /knowsystem/general-requirements-10

* iVeri Lite Process Flow * ** iVeri Lite requires very little integration and is aimed at Internet merchants who have limited technical resources. Lite transactions are processed on a web site and secured via an SSL certificate without the merchant having to buy SSL since iVeri lite takes care of it on their behalf. Although ideal for websites with small catalogs, iVeri Lite still provides a powerful processing engine. */ Process Flow /* This diagram illustrates the flow of events of an iVeri Lite transaction: iveri%20Lite%20flowchart%20-%20horizontal%20-%202024 [1] /*Process Flow Description:*/ (1) The cardholder is at the point in the purchase process where the basket has already been selected and he is now on the brink of paying for it. The website thus knows the price of the basket, t

Section 1: All Customers ** This section will provide release notes relevant to All iVeri Customers, categorized into compliance, optimization, and feature enhancements. Features ** Subject*: New Feature: Lite Fund Me – Generic, Non-Expiring Link Product/Platform:* Gateway – Lite Release Description:* What’s New: Merchants can now create a generic, non-expiring Fund Me link that anyone can access. How It Works: Customers can enter the amount they wish to pay, provide their contact details (email), and add a description. They can then proceed to pay the specified amount directly to the merchant. Why This Matters: This feature enables merchants to accept payments at any time with customer-defined amounts, making it ideal for: Donations Fundraising campaigns Pay-what-you-want models Benefits:

Process Flow in Visa Check-Out with Lite * ** Cardholder selects Visa Check-Out as payment method iVeri Lite calls Visa Light Box or Widget and presents it to the Cardholder to Login Cardholder Logins via Visa Light Box Cardholder selects a card and presses Continue Upon clicking Continue, iVeri Lite receives a Call ID (uniquely identifies the transaction) iVeri Lite uses the Call ID to get the Payload from Visa services Payload is returned by Visa services to iVeri Lite iVeri Lite decrypts the Payload and retrieves the PAN iVeri Lite sends the transaction request to the gateway/acquire When the response is received, Visa services is updated with either a Failed or Successful response Lastly, a redirect to the merchant with the transaction response is made.

Illustration of Visa Check-Out Process With iVeri Lite* ** Image [1] [1] data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAeAB4AAD/2wBDAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsKCwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRT/2wBDAQMEBAUEBQkFBQkUDQsNFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBT/wAARCALlBS0DASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp

Token Verification Logic in the Hosted Payment Page * ** If Enable Token Verification has been set to YES and Lite Shared Secret has not been set an exception will be thrown when submitting a transaction request If Enable Token Verification has been set to YES and Lite_Transaction_Token has not been set an exception will be thrown when submitting a transaction request  If Enable Token Verification has been set to YES and the Lite_Transaction_Token does not match the calculated token an exception will be thrown

Prerequisites * ** The below parameters must be set in the merchant Backoffice Enable Token Verification to “Yes” (By default this parameter is set to “No”)  Populate the Lite Shared Secret key parameter. Maximum length 32 characters (alpha-numeric)