Gateway Release Notes V 4.130

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

Lite

Transactions  ** View * Purpose *   - To view the list of Successful Orders for a selected Date or Period in order to check these against your confirmation emails or to view ALL details related to individual transactions. Action: * In the menu bar, Mouse over Lite Transactions - View - Successful. 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. Image [1] Choose a specific  Application ID* Image [2] * Choose a date range to start your  Search* View%20-%20Successful%203 [3] View%20-%20All%20Transactions%204 [4] Successful * Purpose *   - To view the list of Successful  Transactions for a selected Date or Period in order to check these against your confirmation emails or to view ALL details related to

Parameter description

* * * Parameter description *** Command * Authorisation * Debit * Credit * AutohorisationReversal * Void* GetData* Cancel* GetHMAC* GetSystemInfo* Parameter* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* In* Out* Description* AcquirerCode O O O O O The Acquirer ISO code returned for this transaction.  Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription.  This is only made available as extra information and may not exist in all response. AcquirerDescription O O O O O The Acquirer ISO description returned for this transaction.  Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription

Example Message Format

Example Message Format * **

Network Topology

Network Topology** The generic solution is premised on the following network topologies and depends on whether or not the Indigo Server and/or the POS Server, if it exists, are located inside or outside of the merchant’s location. At the point that a payment by the customer must be made the POS Till or POS Server will, using the protocol described in this document, contact the Indigo Server which will control the appropriate device to prompt for payment from the cardholder. Once the required card details have been collected on the device the Indigo server will process the transaction to the iVeri Gateway before returning a response to the POS Till or POS Server which will then be able to close the invoice created and indicate to the cashier at the POS Till that the invoice has been paid. I

How to measure the network performance

How to measure the network performance * ** The following commands should be executed on the Indigo server and the destination should be the connected Devices. If there is any variation from a network point of view between the location of the various devices connecting to an Indigo Server, then they should be tested separately. Windows PS C:\Users\roland> ping -n 1000 -l 512 192.168.128.14 Pinging 192.168.128.14 with 512 bytes of data: Reply from 192.168.128.14: bytes=512 time=1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 . . . Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512

Initial Transaction

Initial Transaction * **

Followup

Followup * **

Authorisation

Authorisation * **

JSON Request

JSON Request * ** { "Command": "Authorisation", "DeviceSerialNumber": "81546628", "MerchantReference": "Roland20190212.1", "Currency”: “ZAR”, "Amount": 1001, "BudgetPeriod" : 0, "CashAmount": 0, "Terminal" : "Roland" }