How to measure the network performance * ** The following commands should be executed on the Indigo server and the destination should be the connected Devices. If there is any variation from a network point of view between the location of the various devices connecting to an Indigo Server, then they should be tested separately. Windows PS C:\Users\roland> ping -n 1000 -l 512 192.168.128.14 Pinging 192.168.128.14 with 512 bytes of data: Reply from 192.168.128.14: bytes=512 time=1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 . . . Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512 time<1ms TTL=63 Reply from 192.168.128.14: bytes=512

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.

Example Message Format * **

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

Cardinal & Indigo Release Notes V 20231204 ** The release notes contained in this document are available in iVeri’ s repository in production and can be installed on any Cardinal and or indigo installation on a case-by-case bases as agreed with Customers and or Integrators. Available to All Cardinal/indigo Customers  * Enhancements * PosPort * Introduction of additional parameters on the PosPort channel to facilitate the configuration of two IPs and two DNS entries. This enhancement enables the device to seamlessly connect to multiple designated addresses during transaction processing. IndiGo * A new configuration is introduced for the country code on IndiGo.  This enhancement replaces the previously hardcoded value with a configurable parameter known as "Terminal Country Code."  Additiona

Transaction Life Cycle * ** The following diagrams describe how related stages can be executed during the life cycle of a transaction. There are three diagrams to illustrate the three possible starting points that a transaction life cycle can start from and, once it has started, what follow-up transactions can be performed on them. The data which links transactions together is the MerchantReference which is generated by the POS Till and/or MerchantTrace which is generated by the Indigo Server and returned in appropriate response messages to the POS Till. There is a subtle distinction between a Refund (command = Credit) and Payment (command = Credit); a Refund is the term used when returning money previously taken from a cardholders account by a Sale (command = Debit). A Payment is not link

Introduction * **

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

Introduction ** This content is called the Shopify Merchant Take on Guide. This Learner guide provides an overview of the Merchant onboarding process on the Gateway as well as the Shopify Merchant interface and how merchants would navigate the platform to configure iVeri as their payment provider through their Shopify store. The Guide covers the iVeri Admin Portal used by the Acquirer to onboard a Merchant and the Shopify Back end used by the Merchant to configure iVeri as their payment provider. Objectives ** The Objective of this user guide is to outline the actions on the iVeri Admin Portal and Shopify Back End interface through the use of step by step screen representations. The user guide explains in detail how the merchant interface works and the related functionalities available wit

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