* *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

Transactions ** Create Transaction Request * Purpose  /* - This function allows you to create a request for payment to be sent to cardholder Action: */ To create a transaction request, start by navigating to the DiVert tab on the homepage. Then, select Transactions and click on Create Transaction Request. image%20%282%29 [2] Action:* Here, choose the Live application ID. Once selected, you’ll be redirected to the Create Transaction Request form, where you can enter all the transaction details. image%20%283%29 [3] Create%20a%20Transaction%20Request%20-%203 [4] Let’s go through the details you’ll need to enter when creating a transaction request: Cardholder Name*: Enter the cardholder’s name exactly as it appears on the card. Cardholder Email*: Input the cardholder’s email address. This is

DiVert Batch Upload File XML Specification * ** Divert Batch Upload * This section describes the contents of the Divert batch file uploadable in Backoffice with Command “DivertUpload”. The Divert Backoffice user guide on how to upload the Divert Batch XML file in Backoffice. The same functionality can be implemented using Enterprise API. The Divert Batch Upload File has the following XML tags: V_XML Version="2.0" Direction="Request"> <DiVert Version="1.0" Command="DiVertUpload" Count="" Amount=""> <Date></Date> <Filename></Filename> <CreateTransactionUrl></CreateTransactionUrl> <DiVertItem ApplicationID="" Mode="test" Command="Debit"> <Amount></Amount> <Currency></Currency> <OrderDescription></OrderDescription> <MerchantReference></MerchantReference> <AllowBudgetPeriod>false</AllowBudgetPe

Introduction  *** Divert is a payment solution that allows merchants to request payment from their cardholders for services rendered. Traditionally, this functionality has only been available by accessing the merchant portal – Backoffice where merchants can populate the cardholder data and the payment amount agreed between the merchant and cardholder. On completion, a payment link via email would be distributed to the intended cardholder. The API implementation carries the same functionality found in Backoffice, the aim of the API is to extend the existing functionality to a wider audience whose requirement may be to automate the process of generating the payment link from the Gateway thus giving control and flexibility to the merchant, making it possible for merchants to integrate the pay

Downloads *** Download for products

Enabling ABU on the Admin Portal * ** Below we will look at the step-by-step process of enabling a merchant for Automatic Billing Updater via Admin Portal. Navigation Path: To navigate to this screen, Select Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab. Navigate to the ‘Supplementary’ parameter and click on the expansion tab. Navigate to the ‘ABU enabled’ parameter. This parameter defaults to ‘No’. To enable ABU, untick the default value. From the dropdown, select ‘Yes’. The next parameter that needs to be populated is the ‘ABU Merchant ID’. This parameter needs to be populated with the Merchant ID. The Merchant ID is provided / supplied by the Acquirer. Untick the default value and enter the ABU Merchant ID Lastly, save the changes that you hav

Below we will look at the step-by-step process of enabling a merchant for MauCAS via the Administration Website. Navigation Path: To navigate to this screen, Select Applications > Update > Provider Specific. 1. Click on the ‘Common Provider’ expansion tab. 2. Navigate to the ‘Third Party’ parameter and click on the expansion tab. 3. Navigate to the ‘MauCAS enabled’ parameter. This parameter defaults to ‘No’. 4. To enable MauCAS, untick the default value. 5. From the dropdown, select ‘Yes’. 6. The next parameter that needs to be populated is the ‘MauCAS Merchant ID’. This parameter needs to be populated with the Merchant ID. The Merchant ID is provided / supplied by the Acquirer. 7. Untick the default value and enter the MauCAS Merchant ID. 8. Lastly, save the changes that you have captured

Enabling Merchants for Recurring transactions * ** Merchants that process recurring transactions need to be enabled as such via the Admin Portal. In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions. We will have a look at how to enable a merchant for recurring transactions via the Admin Portal. Navigation Path to this screen: Applications > Update > Provider Specific. Navigate and expand on the ‘Processing’ parameter. Scroll down to the ‘Cardholder Presence default’ parameter. The parameter is defaulted to ‘no’ Untick the default value. From the dropdown menu, select ‘Recurring transaction’ The next parameter that ne

Below is the process of how to enable MOTO transactions for a merchant on the Admin Website: Navigation Path: Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab as illustrated. 1. Navigate to the ‘Processing’ parameter and click on the expansion button. moto1 [1] 2. Navigate your way to the ‘Cardholder Presence Default’ Parameter. This parameter will be defaulted to ‘Not specified’. moto2 [2] 3. Untick the ‘Use Default’ tab. From the drop down, select ‘Mail/Telephone Order (single transaction)’. moto3 [3] 4. Lastly, to ensure the change has been saved, click on the ‘Update Parameters’ tab. moto4 [4] [1] /web/image/351226-55085015/moto1.png?access_token=a03576b8-fe21-4b94-b4c7-b2fe65ec31f6 [2] /web/image/351227-0b632be4/moto2.png?access_token=8d6f6399-44

Merchants that process recurring transactions need to be enabled as such via the Admin Portal. In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions. We will have a look at how to enable a merchant for recurring transactions via the Administration Website: Navigation Path: Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab as illustrated. 1. Navigate to the ‘Processing’ parameter and click on the expansion button. me1 [1] 2. Navigate your way to the ‘Cardholder Presence Default’ Parameter. This parameter will be defaulted to ‘Not specified’. me2 [2] 3. Untick the ‘Use Default’ tab. F