* *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
Appendix G – Postman *
**
Developers may want to test the protocol independent of their implementation by making use of Postman.
When configuring Postman, the Headers must have an additional attribute added to set Content-Type to the value “application/json” as shown below.
The Body should be set to the JSON as defined in this document to execute the command that is being tested as shown below:
The result received in the response is displayed in the pane below the request. In this case the device 20605360 is not online so the result informs us of that.
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
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
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
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 upcoming production release scheduled for 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
Point 1.
Point 2.
Point 3.
Point 4.
JSON Request *
**
{
"Command": "Cancel",
"DeviceSerialNumber": "81546628"
}