Field Justification *
**
All Fields are justified in the following manner:-
Numeric Fields are pre-pended with 0's to the full width of the format Alphanumeric Fields are left justified and ' ' (spaces) appended to the full width of the format A* means an unspecified length field - we read to the end of the line.
FNBBase24FNBSouthAfrica
**
Log on at https://admin.aws.iveri.com/ [1] and check the provider status for FNBBase24FNBSouthAfrica.
If any issues exist, contact Retail Assist.
[1] https://admin.aws.iveri.com/
/ Nedbank Gateway /* – Applicable for Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland
Website *
URL *
Port *
BackOffice *
[1] https://backoffice.nedsecure.co.za/
443 *
Lite
[2] https://portal.nedsecure.co.za/Lite/Authorise.aspx
Authorization Information
[3] https://portal.nedsecure.co.za/Lite/AuthoriseInfo.aspx
/ CIM Hosted Gateway /* – Applicable for merchants acquired by CIM Finance in Mauritius
Website *
URL *
Port *
BackOffice *
[4] https://backoffice.merchant.cim.mu/
443 *
Lite
[5] https://portal.merchant.cim.mu/Lite/Authorise.aspx
Authorization Information
[6] https://portal.merchant.cim.mu/Lite/AuthoriseInfo.aspx
/ CSC Hosted Gateway */– Applicable for merchants that acquired by banks af
This purpose of this sections is to give some domain knowledge to people not familiar with the payment domain.
Card Present vs. Card Not Present *** A Merchant interfaces with a card holder and submits a Card Present Transaction request whilst the card holder is waiting, and the card holder authenticates the transaction (typically via signature or PIN entry). In the event of a dispute of the transaction, the merchant must prove that the card holder authorized it, else merchant is liable to refund the card holder.
A Merchant submits a Card Not Present Transaction according to previously arranged agreement with a card holder. The card holder is not present to authenticate the transaction. In the event of a dispute on the transaction, the merchant must prove the card holder authorized it, e
Gateway Release Notes *
**
The release notes contained in this document will be applied on the Hosted Gateway and Nedbank Gateway Notes
Gateway Release Notes V 4.130 *
**
/ Hosted Gateway: /*
Date: 21/05/2023
Start Time: 20:00 UCT +2
Duration: 2-4hrs
Expected Downtime: 5-10mins.
/ Nedbank Gateway: /*
Date: 11/06/2023
Start Time: 20:00 UCT +2
Duration: 2-4hrs
Expected Downtime: 5-10mins.
Enhancements *
Compliance – Mastercard Edits*
MCI: Edit 7 - TermPOS
The Terminal Operating Environment value in POSDATA element has been updated from value “5” to “0” for instances where POSEntryMode is set to “01
Amendments have been made on DE 123 for MasterPass Pin authenticated transactions.
Backoffice 2 *
The inclusion of the "View All" option for Batch users together with the ability to view transactions performed under specific users has been introduced. With this change it is now possible for users to view and do subsequent actions
* Gateway Release V4.136 *
**
* Nedbank Gateway: *
Date: 05/11/2023
Start Time: 20:00 UCT +2
Duration: 2-4hrs
Expected Downtime: 5-10mins.
* 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 5th 2023, on the Nedbank Gateway .
** 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 softwa
The release notes contained in this document will be applied on the Gateway and will be in effect as of July 2026.
Production Release 5.29
Section 1: All Customers ** This section will provide release notes relevant to All iVeri Customers, categorized into compliance, optimization, and feature enhancements.
Features **
Subject:* Add merchant webhook notifications for successful Lite transactions
Product/Platform: *Gateway – Lite
Release Description:*
Added support for posting signed transaction webhook notifications to a configured merchant endpoint after successful Lite transactions. Merchants can configure a webhook endpoint URL, transaction authentication type, and authentication secret; the gateway posts the transaction result payload with a LiteWebhookSignature so the merchant server
The release notes contained in this document will be applied on the Gateway and will be in effect as of July 2026.
Production Release 5.29
Features **
Subject:* Add merchant webhook notifications for successful Lite transactions
Product/Platform: *Gateway – Lite
Release Description:*
Added support for posting signed transaction webhook notifications to a configured merchant endpoint after successful Lite transactions. Merchants can configure a webhook endpoint URL, transaction authentication type, and authentication secret; the gateway posts the transaction result payload with a LiteWebhookSignature so the merchant server can verify the notification.
Subject:* Add BackOffice configuration for transaction authentication and webhooks.
Product/Platform: *Gateway – Lite
Release Description:*
A