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

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.

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

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)

Subsequent Transactions implementation * ** On the request to the Gateway, the merchant developer has to pass all the required variables that pertain to a subsequent transaction so as to make sure that the iVeri Gateway handles the request appropriately. Variables that should be present in the request to the iVeri Gateway are as follows: The Lite_PanFormat must be set to TransactionIndex  Set the Lite_TransactionIndex to the actual TransactionIndex value e.g {000000-000000- 000-0000 0000000}  Set the Ecom_Payment_Card_Number to the Dotted PAN value Note:* These variables are defined in 8.2 iVeri specification. In addition to these the merchant will still need to pass all the other required variables.

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

Initial Transaction * ** When a merchant sends a transaction request(POST) to the iVeri Gateway, the response returned to the merchant generally contains a number of variables, some of which are important when performing subsequent transactions, in order for the merchant to implement subsequent transactions the following variables must be stored on the merchants database. Lite_TransactionIndex Ecom_Payment_Card_Number  Ecom_Payment_Card_ExpDate_Month  Ecom_Payment_Card_ExpDate_Year

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

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

/ 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