Reversal of a previously successful Authorisation *
**
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 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
* *Divert is a payment solution that allows merchants to request payment from their cardholders for services rendered. Traditionally, this functionality has only been available by accessing the merchant portal – Backoffice where merchants can populate the cardholder data and the payment amount agreed between the merchant and cardholder. On completion, a payment link via email would be distributed to the intended cardholder.
The API implementation carries the same functionality found in Backoffice, the aim of the API is to extend the existing functionality to a wider audience whose requirement may be to automate the process of generating the payment link from the Gateway thus giving control and flexibility to the merchant, making it possible for merchants to integrate the payment requests i
Benefits of ABU *
**
Here are some of the benefits of Automatic Billing Updater (ABU):
Reduce transaction disruptions due to account changes Prevent late fees and service disruption Lower operating and processing costs by reducing Card-Not-Present declines
Which iVeri products are ABU applicable to?
Lite Enterprise DiVert Batch Link IYS
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
* What is IYS? *
Iveri has partnered with an eCommerce 3rd party that specializes in the creation of applications (i.e. mobile and website) that enable merchants to be able to display their goods and services they are selling in order to receive payments (i.e. online payments). Merchants will be able to do this through the use of an App that was created and renamed for iVeri, called IYS – Increase Your Sales.
Utilizing the designated API, it provides merchants the ability to set up their online stores to be able to receive payments based on what they are actively selling, allowing them to categorise and display what they want to present to their end customers.
*Co-partnership with iVeri*
The eCommerce 3rd Party has partnered with iVeri to enable their merchants to be able to implement this
Below is a step-by-step illustration of how to create a new BIN. This request will come from authorized personnel ONLY at the Acquiring bank for the creation of a new BIN.
Navigation Path:*
From the main menu select:
Systems > iVeriDB BIN > Local BIN*
1. Select the ‘Create New’ tab to initiate the process of creating a new BIN.
The following General information’s tab will appear.
2. Here the user will complete the information relating to the BIN as received from the Acquirer.
BIN – BIN number will be provided by the Acquirer. This applies to the creation of a new BIN as well as amending the parameters of an existing BIN.
Card Number Length – We require confirmation from the Acquirer regarding the Card Number length. Specifically, we need confirmation of both the minimum (referencing the fi