* General Requirements * ** iVeri Lite implementation consists of doing a submission of a form post to the Gateway endpoint while including all required/mandatory parameters. Applicable Parameters to be passed in the request are common to all the integration methods supported on iVeri Lite, and elaborated in this documentation. The list of applicable parameters can be found None [1] here [1] /knowsystem/parameters-14

* Full Redirect – Hosted Payment Page *** full%20redirect [2] An example is available online on None [1] this link [1] https://examples.iveri.net/Example/Setup [2] /web/image/221346-df600793/full%20redirect.jpg?access_token=fee03403-03fd-427a-8bec-a2a61e1cf80e

LiteBox Hosted Payment Page * ** The LiteBox hosted payment page is an e-commerce solution that allows merchants to connect, send payment requests to the iVeri Payment Gateway without redirecting the cardholder away from their website. When implemented, the LiteBox pops up and sits in-front of the merchant’s website. From a merchant/cardholder point of view the LiteBox solution provides a more seamless checkout experience. Picture3 [7] An example is available online on None [1] this link . To simulate the LiteBox behaviour, click on “Modal”. Merchants’ developers can download the JavaScript library that handles the events to generate the button. The library can be found on the following URLs: For Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland

* Shopping Carts * ** iVeri Lite plug-in is available for download for the following Shopping Cart platforms: WooCommerce: https://www.iveri.co.za/docs/woocommerce-6 [1] OpenCart: https://www.iveri.co.za/docs/opencart-14 [2] VirtueMart: https://www.iveri.co.za/docs/virtuemart-15 [3] [1] https://www.iveri.co.za/docs/woocommerce-6 [2] /docs/opencart-14 [3] https://www.iveri.co.za/docs/virtuemart-15

* 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

* Query Transaction Status * ** /*Note*/: This is just an extra step that can be used by the Merchant to make sure about the Transaction results. We would recommend that a Merchant should use this as a call to make sure the results he received back from the Authorization (Debit) of a transaction are consistent with the results returned here. The URL to post to is defined under the None [1] Gateway Addresses * Name * *General Description* * Length * *Notes* Lite_Merchant_ApplicationId iVeri ApplicationID 36 Allocated to the merchant during registration Lite_Merchant_Trace Merchant Trace 64 Unique merchant identification for the request. This value is to be used by the merchant to confirm the status of the transaction. The response to the Authorisation Information request is the following: L

/ Transaction Notification /* ** / Email to Merchant */ This is an order confirmation from the Payment Gateway to Lite Application. We have received the following Sale from your customer: Customer Details: Name : Mr. John Doe Email : John Payment Details: Transaction Type : Sale Transaction Index : A0394EB4-BBC1-4567-BBCB-A56B702050DD Merchant Reference : LITE0000028 Card Number : 4242........4242 Expiry Date : 092025 Acquirer Reference : 80903:09089990 Electronic Commerce Indicator : SecureChannel Order Details: Purchase DateTime : 2022-09-03 09:08:32 Total Order Amount : R 100.00 Line Item Details: Item Description Quantity Unit Cost Line Total ----------------------------------------------------- Donation product#1 1 100.00 100.00 Additional Info: Please contact <Distributor> should yo

Additional Variables * ** Note: *These are form variables that are not part of the iVeri Lite specification but may be required by the merchant. These form variables (if used) will be returned to the website together with all the iVeri Lite form variables. For added security, to prevent possible fraud by someone obtaining the websites return URL and parameters, we highly recommend that you submit an additional form variable of arbitrary name chosen by the merchant and random value which changes from transaction to transaction. This will be returned to the website along with all the iVeri Lite form variables and all you need to do is check for the existence of the form variable and that the value thereof is the same as that generated and used during the submission of the iVeri Lite page

* *3D secure (Secure Code or Verified by Visa), is all about call back protection and making sure card holders are who they say they are. The Illustration and process that follows, shows 3D secure in use as implemented by Merchants using iVeri Enterprise and not iVeri Lite. Illustrating the process in this way, helps to show how each entity is involved even if certain functions are performed on behalf of Merchants using iVeri Lite.

3D secure transaction process flow * ** Image [1] 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 a