Prerequisites * ** The below parameters must be set in the merchant Backoffice Enable Token Verification to “Yes” (By default this parameter is set to “No”)  Populate the Lite Shared Secret key parameter. Maximum length 32 characters (alpha-numeric)

Requirements * ** Merchants must generate the token on their web server and pass the generated token to the transaction request. The generated token must encompass the following data elements: Lite_Order_Amount: Total amount of the order as specified in 8.2 Lite_Merchant_ApplicationId – The merchants app ID as specified in 8.2 Ecom_BillTo_Online_Email – Email of the cardholder as specified in 8.2  TimeStamp – The timestamp when the token is generated

Token Verification Logic in the Hosted Payment Page * ** If Enable Token Verification has been set to YES and Lite Shared Secret has not been set an exception will be thrown when submitting a transaction request If Enable Token Verification has been set to YES and Lite_Transaction_Token has not been set an exception will be thrown when submitting a transaction request  If Enable Token Verification has been set to YES and the Lite_Transaction_Token does not match the calculated token an exception will be thrown

* Merchant Hash Token Generation * ** /* *secretKey - Lite Shared Secret *resource - /Lite/Authorise.aspx *applicationId - Lite Application Id *amount - Lite Order Amount *emailAddress - Ecom BillTo Online Email */ public static string GenerateTransactionToken(string secretKey, string resource, string applicationId, string amount, string emailAddress) { string time = Convert.ToString(UnixTimeStampUTC()); string token = secretKey + time + resource + applicationId + amount + emailAddress; return String.Concat("x:", time, ":" + GetHashSha256(token)); } public static Int32 UnixTimeStampUTC() { Int32 unixTimeStamp; DateTime currentTime = DateTime.Now; DateTime zuluTime = currentTime.ToUniversalTime(); DateTime unixEpoch = new DateTime(1970, 1, 1); unixTimeStamp = (Int32)(zuluTime.Subtract(unixE

* *Visa Check-Out is a digital representation of a cardholders Visa Card. Cardholders can register their debit or credit cards by downloading the Visa Check-Out app. Once cardholders have their profiles and card details loaded in Visa Check-out, they are able to make purchases at merchants who are accepting with Visa Check-Out payments. The Visa Check Out process flow explained below showcases the different parties involved.

Process Flow in Visa Check-Out with Lite * ** Cardholder selects Visa Check-Out as payment method iVeri Lite calls Visa Light Box or Widget and presents it to the Cardholder to Login Cardholder Logins via Visa Light Box Cardholder selects a card and presses Continue Upon clicking Continue, iVeri Lite receives a Call ID (uniquely identifies the transaction) iVeri Lite uses the Call ID to get the Payload from Visa services Payload is returned by Visa services to iVeri Lite iVeri Lite decrypts the Payload and retrieves the PAN iVeri Lite sends the transaction request to the gateway/acquire When the response is received, Visa services is updated with either a Failed or Successful response Lastly, a redirect to the merchant with the transaction response is made.

Illustration of Visa Check-Out Process With iVeri Lite* **

MasterPass is a safe and easy way in which merchants can present the QR code which customers can scan using a MasterPass application to affect a payment. */Requirements/* Merchant must be onboarded for MasterPass on the iVeri Gateway and on the MasterPass platform.

** * Payment Features * ** Depending on the acquirer involved, iVeri Lite has the capacity to offer the following * payment methods * : Card: VISA MasterCard AMEX Diners UPI Mobile Money EcoCash M-Pesa Additional payment methods: MasterPass Visa Checkout Visa Account Funding Transactions Mastercard Funding Transactions Account-to-Account Transfer: Ozow *Other functionalities available:* *3DSecure: *iVeri Lite, being an e-commerce product, allows for 3DSecure protocol for payer authentication in online transactions, if configured accordingly. To learn more about 3D Secure, visit None [1] this page . *Fraud Management* *Transaction history reporting* *Merchant Portal - BackOffice*: Merchant Portal includes features that are merchant-specific such as reporting, payment pa

* 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