POS Parameters * * Parameter Node Type Data Type Min Length Max Length Description DeviceFirmware Tag String 64 The firmware (software) currently loaded on the device. This may be set as an integer DeviceFirmwareVersion Tag String 64 The version of the firmware (software) currently loaded on the device. DevicePINKey Tag Hex 32 32 Master/Session encryption specific: The device PIN Key encrypted under the device master key i.e. DMK(DPK) MACDevicePINKey Tag Hex 8 8 Master/Session encryption specific: The MAC of the device PIN Key i.e. MAC(DPK) AccountType Tag A 0 32 The type of account that this transaction relates to (known to the cardholder Cheque Not specified Savings Credit AvailableBalance Tag N 12 The available amount in the cardholders account given in the smallest unit of currency of

* Terms and Conditions * * */ Configuration Purpose /*– Two show how a merchant can configure the terms and conditions. There are two ways in which this is possible - Free Text – Terms and Conditions Message or Merchant URL Link There are two ways in which the merchant can configure how they would require their clients to accept terms and conditions. Where applicable, merchants must present their terms and conditions and must be accepted by the client before a payment is made on the payment page

Mode: Test Vs Live * ** The iVeri Gateway provides a mechanism where a merchant can perform test transactions that are routed to an iVeri    Gateway issuer simulator. This enables a merchant to complete testing within a test environment. When the merchant is ready s/he can perform live transactions, which are routed to the genuine card issuer. merchant specifies the mode of a transaction by setting Mode as “Test” or “Live” and sends their corresponding Test or Live ApplicationID. Sending the following card numbers to the Test environment has the following results: PAN Result 4242424242424242 returns "Authorised" 2121212121212121 randomly returns "Hot Card", "Please Call" or "Denied" 5454545454545454 randomly returns "Unable to process" or times out All other card numbers (eg "1111222233334

Debit with PIN and Balance Enquiry * ** The merchant determines if the card is PIN based typically via a local bin list (section 17.6.4). If it is PIN based, the merchant reads in the PIN from the PED, and obtains an encrypted PINBlock. A PIN based request is identified by the existence of a PINBlock tag. The existence of the PINBlock tag implies Track2, DeviceSerialNumber, DeviceMake and DevicePINKey is mandatory. Account Type is 'Savings' or 'Cheque' or 'Credit' or 'NotSpecified'. Debit with PIN * The mandatory Amount tag refers to the total transaction amount. The optional CashAmount tag is any cash portion of the transaction. Therefore, always Amount >= CashAmount. Normal Withdrawal: CashAmount = Amount Normal Sale: CashAmount = 0 (or not specified) Combined Sale and Withdrawal: 0 < Ca

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://

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

EMV Parameters * * Parameter Node Type Data Type Min Length Max Length Description EMV_AuthorisationRequestCryptogram Tag Hex 16 EMV tag 9F26 EMV_ApplicationIdentifier Tag Hex 32 EMV tag 9F26 EMV_ApplicationInterchangeProfile Tag Hex 4 EMV tag 82 EMV_CardSequenceNumber Tag Hex 2 EMV tag 5F34 EMV_ApplicationTransactionCounter Tag Hex 4 EMV tag 9F36 EMV_ApplicationVersion Tag Hex 4 EMV tag 9F08 EMV_CardHolderVerificationMethodResult Tag Hex 6 EMV tag 9F34 EMV_CryptogramInformationData Tag Hex 2 EMV tag 9F27 EMV_IssuerApplicationData Tag Hex 64 EMV tag 9F10 EMV_TerminalCapabilities Tag Hex 6 or 8 EMV tag 9F33 EMV_TerminalType Tag N 2 EMV tag 9F35 EMV_TransactionType Tag N 2 EMV tag 9C EMV_TerminalVerificationResult Tag Hex 10 EMV tag 95 EMV_UnpredictableNumber Tag Hex 8 EMV tag 9F37 EMV_Trans

Customize Transaction Form * ** / Purpose - /* Customise the payment page that cardholder interacts with / Action: /* On the main menu go to DiVert – Configure Application – Choose an application ID and then select Customize Transaction Form / Action: /* Click on the Application ID you want to customize, i.e., either the Test or the Live. Make the relevant changes and click on Submit. / Please Note:  /* Under Upload Logo, you can upload a company logo Under Style, you can amend the font colors, font, and background color.

*/ Purpose /*- This configuration allows you to compile a list of credit card numbers that you wish to decline. Before forwarding any transaction to the bank for processing, the iVeri gateway will check this list. If a card number matches one on your list, the transaction will be instantly rejected. The reasons for adding card numbers to this list are determined by each merchant individually and will only result in rejections by your business. */ Action:  /* from the main menu, navigate to: *Configure - Black card List.* */ Action: /* If you have more than one Application ID and want to capture the card number to be blocked for all your applications, click on Go next to All Applications at the top. If not, then click on the Application ID in the bottom section and the next page will be dis