• Tags

Introduction

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.

Introduction

​ 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.

Introduction

​ Bank Identification Number (BIN) is s set of numbers that identify among many other things the banking/final institution that issues the card. BINs can be found on various payment cards, including credit card, charge cards, and debit cards etc. The BIN helps merchants to evaluate and assess their payment card transactions.

Introduction

This content is called the “IYS” General Merchant Guide, This Learner guide is aimed to provide an overview of the functionality available on the IYS Merchant interface and how merchants would navigate the platform when setting up their own store. The Guide covers the Back End System that will be utilised by the merchant when setting up their online store and the essential configurations that a merchant must have completed to properly onboard themselves as participants on the IYS Website or App store.

Introduction

Introduction * ** Automatic Billing Updater (ABU) is a web service that provides access to updated account credentials (cards). This can be leveraged by Merchant/Acquirers/Payment Service Providers to ensure that they always have their customers’ most up to date card credentials for recurring and card-on-file payments. Simply put, ABU allows card details to be updated automatically in the event they are no longer valid. Types of updates include: Expiration dates Replacement card numbers Account closures Issuer brand changes to Visa and MasterCard

Introduction

Introduction * ** This document describes the XML specification of the Batch Upload File and the Batch Result File. The Batch Upload File can be uploaded either from the iVeri BackOffice or by using the iVeriClient software (the latter applies to Enterprise merchants only). The Batch Result File can be downloaded through these same mechanisms. Note that the Batch Result File is available for download only after processing of the batch has completed. Note that the Reconciliation Status of the individual transactions might not yet be updated, since the reconciliation process only occur the day after processing. The XML specification of other downloadable XML files is described in the “iVeri Download Files XML Specification” document available from the iVeri website.

Introduction

Introduction * ** This document describes the fixed specification format of the Batch Upload File and the Batch Result File. Both of these are ASCII text files with fixed field record structure where each transaction is recorded as a single line in the text file. The Batch Upload File can be uploaded either from the iVeri BackOffice or by using the iVeriClient software (the latter applies to Enterprise merchants only). The Batch Result File can be downloaded through these same mechanisms. Note that the Batch Result File is available for download only after processing of the batch has completed. Note that the Reconciliation Status of the individual transactions might not yet be updated, since the reconciliation process only occur the day after processing.

Introduction

Introduction * **

Introduction to 3D Secure

* *3D secure (Secure Code or Verified by Visa), is all about call back protection and making sure card holders are who they say they are. The Illustration and process that follows, shows 3D secure in use as implemented by Merchants using iVeri Enterprise and not iVeri Lite. Illustrating the process in this way, helps to show how each entity is involved even if certain functions are performed on behalf of Merchants using iVeri Lite.

Introduction to Enterprise

* Enterprise Introduction  *** The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd provides proven credit card payment solutions for businesses that have online or physical presence. The use of Enterprise API's is ideal for merchants that want complete control & flexibility of the payment page and transaction mechanisms supported. Enterprise API’s currently support the following Webservices REST SOAP */Merchant Requirements/* Merchants are required to enter into a “Agreement” with an authorised Acquiring Institution. Once there is a merchant agreement in place, a merchant profile can be created With Enterprise calls to the Gateway, the presence of a certificate ID is required, with the actual physical certificate available as optional means to authentica