Integrate 3D Secure * ** Integrate 3D Secure functions via the iVeri Gateway * Implement a form post with the required data  When received, the Gateway will process and handle the enrollment lookups, authentication with the 3DS provider on your behalf  On completion, of the authentication, the merchant can submit payment instruction with the 3D 2 authentication data Integrate 3D Secure directly with the 3DSecure MPI vendor  * Contact 3D secure Vendor Integrate the 3D secure using the 3D secure integration specification from the MPI/3D Secure  vendor On completion of the 3D secure process, merchants, or Payment service Provider (PSP) can include 3D secure authentication data on the payment instructions to the iVeri Gateway. When received, the Gateway will process the payment to the appropri

Delete Code * ** Function: Delete a code that has been created Delete Code Parameters * Request Parameter Description MasterPassAction Mandatory, The action to perform. MasterPassMerchantID Mandatory, The merchant id as captured on MasterPass. MasterPassCode Mandatory, The result code that must be deleted Response Parameter Description MasterPassAction The action that was performed Delete Code – REST Sample * Request Response { "Version" :  "2.0" , "CertificateID" :  "{xxxxxxxx-71dd-4044-802d-xxxxxxxxxxxx}" , "ProductType" :  "Enterprise" , "Direction" :  "Request" , "Enquiry" : { "ApplicationID" :  "{xxxxxxxx-68e0-42eb-aba9-xxxxxxxxxxxx}" , "Mode" :  "Live" , "command" : "MasterPassQuickResponseCode" , "MasterPassMerchantID" :  "xxxxx" , "MasterPassAction" :  "DeleteCode" , "MerchantRefer

* *3D secure (Secure Code or Verified by Visa), is all about call back protection and making sure card holders are who they say they are. The Illustration and process that follows, shows 3D secure in use as implemented by Merchants using iVeri Enterprise and not iVeri Lite. Illustrating the process in this way, helps to show how each entity is involved even if certain functions are performed on behalf of Merchants using iVeri Lite.

* Authorisation Reversal * * Unreserve the funds previously reserved on the cardholder’s account.

Transactions – View- Transaction History* Purpose * - To view a list of all transactions performed for a selected Date or Period. Action: * In the menu bar, Select Enterprise, Transactions, View, Transaction History. Click on the Application ID you wish to view Transactions. If you only have one Application ID, this page will NOT be displayed, and you will be automatically taken to the Choose Date/Period page. Select the Date or Date range and click on Search. This will bring up the list of ALL transactions performed for your selection. Choose a specific Application ID Choose a date range to start your Search Action: * Allows you to get details pertaining to a specific transaction – available when clicking on the actual transaction detail.

Download Reconciliation * ** / Purpose - /*To download and save the selected reconciliation file in XML format. / Action: /* Mouse over the menu function Reconciliation then click on Download File. This will bring up the following form / Action: /* If you have only one merchant Card Acceptor ID, simply click on Submit. If you however have more than one, then click on the drop down and select the Card Acceptor ID number for which you want the report before you click on Submit. Select the cycle you wish to view. / Please Note:  /* If your file contains more than 10000 records, then the time in the message above will show 20 minutes. It is recommended that you click on the words Click Here and you will receive an email when your file is ready for retrieval.

Profile Parameters * ** Purpose - * To set the Security Parameters for all users in terms of their passwords, validity, suspension, and login notifications. These parameters can only be set by the Back Office Administrator. Action:  * In the menu bar, click on User Manager, scroll to, and click on Security Configuration. This will bring up the following form on which you can now change the system defaults to suit your own requirements. Please remember that changes made to the defaults will apply to ALL users that you have given BackOffice access to / Note: /* Strong Password: The default is No. This means that the password can be anything if it is not less than the default minimum length. If you change the default to Yes, then the user’s password must be a combination of alpha/numeric and

Test File * ** Purpose *– A test batch file can be created to validate that the file format uploaded is in accordance with the iVeri Batch Specification. The test results will provide details should there be any errors within the Test file. Action: * From the main menu the user will navigate to: Batch - Test File.* Action: * The user will click on "Browse" to locate the created batch. When located on your PC (file directory), select the file, and click on Open.  Alternatively the user can drag and drop the file in the space provided. Lastly the user will click on "Submit" to upload the test file. The result of the format test of the selected batch will be displayed.

Cardinal Posport Indigo Release Notes V 20230323 *** The release notes contained in this document are available in iVeri’ s repository in production and can be installed on any Cardinal and or indigo installation on a case-by-case bases as agreed with Customers and or Integrators. / Whats new  /* Indigo Ingenico * A change is implemented to make Ingenico devices reboot once a day to comply with PCI requirement. The default time is set to be at midnight. PosPort * Device Status is included as part of the data synchronized from Cardinal into MIS allowing for a better filtering in reports generated from MIS. Allowances that make it possible to enable "CashAdvance" in parallel with "Sale" transaction type have been made SMYL Loyalty  * As part of the loyalty offering on the N700 device, enabli

*/ Purpose /* - This function allows you to create a request for payment to be sent to cardholder /* Action: */ On the main menu bar, select the DiVert menu, Select Transactions and click on Create Transaction Request. */ Action: /* Select the relevant Application ID. A Capture Transaction screen will be displayed */ Action: /* Complete the details on the capture page and click Submit. A resultant page will then be displayed. Once completed the Submit button is selected and the below Pop up screen will be displayed.