Requirements ***
Merchant profile that contains credentials to login to the merchant portal - Backoffice Merchant must login to Backoffice and request a certificate, [1] only the certificate ID is required.
The Gateway endpoints [2] are the same for Live & Test
For integration purposes, a test applicationID must be used, while the LIVE application iD must be use real payments
Optional Headers:* Authentication [3] of the user using AuthenticationToken & AuthenticationKey can be set in the headers
Authentication * ** When interfacing with the iVeri Gateway, there are 2 forms of authentication that are supported.
Digest Authentication (Optional): *Adding AuthenticationKey and AuthenticationToken in the headers and adding the certificateID in the body of the transaction or enquiry request i
The iVeri Lite Payment Gateway is a plugin that extends WooCommerce, allowing merchants to accept payment through the iVeri Payment Gateway. The extension works by giving customers the option to pay via iVeri and then redirecting them to iVeri to make payment.
/Installation/ *
The plugin can be installed in 2 ways:
1. Upload the zip file using the WordPress Admin Plugin Upload
2. Upload the extracted zip file via FTP to /wp-content/plugins/ on your WordPress website
To change the logo that appears on the website, replace the logo.png file with the correct logo.png file you would like to make use of. The file is located under /assets/images/. Please keep the file name the same and the dimensions of the logo/image the same.
/ Usage /*
A merchant account and related iVeri Lite profile is need
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
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 ***
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 *
**
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 *
**
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