* Development phase * ** At this stage you will proceed with development based on the integration method [1] you have selected, and may reach out for your contact at the acquiring bank if you require support. [1] /knowsystem/general-requirements-10

* iVeri Lite Process Flow * ** iVeri Lite requires very little integration and is aimed at Internet merchants who have limited technical resources. Lite transactions are processed on a web site and secured via an SSL certificate without the merchant having to buy SSL since iVeri lite takes care of it on their behalf. Although ideal for websites with small catalogs, iVeri Lite still provides a powerful processing engine. */ Process Flow /* This diagram illustrates the flow of events of an iVeri Lite transaction: /*Process Flow Description:*/ (1) The cardholder is at the point in the purchase process where the basket has already been selected and he is now on the brink of paying for it. The website thus knows the price of the basket, the Invoice Number (the merchant could also have iVeri Bac

Updating Cipher Suites for Web Application Firewall (WAF) Security ** Release Description:* Updating Cipher Suites for Web Application Firewall (WAF) Security Category: *Compliance Target Audience: * Implementation date: 20/01/2025* Ciphers:  * The primary purpose of ciphers is to ensure confidentiality, integrity, and authenticity of data during transmission. Using strong ciphers as outlined by PCI DSS is crucial for protecting sensitive cardholder data and ensuring compliance with industry standards, ultimately helping to safeguard against data breaches and cyber-attacks. Strong Ciphers: * Strong ciphers provide high levels of security, making it extremely difficult for unauthorized parties to decipher the encrypted data without the correct decryption key. Importance of Strong Ciphers:*

BIN Management **

*Registering as a merchant * ** Merchant account can be attained by registering with an acquiring bank, a list of which can be found on this page [1] [1] /knowsystem/distributors-contact-information-33

Transaction Sequence ** Authorisation Flow * The possible transaction sequence flow with an initial Authorization is the following: Image [1] Debit/Sale * * The possible transaction sequence flow with an initial Debit is the following Image [2] Refund/Credit * * The possible transaction sequence flow with an initial Credit is the following: Image [3] Transaction Commands *** The following transaction types encompasses the payment mechanism which the iVeri Gateway supports and may cause the transfer of funds from cardholder to merchant or vise-versa. Transaction Commands* Description* Authorisation (also known as “Preauthorisation”) Causes a reservation of funds on the cardholder’s account. Authorisation Reversal Unreserve the funds previously reserved on the cardholder’s account. De

An action corresponds to the combination of a payment mechanism and a command. The concept of an action is used within the documentation and examples as a means of describing functionality. The Enterprise API and iVeri Gateway use the concepts payment mechanism and command instead of Action. The iVeri Gateway allows for the following actions: Authorisation with PAN Reserve funds when a card is not present. This action is commonly known as a "Pre-Auth/Pre-Authorisation" Authorisation with Track2 Reserve funds when a card is present. Funds reservation is not applicable for cards requiring a PIN. This action is commonly known as a "Pre-Auth/Pre-Authorisation" Authorisation with VisaCheckoutCallID Reserve funds when a card is present. Funds reservation is not applicable for cards requiring a P

This document uses certain iVeri specific terminology which can be referenced in Parameter Description [1] [1] /docs/enterprise-developer-guide-58#parameter-description-1330-0

Merchants are required to enter into a “Agreement” with an authorized Acquiring Institution. Once there is a merchant agreement in place, a merchant profile can be created. With Enterprise calls to the Gateway, the presence of a certificate ID is required, with the actual physical certificate available as optional means to authenticate merchant requests.  Test Mode should be used during integration, testing, and validation. Test application ID must be used with Mode Test

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 August 2025, on the Hosted Gateway. iVeri Gateway Release Version 5.10* ** Section 1: All Customers * This section will provide release notes relevant to All iVeri Customers, categorized into compliance, optimization, and feature enhancements.: Compliance* Subject: Updated Procedure for Removal of Blacklisted Cards Product/Platform: Gateway - Core Release Description: The stored procedure that handles the removal of blocked cards has been updated to extend the blocking period from 3 months to up to 1 year. This enhancement supports new merchant advice codes that mandate a longer blocking duration of one year. Subject: Implementation of PCI-D