Skip to content

3.4 Delivery protocol

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 51 PDF pages: 51

sent via Nedbank's NedAcad statements service. Please contact your Transactional Banker for more information.

  • Greater customer satisfaction with the service you render

Note: Provisional transaction information is for operation purposes only and must not be used as final statement information to update financial systems.

Provisional transactions can be delivered in real time or near real time. Transactions can be be delivered in real time manner only as a single transaction, via a real time delivery protocol. Transactions can be delivered in near real time manner i.e., transactions are batched at your specified intervals and can be delivered via a real time or near real time delivery protocol. If it is delivered on a near real time protocol it is delivered as a file with the file name specified in section 1.3. If a batch of transactions is delivered via a real time protoco l it does not have a file name and the message will be contained in the data payload(s). The following delivery protocols are available for PTI:

a) Real time delivery protocols

  • Email (only delivery protocol available on NetBank Business)
  • Web Services (Host to host solution)
  • IBM MQ (Host to host solution)
  • SWIFT

b) Near real time delivery protocols

  • Email (only delivery protocol available on NetBank Business)
  • SFTP (Host to host solution)
  • Connect: Direct (Host to host solution)
  • SWIFT FileAct (Host to host solution)

See section 1.8 for more detail.

Note: Nedbank will only be able to connect to static public IP addresses.

3.5 Delivery preference

You have the option to receive provisional transactions processed on your account in real time ie, as the transaction takes place, or near real time, ie receive a file containing provisional transactions, which have taken place over a specified interval.