QR Code - MasterPass

* QR Code – MasterPass Parameters * * * Context * * Parameter * * MasterPassQuickResponseCod *e* * * MasterPassPaymentNotification * * Credit with TransactionIndex * * Void * Core ApplicationID * M * * M * * M * * M * Core Category * M * * M * * M * * M * Core CertificateID * M * * M * * M * * M * Core Gateway * O * * O * * O * * O * Core Command * M * * M * * M * * M * Core Mode * M * * M * * M * * M * Common Amount *   * *   * *   * *   * Common ExipiryDate *   * *   * *   * *   * Common Currency *   * *   * *   * *   * Common MerchantReference *   * *   * *   * *   * MasterPass MasterPassAction * M * *   * *   * *   * MasterPass MasterPassMerchantID * M * *   * *   * *   * MasterPass MasterPassShortDescription *   * *   * *   * *   * MasterPass MasterPassCodeExpiryDate *   * *   * *   *

Print Report – Batch Details * ** Purpose *- To view a list of all transactions performed for a selected Date or Period. Action: * In the menu bar, Select Batch - Print Report - Batch Details.  * Action: * The user will select the applicable application ID. Action: * The user will select the Date range and click on Search. This will bring up the list of ALL transactions performed for your selection. Action:  * Select the file format you wish to obtain from the drop down (either the default PDF, CSV or XLS) and then select the file from the list which you want to download and click on Print. This will bring up the following screen. The Print Button will start an automatic download to your PC.

User Manager

User Manager ***

Introduction to Enterprise

* Enterprise Introduction  *** The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd provides proven credit card payment solutions for businesses that have online or physical presence. The use of Enterprise API's is ideal for merchants that want complete control & flexibility of the payment page and transaction mechanisms supported. Enterprise API’s currently support the following Webservices REST SOAP */Merchant Requirements/* Merchants are required to enter into a “Agreement” with an authorised Acquiring Institution. Once there is a merchant agreement in place, a merchant profile can be created With Enterprise calls to the Gateway, the presence of a certificate ID is required, with the actual physical certificate available as optional means to authentica

* Request Payment – Divert Parameters * * * * Context * * Parameter * * RequestForDebit * * RequestForAuthorisation * Core ApplicationID * M * * M * Core Category * M * * M * Core CertificateID * M * * M * Core Gateway * O * * O * Core Command * M * * M * Core Mode * M * * M * Common Amount * M * * M * Common Currency * M * * M * Common MerchantReference * M * * M * Common CardholderName * M * * M * Common CardholderEmail * C * * C * Common OrderDescription * O * * O * Common AllowBudgetPeriod * O * * O * Common RequestExpiryDate * O * * O * Common CreateTransactionUrl * O * * O *

Download File – By File * ** Purpose *– To download a selected file by a specific file name. Action: * From the main menu, the user will navigate to: Batch - Download File - By File.* Action: * Select the date range that the file was created/uploaded by manually changing the default dates above or clicking on the calendar icon next to each date and select each date in the calendar that is displayed. Then click on Search. The result of your search will then be displayed. Action: * Select the filename of the file you want to download. The following page will be displayed. Your selected file is displayed for you to download. Click on "Download". Select the file format you wish to obtain from the drop down (either the default Fixed File Text format or XML) and then click on Download. You can n

Enterprise

Enterprise * **

Developer Guides

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

BackOffice User Guide

BackOffice User Guide * ** This document details the functionality available in Backoffice for merchants. The merchant interface (URL) to be accessed depends on the acquirer in which the merchant has an agreement with.

Card Present Parameters

/ Sale/Purchase /* * Context * Parameter * Debit with Track2 * Debit with TransactionIndex * Credit with Track2 * Credit with TransactionIndex * Void * Core ApplicationID M * M * M * M * M * Core Category M * M * M * M * M * Core CertificateID M * M * M * M * M * Core Gateway O * O * O * O * O * Core Command M * M * M * M * M * Core Mode M * M * M * M * M * Common Amount M * M * * * * Common ExipiryDate M * M * * * * Common Currency M * M * * * * Common MerchantReference M * M * * * * Common MerchantTrace O * O * * * * Common BudgetPeriod O * O * * * * Common OriginalMerchantTrace * * * * * Common Track2 M * C * * * * Common PANMode M * C * * * * Common Terminal M * C * * * * Common AccountType M * C * * * * POS CashAmount O * O * * * * POS DeviceFirmware O * O * * * * POS DeviceFirmwareVe