Download File – By File * ** Purpose *– To download a selected file by a specific file name. Action: * From the main menu, the user will navigate to: Batch - Download File - By File.* Action: * Select the date range that the file was created/uploaded by manually changing the default dates above or clicking on the calendar icon next to each date and select each date in the calendar that is displayed. Then click on Search. The result of your search will then be displayed. Action: * Select the filename of the file you want to download. The following page will be displayed. Your selected file is displayed for you to download. Click on "Download". Select the file format you wish to obtain from the drop down (either the default Fixed File Text format or XML) and then click on Download. You can n

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

Application Parameters * ** / Purpose /* – This function is used to allocate application ID(s) that a User is only allowed to have access to. This application refers to specific product and what a merchant uses to process transactions through iVeri. Example below indicates that when you select a particular Application ID an Administrator can configure what functions can this user perform in a particular Application ID. If no function is associated to an Application ID, no access is granted to that user. Administrator can configure what Transaction Types a user can perform on a specific Application ID. If no Transaction Types are configured for a user, the user will be unable to process transactions for any of the Application IDs. / Action /*: Select the product and Live Application IDs you

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

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

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

* / Purpose /* - The 'Active Session' tab reflects who is logged in and provides the menu options which the logged in user is able to access or use.

3D Secure 2 Test Cases BY 3D secure Vendor/MPI * ** The MPI test cases that should be used are depended on the acquiring bank that holds the merchant agreement or PSP that will be processing the payments on the Gateway on behalf of the merchant Things to note about the test cards:* CVV not required Expiry must be current or future date BANKSERV  * For merchants and acquiring banks in South Africa and Kenya Frictionless Full authentication * Scenario 1 * Authenticated Frictionless Transaction * Test Values * Visa*:4069425217889137 MC:*5163426869252246 DINERS*:36135230403232 Expected results - Lookup * EnrolledStatus: Y paresTxStatus: Y TDS2.transStatus: Y ECI (Visa): 05 ECI (MCI): 02 ECI (DINERS): 05 PARESVERIFIED: true PROTOCOL: 3DS 2.1.0 MD_STATUS: 1 MD_ERROR_MESSAGE: Authenticated Action

Batch is a payment solution that allows for bulk payment uploads using the iVeri system. It enables a merchant to create and process large volume, card not present transactions. Batch requires merchants to create a file in a specific format and to upload It securely to the iVeri Payment Gateway for processing. Alternatively, merchants can also use the Create Batch function to manually create batches for uploading and processing. iVeri automatically creates the batch in the required format. Batches are uniquely identified and can be set up to be processed on a date in the future. This is ideal for month ends that fall on a weekend or a public holiday. Batch merchants are able to return to iVeri Back Office and view the status of their batch once it has been processed.

* 3D Secure 2 implementation using the Form Post * * Merchant can POST Form variables to the 3DS 2 endpoint, which is redirect over the browser. On completion of the 3D secure process, the Gateway will return the result to the merchant ReturnURL. The result returned to the merchant will either allow for the continuation of the Authorisation/debit instruction or result in the termination of the transaction by the merchant to the customer. Format: Form Data * Form Post request Sample * <form name="Form1" method="post"action="https://portal.iveri.net/threedsecure/EnrollmentInitial" id="Form1"> <input type="hidden" name="ApplicationID" id="ApplicationID" value="{ca8a6eae-a469-4b39-bef3-aa029ca3a806}" /> <input type="hidden" name="ReturnUrl" id="ReturnUrl" value="https://[domain]/Lite/Result.as