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
Enabling ABU on the Admin Portal *
**
Below we will look at the step-by-step process of enabling a merchant for Automatic Billing Updater via Admin Portal.
Navigation Path:
To navigate to this screen,
Select Applications > Update > Provider Specific.
Click on the ‘Common Provider’ expansion tab.
Navigate to the ‘Supplementary’ parameter and click on the expansion tab.
Navigate to the ‘ABU enabled’ parameter. This parameter defaults to ‘No’.
To enable ABU, untick the default value.
From the dropdown, select ‘Yes’.
The next parameter that needs to be populated is the ‘ABU Merchant ID’. This parameter needs to be populated with the Merchant ID.
The Merchant ID is provided / supplied by the Acquirer.
Untick the default value and enter the ABU Merchant ID
Lastly, save the changes that you hav
Enabling Merchants for Recurring transactions *
**
Merchants that process recurring transactions need to be enabled as such via the Admin Portal.
In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions.
We will have a look at how to enable a merchant for recurring transactions via the Admin Portal.
Navigation Path to this screen:
Applications > Update > Provider Specific.
Navigate and expand on the ‘Processing’ parameter.
Scroll down to the ‘Cardholder Presence default’ parameter.
The parameter is defaulted to ‘no’
Untick the default value. From the dropdown menu, select ‘Recurring transaction’
The next parameter that ne
JSON Request
**
{
"Command": "Credit",
"DeviceSerialNumber": "81546628",
"MerchantReference": "Roland20190212.3",
"Currency”: “ZAR”,
"Amount": 1003,
"Terminal" : "Roland"
}
In order to list iVeri as your payment method option, merchants would need to select this from the Apps menu, the iVeri payments application, in order to receive card payments.
*Below are the steps to setup iVeri as your payment method option:*
The Merchant is able to access the iVeri payment application by navigating:
From the menu, under Configuration > select Payment
Scroll down to ‘Payment alternatives’ menu.
Here the user Would need to select iVeri as their payment provider.
Click on the ‘Choose payment processor’ dropdown.
Scroll down to locate IYS as your payment provider:
The Merchant is able to access the iVeri payment application by navigating:
From the menu, under Configuration > select Payment
Insert your iVeri provided store credentials.
These are the merchants BackOffice acco
Appendix B – QA Environment for Development and Certification *
**
During the development and certification phases of an integration project the Indigo server will be located within iVeri's QA environment and a Merchant Profile for the Integrator performing the integration must be created on iVeri's QA Gateway as well as on the iVeri QA Indigo Server and the resulting credentials distributed to the Integrator. This must be performed by iVeri Support who can be contacted at assist@iveri.com. Please make sure in all communication with Support that they must deal with QA Indigo and the QA Gateway.
Network wise, the Integrator must ensure that the POS/Till system which will be communicating to the Indigo server using the Generic POS Channel protocol has outbound internet access to the iVeri QA
Appendix A *
**
The prompts are specific to devices so depending on which devices are attached to the Indigo server will determine which prompts are used. These prompts are, in general, loaded onto the device at initialisation so if this has not been done then prompts will not be supported. There is a hardcoded default prompt so that if the Index used from the list below does not happen to be loaded on the device or does not exist on the device then this prompt will be used as a generic request for data to be entered.
Pre-Requisites *
**
Acquirer Collaboration for ABU Implementation: Establish an agreement with the Acquirer regarding the submission process for the Merchant Registration file. Follow the necessary steps to conclude the project with MasterCard, including customization, testing, and obtaining final approval. Acquirer Configuration on Admin Portal: Input the provided ICA value from the Acquirer under "System > Distributor > Parameters" on the Admin portal. Merchant Eligibility Requirements: Merchants must be actively processing Card Not Present (CNP) transactions using any of the following platforms: Lite, Enterprise, DiVert, Batch, or Link. Mastercard Transaction Processing: Merchants should be actively processing transactions with Mastercard.
Appendix C – Test Plan *
**
The purpose of the following section is to validate the implementation of the Generic POS Channel protocol for the transaction sets chosen by the Integrator. An Integrator may choose to only implement a subset of all the Test Cases (1, 2, 3, 4 and 5) below but, having chosen a Test Case, all sub Test Cases and the transaction types applicable to these Test Case must be performed. By way of example, if an Integrator only wants to perform Debits then only Test Case 3 comprising 3.0, 3.1, 3.2, 3.3 and 3.4 need to be tested and logs for these submitted. In this case logs for 3.0a, 3.1a, 3.1b, 3.2a, 3.3a, 3.3b, and 3.4a would need to be submitted.
Integrators should keep logs of all requests sent to the Indigo Server as well as the responses received and the data and