Configure – Application *
**
Purpose * – Configuring your application needs to take place before a user can create a batch. To capture the email address of the person to whom the confirmation email will be sent after the upload of a batch confirming either the successful upload or an error in the upload to the selected Application ID.
Action *:
The user will select the applicable Application ID.
Action * :
On the application settings form, the user will capture the email address where all notifications will be sent.
The success message, “Application Fields Modified” will be displayed indicating that the application has been configured successfully.
Duplicate transactions *
**
A problem of a duplicate transaction can occur if a merchant submits a previously successful transaction in a new request. A duplicate transaction of this nature is typically due to a user's unintentional mistake, e.g. pressing the “Submit” button twice, or submitting the same batch twice. It is responsibility of the merchant to ensure that a single transaction request is not submitted successfully more than once.
Nevertheless, the iVeri Gateway provides three mechanisms to protect against duplicate transactions. Specifying a unique MerchantTrace is a client-side configuration, while the latter to require contacting your local distributor.
Specify a unique Merchant Trace for each step in a Transaction Sequence *
As mentioned in section 8.2, a MerchantTrace is a
* Purpose * - To view the list of Successful Orders for a selected Date or Period in order to check these against your confirmation emails or to view ALL details related to individual transactions.
* Action: *
In the menu bar, Mouse over Lite Transactions - View - Successful. If you only have one Application ID, this page will NOT be displayed, and you will be automatically taken to the Choose Date/Period page.
Choose a specific *Application ID*
* *
Choose a date range to start your *Search*
*/ Purpose /* - This function allows you to create a request for payment to be sent to cardholder
/* Action: */
On the main menu bar, select the DiVert menu, Select Transactions and click on Create Transaction Request.
*/ Action: /*
Select the relevant Application ID. A Capture Transaction screen will be displayed
*/ Action: /*
Complete the details on the capture page and click Submit. A resultant page will then be displayed.
Once completed the Submit button is selected and the below Pop up screen will be displayed.
** * Payment Features * ** Depending on the acquirer involved, iVeri Lite has the capacity to offer the following * payment methods * :
Card:
VISA MasterCard AMEX Diners UPI Mobile Money
EcoCash M-Pesa Additional payment methods:
MasterPass Visa Checkout Visa Account Funding Transactions Mastercard Funding Transactions Account-to-Account Transfer:
Ozow *Other functionalities available:*
*3DSecure: *iVeri Lite, being an e-commerce product, allows for 3DSecure protocol for payer authentication in online transactions, if configured accordingly.
To learn more about 3D Secure, visit None [1] this page . *Fraud Management* *Transaction history reporting* *Merchant Portal - BackOffice*: Merchant Portal includes features that are merchant-specific such as reporting, payment pa
Test File *
**
Purpose *– A test batch file can be created to validate that the file format uploaded is in accordance with the iVeri Batch Specification. The test results will provide details should there be any errors within the Test file.
Action: *
From the main menu the user will navigate to: Batch - Test File.*
Action: *
The user will click on "Browse" to locate the created batch. When located on your PC (file directory), select the file, and click on Open. Alternatively the user can drag and drop the file in the space provided. Lastly the user will click on "Submit" to upload the test file.
The result of the format test of the selected batch will be displayed.
* Print Report *
**
*/ Purpose /*- To View / Print / Save reconciliation files for a specific acquirer cycle / settlement period in the following file formats:
PDF
XLS
CSV
*/ Action: /*
Navigate to the menu and select ‘Reconciliation’. From the drop-down menu, select ‘Print Report’.
*/ Action: /*
If you have only one Merchant Card Acceptor ID, simply click on Submit. If you however have more than one, then click on the drop down and select the Card Acceptor ID for which you want the report before you click on Submit.
The following screens and points highlight the various parameters that need to be selected before viewing the report.
* Action: *
Select the required Output format – either PDF or XLS. Find the acquirer cycle number you want to view and click on the actual cycle number. You ca
Download Reconciliation *
**
/ Purpose - /*To download and save the selected reconciliation file in XML format.
/ Action: /*
Mouse over the menu function Reconciliation then click on Download File. This will bring up the following form
/ Action: /*
If you have only one merchant Card Acceptor ID, simply click on Submit. If you however have more than one, then click on the drop down and select the Card Acceptor ID number for which you want the report before you click on Submit. Select the cycle you wish to view.
/ Please Note: /*
If your file contains more than 10000 records, then the time in the message above will show 20 minutes. It is recommended that you click on the words Click Here and you will receive an email when your file is ready for retrieval.
* Application Parameters *
**
*/ Purpose /* – This function is used to allocate application ID(s) that a User is only allowed to have access to. This application refers to specific product and what a merchant uses to process transactions through iVeri.
Example below indicates that when you select a particular Application ID an Administrator can configure what functions can this user perform in a particular Application ID. If no function is associated to an Application ID, no access is granted to that user.
Administrator can configure what Transaction Types a user can perform on a specific Application ID.
If no Transaction Types are configured for a user, the user will be unable to process transactions for any of the Application IDs.
*/ Action /*:
Select the product and Live Application IDs