V4.144 10/05/2024 ** 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 May 19th, 2024, on the Hosted Gateway. 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 requirements, follows best practices, and aligns with established security and quality Optimisation* - The process of refining or

​

CyberSource Parameters * * Parameter Node Type Data Type Required/Optional Max Length Description DeliveryMethod subTag 0 O 255 Physical or Virtual DeviceFingerprintID SubTag AN 0 88 Session ID for the fingerprint. BillTo_FirstName SubTag AN R 60 First name of cardholder BillTo_LastName SubTag AN R 60 Last name of cardholder BillTo_Street subTag AN R 60 Street address of cardholder BillTo_City subTag AN R 60 Billing city for cardholder BillTo_State subTag AN 0 2 State or province of the cardholder. Required for U.S. and Canada. Use the two-character state, province, or territory codes. BillTo_Country subTag AN R 2 Billing country for cardholder. Use the two-character country codes. BillTo_PostalCode subTag AN O 10 Postal code of the billing address. Required only if the BillTo_Country fiel

* Download by File * * */ Action: /* On the main menu go to DiVert – Batch – Download File – By File */ Action: /* Select the Date range, click “Search”; Click on the File name, the file will start downloading

Configure Application * ** / Purpose - /* Configuring your application is important. Configuring your application needs to take place before a user is able to create a transaction request. The user would need to configure: If E-mail confirmations can be sent to a cardholder.  Confirm the E-mail address confirmations are sent to and from. Receive a copy of the payment request that has been sent to the cardholder. Customise the message on payment page. Customise the message on payment request e-mail. Link Merchants Terms and Conditions Show Associated Logos / Action: /* On the main menu go to DiVert – Configure Application. / Action: /* Click on the Application you want to configure, i.e., either the Test or the Live. To make the relevant changes, click on Save Changes. Please note:* 1.* The

**

Batch is a payment solution that allows for bulk payment uploads using the iVeri system. It enables a merchant to create and process large volume, card not present transactions. Batch is a solution that facilitates collections from your customers' card accounts. It is an effective way to collect regular payments. Batch is aimed at merchants who accept cards and do not need to process transactions in real-time.

Payment Mechanisms: Pan Vs Track2 Vs Pin * ** iVeri Gateway separates accounts into 3 different payment mechanisms: PAN Track2 PIN To process a transaction with an account you need to know which payment mechanism you are going to use /Note /*that independent of the payment mechanism is used, the iVeri Gateway returns a dotted out “PAN” which can be used for display purposes. PAN (also known as “Card Not Present” or “Keyed”) * The Primary Account Number (PAN) is given by the card holder to the merchant. Either the card is not present with the Merchant, or the Merchant does not have a card reader to “swipe” the card. The account can be any card that has the PAN embossed or printed on the card but does not require a PIN. Mandatory Input Parameters: PAN, ExpiryDate. Optional Input Parameters:

PAN encryption via Dukpt encryption * ** A POS Device Integration architect has the option sending the PAN to the iVeri Gateway in an encrypted format. This optional functionality is there as an extra security measure against someone sniffing the data between the device and the server communicating with the iVeri Gateway. The Dukpt PAN encryption process flow is the following: A Device (with a DeviceSerialNumber and a DeviceMake) is injected in a Trusted Centre with a Track2 IPEK (initial pin encryption key). This IPEK is different from the one injected for Dukpt PIN encryption. For this encryption, the following are mandatory input parameters together with the PAN tag: DeviceSerialNumber DeviceMake PANKeySerialNumber

Refund – “Follow-Credit” ** Allows for a previously debited amount to be returned to the cardholders account using a detail of a previously processed transaction. REST SOAP Request { "Version" :  "2.0" , "CertificateID" :  "{5c4b9c74-0063-4240-9cff-f730675c5bd0}" , "ProductType" :  "Enterprise" , "ProductVersion" :  "WebAPI" , "Direction" :  "Request" , "Transaction" : { "ApplicationID" :  "{d8d5a94-8fa0-428d-a539-3a5baf166f7f}" , "Command" :  "Credit" , "Mode" :  "Test" , "Amount" :  "1000" , "MerchantTrace" : "20220812_1107" , "MerchantReference" :  "20221123_1106" , "TransactionIndex" :  "{CB7A9E38-4797-4513-85EE-AFE63C957ED3}" } } < soap:Envelope   xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd = "http://www.w3.org/2001/XMLSchema"   xmlns:soap = "http://schemas.xmlso