-
Introduction
-
Commands & Actions
-
Transaction Sequence
-
MasterPass
-
Visa Checkout
-
Foreign Exchange
-
Parameter Description & Action
-
Gateway Domain Knowledge
-
Transaction Result Codes
-
Out Of Band
-
Payment Facilitator
-
Tokenization
-
SOAP API
-
Pos Device Intergration
-
Acquire Contact Information
-
3D Secure
-
Enterprise API Samples
-
Card on File
-
Additional Data Transactions
Getting Started
The SOAP services allows for processing of transactions in different payment forms, making it possible for merchants to incoporate tokenisation of cards, authenticated transactions through 3D secure, verification of accounts and more.
To begin processing transaction to the iVeri Gateway, the following has to be in place:
- Merchant Profile
- Generate a certificate in Backoffice.
- Only the generated certificate ID is required on transaction request to iVeri Gateway
- Before use the certificate ID has to be linked to the merchants application on the Gateway, reach out to iVeri support on assist@iveri.com to action
With the SOAP API, merchants can implement various payment mechanisms supported. For further details, refer to the following sections
Commands and Action
Payment Flow
Parameter Description
Parameter Per Action
SOAP Webservice Gateway Address
SOAP service uses the following iVeri Gateway endpoint
- SOAP Endpoint:[portal]/iVeriWebService/Service.asmx
Service Description and Gateway domain address per acquiring bank partner
- Nedbank: https://portal.nedsecure.co.za/iVeriWebService/Service.asmx?wsdl
- I&M Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl
- CBZ Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl
- CSC Bank: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl
- CIM Finance: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl
- iVeri PSP merchants: https://portal.host.iveri.com/iVeriWebService/Service.asmx?wsdl
Message Formats
- Communication between the client and web service is via SOAP protocol
- Format supported: XML
- The SOAP requests and responses are shown for each method provided by the web service
Web Service implementation
- All methods provided by the web service return a V_XML formatted response.
- The V_XML request and response format is defined by the V_XML.xsd schema.
- 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
- In order for a client to call the execute method the client certificate ID must be provided with the HTTP Request.
- For card present transactions, the GetPinBlock method will return a PINBlock data structure
Webservice Methods
The webservice supports the following methods:
DownloadFile
Execute
GetPinBlock
IsDataAvailable
UploadFile