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 in the body of the request. While the inclusion of the AuthenticationToken and AuthenticationKey in the headers is optional. Test Mode should be used during integration, testing, and validation. Test application ID must be used with Mode Test Test cards should be used during integration testing and validation

Subsequent Transactions* ** When TransactionIndex is used on subsequent transactions, regular customers do not have to re-supply the card data details however this ONLY works if the merchant developer has made provisions for the following: Ability for the merchant to identify the customer, usually by means of user sign-in  The merchant has successfully processed a transaction on the customers card at some point in time using the iVeri Gateway  That the customer's profile is mapped to the correct Tokenised card details (TransactionIndex, Expiry date etc) returned on the initial or previously processed transaction Once the above provisions are made, the merchant developer would be able to display to the cardholder a masked/dotted card number and the expiry date of the card. The cardholder wo

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

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

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

3D secure transaction process flow * ** Cardholder is on the merchant’s checkout page, ready to pay for their order. They will input and submit their card details on the payment page hosted by the Gateway. The Gateway will proceed to check if the card in use is enrolled in 3DS by sending a request to the Directory Server. Directory Server will respond with enrollment status. Considering the response is positive and the card is enrolled for 3DS,  The Gateway will redirect to the issuer ACS for authentication The ACS will prompt the cardholder to insert and submit OTP/Password/credential(etc.) Considering the authentication was successful, the response is returned to the gateway to confirm successful authentication Gateway then forwards the transaction details to the acquirer for authorizati

* Parameters * ** The following parameters are expected in the form submitted to the Gateway at step 3 of the iVeri Lite None [1] process flow and/or returned by the Gateway in the response at step 6 to the cardholder via the merchant's website. Note: Not all of the fields in this specification are mandatory.The list of parameters below has been split to reflect mandatory and optional data. You can simulate a test form post, using data corresponding to your request, on None [2] this link *Mandatory Parameters:* * Name * *General Description* *Length* * Notes * Lite_Merchant_ApplicationId iVeri Application id 36 Allocated to the Merchant during registration Lite_Order_Amount Amount to authorize 10 The total amount for the order including tax in cents. This must be equal to the sum of the

* 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

Delete Code * ** Function: Delete a code that has been created Delete Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be deleted Response Parameter Description MasterPassAction The action that was performed Delete Code – REST Sample * Request Response { "Version" :  "2.0" , "CertificateID" :  "{xxxxxxxx-71dd-4044-802d-xxxxxxxxxxxx}" , "ProductType" :  "Enterprise" , "Direction" :  "Request" , "Enquiry" : { "ApplicationID" :  "{xxxxxxxx-68e0-42eb-aba9-xxxxxxxxxxxx}" , "Mode" :  "Live" , "command" : "MasterPassQuickResponseCode" , "MasterPassMerchantID" :  "xxxxx" , "MasterPassAction" :  "DeleteCode" , "MerchantRefer