​ The Mauritius Central Automated Switch (MauCAS), a digital hub exclusively owned and managed by the Bank of Mauritius, facilitating seamless 24/7 payment routing among various operators. CIM Finance is introducing QR-code-based payments through seamless integration with MauCAS, thereby diversifying the payment options for their valued merchants.

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. Available to All Cardinal Customers * What’s New* Support of newly introduced DIGEST based authentication to cardinal level to be able to download recon/transactions/EMV parameters/hot cards, etc. from gateway. Introduction of a function to extract detailed reports on User Roles and Access Rights from the related Cardinal, enhancing access management. This report can be scheduled upon request, per cardinal. PosPort/* The user’s last login is now added to the "Users" View Module in BackOffice. An API is now available for management of NewPOS devices on merchant

The document is titled the 'Merchant Onboarding Guide.' Its primary objective is to offer a comprehensive, step-by-step walkthrough of the Merchant onboarding process within the FNB Administration Website.

Point 1. Point 2. Point 3. Point 4.

Onboarding a merchant is a vital initial step when signing up a new merchant. This process involves gathering the necessary merchant information and tailoring enablement requirements to meet their specific needs. Acquirers must have a clear understanding of the correct procedures to ensure a smooth and successful onboarding experience.

Introduction *** Welcome to the PosPort Training Session, this session is aimed to provide details on the processes and procedures that need to be followed when onboarding and configuring a PosPort merchant. This process is important to ensure a merchant is accurately set up, so as the merchant can seamlessly process transaction as expected without any errors. Assumptions *** Actions assumed to be in place The Objectives of this learner guide are attainable on the assumption that the merchant profile already exist/captured on the Gateway Admin website by the acquiring bank. The Device/Terminal also needs to already be created and should exist on the gateway on request by the acquirer to None [1] assist@iveri.com . NEWPOS Devices have already been injected or loaded with the necessary key

The merchant portal Backoffice allows for the following core functions: Management of User Creation of users Transaction Types allowed per user created Backoffice functionality views allowed Applications permitted on a user created Transaction Reports & Listing & Lookups Reconciliation  Reports Blacklisting of cards Customise payment request page with Merchant’s Corporate Identity. Create Transaction Requests Process Subsequent Transactions (Refunds)

The error codes below can be resolved without returning a device back to Touchpoint Payments Error Code* Error * Solution * 100 Transaction declined by bank / blocked card Try another card 109 Merchant ID / Terminal ID / Serial number mismatch Please validate these settings on the iVeri server 399 Incorrect date and time on POS – Please update POS parameters [ FUNC + 1] 902 Device deactivated on server Please forward serial number to us to activate 921 Invalid data authentication Please insert the card and process PIN based transaction 908 Unknown host Please insert the card and process PIN based transaction 909 Various errors Please try PIN based transaction. If still fails please call Touchpoint to further investigate before shipping back to us No terminal params Please download terminal

The release notes provided in V1 of this page serve as an initial preview of the changes expected in the upcoming production release of the PocketPos application Summary* The PocketPos release notes will contain information related to the new PocketPos application 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 a software solution to enhance its

Overview of iVeri Lite - The Hosted Payment Page ** The iVeri Lite hosted payment page is an ecommerce solution designed for merchants who want to accept card payments in their online stores. The iVeri Lite hosted payment page can be integrated in one of three ways: Full Redirect* -  A full Redirect to the Hosted payment page shifts the interaction of the shopper/buyer away from the merchant’s website and only goes back to the merchant website when the transaction is complete. LiteBox *- The LiteBox hosted payment appears or pops up within the merchant’s website, the merchant’s website remains unchanged, providing for a more user friendly and seamless checkout experience for both cardholder and merchant.  Shopping Carts* - The iVeri Lite hosted payment page is integrated to some of the c