Checklist – Cardinal & Admin Website Quality Check ** What to check * How to Check it * * 1. Check Profile Creation * Check if the profile is completed accurately. Go to Merchant Profile >> Update >> General. * 2. Check Billing * Check if charges are applied properly based on what has been agreed, (i.e. net settlement or EFT etc). Merchant Profile >> Update >> Parameters . * 3. BackOffice Services Update * Check if all the Service updates are done for Merchant Admin, Cardinal and iVeri Backoffice . Go to Merchant Profile >> Update >> Back Office Services . * * 4. Cardinal Authentication method * Check if the merchant has been properly created in cardinal to create the link between IYS and Cardinal for iVeri to be the Payment Provider. Go to Cardinal Admin >> Merchant Login >> Login in as

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 production release scheduled on 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 improving

Authorisation * **

Merchant BIN management is crucial. The BIN configuration determines what actions a merchant is permitted or restricted to perform.  A Merchant may request certain restrictions within a BIN The below scenario will demonstrate the importance of the BIN Management process that may be amended at a Merchant level: Meet John. John is a merchant who has expanded his business over the past 5 years. He has international clients but has decided to shift his business focus from international to local, highlighting economic downturn and the fees attached to international cards as his main reasons. John no longer wishes to do business internationally. In line with his cost cutting initiatives, he has also decided that he will no longer accept credit cards. John proceeds lodges a query with support to

OpenCart (ver 1.4.0) ** iVeri Lite OpenCart Plugin ** The iVeri Lite Payment Gateway is a plugin that extends OpenCart, allowing merchants to accept payment through the iVeri Payment Gateway. The extension works by giving customers to option to pay via iVeri and then redirecting them to iVeri to make payment. * Installation ** The following steps need to be followed when installing the OpenCart plugin: Unzip the module to a temporary location on your computer Copy the “admin” and “catalog” folders in the archive to your base “OpenCart” folder This should NOT overwrite any existing files or folders and merely supplement them with the iVeri files This, however, is dependent on the FTP program you use If you are concerned about this, rather copy the individual files across as per instruction

Generic POS Channel API Developers Guide * **

JSON Response *** { "GatewayInfo": [ { "Status": "Up", "StatusSince": "2019-02-12 03:22:45", "GatewayDNS": "https://portal.iveri.net%22%2C/ "Name": "Gateway Provider", "Latency": 124 }, { "Status": "Up", "StatusSince": "2019-02-12 03:22:47", "GatewayDNS": "https://portal.iveri.net%22%2C/ "Name": "NBPostilion NBSouthAfrica Gateway Provider", "Latency": 93 } ], "DeviceInfo": [ { "Status": "Disconnected", "Transactions": 11, "LastTransactionEnd": "2019-02-11 14:38:51", "LastTransactionStart": "2019-02-11 14:38:30", "Version": "IPP350 - RA12105", "ConnectedSince": "2019-02-11 13:13:50", "DeviceSerialNumber": "81528455", "SocketAddress": "192.168.128.85:1030", "Latency": 312 }, { "Status": "Idle", "Transactions": 0, "LastTransactionEnd": "", "LastTransactionStart": "", "Version": "IPP350 - RA11

REST Endpoints * ** • Only one REST endpoint exists on the Indigo server and it will be at http://ipaddress/rest/transaction/transact or https://ipaddress/rest/transaction/transact where ipaddress is the local or external ip address or dns of the Indigo server as appropriate. Note that only TLS1.2 or above should be used. • Only POST method is supported, and the data submitted must be in JSON format. • The response from the Indigo server will also be in JSON format • In the request header set request.Accept = "application/json"; • in the request header set request.ContentType = "application/json"; The design of this interface is to use synchronous REST calls to perform either an “Authorisation”, “Debit” or “Credit” which leads to a potential problem in the event that a card is not presente

The Objective of this user guide is to outline IYS Back End interface through the use of step by step screen representations, explaining in detail how the merchant interface works and the related functionalities available within IYS.

JSON Response* ** { "MerchantReference": "Roland20190212.5", "Command": "Void", "DeviceSerialNumber": "81546628", "Result": { "Description": "Void Approved", "Code": "0" }