Overview

The Netcash Lead status file is generated on request via the NIWS_partner* web service.

The file contains the remote account number supplied when the lead was logged, the number of the Netcash account which was opened when the lead was logged, the current status of the account as well as any detail which is captured for the account on the Netcash system.

A unique Lead Generator Service Key is required to use this service.

The remote system supplies the Lead Generator Service Key and the Netcash Account Number, which was used to register the original lead and polls to retrieve the lead status file generated by the Netcash system.

Access

NIWS_PARTNER is an asynchronous web service which exposes multiple methods. The method BatchFileUpload allows an external system to submit a batch file of leads to the Netcash system

Endpoint url:

https://ws.netcash.co.za/niws/niws_partner.svc *

 

*niws_partner service uses SOAP 1.2. with WS-* addressing. See example

Methods:

public string RequestAccountStatus(string LeadGeneratorKey, string AccountNumber)

Returns either

  • 100
  • 200
  • 300
  • FileToken

public string RetrieveAccountStatus (string LeadGeneratorKey, string FileToken)

 

Returns either

  • 200
  • FILE NOT READY
  • Lead Status File

Response

The web service is asynchronous.

The remote system calls the RequestAccountStatus method, which returns a file token.

The remote system then calls the RetrieveAccountStatus method using the file token returned in the previous call to retrieve the account status data.

If a postback URL has been supplied, the load report will be returned to the URL as an HTTP post.

Web service validation

The NIWS web service performs initial validation on the incoming web service method call. If the validation fails, the service will return an error code.

CodeDescription
100Authentication failure. Ensure that the Lead generator key in the method call is correct
200General code exception. Please contact Netcash Technical Support.
300Account not found

Lead status file format

The file is a tab-delimited text file.

The file contains the latest data for the requested account, as it exists in the Netcash database.

File header and footer records bind the file.

File header

Occurs once at the start of the file

FieldNameTypeValue
1Record identifierAFH
2File date stampNCCYYMMDDHHMMSSS
3Lead generator keyANThe GUID key issued by Netcash
4Remote Software account numberANThe account number of the remote software
5Netcash account numberN11The number of the linked Netcash account
6Account statusN

0 – Inactive opportunity

1 – Lead opportunity

2 – Active opportunity

10 – Busy registering

11 – Registration complete

12 – Registration verification

20 – Active pending

21 – Active

22 – Suspended

30 – Closed

31 – Unused account

Account detail

FieldNameTypeValue
1Trading nameANAccount trading name
2Registration numberANRegistration number
3Registered nameANAccount registered name
4VAT numberANVAT registration number
5Legal entityN2

1 = Registered company (Pty Ltd)

2 = Close corporation

3 = Section 21 company

4 = Non-profit organisation

5 = Trust

6 = Co-operative

7 = Sole proprietor

8 = Partnership

9 = Educational institution

10 = Unknown

11 = Association

12 = Incorporation

6Company web addressAN50The “//:” and “.” symbols are allowed in this field
7Phone numberN11Include dialing codes EG: 27117822349
8Fax numberN11Include dialing codes EG: 27117822349
9Physical address line 1AN50
10Physical address line 2AN50
11Physical suburbAN50
12Physical cityAN50
13Physical codeN4
14Physical provinceN1

1 = Western Cape

2 = Gauteng

3 = Eastern Cape

4 = Free State

5 = KwaZulu Natal

6 = Limpopo

7 = Mpumalanga

8 = Northern Cape

9 = North West

15Postal address line 1AN50
16Postal address line 2AN50
17Postal suburbAN50
19Postal cityAN50
20Postal codeN4
21Postal provinceN1

1 = Western Cape

2 = Gauteng

3 = Eastern Cape

4 = Free State

5 = KwaZulu Natal

6 = Limpopo

7 = Mpumalanga

8 = Northern Cape

9 = North West

22Account user IDN13Primary account user details
23Account user surnameA15Primary account user details
24Account user first nameA10Primary account user details
25Account user titleN1

1 = Mr

2 = Mrs

3 = Ms

4 = Miss

5 = Dr

6 = Prof

26DesignationA25Director, Member, Trustee, Sole proprietor, etc
27Job descriptionA25Manager, Owner, Bookkeeper, etc.
28Email addressAN50
29Telephone numberN11Include dialing codes EG: 27117822349
30Mobile numberN11Include dialing codes EG: 27117822349
31Bank account holderAN50The name linked to the bank account
32Bank account typeN1

1 = Current / Checking

2 = Savings

3 = Transmission

33Bank account branchN6The branch code of the homing account. This field MUST be 6 digits. Pre-fill with zeroes if less than 6.
34Bank account numberN11The homing bank account number.
35Extra 1ANUser-defined data received in upload file
36Extra 2ANUser-defined data received in upload file
37Extra 3ANUser-defined data received in upload file

File Footer

Occurs once at the end of the file

FieldNameTypeValue
1Record identifierAFF
2End of file indicatorAN#END#

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.