* Merchant Requirements * * Merchants are required to enter into a “Agreement” with an authorized 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 authenticate merchant requests.  Test Mode should be used during integration, testing, and validation. Test application ID must be used with Mode Test

Merchants are required to enter into a “Agreement” with an authorized 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 authenticate merchant requests.  Test Mode should be used during integration, testing, and validation. Test application ID must be used with Mode Test

* Terminology * * This document uses certain iVeri specific terminology which can be referenced in Parameter Description

This document uses certain iVeri specific terminology which can be referenced in Parameter Description

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 Client code must check the respective Result fields to determine if the web service method was successful or not. (Result fields are defined by the V_XML specification) For a client to call the execute method the client certificate ID must be provided with the HTTP Request

* Webservice Gateway Address * * iVeri WebService uses the Gateway addresses below with the following: [portal]/iVeriWebService/Service.asmx

* Service Description * * Nedbank: https://portal.nedsecure.co.za/iVeriWebService/Service.asmx?wsdl [1] I&M Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [2] CBZ Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [3] ECS Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [4] CSC Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [5] CIM Finance: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [6] [1] https://portal.nedsecure.co.za/iVeriWebService/Service.asmx?wsdl [2] https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [3] https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [4] https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl [5] https://portal.host.ive

*Message Formats* * Communication between the client and web service is via SOAP protocol. Format supported is in XML.The SOAP requests and responses are shown for each method provided by the web service.

WebService Methods * **

* Execute - (bool validateRequest, string protocol, string protocolVersion, string request) * * Usage: For posting of transactions to the Gateway * Description * Execute Execute the V_XML formatted request. The action to be performed is determined by the V_XML, as defined by the V_XML specifications. ie. Transaction (Sale, Refund etc) * Returns * A V_XML formatted string (The return string will need to be URL decoded) * Client Certificate * Is required (provided with HTTP Request) * Parameters * * ValidateRequest: boolean * * true * : Will validate the V_XML request against the schema definition. If there are any schema errors processing of the request will terminate and the request will not be passed on to the relevant provider. * or * * false: * Will not validate the V_XML request. The V