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)
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        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
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        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
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        DiVert Functionality *
**
The Divert API has a parameter “CreateTransactionUrl” that can be set to either “True or “False”. The value set determines how the Gateway handles and processes the message request.
Scenario 1 *
If CreateTransactionUrl” is set to“True” - the Gateway generates a transaction URL and makes a callback to the merchant with the URL.
The merchant can then construct and format their own message, including the URL (returned by the Gateway) and distribute the message to their cardholder using either SMS|Email
When the cardholder receives the messages, it will have all the particulars of the merchant, the cardholder can then click on the URL, and be redirected to a payment page wherein they can make a payment to the merchant
Scenario 2*
If CreateTransactionUrl is set to “Fal
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        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
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        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
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        *** Requirements ***
With the API, merchants are able to generate payment requests to their clients by implementing the “DebitRequest” command and include the specific data parameters that are expected in the message request to the Gateway. The data elements required in the “DebitRequest” command are covered in the Enterprise Documentation
In order to implement the DebitRuquest method, the following should be downloaded or in place.
Reference the Divert Specification Guide  Reference the using the “RequestDebit” method in the Enterprise Documentation  Merchant Agreement with an acquirer with Divert as the solution which will result in a merchant profile on the Gateway
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        * Full Redirect – Hosted Payment Page ***
An example is available online on None [1]  this link
[1] https://examples.iveri.net/Example/Setup
                     
                    
                
            
         
        
            
            
                
                    
                        * *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
                     
                    
                
            
         
        
            
                
                    
                
            
            
                
                    
                        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