Airline Data **
Parameter
Node Type
Data Type
Min Length
Max Length
Description
PassengerName
subTag
AN
0
60
Passenger's first name.
PrimaryTicketNumber
subTag
AN
0
60
FirstDepartureLocationCode
subTag
AN
0
32
FirstArrivalLocationCode
subTag
AN
0
32
OfficeIATANumber
subTag
AN
0
32
OrderNumber
PlaceOfIssue
DepartureDate
Note: The fields in Blue will only be used when doing CyberSource Advanced Fraud Screening.
CompleteRoute
DepartureTime
JourneyType
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
CyberSource Fraud Management
**
CyberSource data is additional transaction data which iVeri Payment Technologies Ltd needs to process orders within CyberSource's fraud screening solution.
Device Fingerprinting *
To successfully implement Device Fingerprinting, a 1-pixel image file (which cannot be seen) and two scripts need to be placed in the <body> tag of the merchant’s checkout page*. This will ensure a 3-5 second window in which the code segments can complete the data collection necessary to create a fingerprint for the device making the order.
Below are the code segments for implementing Device Fingerprinting:
PNG Image
<p style="background:url(https://h.online-metrix.net/fp/clear.png?org_id= <org ID> &session_id= <merchant id><session ID> &m=1)"></p> <img src="https://h.onli
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
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
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
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
Void
**
Void should be performed on an event where transactions are not responded to or not completed to the merchant’s application which could be due to a timeout scenario. When used the void message should be performed closer to the time it relates. For more on the use of Void messages, refer to the Ensuring end to end Transaction Integrity
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" : "Void" ,
"Mode" : "Test" ,
"OriginalMerchantTrace" : "DIAAAY22734" ,
"OriginalRequestID" : "{9667792F-635A-4121-AC85-E06856ADC3EF}"
}
}
< soap:Envelope xmlns:xsi = "
Refund – “Initial Credit”
**
Allows the merchants to essentially “pay” or “credit” the cardholder without referencing any original or previously processed transaction
REST
SOAP
Request
{
"Version" : "2.0" ,
"CertificateID" : "{cf4b7e7a-4fec-43b4-a2cb-221263c0a34b}" ,
"ProductType" : "Enterprise" ,
"ProductVersion" : "WebAPI" ,
"Direction" : "Request" ,
"Transaction" : {
"ApplicationID" : "e7c523a4-7da7-4e59-b888-569fe65c535b" ,
"Command" : "Credit" ,
"Mode" : "TEST" ,
"MerchantReference" : "20211014_0129" ,
"MerchantTrace" : "NAHSI-1112" ,
"Currency" : "ZAR" ,
"Amount" : "1000" ,
"ExpiryDate" : "1025" ,
"PAN" : "4242424242424242"
}
}
< soap:Envelope xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd = "http://www.w3.org/2001/XMLSchema" xmlns:soap = "http://
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