Skip to content

3.6 Available PTI settings at an instance level

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 52-56 PDF pages: 52-56

a) Real time

Provisional transactions will be sent to you within 60sec of the transaction being processed on your account. Transactions can only be sent real time on a real time delivery protocol.

Note: This SLA will not apply during Nedbank system maintenance ie software or hardware updates. Daily maintenance is scheduled between 23:45 and 00:30. All transactions processed during this maintenance slot will be delivered once the maintenance has been completed. The SLA provided refers to provisional transactions leaving the Nedbank infrastructure.

b) Near real time

If you choose to use a near real time delivery protocol any provisional transaction processed during your specified time interval will be batched and sent to you in a file.

If you choose to use a real time delivery protocol all transactions that are processed during your specified interval will be held back and only delivered when your time preference has been met.

You have a choice of the following time intervals:

  • 15min
  • 30 min
  • 60 min or
  • Once a day (You can specify the time)

Note: In reference to the time interval, each subsequent file will be dependent on when the previous file was sent. For example, if you are on a 15 min time interval and the first file was sent at 13:05 the next file will be sent at approximately 13:20.

Note: Transactions are sent dependent on the type of transactions (eg debits only) and time preference (eg 8:00 to 17:00) selected.

A. Type of transactions

You can select one of the following types of transactions to be notified on:

a) All transactions

b) Debits only (money leaving your account)

This will include debit transactions and reversals of debits.

c) Credits only (money coming in to your account) or;

This will include credit transactions and reversals of credits.

d) Balance only

B. Threshold limit

You can choose to receive transactions for all amounts or specify to receive transactions only if it is above a certain amount.

C. Accounts and channels

At an instance level you have the option to specify the accounts you would like to be notified on. In addition for each selected account you can choose to be notified only if the transaction is processed through one of the following channels:

a) Electronic Banking

  • NetBank Business (NBB)
  • NetBank Retail (NRB)
  • SST
  • CPS
  • Real time payments (RTC, RTGS)
  • Manual unpaid
  • Interbank EFT

b) Mobile Banking

  • Mobile banking including the Nedbank App
  • Telephone banking
  • USSD
  • WAP

c) Branch

  • Teller

d) Card

  • Online purchases
  • International transactions (POS, ATM, TELLER)

e) ATM

  • Local ATMs
  • Intelligent deposit device (Local cardless cash deposits)

f) Point Of Sale (POS)

  • Local POS transactions

g) Cash solutions

  • Cash online
  • Cash vault device

h) All the above

D. Template groups

You have the ability to select a template that will best suite your business needs. The templates available are dependent on the delivery protocol and type of transactions selected.

Available templates

  • Real time

  • TI PTI XML (RT)

  • TI PTI CSV (RT)
  • TI PTI TXT (RT)
  • TI SWIFT MT900
  • TI SWIFT MT910
  • TI SWIFT MX900 - camt.054 (Bank to customer credit / debit Notification)
  • TI SWIFT MX910 - camt.054 (Bank to customer credit / debit Notification)
  • TI SWIFT MX941 - camt.052 (Bank to customer account report)

  • TI SWIFT MT941

  • Near real time

  • TI PTI XML (NRT)

  • TI PTI CSV (NRT)
  • TI PTI TXT (NRT)
  • TI SWIFT MX942 - camt.052 (Bank to customer account report)
  • TI SWIFT MT942
  • Multicash AUSZUG
  • Multicash UMSATZ

Refer to 1.12 and Appendix A and D for detailed information on PTI templates

Note: If SWIFT has been selected as a delivery protocol only the SWIFT templates can be selected, however SWIFT templates can be sent on all delivery protocols.

E. Time preference

You can select to receive provisional transaction information all day or during a specified time. Nedbank will delay sending your Notifications if it is outside your selected time preference (eg 8am to 5pm) and only send the Notification when your time preference has been met.

F. PTI end of day file

a) Introduction

End of day files are optional and are generally used to identify any transactions that was sent by Nedbank but not received by you. This can occur if you select a delivery protocol that does not assure delivery (eg Web Services, email).

The end of day file is a summary of all transactions sent to you since the previous end of day file. This will only include transactions based on the settings for this instance. However, for each instance you have the option to select a different delivery protocol and template for the end of day file.

Note: End of day file is not available if you select balance only as your transaction type.

b) Delivery of end of day file:

  • If your time preference selection is all day then your end of day file will contain all transactions sent to you from 6pm the previous day to 6pm today.

  • If you have specified a time preference to receive Notifications your end of day file will be generated to include all transactions sent to you from your previous end of day file to the end of the your selected time preference.

Example: If your selected time preference is 9am to 5pm, the end of day file will include transactions from 5pm the previous day to 5pm today.

  • The SLA is an hour to receive an end of day file.

c) Available delivery protocols

Only near real time protocols can be used for the end of day file. Refer to section 1.8 for more detail

Note: For the email delivery protocol, you can only have one address for the end of day file.

d) Available templates groups

Only near real time templates are available for the end of day file. Refer to 1.12 and Appendix A for detailed information on P TI templates

Note: End of day files can only be sent using a near real time delivery protocol.

G. Enotes PTI file naming convention

Note: This file naming convention is only for information purposes for clients that were migrated from the old PTI solution and will not be available to new clients. All new clients will be required to use the TI file naming convention as defined in section1.3.

The Enotes PTI file naming convention is not applicable to TI PTI clients and is only a reference for the old PTI clients that migrated from the old system to the new system. A PTI file, used for the near-real-time delivery protocols, contains all transactions that occurred during the interval specified by the client. The PTI file (from Nedbank host to the client's LOB system) must adhere to the following naming convention:

PNGG00.CDPACK.**OTnn.D0.SQ730

Nedbank will assign a unique two-letter alpha code to each of the PTI clients. The '**' represents the alpha code, ie AA, AB, AC. This unique alpha code will be incorporated into the file name, as displayed above. The O character is for the output file. The twodigit number, represented by nn, is a sequential number (starting from 01 and going up to a maximum of 99) that Nedbank will increment when sending out new files. This number will be reset to 01 at the beginning of each day.

Note: A file should not contain a duplicate file name, as the file will not be processed, even though it might contain new client data.

During testing the following naming convention will be used:

QNGG00.CDPACK.**OTnn.D0.SQ730

A Q is used instead of a P. ('Q' refers to a QA testing file, while 'P' refers to a production file.)