Overview

ID Validations is a web service that uses an algorithm the ID number of an employee, debtor or creditor. Any software that allows for the capture of bank account details should implement this web service as it is critical for the success of other Netcash services requiring bank details such as ID number, verification, bank codes or payments. This service does NOT verify (See ID Verification) that the ID number is active or belong to the employee, debtor or creditor.

This service is to be used on input of data into the application to ensure that the Banking details supplied are valid. It is recommended that Universal Branch Code processing is used for the validation to be effective

Technical Information

NIWS_Validation is an online, synchronous web service which allows an external system to request a validation and receive an immediate response.

NB! This service permits a single request per web service call. For bulk file requests click here

From your application call:

Input

Submit the following parameters.

Service key Account service key issued by Netcash
ID number Must be 13 digits

Output

You will receive the following numeric code which you need to replace with the description in your application.

Numeric Response Description
0 Identity number valid
1 Id number too long
2 Id number too short
3 Id number failed check digit validation
100 Authentication failed
200 Web service error contact support@netcash.co.za

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

Netcash may provide example/sample/demo ‘code snippets’ and/or external links in this Technical Document. Such are for guidance purposes only and may not function on every developer’s system/s. Netcash disclaims any and all liability for the usage of guidance resources provided -and you as the Developer; must accept full responsibility for the usage of such. While every possible effort has been taken to ensure compatibility across multiple system configurations, the contents of this document cannot be guaranteed to work on all systems, with all operating systems -and/or with all system configuration/s.