Input
Requests to the web service are sent as a string.
Example: public string BatchFileUpload(string ServiceKey, string File)
Output
Successful request
If the method call was successful and the file is being processed, the web service will return a file token which is used to retrieve the load report
Example: 20000000.2550236530.0483.2.2
Unsuccessful request
If the method call fails, the web service will return an error code:
Code | Description |
100 | Authentication failure. Ensure that the service key in the method call is correct |
102 | Parameter error. One or more of the parameters in the string is incorrect |
200 | General code exception. Please contact Netcash Technical Support. |
Input File Structure
Each file has the following mandatory records:
H – Header record identifies the upload and passes instructions to the Netcash server to determine the purpose of the file.
K – Key record must follow the header record. The key record describes the transaction records which follow. The format defined in the key record is used to validate the record structure and content.
T – Transaction records follow the key record. The fields in the transaction records must conform to the layout defined in the key.
F – Footer record must be the last record in the file and confirms that the file is complete.
Header record (H)
Every file must contain a header record as the first record in the file.
Record Structure
Field | Name | Type | Value |
1 | Record Identifier | AN | H |
2 | Service Key | AN | Service GUID |
3 | Version | AN | 1 |
4 | Instruction | AN | Purpose of the file |
5 | Batch name | AN | Your identifier |
6 | Action date | N | CCYYMMDD |
7 | Software vendor key | AN | The Software vendor key is issued by Netcash to identify the software origin of transactions. (only used by Netcash ISV‘s else use the default value: 24ade73c-98cf-47b3-99be-cc7b867b3080) |
Field explanations
Field | Explanation |
Record Id | “H” – Identifies the record as a header |
Service key | XXXXX |
Version | “1” – This is the Netcash version of the file specification |
Instruction | XXXXX |
Batch name | Use this field as an identifier of your batch. |
Action date | XXXXX |
Software Vendor Key | TThe Software vendor key is issued by Netcash to identify the software origin of transactions. (only used by Netcash ISV‘s else use the default value: 24ade73c-98cf-47b3-99be-cc7b867b3080) |
Key record (K)
- The key record is mandatory and must appear in the file between the header record and the transaction records.
- The key defines the content, order and length of the transaction records in the file. It can be likened to the column headings in a spreadsheet.
- The key lists all the possible fields contained in the subsequent transaction records, even if not every transaction record contains data in all the fields.
- While the file is customizable, it is recommended that keys are listed in ascending numerical order for ease of debugging and support.
Transaction record (T)
- There must be at least one transaction record in the file.
- The transaction records must conform to the order of the fields as described in the key record.
- Every transaction record must have the same number of fields as defined in the key record (K).
- Empty fields should be replaced by a blank tab or a default value, where one has been defined.
Where fields are left empty, the Netcash system will assume spaces or zeroes for fields defined in the key record.