Delete Code * ** Function: Delete a code that has been created Delete Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be deleted Response Parameter Description MasterPassAction The action that was performed Delete Code – REST Sample * Request Response { "Version" :  "2.0" , "CertificateID" :  "{xxxxxxxx-71dd-4044-802d-xxxxxxxxxxxx}" , "ProductType" :  "Enterprise" , "Direction" :  "Request" , "Enquiry" : { "ApplicationID" :  "{xxxxxxxx-68e0-42eb-aba9-xxxxxxxxxxxx}" , "Mode" :  "Live" , "command" : "MasterPassQuickResponseCode" , "MasterPassMerchantID" :  "xxxxx" , "MasterPassAction" :  "DeleteCode" , "MerchantRefer

Query Code * ** Function: Query a code that has been created. Query Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be queried Response Parameter Description MasterPassAction The action that was performed MasterPassShortDescription Short decription linked to the code MasterPassCodeExpiryDate Date until the code is valid. This is in epoch time. MasterPassMerchantName The name of the merchant as captured on MasterPass Amount Amount linked to the code. Currency The currency is tied to the merchant setup. MerchantReference Linked to the code. Query Code – REST Sample * Request Response { "Version" :  "2.0" , "Certifica

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

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

Illustration of Visa Check-Out Process With iVeri Lite* ** Image [1] [1] data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAeAB4AAD/2wBDAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsKCwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRT/2wBDAQMEBAUEBQkFBQkUDQsNFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBT/wAARCALlBS0DASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp

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