Create Code * ** Function: Generate a transactional code that can then be paid for by a cardholder. This code can be represented as a QR code, transferred using NFC or manually entered a device. The code can also be used as part of an In-App payment. /Create Code Parameters/* Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassShortDescription Mandatory, This will be displayed to the consumer at the time a code is scanned. Length is 5 to 45 characters MasterPassCodeExpiryDate Optional. If this is empty the code will by default expire in 30 minutes from issue. If this value is 0 the code will never expire. This time is specified in epoch. Amount Mandatory, To use a variable amou

* 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: iveri%20Lite%20flowchart%20-%20horizontal%20-%202024 [1] /*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, t

Parameter per Acton * ** M Mandatory O Optional C Conditional blank not relevant Context Parameter Authorisation with PAN Authorisation with Track2 Authorisation with VisaCheckoutCallID Additional Authorisation with TransactionIndex AuthorisationReversal with TransactionIndex Debit with PAN Debit with Track2 Debit with PIN Debit with VisaCheckoutCallID Debit with TransactionIndex Credit with PAN Credit with Track2 Credit with TransactionIndex Void Balance Enquiry with PIN PAN Enquiry with PAN PANToken Enquiry PAN Enquiry with Track2 Ping Get Device PIN Key ThreeDSecureCheckEnrollment ThreeDSecureValidateAuthentication RequestForDebit MasterPassQuickResponseCode MasterPassPaymentNotification DynamicCurrencyConversion MultiCurrencyPricing Core * ApplicationID * M * M * M * M * M * M * M * M

*Registering as a merchant * ** Merchant account can be attained by registering with an acquiring bank, a list of which can be found on this page [1] [1] /knowsystem/distributors-contact-information-33

The merchant portal Backoffice allows for the following core functions: Management of User Creation of users Transaction Types allowed per user created Backoffice functionality views allowed Applications permitted on a user created Transaction Reports & Listing & Lookups Reconciliation  Reports Blacklisting of cards Customise payment request page with Merchant’s Corporate Identity. Create Transaction Requests Process Subsequent Transactions (Refunds)

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

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

* 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

* *Below is the contact information per distributor for registering billing and banking details with iVeri. An iVeri Distributor markets the services of the iVeri Gateway and products within a locality. Nedbank South Africa * *Location*: South Africa *Telephone*: 0860 114 966 *Websites*:  http://www.iveri.co.za/ [1]    |  http://www.nedbank.co.za/ [2] *Email*: ·        Technical Assistance  operations@iveri.com [3] ·        Non-technical requests/questions (e.g. costs, agreements, product information etc):  info@iveri.co.za [4] Nedbank Namibia * Location*: Namibia Websites*:  http://www.iveri.co.za/ [5]    |  http://www.nedbank.co.za/ [6] Email*: ·        Technical Assistance  operations@iveri.com [7] ·        Non-technical requests/questions (e.g. costs, agreements, product information et

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.