Sale/Purchase * * * M Mandatory O Optional C Conditional blank not relevant Context * Parameter * Debit with PAN * Debit with TransactionIndex * Void * Credit with PAN * Credit with TransactionIndex * 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 * * M * M * Common CardSecurityCode O O O O Common PAN M M M Common Currency M * M * * M * M * Common ExpiryDate M * M * * M  * M * Common MerchantReference M * M * * M * M * Common OriginalMerchantReference * * M * * * Common MerchantTrace O * O * * O * O * Common OriginalRequestID * * M * * * Common PANFormat * M * * * M * Common TransactionIndex * M * * * M * Common

QR Code – MasterPass Parameters * * Context * Parameter * MasterPassQuickResponseCod *e * MasterPassPaymentNotification * Credit with TransactionIndex * Void * Core ApplicationID M * M * M * M * Core Category M * M * M * M * Core CertificateID M * M * M * M * Core Gateway O * O * O * O * Core Command M * M * M * M * Core Mode M * M * M * M * Common Amount * * * * Common ExipiryDate * * * * Common Currency * * * * Common MerchantReference * * * * MasterPass MasterPassAction M * * * * MasterPass MasterPassMerchantID M * * * * MasterPass MasterPassShortDescription * * * * MasterPass MasterPassCodeExpiryDate * * * * MasterPass MasterPassMerchantName * * * * MasterPass MasterPassCode * * * * MasterPasss MasterPassTransactionID * * * *

View Batch * ** Purpose * - To view the status of batches that have been uploaded for processing and view any errors / failed transactions in a completed batch. Action: * From the main menu, the user will navigate to: Batch - View Batch.* Action: * The user will select the applicable Application ID. Action: * The user will select the date range for the Batch they would like to view. Action: * The user will now be able to view the Batch for the selected date range. To view any errors within the Batch or applicable to a specific transaction, the user can click on the "Errors".

Data Types * ** The following key table is used for data types: Data Type * Description * A Alpha only (A-Za-z) AN Alphanumeric (a-zA-Z0-9) Base64 Base64 encryption of binary data Boolean True or False Guid Globally Unique Identifier:  {[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\} (eg {8E51611F-E19A-4FF0-B229-6A69F42AAA62}) Hex Hex (0-9A-Fa-f) N Numeric (Positive integer) N. Digits and dots (.) (e.g's 4242........4242, 1.0) N: Digits and colons String ANPS Free format string containing: Alpha, numeric, special and padding (printable ASCII) Z Positive or negative integer Node Type * Set input parameter value * Get output parameter value * attribute enterprise.setAttribute(..) enterprise.getAttribute(..) tag enterprise.setTag(..) enterprise.getTag(..) parame

Print Report – Batch Details * ** Purpose *- To view a list of all transactions performed for a selected Date or Period. Action: * In the menu bar, Select Batch - Print Report - Batch Details.  * Action: * The user will select the applicable application ID. Action: * The user will select the Date range and click on Search. This will bring up the list of ALL transactions performed for your selection. Action:  * Select the file format you wish to obtain from the drop down (either the default PDF, CSV or XLS) and then select the file from the list which you want to download and click on Print. This will bring up the following screen. The Print Button will start an automatic download to your PC.

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

3D secure transaction process flow * ** Cardholder is on the merchant’s checkout page, ready to pay for their order. They will input and submit their card details on the payment page hosted by the Gateway. The Gateway will proceed to check if the card in use is enrolled in 3DS by sending a request to the Directory Server. Directory Server will respond with enrollment status. Considering the response is positive and the card is enrolled for 3DS,  The Gateway will redirect to the issuer ACS for authentication The ACS will prompt the cardholder to insert and submit OTP/Password/credential(etc.) Considering the authentication was successful, the response is returned to the gateway to confirm successful authentication Gateway then forwards the transaction details to the acquirer for authorizati

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

* Development phase * ** At this stage you will proceed with development based on the integration method [1] you have selected, and may reach out for your contact at the acquiring bank if you require support. [1] /knowsystem/general-requirements-10

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