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.

* Upload File * ** * Purpose * – To upload a batch file on to the iVeri Gateway for processing. * Action: * Click on Browse to locate the batch you wish to upload. When located on your PC, highlight the file, and click on Open. Then click on Submit. The message “/Thank you, your file has been uploaded to our server. / /Once the file has been loaded into our database an e-mail will be sent to/…” will be displayed. If the upload was not successful, the reason for the failure will be displayed. A little while later, an email will be sent to the address captured in Batch – configure Applications, confirming either success or failure of the upload

Enterprise BackOffice User Guide * ** Corporate Strength APIs Enterprise consists of two APIs which are intended for businesses that need the flexibility to integrate and customise a transaction processing engine to their own unique business requirements. This solution provides businesses with the ultimate control to manage their card processing requirements. iVeri Enterprise APIs also allow for central processing of multichannel card payments. Payments received from the internet, the call centre and from the physical point of sale or kiosk can all be processed using the power and versatility of IVeri Enterprise. Developers can chose between the Rest or SOAP versions of iVeri Enterprise API.

Reconcilation* **

V4.136 12/11/2023 Hosted * ** Hosted Gateway: * Date: 12/11/2023 Start Time: 20:00 UCT +2 Duration: 2-4hrs Expected Downtime: 5-10mins. Release Notes Overview * The release notes provided in this document serve as an initial preview of the changes expected in the upcoming production release scheduled for November 12th 2023, on the Hosted Gateway . Summary * * The Gateway release notes will contain information related to the new iVeri software release. The release notes will include the impact of software release to the intended target audience. / The release notes will adopt the format outlined below, as applicable:*/ Compliance - *Refers to the adherence of the software to specific industry standards, regulations, or internal policies. This includes ensuring that the software meets legal

IYS Implementation Guide **

1.Make a selection on what you want to purchase. 2. Select Add to Bag 3. Select Go to checkout Here you can either select Checkout or select the Bag icon it is still the same. 4.Insert your email address and the select Checkout This cardholder email is used to send the correspondent updates regarding the transaction and order status updates 5.Complete the Shipping & Delivery details for the delivery of the goods. Select Continue 6.Complete the delivery date details Select Continue */Please Note!/* The Store owner needs to set the charges and shipping method under “Shipping and Pick Up” on their Back End IYS Profile. 7.Choose how you choose to pay for this order. Which in this case it is iVeri Scroll down 8. Select Go to Payment */Please Note!/* Payment Instruction is set up by the merchant

** The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd ( www.iveri.com) [1] provides proven credit card payment solutions for businesses that have online or physical presence. The use of Enterprise API's is ideal for merchants that want complete control & flexibility of the payment page and transaction mechanisms supported. Enterprise API’s currently support the following Webservices. REST  [2] SOAP [3]   Merchant Requirements * Merchants are required to enter into a “Agreement” with an authorised Acquiring Institution. Once there is a merchant agreement in place, a merchant profile can be created With Enterprise calls to the Gateway, the presence of a certificate ID is required, with the actual physical certificate available as optional means to aut

*Registering as a merchant * ** Merchant account can be attained by registering with an acquiring bank, a list of which can be found on this page [1] [1] /knowsystem/distributors-contact-information-33