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
The Objective of this user guide is to outline IYS Back End interface through the use of step by step screen representations, explaining in detail how the merchant interface works and the related functionalities available within IYS.
Objectives *
**
This guide aims to foster awareness and comprehension of Automatic Billing Updater (ABU) while clearly delineating the roles and responsibilities of all stakeholders engaged in the ABU enablement process for a merchant.
Through visual aids, we will walk you through the process of enabling ABU for a merchant via the Admin Portal, including any additional configurations that may be necessary.
/Note:/* This guide aims to demonstrate to the user how to enable ABU, assuming that the user is capable of onboarding a merchant.
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
Out of Band Transaction notification is a dedicated messaging system that allows merchants to receive their transaction outcome reliable and timeously. The transaction outcome available in the Out of Band notification system contains the same data elements as would be found when doing a transaction look up in the gateway's endpoint or directly from Backoffice. Merchant developers can implement a webservice that will consume the transaction notification payload. The transaction notifications are usually available when the cardholder completes a payment to the merchant.
Format of the OOB Transaction Notification The transaction notifications to the merchant are JSON formatted, the body of the message contains a Base64 string of the VXML response. The VXML response parameters are defined in
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
* 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
This section describes the various gateway parameters available. For more on input and output parameters per transaction type refer to Parameter Description & Action [1]
Data Types * **
The following key table is used for data types:
Data Type *
Description *
A
Alpha only (A-Za-z)
AN
Alphanumeric (a-zA-Z0-9)
Base64
Base64 encryption of binary data
Boolean
True or False
Guid
Globally Unique
Identifier: {[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\} (eg {8E51611F-E19A-4FF0-B229-6A69F42AAA62})
Hex
Hex (0-9A-Fa-f)
N
Numeric (Positive integer)
N.
Digits and dots (.) (e.g's
4242........4242, 1.0)
N:
Digits and colons
String
ANPS Free format string containing:
Alpha, numeric, special and padding (printable ASCII)
Z
Positive or negative integer
Node Type *
Set
*
*
* Parameter description ***
Command *
Authorisation *
Debit *
Credit *
AutohorisationReversal *
Void*
GetData*
Cancel*
GetHMAC*
GetSystemInfo*
Parameter*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
In*
Out*
Description*
AcquirerCode
O
O
O
O
O
The Acquirer ISO code returned for this transaction. Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription. This is only made available as extra information and may not exist in all response.
AcquirerDescription
O
O
O
O
O
The Acquirer ISO description returned for this transaction. Note that the success or failure of this transaction MUST be determined by the Result Code and NOT by the AcquirerCode nor the AcquirerDescription
Core Parameters ***
Parameter*
Description*
ApplicationID
Identification of the merchant’s configuration within the iVeri Gateway
CertificateID
The iVeri CertificateID installed on the server communicating with the
iVeri Gateway
CertificatePath
Valid Path to directory where the KeyStoreFile or CertificateFile exists
on the filesystem
CertificateFile
Existing certificate file
CertificatePassword
Password of the certificate
Gateway
The name of the gateway connecting to. If not explicitly set, the default
gateway is used.
RequestID
A unique identifier generated by the iVeri Gateway for this request
Mode
The mode of the corresponding ApplicationID.
Test*| Live*
GetDevicePINKey
Get DevicePINKey (use Category='Security')
Ping
Ping (use Category='System')
Category
use if Command = 'Debit' or 'Cre