Airline addendum data ** Airline addendum data is additional transaction data which appear on a card holder's statement when buying a ticket from an airline merchant who include this data in a transaction request. Airline addendum data is currently only available for Nedbank. In addition, the airline addendum data is currently only supported for follow-up debit (pre-authorised debit) transactions. Coding for Airline addendum data * The following is a code snippet in C#: enterprise.openElement("AirlineData"); enterprise.setTag("PassengerName", passengerName); enterprise.setTag("PrimaryTicketNumber", primaryTicketNumber); enterprise.setTag("FirstDepartureLocationCode", firstDepartureLocationCode); enterprise.setTag("FirstArrivalLocationCode", firstArrivalLocationCode); enterprise.setTag("PNR

Add User * ** / Purpose /* - To add/capture the details for a new user. / Action /*: Hover over to Users. The following screen will appear. Select “Add New User”. Fill in all the mandatory fields (marked [*]) and click on “Save changes”. A resultant message will be displayed.

Authenticated Collections ** Authenticated collections are intended to enable a merchant who wants to make regular direct debits to a customer’s account to authenticate the customer. This has two benefits: The merchant has proved that the customer has consented to these regular debits  The customer has verified themselves by way of a pin validation so there is a higher level of comfort that the customer's account is a valid account and does belong to the customer. Authenticated Collections is currently only available from Nedbank. In addition, the Authenticated Collections provider parameter must be enabled otherwise the transaction will be declined. Coding for Authenticated Collection data The following is a code snippet in C#: enterprise.openElement("AuthenticatedCollectionData"); enterp

Fleet card transactions ** Fleet cards facilitate the tracking of costs and managing statistical information of a fleet of vehicles. A Fleet transaction refer to special processing for a Fleet card.  Fleet transactions are currently only available within distributor Nedbank.  If a fleet card is received with other distributors, then the fleet specific parameters are ignored.  Coding for Fleetcards  * The following optional input parameters are Fleet specific per transaction: CustomerReferenceIdentifier The following optional input parameters are Fleet specific per Line item: ProductCode  Quantity  QuantityDecimalPlaces  UnitCost The latest available values of the ProductCode field are obtained via the “Inventory” download command (See section 22). Only use the ProductCodes with Type='Fle

* LiteBox Hosted Payment Page * ** The LiteBox hosted payment page is an e-commerce solution that allows merchants to connect, send payment requests to the iVeri Payment Gateway without redirecting the cardholder away from their website. When implemented, the LiteBox pops up and sits in-front of the merchant’s website. From a merchant/cardholder point of view the LiteBox solution provides a more seamless checkout experience. An example is available online on None [1] this link . To simulate the LiteBox behaviour, click on “Modal”. Merchants’ developers can download the JavaScript library that handles the events to generate the button. The library can be found on the following URLs: For Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland: https://p

Enterprise

Enterprise * **

Refund – “Follow-Credit” ** Allows for a previously debited amount to be returned to the cardholders account using a detail of a previously processed transaction. REST SOAP Request { "Version" :  "2.0" , "CertificateID" :  "{5c4b9c74-0063-4240-9cff-f730675c5bd0}" , "ProductType" :  "Enterprise" , "ProductVersion" :  "WebAPI" , "Direction" :  "Request" , "Transaction" : { "ApplicationID" :  "{d8d5a94-8fa0-428d-a539-3a5baf166f7f}" , "Command" :  "Credit" , "Mode" :  "Test" , "Amount" :  "1000" , "MerchantTrace" : "20220812_1107" , "MerchantReference" :  "20221123_1106" , "TransactionIndex" :  "{CB7A9E38-4797-4513-85EE-AFE63C957ED3}" } } < soap:Envelope   xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd = "http://www.w3.org/2001/XMLSchema"   xmlns:soap = "http://schemas.xmlso

Advanced Fraud Screening ** The following optional input parameters are CyberSource specific per Line item: Discount  ItemCommodityCode  ItemDescriptor  ProductCode  Quantity  TaxRate  Total  UnitCost  UnitOfMeasure  PassengerFirstName  PassengerLastName  PassengerID  PassengerStatus  PassangerType Note: The fields in Blue will be used when doing Advanced Fraud Screening and is not recorded on the iVeri system. Since Line items are repeated, the advanced Enterprise methods openElement and closeElement must be used. The following is a code snippet in https://vb.net/ enterprise.setTag("ShippingTaxRate", shippingTaxRate) enterprise.setTag("TransactionDiscount", transactionDiscount) enterprise.setTag("UniqueVATInvoiceReferenceNumber", vatReferenceNo) Dim dr As DataRow For Each dr in myTable.Ro

3D Secure

3D Secure * ** 3D secure is an XML-based security protocol for online credit and debit card transactions. 3D Secure adds an authentication step for online payments, making it possible for cardholders to authenticate their online transactions with their card issuers, using a password or OTP. Benefits of using 3D secure * Reduces fraudulent debit & credit card transactions processed through online platforms Gives the merchants and acquiring bank liability protection 3D secure providers * CyberSource Bankserve 3D secure with iVeri * High: 3D secure – If a merchant is deemed high risk, the acquiring bank can set merchants on this level. Merchants that want lowest possible risk can also opt for this level. Medium: 3D secure/attempted- This option gives merchants a broader reach in the cards the

Additional Data for Procurement Transactions ** Procurement transactions refer to transactions that contain the line item (or order basket) details. If the line-item details are sent to iVeri within a transaction, then a procurement card holder get those details from their issuing bank (for example on their monthly statement). This is of assistance in tracking business to business transactions particularly in large corporations. Procurement transactions are currently only available within distributor Nedbank. Coding for Procurement  * The following optional input parameters are Procurement specific per transaction: CustomerReferenceIdentifier  CustomerVATRegistrationNumber  DestinationCountry  DestinationZIPCode  NationalTax  NationalTaxIndicator  OrderDate  PurchaseIdentifier  ShipFromZIP