The iVeri Lite Payment Gateway is a plugin that extends WooCommerce, allowing merchants to accept payment through the iVeri Payment Gateway. The extension works by giving customers the option to pay via iVeri and then redirecting them to iVeri to make payment. /Installation/ * The plugin can be installed in 2 ways: 1. Upload the zip file using the WordPress Admin Plugin Upload 2. Upload the extracted zip file via FTP to /wp-content/plugins/ on your WordPress website To change the logo that appears on the website, replace the logo.png file with the correct logo.png file you would like to make use of. The file is located under /assets/images/. Please keep the file name the same and the dimensions of the logo/image the same. / Usage /* A merchant account and related iVeri Lite profile is need

Developer Guides * ** These Guides are for developers and will be specific to each of the iVeri products

Test phase * ** The iVeri Gateway provides a mechanism where a merchant can perform test transactions that are routed to an iVeri Gateway issuer simulator. This enables a merchant to complete testing within the test environment. When the merchant is ready to process LIVE transactions, the acquiring bank can activate the merchant profile for LIVE processing which will be routed to the genuine card issuer. When performing a test transaction, using your Test Application ID, the following credit card numbers must be used, based on whether 3DS is enabled, and the MPI (3DS Provider) at play: / Non-3DS iVeri Gateway test cards: */ Card Number * Result Status * Result Description * 4242424242424242 Expiry Date * : Current or future date 0 “” 2121212121212121 (Randomly returns one of 3 results) Ex

* 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

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

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

* 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

* *This section explains how to implement a follow up/subsequent transaction using the TransactionIndex returned from an initial/previous transaction processed successfully. Merchants that wish to accept payments from regular customers without worrying about PCI DSS burdens of storing or retaining the card number have an option of submitting a unique identifier associated with the customers card number from a previously successfully processed transaction. In iVeri's realm, the identifier which the merchant can pass on subsequent transactions is called the “TransactionIndex”. This variable is an iVeri Gateway generated identifier commonly found in Gateway responses to the merchant.