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.

The objective is to demonstrate through screen representation the BIN Management process via the iVeri Administration Website. The content will cover the following objectives:* At an Acquirer level – Per Gateway or Across Acquirers if on Hosted: Any BIN management updates made would apply across the merchant base: How to create a new BIN  How to amend an existing BIN At a Merchant level: Any BIN management updates made would apply to the specific merchant: BIN management related to a merchant A possible scenario when a BIN type and Description may be required to be amended for a merchant. / Target Audience: /* This guide is intended for the support team tasked with generating new and modifying existing BINs upon request from Acquirers. / Pre-requisites: */ Requesting a new BIN: Select pers

This guide is crafted to empower you with the knowledge and skills essential for enabling MauCAS for a merchant using iVeri’s Administration Website. Through detailed screen representations, it elucidates the step-by-step process by which a Merchant can select MauCAS QR as the preferred payment method during transaction processing.

The purpose of this content is to provide teams who are responsible for onboarding merchants with clear guidance and support for onboarding merchants via the Admin website. By utilizing visual screen representations and detailed explanations, the content aims to simplify and streamline the onboarding process, ensuring teams have the resources they need to complete the task efficiently and accurately.

Acquiring Bank * Gateway Address* Nedbank Merchants https://portal.nedsecure.co.za/ [1] CSC acquiring bank merchants https://portal.cscacquiring.com/ [2] CBZ Bank merchants https://portal.host.iveri.com/ [3] I&M Bank merchants https://portal.host.iveri.com/ [4] CIM Merchants https://portal.merchant.cim.mu [5] [1] https://portal.nedsecure.co.za/ [2] https://portal.cscacquiring.com/ [3] https://portal.host.iveri.com/ [4] https://portal.host.iveri.com/ [5] https://portal.merchant.cim.mu/

Cardinal Posport IndiGo * ** 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.

Cardinal Posport Indigo Release Notes V 20230323 *** 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. / Whats new  /* Indigo Ingenico * A change is implemented to make Ingenico devices reboot once a day to comply with PCI requirement. The default time is set to be at midnight. PosPort * Device Status is included as part of the data synchronized from Cardinal into MIS allowing for a better filtering in reports generated from MIS. Allowances that make it possible to enable "CashAdvance" in parallel with "Sale" transaction type have been made SMYL Loyalty  * As part of the loyalty offering on the N700 device, enabli

Query Code * ** Function: Query a code that has been created. Query Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be queried Response Parameter Description MasterPassAction The action that was performed MasterPassShortDescription Short decription linked to the code MasterPassCodeExpiryDate Date until the code is valid. This is in epoch time. MasterPassMerchantName The name of the merchant as captured on MasterPass Amount Amount linked to the code. Currency The currency is tied to the merchant setup. MerchantReference Linked to the code. Query Code – REST Sample * Request Response { "Version" :  "2.0" , "Certifica

Generic POS Channel API Developers Guide * **

Transaction Life Cycle * ** The following diagrams describe how related stages can be executed during the life cycle of a transaction. There are three diagrams to illustrate the three possible starting points that a transaction life cycle can start from and, once it has started, what follow-up transactions can be performed on them. The data which links transactions together is the MerchantReference which is generated by the POS Till and/or MerchantTrace which is generated by the Indigo Server and returned in appropriate response messages to the POS Till. There is a subtle distinction between a Refund (command = Credit) and Payment (command = Credit); a Refund is the term used when returning money previously taken from a cardholders account by a Sale (command = Debit). A Payment is not link