Requirements  *** Merchant profile that contains credentials to login to the merchant portal - Backoffice Merchant must login to Backoffice and request a certificate, [1] only the certificate ID is required. The Gateway endpoints [2] are the same for Live & Test For integration purposes, a test applicationID must be used, while the LIVE application iD must be use real payments Optional Headers:* Authentication [3] of the user using AuthenticationToken & AuthenticationKey can be set in the headers Authentication * ** When interfacing with the iVeri Gateway, there are 2 forms of authentication that are supported. Digest Authentication (Optional): *Adding AuthenticationKey and AuthenticationToken in the headers and adding the certificateID in the body of the transaction or enquiry request  i

Introduction *** Welcome to the PosPort Training Session, this session is aimed to provide details on the processes and procedures that need to be followed when onboarding and configuring a PosPort merchant. This process is important to ensure a merchant is accurately set up, so as the merchant can seamlessly process transaction as expected without any errors. Assumptions *** Actions assumed to be in place The Objectives of this learner guide are attainable on the assumption that the merchant profile already exist/captured on the Gateway Admin website by the acquiring bank. The Device/Terminal also needs to already be created and should exist on the gateway on request by the acquirer to None [1] assist@iveri.com . NEWPOS Devices have already been injected or loaded with the necessary key

This section describes the various gateway parameters available. For more on input and output parameters per transaction type refer to Parameter Description & Action [1] 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

Web Service implementation *** All methods provided by the web service return a V_XML formatted response. The GetPinBlock method is the only exception. For card present transactions, the GetPinBlock method will return a PINBlock data structure. The V_XML request and response format is defined by the V_XML.xsd schema, which can be downloaded from https://portal.nedsecure.co.za/schemas/v_xml/7.0/v_xml.xsd [1] Client code must check the respective Result fields to determine if the web service method was successful or not.  For a client to call the execute method the client certificate ID must be provided with the HTTP Request Webservice Gateway Address** SOAP Webservic EndPoints Purpose Usage Live and Test:  */iVeriWebservice/Service.asmx HTTP Method:* POST Submit transactions to iVeri Gatew

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. Available to All Cardinal Customers * What’s New* Support of newly introduced DIGEST based authentication to cardinal level to be able to download recon/transactions/EMV parameters/hot cards, etc. from gateway. Introduction of a function to extract detailed reports on User Roles and Access Rights from the related Cardinal, enhancing access management. This report can be scheduled upon request, per cardinal. PosPort/* The user’s last login is now added to the "Users" View Module in BackOffice. An API is now available for management of NewPOS devices on merchant

Integrate with the iVeri Gateway using our *Enterprise solution*, and start accepting payments across multiple channels through a *single API*—available in both * REST [1] * and * SOAP [2] * formats. Payments Options available: *Online Payments*: Accept card payments on your website or mobile app by integrating a customized payment page tailored to your brand. *Payment Links*: Generate secure payment links via the iVeri Gateway and share them through your website, WhatsApp, or SMS—making it simple for customers to pay anytime, anywhere. *Recurring Payments*: Automate regular billing by leveraging our API for batch processing or submitting individual transactions—ideal for subscriptions and repeat services. *Transaction Reporting*: Streamline your reconciliation process by integrating our S

Transactions ** Create Transaction Request * Purpose  /* - This function allows you to create a request for payment to be sent to cardholder Action: */ To create a transaction request, start by navigating to the DiVert tab on the homepage. Then, select Transactions and click on Create Transaction Request. image%20%282%29 [2] Action:* Here, choose the Live application ID. Once selected, you’ll be redirected to the Create Transaction Request form, where you can enter all the transaction details. image%20%283%29 [3] Create%20a%20Transaction%20Request%20-%203 [4] Let’s go through the details you’ll need to enter when creating a transaction request: Cardholder Name*: Enter the cardholder’s name exactly as it appears on the card. Cardholder Email*: Input the cardholder’s email address. This is

Transaction Result Codes ** Result Status* Result Code* Result Description* Additional Information * 0 (OK) 0 Approved/Successful -1 (Not OK) 1 Timeout waiting for response Either stop the transaction or wait a while before re-submitting.  Do not re-submit forever, have a limit in place of how many times a transaction can be re-submitted. -1 (Not OK) 2 Gateway unreachable Either stop the transaction or wait a while before re-submitting.  Do not re-submit forever, have a limit in place of how many times a transaction can be re-submitted. -1 (Not OK) 3 Hot card -1 (Not OK) 4 Denied -1 (Not OK) 5 Please call Merchant can phone their acquiring bank to obtain a telephonic authorisation.  If this is not possible then the transaction should be Denied. -1 (Not OK) 7 Invalid Authentication Data Car

Prognosis ** Merchants using NewPOS 7210 devices are experiencing an  inability to trade* due to the  “Wnet Run Fail”* error. This error is caused by the expiry of the  WNET file*, which manages SIM-based wireless connectivity on the device. Impact ** Devices relying on SIM connectivity are unable to establish a network connection, preventing merchants from processing transactions and trading. Action Required ** To restore connectivity and resume trading, the following actions are a necessity: Pre-Step* -  Ensure device serial numbers impacted are loaded onto the terminal management software (TMS). This step is to ensure the newPOS application update is made available for download to the devices.  This should be actioned by iVeri/TouchPoint, acquirers can provide a list of serial numbers a

This section explains how to implement a follow up/subsequent transaction using the TransactionIndex returned from an initial/previous transaction processed successfully. Merchants that wish to accept payments from regular customers without worrying about PCI DSS burdens of storing or retaining the card number have an option of submitting a unique identifier associated with the customers card number from a previously successfully processed transaction. In iVeri's realm, the identifier which the merchant can pass on subsequent transactions is called the “TransactionIndex”. This variable is an iVeri Gateway generated identifier commonly found in Gateway responses to the merchant. Initial Transaction ** When a merchant sends a transaction request(POST) to the iVeri Gateway, the response retur