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
* 3D Secure 2 implementation using the Form Post *
*
Merchant can POST Form variables to the 3DS 2 endpoint, which is redirect over the browser. On completion of the 3D secure process, the Gateway will return the result to the merchant ReturnURL. The result returned to the merchant will either allow for the continuation of the Authorisation/debit instruction or result in the termination of the transaction by the merchant to the customer.
Format: Form Data
* Form Post request Sample *
<form
name="Form1" method="post"action="https://portal.iveri.net/threedsecure/EnrollmentInitial"
id="Form1">
<input
type="hidden" name="ApplicationID"
id="ApplicationID"
value="{ca8a6eae-a469-4b39-bef3-aa029ca3a806}" />
<input
type="hidden" name="ReturnUrl" id="ReturnUrl"
value="https://[domain]/Lite/Result.as
Gateway Release Notes *
**
The release notes contained in this document will be applied on the Hosted Gateway and Nedbank Gateway Notes
Batch is a payment solution that allows for bulk payment uploads using the iVeri system. It enables a merchant to create and process large volume, card not present transactions.
Batch requires merchants to create a file in a specific format and to upload It securely to the iVeri Payment Gateway for processing. Alternatively, merchants can also use the Create Batch function to manually create batches for uploading and processing. iVeri automatically creates the batch in the required format.
Batches are uniquely identified and can be set up to be processed on a date in the future. This is ideal for month ends that fall on a weekend or a public holiday.
Batch merchants are able to return to iVeri Back Office and view the status of their batch once it has been processed.
*Configure Application*
**
* Purpose *- To receive e-mail confirmations after processing successful transactions and to set-up your transaction viewing preferences, you will now need to set up your choice of transaction configuration.
* Action: *
On the main menu go to Lite – Configure Application.
* Action: *
Click on the Application you want to configure, i.e., either the Test or the Live. Make the relevant changes and click on Submit
Below are some of the details a user would need to configure under Application settings:
E-mail confirmations can be sent to a cardholder. Confirm the E-mail address confirmations are sent to and from. Customise the message on the payment page. Customise the message on payment request e-mail. Copy or Link Merchants Terms and Conditions Show Associated Logo
/ 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
Download File – By Application *
**
Purpose: *
*– To download a processed file for a selected Application ID e.g., Live or Test or if you have more than one Live Application ID you can select the particular Application ID you wish to download. These could also be for the purposes of reusing the file for another entry.
Action: *
From the main menu the user will navigate to: Batch - Download File - By Application.*
Action: *
The user will select the applicable Application ID for which you want to download the file i.e., Either Live or Test.
Action: *
Choose the date that the file was created/uploaded in
the range above 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
* Shopping Carts *
**
iVeri Lite plug-in is available for download for the following Shopping Cart platforms:
WooCommerce: https://www.iveri.co.za/docs/woocommerce-6 [1]
OpenCart:
https://www.iveri.co.za/docs/opencart-14 [2]
VirtueMart:
https://www.iveri.co.za/docs/virtuemart-15 [3]
[1] https://www.iveri.co.za/docs/woocommerce-6
[2] /docs/opencart-14
[3] https://www.iveri.co.za/docs/virtuemart-15
Authorisation Header *
**
When interfacing with the Gateway endpoints, merchants
can include the AuthenticationKey and AuthenticationToken in the headers for
both transaction status queries and transaction submissions.
AuthenticationKey*
The key consists of the username. The key and username must be in lowercase
The Username must be encoded to base64 i.e bWVyY2hhbnRwcm9maWxlPTYxNjk1NA
AuthenticationToken*
The token consists of:
AuthenticationSecret *
This is the secret key generated by the merchant
within Backoffice, which the merchant has to store on the merchant’s system.Once the secret is generated, it remains readable in
plain text for a couple of minutes, after which it is hashed. Merchant must copy the secret immediately
after the secret is generated.
If the merchant loses their sec