Skip to content

1 Transactional Information

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 10-40 PDF pages: 10-40

1.1 Introduction

Transactional information (TI) consists of the following set of products:

A. Notifications

The Notification service will send you a sms or email, informing you of any transaction processed on your account as well as other value added Notification options eg low balance alert. You can receive Notifications on any current or savings account you hold with Nedbank.

The Notification service is a dynamic solution that will allow you to customise the Notification to suit your business needs. You can set up to 10 000 different types of Notifications, each on a separate Notification instance ie you can have different Notification instance for the Chief financial Officer and a different Notification instance for the debtors clerk. Each instance is customisable to send out specific Notifications to specific recipients, ie each instance setup allow you to:

  • Specify the account/s to be notified on
  • Specify the type of transaction to be notified on

  • Specify the value of the transaction to be notified on eg if a company has mandates in place you can setup the instance to only send transaction above a certain value to the CFO

  • The option of receiving certain Value Added Notifications eg to be notified if your account balance drops below a specified amount or if the usage of your account overdraft limit reaches a certain percentage.

  • Specify a time preference, if you would not like to receive Notifications during specific hours of the day eg only send Notifications between 8am and 5pm
  • Specify up to 10 email addresses or cellphone numbers

B. Provisional Transactional Information (PTI)

The Provisional Transaction Information (PTI) service will send you a Notification in a machine-readable format when a provisional transaction has been processed to your current and/or savings accounts. This PTI service will send a Notification that can be integrated directly into your line-of-business (LOB) system providing you with the ability to automate operational processes. Note, this is only provisional information so it is up to the client if they would like to rely on this information for operational decisions.

Example: If you sell 'prepaid electricity' as soon as money is deposited into your account, PTI will send a Notification to your line of business system and based on the information your system will release the prepaid electricity to your client in a real time manner.

C. Final Transaction Information (FTI)

The Final Transaction Information (FTI) service offers you a statement in a machinereadable format of confirmed financial transactions that have been processed through your current or savings accounts. These confirmed transactions are extracted from your accounts, formatted and delivered to you as per your selected preferences. This file can be integrated directly into your line of business system allowing you the ability to automate the reconciliation of your bank statement.

Example: you will receive a file between 3am and 8am (client preference) of all confirmed financial transactions for the previous day, allowing your system to complete the bank recon and create an exception file of un-reconcilable items before your next business day starts.

D. Information Request (IR)

Information Request (IR) is an automated solution that will allow you or an authorised third party bank to request statement information on your current or savings account using the SWIFT network.

The authorised requester of the statement information will require a valid SWIFT address and will send Nedbank a MT920 SWIFT message requesting the relevant statement information. On receipt of the MT920 message the TI system will validate if the SWIFT address has been given permission to request statement information on the

selected account, it will then generate the relevant SWIFT message and send it to the requestor via the SWIFT gateway. The following statement information can be requested:

  • MT940 (Final statement, bank-to-customer)
  • MT950 (Final statement, bank-to-bank)
  • MT941(Balance report)
  • MT942 (Provisional statement, intra-day-statement)

E. Images on Demand (IOD)

The Images On Demand (IOD) solution will deliver images of cheques, cash slips and/or deposit slips, processed through your current or savings accounts. These images can be delivered directly to your LOB on a secure host protocol or via email. These images are indexed which will allow you to build your own image viewer or image search functionality on your LOB system. Alternatively, you can elect to use the image viewer provided by Nedbank.

IOD can assist you with;

  • Bank account reconciliation ie, the additional information (eg contact number of the depositor) available on the image can help you to identify irreconcilable cash or cheque transactions.
  • Risk mitigation ie, you will be receiving the image directly from the bank, removing the risk of dispatching goods or services based on fraudulent / altered deposit slip.
  • Controlling access to your bank statements ie, images can be sent to your employees so that they can make the relevant operational decisions. Your employees do not need access to your bank accounts.
  • Improving operational processes ie, employees are no longer required to contact the bank to verify the validity of a cheque or cash deposit. 1.2 Qualifying criteria

You must hold at least one current or savings account with Nedbank. You must have a profile created to maintain the required profile settings.

Note: A minimum of one current account must be opened or must exist as a charge account. The account must be held with Nedbank and must be specified as the charge account on your profile

These details are:

  • Client name Your company name is required for capturing on the system.
  • Client contact details Your contact details are required for capturing on the system.

The following legal requirements are applicable:

  • You must ensure that the relevant consent has been obtained to allow you to disclose your data to Nedbank and allow Nedbank to use the data in relation to the provision of the service.
  • The onus is on you to ensure that the information provided to Nedbank is correct.

1.3 TI file naming convention

A TI file, used for the near real time delivery protocols, contains all transactions that occurred during the intervals you specified. This file will have the following naming convention.

Example: PNGG00.CDTIPK. A13OP678.EN0610.I1234C.SQ1234

Field numbers Data Element Valid Values Description Notes 1 2 3 4 5 6 Applicable environment QNGG00 PNGG00 Q = Test environment P = Production environment These are standard fields and cannot be amended Field 1 - 4 are alpha Field 5 and 6 are numeric ie zero, zero P N G G 0 0 7 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 8 9 10 11 12 13 Product environment CDTIPK To identify the file as a Transaction Information product

C D T I P K 14 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 15 16 17 Client Prefix Please refer to description Field 15:Only alpha character are valid Field 16 and 17: Only alphanumeric characters are valid To identify the client to whom the file will be delivered. This prefix will be issued by Nedbank A 1 3 18 Input / Output indicator O = Output I = Input

Only the specified alphanumeric characters are valid O = When you receive a file from Nedbank I = When you send the file back to Nedbank eg this will only be applicable if you use a delivery protocol that has the capability for file acknowledgeme nt O 19 Product ID N = Notifications P = PTI I = IOD F = FTI R = IR Only specified alphanumeric characters are valid To identify which product you are receiving the file for P

Example: PNGG00.CDTIPK.A13OP 678.EN0610.I1234 C.SQ1234 Field numbers Data Element Valid Values Description Notes 20 21 22 File sequence numbers 001 to 999 These fields represent the file's sequential numbers and will be numeric It will be sequentially incremented by 1 for every file sent for that day. The number is reset to 001 the next day at midnight 6 7 8 23 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 24 File type D = Data file and E = End of day file Only the specified alpha characters are valid E = End of day file is applicable to the PTI end of day file only D 25 Resend indicator R = Resend N = Normal Only the specified alpha characters are valid If you receive a file with a R value in the field the system must not automatically process the file N 26 27 Day indicator 01 to 31 Only numeric characters are valid

DD = Indicates day of the month that the file was created and does not indicate the date of the transactions

0 6 28 29 Month indicator 01 to 12 Only numeric characters are valid MM = Indicates the month of the year that file was created and does not indicate the date of the transactions

1 0 30 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 31 Instance ID I = Instance Only the specified alpha character is valid

I 32 33 34 35 Instance number 0001 to 9999 Each TI product can have up to 9999 instances per profile An instance is a grouping of your accounts, settings and delivery protocol eg Instance 0001 account1 selected settings 'credits only' and delivered via email 1 2 3 4

Example: PNGG00.CDTIPK.A13OP678.EN0610.I1234 C.SQ1234 Field numbers Data Element Valid Values Description Notes 36 Protocol ID C = Connect: Direct E= Email S = Swift W = Web Services M = IBM MQ A = FileAct F = FTP P = SFTP Q = IBM MQ FTP Only the specified alpha characters are valid This is the delivery protocol selected for this instance. Please note if the file is resent to the alternative email address the file name will contain the original protocol ID and not the email ID C 37 Separator . To separate data elements The full stop cannot be replaced with a comma as the file validation will fail . 38 39 Sequential SQ Only the specified alpha characters are valid These values cannot be amended S Q 40 41 42 43 Data record length 0001 to 9999 These fields will indicate the fixed length of the data record. Only numeric characters are valid All TI files are fixed length 1 2 3 4

Note: The file name for all delivery protocols for the IOD product will always end with .ZIP and not end with .SQ1234. All IOD files have a fixed length of 256 bytes. For all other TI products files that are sent on the email, the delivery protocol will include the file format as an extension at the end of the file name eg, .xml, .csv etc. This is to enable the opening of the file in the correct application.

1.4 Nomination of a contact person

You must nominate a person with proper authority to deal with all communication matters to Nedbank. Nedbank will direct all correspondence and enquiries to the nominated contact person who is the acting authority of the organisation and will be perceived as such if any instructions are received from him/her.

Note: The contact person must be from the data processing department of the organisation. Technical consultations during the development phase may be at a different level.

1.5 Resend of transactions and files

A. Resend of transactions

a) Products to receive resent transactions

The resend of real time transactions is only available to Notifications and PTI.

b) Resend addresses

For the PTI product you can request the bank to resend transactions to the delivery address on the instance or to the alternate email address. Transactions can only be sent to the alternate email address if the alternate email address is currently captured on your PTI instance.

If the alternate email address is not currently captured on the instance you can update it on NetBank Business or for Host clients send through a maintenance request. If the resend key is greater than 0 it indicates that this is a resend of a previous transaction.

B. Resend of files

a) Products to receive resent files

This functionality is only available for files that were sent for the IOD, FTI and PTI products.

b) Resend addresses

You can request the bank to resend the file to the delivery address on the instance or to the alternate email address. The file can only be sent to the alternate email address if the alternate email address is currently captured on your instance.

If the alternate email address is not currently captured on the instance you can update it on NetBank Business or for Host clients send through a maintenance request. In field 25 of the TI file name the R indicates that this is a resend of a previous file.

C. How to request a resend

a) Host Clients

You may contact Client Integration Support should you require any of your transactions or files to be resent. Refer to 1.8.1 for contact details

b) NetBank Business Clients (SMS / Email delivery protocol only)

You may contact the NetBank Business Help Desk to request your transactions or files to be resent. Refer to 1.8.2 for Internet banking contact details

Note: You can only request to resend the original file once a day. If you do not receive the resend, you will have to wait for the next business day to request the resend of that file.

Note: Nedbank holds your data of previous transactions or files sent for a period of 90 days, therefore you can only request a resend of a transaction or file up to 90 days in the past. The resend transaction or file will be formatted and sent based on the current template and delivery address captured on your instance, and not the original settings at the time the file was first sent.

1.6 Responsibilities

It is your responsibility to ensure that connectivity is active and operational in order to receive transaction information.

1.7 System Availability

  • You are responsible for the provision and cost of the delivery protocol.
  • The TI service will be interrupted periodically for hardware and software maintenance.

Note: Nedbank system maintenance is scheduled daily between 23:45 and 00:30. All transactions processed during this maintenance slot will be delivered once the maintenance has been completed.

1.8 TI service support

1.8.1 Host connectivity support

Client integration services (CIS) will provide you with contact details for a support person to handle all host to host related queries:

Contact number: 011 295 8737 / 083 627 7712 Email: h2hcs@nedbank.co.za

1.8.2 Internet banking (NetBank Business) connectivity support

For any queries related to Notifications, PTI, FTI and IOD on NetBank Business (NBB) contact NCCS for support:

Corporate Banking clients: 0860 102 187 Business Banking clients: 0860 111 055 NCC Relationship Banking clients: 0860 116 400 From outside South Africa: +27 (0)11 710 4311

1.9 Delivery protocols

1.9.1 Real time delivery protocol

A. IBM MQ

a) What is IBM MQ?

IBM MQ is sometimes referred to as message-oriented middleware and is an IBM standard for program-to-program messaging across multiple platforms. It is a protocol that sends data in real time and is a reliable messaging service that guarantees delivery through persistent sending capability. It can provide feedback on successfully sent messages and if no confirmation is received, the message can be resent. IBM MQ is offered over a leased line.

b) Information required from you

  • Your MQ Manager name
  • Your MQ Queue name
  • Your Static Public IP Address which is hosting the MQ Manager
  • Port number the MQ listener is running on
  • Channel name is based on the names of the two MQ Managers involved

Note: Depending on your environment you may have different configurations for your test, disaster recovery and production environment. If applicable, Nedbank will require all these data.

c) Nedbank Information you would require

Nedbank will provide you with the following information:

  • Leased Line: MQ Manager Name QA - PROD - DR - Static Public IP Addresses QA - PROD - DR -
  • Internet: MQ Manager Name QA - PROD - DR -

Static Public IP Addresses QA - PROD - DR -

  • Security protocol ie SSL using a trusted public security certificates

d) Hardware / Software requirements

The IBM MQ software is compatible with the following platforms and operating systems:

  • AIX
  • HP -UX
  • Linux for System x
  • Linux for System P
  • Linux for System z
  • Solaris
  • Windows
  • I5/OS
  • IBM
  • z/OS

Note: Contact your CIS manager for detailed IBM MQ hardware and software requirements related to your platform or operating system.

e) Licensing

Dedicated IBM MQ Manager licenses are required from both ends of the connection.

f) Security infrastructure

IBM MQ Manager version 7.5 and above have advanced message security which includes:

  • End-to-end, message-level security that offers data protection for your point-to-point messaging infrastructure
  • Data encryption and authentication that provides security-rich data transport throughout the messaging cycle

g) Applicable charges for connectivity

Security Certificates

B. Web Services

a) What is Web Services?

A Web Service is a method of communication between two electronic devices over a network. The Web Service protocol sends data in real time. Nedbank's standard is to send / push the data to your Web Service. A WSDL (Web Service Definition Language) will be provided by Nedbank, to which you must conform. Web Services is offered over either a leased line or the internet.

b) Information required from you

  • Static Public IP Addresses
  • Fully qualified URL
  • Require your Certificates for mutual authentication. If required, Nedbank can provide you with a Certificate. For this an additional fee may apply
  • Require the format / template of the encapsulated content which will be sent in the Web Service call

Note: Depending on your environment you may have different configurations for your test, disaster recovery and production environment. If applicable, Nedbank will require all these data.

c) Nedbank Information you would require

  • Leased Line: Static Public IP Addresses QA - PROD - DR -
  • Internet: Static Public IP Addresses QA - PROD - DR -
  • WSDL (Web Service Definition Language) supplied by Nedbank which will form the base for the development of your Web Service protocol
  • Require Nedbank Certificates for mutual authentication

d) TI third-party Web Service contract

  • Step 1: Extract the four files below to a folder on your machine
  • Step 2: Open you development environment
  • Step 3: Initiate or create a Web Service wizard (Wizard name may be different depending on the development tool you are using)
  • Step 4: Use the TIWebDistribution _2013-11-01.wsdl as your primary file
  • Step 5: Continue implementation as per your development environment

TIWebDistribution_2 013-11-01.htm TIWebDistribution_2 013-11-01.wsdl

EnterpriseContext_2 008-09.wsdl EnterpriseContext_2 008-09.xsd

Note: Take note that the data contained in the

1
<TransformedData> element is formatted as per the
template you have selected.

e) Web Services Hardware / Software requirements

The Web Service software is compatible with the following platforms and operating systems:

  • Z/OS
  • UNIX
  • LINUX
  • Windows
  • HP Non-Stop (Tandem)
  • Open VMS
  • OS/600 Series
  • VM/VSE
  • Gentran Integration Suite
  • Java
  • .NET

Note: Contact your CIS manager for detailed Web Services hardware and software requirements related to your platform or operating system.

f) Licensing

The licenses for Web Services can be classified as proprietary or open:

  • Proprietary software licenses allow for the execution of the software (including components) in your computing environment
  • Open source licenses allow you to view, modify and share the source code as well as redistributing the software either for commercial and/or non-commercial purposes

g) Security infrastructure

When using Web Services you must consider the following security aspects:

  • Authentication
  • Authorisation
  • Protection of sensitive data on the network and
  • Handling potentially malicious input

In order to address the above mentioned security aspects Nedbank enforces Mutual SSL, which will address the following:

  • message security or transport security to encrypt and sign messages
  • platform-provided cryptography

  • platform features for key management

  • Periodically changing both our and your keys (renewal of certificates on a periodic basis)

h) Standards utilised by Nedbank for Web Services:

  • SOAP 1.1 or 1.2
  • XML 1.1
  • XML Schema 1.0
  • Web Services definition language (WSDL) 1.0

i) Applicable charges for connectivity

There will be charges applicable if you require a security certificate or a leased line.

j) Describing the Web Service contract

Nedbank initiates a Web Services-ready platform where the enterprise context will already have been populated; you are expected to echo it back on your response message.

Enterprise context headers for all message layouts (request and response) Field name Type (Max Length) Mandatory/ Optional Min occurs Max occurs Description Comment Process context ID String (36) O 0 1 This identifier indicates that the request is part of a bigger process. It is a unique ID for each process request and it must be a globally unique identifier (GUID). Usually populated with a GUID/UUID, used for tracing/tracking. Execution context ID String (36) M 1 1 This identifier is uniquely used to identify the request and it must be a GUID. Usually populated with a GUID/UUID, used for tracing/tracking. Machine IP address String (20) M 1 1 This field contains the IP address of the machine. Source IP Address User principle name String (32) M 1 1 This field contains the username that is used to log on to a machine.

Machine DNS name String (50) M 1 1 This field contains the full qualified domain name of the machine. Source Machine Name Channel ID Long (3) M 1 1 This is the unique identifier for the channel and is used to initiate the request.

Parent instrumentation String (36) M 1 1 This is the instrumentation Usually populated with a

ID ID of the parent instrumentation entry and it must be a GUID. GUID/UUID, used for tracing/tracking. Child instrumentation ID String (36) M 1 1 This is the instrumentation ID of the child instrumentation entry and it must be a GUID. Usually populated with a GUID/UUID, used for tracing/tracking.

Sample Enterprise Context format

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
<ent:EnterpriseContext>
<ent:ContextInfo>
<ent:ProcessContextId>?</ent:ProcessContextId>
<ent:ExecutionContextId>?</ent:ExecutionContextId>
</ent:ContextInfo>
<ent:RequestOriginator>
<ent:MachineIPAddress>?</ent:MachineIPAddress>
<ent:UserPrincipleName>?</ent:UserPrincipleName>
<ent:MachineDNSName>?</ent:MachineDNSName>
<ent:ChannelId>?</ent:ChannelId>
</ent:RequestOriginator>
<ent:InstrumentationInfo>
<ent:ParentInstrumentationId>?</ent:ParentInstrumentationId>
<ent:ChildInstrumentationId>?</ent:ChildInstrumentationId>
</ent:InstrumentationInfo>
</ent:EnterpriseContext>

Description of the request message Tag name Type (Max Length) Usage Min occurs Max occurs Description Format NC-10 Required 1 1 The format of the data as provided by the TI backend SecurityProxyType NC-10 Required 1 1 A value indicating the security gateway to use. DestinationKey Long(9) Required 1 1 Destination Key TransformedData NC-5000 Required 1 1 The generated data

Sample of request message

1
2
3
4
5
6
7
8
<DistributeMsgRq>
<Content>
<Format>XML</Format>
<SecurityProxyType>SECURE</SecurityProxyType>
<DestinationKey>000</DestinationKey>
<TransformedData>Data</TransformedData>
</Content>
</DistributeMsgRq>

Description of the response message (message generated by you in response to the request message) Tag name Type (Max Length) Usage Min occurs Max occurs Description ResultCode NC-3 Required 1 1 R00 - is the required response for a successful transmission of the message (all other codes will be treated as an error to be defined by the client, this list of error codes must be maintained by the client)

Sample of the response message

1
2
3
<DistributeMsgRs>
<ResultCode>R00</ResultCode>
</DistributeMsgRs>

C. Enotes PTI Web Services

Refer to Appendix F for more information on Enotes PTI Web Services.

Note: Enotes PTI Web Services is for informational purposes for clients migrated to TI from Enotes PTI. New clients must use the TI Third-party Web Services contract.

D. SWIFT (Society for Worldwide Interbank Financial

Telecommunication)

a) What is SWIFT?

SWIFT uses a standardised proprietary communications platform to facilitate the transmission of information about financial transactions. This information, including payment instructions, is securely exchanged between financial institutions.

b) Information required from you

SWIFT Address for QA and Production.

c) Nedbank Information you would require

  • Nedbank SWIFT Address for QA and Production: NEDSZAJ0 - QA NEDSZAJJ - Production

d) Hardware / Software requirements

SWIFT is compatible with the following platforms and operating systems:

  • Windows
  • Solaris
  • Linux
  • IBM AIX

Note: Contact your CIS manager for detailed SWIFT hardware and software requirements related to your platform or operating system.

e) Licensing

You need to have an agreement with SWIFT to utilise the SWIFT cloud and have a SWIFT Address.

f) Security infrastructure

As per SWIFT standards and requirements.

g) Applicable charges for connectivity

You will incur the charges as per your agreement with SWIFT.

E. Email

a) What is email?

Electronic mail, most commonly referred to as email is a method of exchanging digital messages from an author to one or more recipients.

b) Information required from you

In order to use this protocol you must have a valid email address.

c) Software requirements

Functioning email server.

d) Security

Nedbank will digitally sign the email.

e) Applicable charges for connectivity

None.

1.9.2 Near real time delivery protocol

A. Connect: Direct

a) What is Connect: Direct?

The Connect: Direct protocol is a file transfer protocol that sends data in near real time. Connect:Direct can be used over a leased line or over a public internet connection to connect to Nedbank. It can be configured to provide feedback on successfully sent files. The Connect: Direct configuration is required once the Connect: Direct software has been loaded. When the Connect: Direct configuration has been completed, the connection will be tested end to end. In most cases, Nedbank coordinates the installation.

b) Information required from you

  • Your Static Public IP Address
  • Your Server name
  • Directory
  • Connect:Direct will connect to port 1364 which must be provisioned on your firewall

Note: The email protocol does not guarantee delivery ie Nedbank can confirm the email has been sent but cannot confirm that you have received it.

c) Nedbank information you would require

  • Leased Line: Static Public IP Addresses QA - PROD - DR -
  • Internet: Static Public IP Addresses QA - PROD - DR -
  • User name Unique per client
  • Nedbank will issue one CA Certificate to you to upload on to your Connect:Direct software.

d) Hardware / Software requirements

The Connect: Direct software is compatible with the following platforms and operating systems:

  • Z/OS
  • UNIX
  • LINUX
  • Windows
  • Select
  • HP Non-Stop (Tandem)
  • Open VMS
  • OS/600 Series
  • VM/VSE
  • Gentran Integration Suite

Note: Contact your CIS manager for detailed Connect: Direct hardware and software requirements related to your platform or operating system. Certain LINUX versions are not supported.

e) Licensing

You will require your own Connect:Direct license or a spoke license can be issued from Nedbank. If you already have an existing spoke license with Nedbank you can use the same license to receive your TI files if capacity allows.

Note: You will not be able to use a spoke license issued by another entity to connect to Nedbank.

f) Security infrastructure

Connect:Direct ensures that your information stays private and that your file transfers are auditable for regulatory compliance through a proprietary protocol, authorisation and encryption.

g) Applicable charges for connectivity

If you require a spoke license from Nedbank there is a monthly license fee and a once off installation fee applicable.

Note: Contact your Transactional Banker for further information.

B. Secure file transfer protocol (SFTP)

a) What is SFTP?

SFTP is a secure file transfer protocol that sends data in near real time. This is a much preferred and enhanced version of transferring files in a more secured manner when compared with FTP (unsecured protocol for file transfer). There are licensing implications for both. A 'staging area' is required where the files will be put in your business environment to be picked up by an application for internal processing. It uses a fire-and-forget pattern and therefore no acknowledgment of receipt is required. You have two options when using SFTP protocol:

  • You must exchange security keys with Nedbank and vice versa and
  • You must supply Nedbank with a user name.

b) Information required from you

  • Static Public IP Address
  • User name
  • Public key
  • Port number 22 must be open on your firewall

c) Nedbank information you would require

  • Leased Line: Static Public IP Addresses QA - PROD - DR -

  • Internet: Static Public IP Addresses QA - PROD - DR -

  • Public key and IP Address Unique per client

d) Software requirements

You will require a SFTP server that is compatible with Nedbank's system.

Note: Nedbank uses a Unix operating system SFTP software. Please confirm with your Nedbank Integration Manager.

e) Hardware requirements

The SFTP protocol is compatible with the following platforms and operating systems:

  • Z/OS
  • UNIX
  • Windows
  • Windows NT
  • Mac OS X

Note: Contact your CIS manager for detailed SFTP hardware and software requirements related to your platform or operating system.

f) Licensing

The SFTP is for your own account.

g) Security infrastructure

Mutual SSL ie certificates issued from the SFTP software.

h) Applicable charges for connectivity

None

C. SWIFT FileAct

a) What is SWIFT FileAct?

SWIFT FileAct provides a way to transfer large volumes of data in different formats to your correspondents, whether you need to transfer mass payments information, documents, images, or other data. In the case of TI you can opt to receive your FTI, PTI and / or IOD files using SWIFT FileAct.

The mechanism used by Nedbank to transfer TI files on SWIFT FileAct is to use store and forward.

Note: Nedbank only uses store and forward for TI, ie realtime is not available.

b) Information required from you:

  • Your SWIFT Address for QA and Production environment. Nedbank will accept the BIC8 or BIC11 SWIFT address.
  • Requester DN Example: o="Client BIC",o=swift

c) Nedbank information you would require:

  • Nedbank SWIFT Address for QA and Production environments are NEDSZAJJ.
  • This information will be applicable to PTI, FTI and IOD:
  • Request Type o PTI = pain.xxx.irtrpt or pacs.xxx o FTI = pain.xxx.eodrpt or pacs.xxx o IOD = pacs.xxx
  • Responder DN: o=nedszajj,o=swift
  • Files for File Act must not be compressed
  • SWIFT Fileact Service to be used for store and forward: o QA = swift.generic.fast!p o Prod = swift.generic.fast

d) Hardware / Software requirements

  • SWIFT Alliance Gateway

e) Licensing

There are no licencing requirements from Nedbank but you need to have a valid SWIFT Address.

f) Security infrastructure

FileAct uses SWIFTNet Public Key Infrastructure (PKI) that enables the authentication and the integrity control for every file transferred.

g) Applicable charges for connectivity

SWIFT charges a FileAct usage fee per transferred file. The transfer fees vary according to the size (in bytes) of the file and the institution's global tier. Nedbank will not levy a charge for connectivity, you will be charged as per your agreement with SWIFT.

D. Email

a) What is email?

Electronic mail, most commonly referred to as email is a method of exchanging digital messages from an author to one or more recipients.

b) Information required from you

In order to use this protocol you must have a valid email address.

c) Software requirements

WinZip and a functioning email server.

d) Licensing

None

e) Security

Any file sent using the email protocol will be zipped using WinZip. The Zip file will be attached to the email and password protected. In addition the email will be digitally signed by Nedbank.

f) Applicable charges for connectivity

None

1.10 Pricing

A. Charge account

You can use the same charge account for all your TI products or if required, you will have the ability to choose different charge accounts for each TI product. Each product can have a separate transaction, subscription and administrative charge account.

Note: Only Nedbank current and savings accounts that belong to the same legal entity can be used as a charge account.

B. Billing date

All charges will be posted to the nominated charge account(s) on your profile billing date.

Note: If you change your profile billing date on any of the TI application or maintenance forms, it will update your billing date for all products on the profile.

C. Product charges

Based on your pricing agreement with Nedbank, you may be charged a different pricing structure (transaction fee or a monthly subscription fee) eg, for PTI a transaction fee and for Notifications a monthly subscription fee. In each pricing structure, the FTI and PTI products will have different charges based on the delivery protocol selected.

Note: Only the zipped file is password protected ie once the file is extracted no password is required.

a) Transaction fee pricing structure

The transaction fee is calculated based on the number of Notifications sent to you, which can be subject to a minimum and maximum fee per month. Up to three transaction fees may be applicable for PTI and FTI based on the delivery protocol selected, ie:

  • A transaction fee for the SWIFT delivery protocol, subject to a minimum and maximum per month
  • A transaction fee for the email delivery protocol, subject to a minimum and maximum per month
  • A transaction fee for all other delivery protocols, subject to a minimum and maximum per month

If a financial transaction is sent to multiple destinations, you will be charged for the delivery to each destination eg, if a cash deposit of R500 is deposited into your account and you request to send the information to:

  • two destination addresses you will be charged 'two times' your Notification fee
  • five destination addresses you will be charged 'five times' your Notification fee

Fees are accumulated and billed to your nominated transaction charge account once a month. This will appear as a separate line item on your charge account statement ie:

1
- <Product> transaction fee <number of notifications sent>
eg PTI transaction fee(10) eg PTI SWIFT fee(8) eg PTI Email fee(9) eg FTI transaction fee(20) eg FTI SWIFT fee(8) eg FTI Email fee(9) eg IOD transaction fee(2) eg IR transaction fee(1) eg Notifications variable fee(4)

Contact your Transactional Banker to confirm your actual pricing.

Note: You can have the same or a different transaction charge account per product. However, the billing date cannot be different to your profile billing date.

b) Monthly subscription fee pricing structure

Your monthly subscription fee will be billed to your nominated subscription charge account on your profile billing date. This will appear as a separate line item on your charge account statement ie:

1
- <Product> subscription fee <number of notifications>
eg PTI subscription fee(1) eg FTI subscription fee(20) eg IOD subscription fee(1) eg IR subscription fee(1) eg Notifications flat fee(4)

Contact your Transactional Banker to confirm your actual pricing.

Note: You can have the same or a different subscription charge account per product. However, the billing date cannot be different to your profile billing date.

D. Additional PTI fee if applicable

  • PTI end of day file charges

You will be billed a monthly fee to your nominated subscription charge account on your profile billing date. This will appear as a separate line item on your charge account statement ie:

1
- PTI end of day fee <number of notifications / files>
eg PTI end of day fee(1) Contact your Transactional Banker to confirm your actual pricing.

Note: You can have the same or a different transaction charge account per product. However, the billing date cannot be different to your profile billing date.

E. Other charges

The below fees are only applicable if you request the bank to resend a Notification or if you have submitted a maintenance request to be actioned.

  • Resend fee

If you request the bank to resend a Notification or file you may be charged a resend fee per request. Fees will be accumulated and billed to your nominated

administration charge account on your profile billing date. This will appear as a separate line item on your charge account statement ie:

1
- <Product> resend fee <number of resends>
eg PTI resend fee(1) eg FTI resend fee(2) eg IOD resend fee(1) eg Notifications resend fee(4)

Contact your Transactional Banker to confirm your actual pricing.

Note: You can have the same or a different transaction charge account per product. However, the billing date cannot be different to your profile billing date.

F. Administration charges

If you request the bank to add or maintain any TI instances, you may be charged an administration fee per maintenance request.

Fees will be accumulated and billed to your nominated administration charge account monthly on your profile billing date. This will appear as a separate line item on your charge account statement ie:

1
- TI admin fee <number of maintenance requests>
eg TI admin fee(10) Contact your Transactional Banker to confirm your actual pricing.

Note: You can have the same or a different administration charge account per product. However, the billing date cannot be different to your profile billing date.

G. Connectivity charges

a) Leased line

Nedbank does not charge you any leased line fees. Your service provider will charge you directly for any leased line costs. If capacity is available on your existing leased line, you may choose to enable the TI products on this line.

b) Connect: Direct license

There will be a once off implementation fee and a monthly license fee. If you have an existing Connect: Direct license with Nedbank, you can use the existing license if capacity is available. Contact your Transactional Banker to confirm these fees.

c) IBM MQ

Nedbank does not charge you any IBM MQ fees unless Nedbank issues you with the security certificate. The Nedbank issued certificate will attract an annual fee. Contact your Transactional Banker to confirm these fees.

d) SFTP

Nedbank does not charge you any SFTP fees unless Nedbank issues you with the security certificate. The Nedbank issued certificate will attract an annual fee. C ontact your Transactional Banker to confirm these fees. In order to use this protocol you will be required to have SFTP software compatible with Unix operating system, which could attract a software license fee.

e) SWIFT FileAct

Nedbank does not charge you any SWIFT FileAct fees. All SWIFT FileAct fees will be charged as per your SWIFT agreement.

f) SWIFT

Nedbank does not charge you any SWIFT fees. All SWIFT fees will be charged as per your SWIFT agreement.

g) Web Services

Nedbank does not charge you any Web Services fees unless Nedbank issues you with the security certificate. The Nedbank issued certificate will attract an annual fee. Contact your Transactional Banker to confirm these fees.

h) Email

Nedbank does not charge you for any email connectivity, this must be negotiated with your service provider.

Note: All Nedbank fees can be discussed with your Relationship Manager or Transactional Banker.

1.11 Security

Due to the implementation of the Protection of Personal Information Act (POPIA) all sensitive information sent, must be delivered using a secure delivery protocol.

The following protocols are supported:

  • Connect: Direct
  • Email attachment
  • IBM MQ
  • SFTP
  • SWIFT
  • SWIFT FileAct
  • Web Services

Note: FTP is no longer supported by Nedbank.

1.12 High level onboarding process for TI host to host delivery protocols

Identifies client need for TI Sales manager Client CIS Generates proposal of TI offering for client Setup meeting with client to discuss proposal Initiate client application Setup initial meeting with CIS and client to discuss options End Client accepts proposal Yes, client wants to take up TI Initial workshop to discuss TI product - connectivity protocol requirements Setup technical workshop with client and Nedbank Technical workshop to gather and explain technical process to be followed for TI to setup - connectivity protocol requirements, file formats etc. Project plan to be put together Provide client with application form for signature Submit document for vetting and loading Vetting and loading successful Client to sign documents and fax to Nedbank or hand to sales manager Client confirms connectivity working Client confirms receipt of transactions Client confirms transactions received in production Ensure connectivity setup between client and Nedbank Generate test transactions Schedule production release date Start 30 day client support

1.13 TI Keys

A. Transaction key

Every transaction is allocated a 16 digit key. If you receive the same transaction key on more than one message it is reporting information about the same transaction. However, note the key is only unique at a product level and not across TI products ie, the same transaction will have different transaction keys on PTI and FTI.

B. Process key

Every process is allocated a 9 digit key. A process uniquely identifies the current client preferences for the transaction. This value is for internal purposes and does not have to be interpreted by you in processing this transaction.

C. Resend key

Every message is allocated a 9 digit key. Any value greater than zero means that the transaction was resent. A resent transaction will have the same transaction key as the initial transaction.

D. Destination key

If a single instance has more than one destination address it will have a different destination key, per delivery address. However, note the key is not uniquely linked to the destination address ie, the same delivery address on the same instance can have a different destination key on two different messages.

1.14 TI Templates

A. TI Template groups

The template groups contain a selection of templates that make a logical fit into a specific group eg any SWIFT proprietary template will be available under the SWIFT group.

Currently the following groups are available:

  • Nedbank
  • SWIFT
  • SAP
  • Other
  • Client Specific

Note: To view the format and detail of the above templates refer to Appendix A for PTI, Appendix B for FTI and Appendix D for IR.

B. The 'Nedbank' Template group

a) Near real time templates

  • PTI Templates:
  • TI PTI XML (NRT)
  • TI PTI CSV (NRT)
  • TI PTI TXT (NRT)
  • Enotes PTI CSV (NRT)
  • Enotes PTI SWIFT MT940
  • Enotes NedAcad
  • Enotes PTI EOD XML
  • Enotes PTI EOD CSV

Note: To view the format and detail of the above templates refer to Appendix A. The Enotes PTI templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.

b) Real time templates

  • PTI Templates:
  • TI PTI XML (RT)
  • TI PTI CSV (RT)
  • TI PTI TXT (RT)
  • Enotes PTI XML (RT)
  • Enotes PTI CSV (RT)

Note: To view the format and detail of the above templates refer to Appendix A. The Enotes PTI templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.

  • FTI Templates:
  • TI FTI XML
  • TI FTI CSV
  • TI FTI TXT
  • NedAcad 4 digit statement - 29 character statement narrative
  • NedAcad 6 digit statement - 27 character statement narrative
  • NedAcad 6 digit statement - 30 character statement narrative

  • NedAcad 4 digit single statement - 29 character statement narrative

  • NedAcad 6 digit single statement - 27 character statement narrative

  • NedAcad 6 digit single statement - 30 character statement narrative

Note: To view the format and detail of the above templates refer to Appendix B. The NedAcad templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.

C. The 'SWIFT' Template group

a) Near real time templates

  • FTI Templates:
  • TI SWIFT MT940
  • TI SWIFT MT950
  • NED SWIFT MT940
  • NED SWIFT MT950
  • TI SWIFT MX940 - camt.053 (Bank to customer statement)

  • TI SWIFT MX950 - camt.053 (Bank to customer statement)

  • PTI Templates:

  • TI SWIFT MX942 - camt.052 (Bank to customer account report)

  • TI SWIFT MT942

  • IR Templates

  • TI SWIFT MT940
  • TI SWIFT MT950
  • TI SWIFT MT942

Note: To view the format and detail of the above templates refer to Appendix A, B and C. The NED SWIFT templates are only applicable to existing clients that are already utilising the templates and will not be available to new clients for selection.

b) Real time templates

  • PTI Templates:
  • TI SWIFT MT900
  • TI SWIFT MT910
  • TI SWIFT MT941
  • 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)

  • IR Templates:

  • TI SWIFT MT941
  • SWIFT MT920 You will be required to use t his template when requesting final or provisional statement information from Nedbank.

Note: To view the format and detail of the above templates refer to Appendix A and C.

D. The 'SAP' Template group

a) Near real time templates

  • PTI Templates:
  • Multicash AUSZUG

  • Multicash UMSATZ

  • FTI Templates:

  • TI SWIFT MT940
  • Multicash AUSZUG
  • Multicash UMSATZ

Note: To view the format and detail of the above templates refer to Appendix A and B.

b) Real time templates

None currently available

E. The 'Other' Template group

a) Near real time templates

b) Real time templates

  • XXXXX

F. The 'Client Specific' Template group

a) Near real time templates

  • None currently available

b) Real time templates

  • Vodacom - PTI

1.15 Testing your TI functionalities for host protocols

A. Process for quality assurance (QA) testing

Due to the complexity of the TI environment, all organisations must go through a testing phase before going into production with the system. This is mainly to verify connectivity, data integrity and client system changes and/or development. During the test phase the following key aspects must be verified:

  • Connectivity using your chosen delivery protocol must be stable and in place
  • Specified file layout must be adhered to
  • Business processes align with business requirements

The organisation must meet the following requirements before testing may begin:

  • The TI file layouts must be set up
  • The organisation and Nedbank must have parallel QA environments in place

During testing the following naming convention will be used:

Example: QNGG00.CDTIPK.A13OP678.EN0610.I1234C.SQ1234

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

B. Testing scenarios

Tests could possibly cover the following scenarios, but can be tailored to your needs:

  • The sending of high-volume files (inclusive of high- and low-volume data)
  • The integrity of the data contained in the files sent (layout of data and file format)
  • The use of a nominated account(s) set up in accordance with the intended production profile
  • The transfer of corrupt files and/or transactions (file-handling process)

Note: QA data is for testing purposes only and is not to be used for any decision-making processes regarding your customers.