Overview
This specification is specific to the NIWS_partner endpoint:- https://ws.netcash.co.za/niws/niws_partner.svc* and describes the input to the ValidateComplianceStatus method
* niws_partner service uses SOAP 1.2. with WS-* addressing. See example
Technical Information
From your application call:
Method name | Usage |
ValidateComplianceStatus | Check a specified Netcash account number to ensure that the account is valid and is compliant at BankServ |
Input
The service accepts an object which contains the Software Vendor Key used for authentication and Netcash account number to be validated.
Output
Example
<ValidateComplianceStatus> <MethodParameters> <request> <MerchantAccount>51005101234</MerchantAccount> <SoftwareVendorKey>0000E4EF-DCC0-0000-BE00-B0000BF00BD0</SoftwareVendorKey> </request> </MethodParameters> </ValidateComplianceStatus >
Response
The service responds synchronously with an object containing Compliance status, Account number and Software vendor key:-
Example
<ValidateServiceKey> <MethodParameters> <ValidateComplianceResponse> <AccountStatus>000</AccountStatus> <MerchantAccount>51005101234</MerchantAccount> <SoftwareVendorKey>0000E4EF-DCC0-0000-BE00-B0000BF00BD0</SoftwareVendorKey> </ValidateComplianceResponse > </MethodParameters> </ValidateServiceKey>
The original data submitted in the request is returned with the compliance status.
Response status
Authentication (once per response)
000 | Success – Account exists, is Valid and is Compliant |
103 | No active partner found for this Software vendor key |
104 | No active client found for this Account number |
200 | General service error – contact Netcash support |
316 | Debit order compliance not completed for this account |
Netcash brand guidelines
Please refer to the Netcash brand guidelines here when using any logos, images, icons, labels, descriptions, and references to Netcash in your software.
Testing
See the Testing section for more details. If you require any integration assistance contact our technical support team