V4.139 7/2/2024
**
Release Notes Overview
The release notes provided in V1 of this document serve as an initial preview of the changes expected in the upcoming production release scheduled for November 12th, 2023, on the Hosted Gateway.
The definitive release notes for deployment in production will be included in V2 of this document.
Summary
The Gateway release notes will contain information related to the new iVeri software release. The release notes will include the impact of software release to the intended target audience.
The release notes will adopt the format outlined below, as applicable:
Compliance - Refers to the adherence of the software to specific industry standards, regulations, or internal policies. This includes ensuring that the software meets legal and regulatory requirem
* 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
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
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.
* 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
* Authorisation Reversal *
*
Unreserve the funds previously reserved on the cardholder’s account.
*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
* / Purpose /* - The 'Active Session' tab reflects who is logged in and provides the menu options which the logged in user is able to access or use.
/ 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
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