Host-To-Host EFT Domestic Payments
Host-To-Host EFT Domestic Payments
Host-To-Host Overview
Overview
EFT Payments gives you the ability to make electronic payments and transfers to another account.
Description
This service allows you to:
- Provide the bank with a payment instruction to make an electronic payment to a beneficiary.
- Provide the bank with a payment instruction to make an electronic payment from one of your accounts to another of your accounts.
Important Update
Initial Status Report (ISR) Transaction Failure:
Initial Status Report (ISR) Transaction Failure:
Certain transactions level failures can now be provided for upfront validations such as Check Digit Validation (CDV) in the Initial Responses Report (ISR). If you opt-in for this functionality, the failed transactions will be reported in the ISR. If you do not opt-in for this functionality, the ISR remains the same and the failures will be reported in the Sponsoring Bank Status Report (SBSR) and Paying Bank Status Report (PBSR).
View Transactions on OBE:
Transactions processed on our channel can now be seen on Online Banking Enterprise under Payments.
Submit and Release:
Transactions submitted on our channel can now be authorised on Online Banking Enterprise.
Hash Totals:
Hash Totals have been included to secure the integrity of EFT Collections on ISO messages.
Message Statuses:
All messages with mixed statuses will carry a "PART" status. This referes to a scenario where some of the transactions have been accepted, whereas others have not yet achieved "Accepted" status.
Getting Started
Overview
EFT Payments require that you have an active account with FNB and be able to send money within your portfolio, or to another account holder in South Africa.
Channel Features
The following channel features are available to you:
- Auto-bumping
- Warehousing
- Itemised or batch processing
- Item limits
- Auto-bumping
- Authorise transactions for processing
- Hash Totals on ISO Messages
- Flexible naming convention of files
- Handshake process for ACB files
- Partial Processing
Response Options
The client may OPT IN and OUT of the following positive responses. Negative responses are always sent. A client cannot opt-out of both Load Report and the Load File, Unpaid Report and Unpaid File. At least one Load or Unpaid response must be selected:
ISO
- Initial Status Report (ISR)
- Sponsoring Bank Status Report (PBSR)
- Paying Bank Status Report (PBSR)
ISO
- Hash File
- Confirm File
- Load Report
- Load File
- Unpaid Report
- Unpaid File
- Error File
- Invalid Error Report
MT
- MT195 Initial Response
- MT195 Final Response
- MT195 Unpaid Response
- MT195 Warehouse Final Response
- MT195 Maintenance Notification
File Naming Conventions
Our channel follows a generic file naming convention to make easier to identify and correlate request and response files, however you also have the ability to configure your own naming convention that works better with your system convention on both request and response files.
Below is an example of our generic naming convention accepted on the channel for EFT.
Available Transports
SFTP
SFTP is a widely accepted protocol, and is recommended if you will be sending high volumes of transactions in one request.
In terms of setup, it is your organisation's responsibility to install the protocol on your Server / AS400 / Mainframe. In addition, you will be required to provide us with your SFTP details for test and production environment if you are connecting on your own account.
If you are connecting on your own account, your system is required to send and fetch responses from the Bank. Our channel does not send responses to or fetch requests from your environment.
Connect Direct
FileAct provides a cost-effective way to transfer large volumes of data in various formats to your correspondents. Useful when you need to transfer mass payments information, documents or other data. FileAct is particularly suitable for transferring large files of structured messages, such as bulk payments files or securities value-added information. Files of almost any format or size may be sent, up to hundreds of MB. FileAct provides the security, availability and reliability your business demands, including the highest availability in the industry.
Swift File Act
FileAct provides a cost-effective way to transfer large volumes of data in various formats to your correspondents. Useful when you need to transfer mass payments information, documents or other data. FileAct is particularly suitable for transferring large files of structured messages, such as bulk payments files or securities value-added information. Files of almost any format or size may be sent, up to hundreds of MB. FileAct provides the security, availability and reliability your business demands, including the highest availability in the industry.
SWIFT FIN
SWIFT FIN is a message type (MT) that transmits financial information from one financial institution to another.
MQ (Message Queue)
Messaging Queue IBM MQ is robust messaging middleware that simplifies and accelerates the integration of diverse applications and business data across multiple platforms.
MQ is recommended for real time processing for maximum efficiency.
In terms of setup, you will be required to issue us with your MQ details for test and production environment if you are connecting on your own account.
MFT
Managed file transfer (MFT) is a technology platform that allows organizations to reliably exchange electronic data between systems and people in a secure way to meet compliance needs. These data movements can be both internal and external to an enterprise and include various types, including sensitive, compliance-protected or high-volume data. It can be offered as software or as a service and may include a single pane for visibility and governance.
MFT is a more reliable and efficient means for secure data and file transfer, outpacing and outperforming applications such as file transfer protocol (FTP), hypertext transfer protocol (HTTP), secure file transfer protocol (SFTP) and other methods.
In terms of setup, you will be required to issue us with your Connect Direct details for test and production environment if you are connecting on your own account.
Message References
EFT Request Message Specification
ISO 20022 A rich, structured and global data standard which is flexible and easier to implement and can be used for making payment (credits) and collections (debits).
MT 101 A SWIFT message enabling EFT of funds from one account to another. ACB - A flat-file-format type mainly used for interactions between banks and its business and corporate clients. It enables companies and other bodies to process files entirely by computerised means. The service can be used both for collecting payments from clients (debits) and for making payments (credits).
EFT Response Message Specification
Clients can expect to get from responses from us through one of the following options:
ISO PAIN
Credit Transfer Initiation Message
The Credit Transfer Initiation Message is based on the banks' specific rules and usage guidelines derived from the base ISO20022 PAIN.001.001.03 and PAIN.001.001.10 messages. The message is sent by the initiating party to the bank to request movement of funds from ones' bank account to the specified recipient/s account/s.
Payment Status Report Message:
The Payment Status Report Message is based on the banks's specific rules and usage guidelines derived from the base ISO20022 PAIN.002.001.03 message. The Payment Status Report Message is based on the banks's specific rules and usage guidelines derived from the base ISO20022 PAIN.002.001.03 message. The report is made available to you by the Bank. It is mainly used to inform you of the outcome of Bank validation's, the status of a payment instruction file sent to the Bank and the status of each payment transaction in the file.
ISR
The response from the paying bank (First Rand for on-us and External Bank for off-us) indicating whether the homing account for the batch and transactions within the batch was fit for processing.
SBSR
The response from the sponsoring bank (First Rand) Eco System indicating whether the nominated account for the batch and transactions within the batch was fit for processing.
PBSR
The response from the paying bank (First Rand for on-us and External Bank for off-us) indicating whether the homing account for the batch and transactions within the batch was fit for processing
ACB
ACB:
The ACB could either contain single of multiple data sets. A data can be defined as several transactions and their related contra records, all having the same user code, and organized not a self-contained batch having its own header and trailer records.
Hash File:
The Hash total is a figure calculated in order to confirm the integrity of the client's data during transmission of the ACB file from the client's computer system to the bank's Fintegrate channel. Only files which Hash totals are successfully validated will be processed.
Confirm File:
The confirmation file which is used to instruct the bank to process the ACB Payment or Collection file.
Load Report
Based on the Bank's specific rules and usage guidelines required to create a Load Report. The Load Report is a readable report which allows for users to immediately see which transactions have been accepted or rejected.
Load File
Based on the Bank's specific rules and usage guidelines required to create a Load File. The Load file format contains the same information as the Load report format. However the intention of this format is for automated integration purposes and for a system to read and interpret.
Unpaid Report
The Unpaid Report displays all returned items to the account holder. It caters for the unpaid, rejected and redirected transactions for on us and off us transactions The unpaid transactions are written into the unpaid report up to 40 days from action date The report is generated overnight for all unpaid transactions received on the day these are extracted from the unpaid transactions database The unpaid report is made available to you a day after action date on your directory e.g.unpaid report generated on Tuesday night is made available on your directory once the report has been generated.
Error Report
Produced when a negative confirmation is received by the bank It is a replica of the original ACBFILE sent to the bank in order for comparison purposes between the file the bank received verses the file you originally produced This file is also produced if the confirmation file does not contain all the corresponding details to each file sent.
Invalid Error
This is produced when there are basic validation errors of the ACB file construction, or if the confirmation process has not been followed in order. A basic indication of file structure validations will indicate what data contents are incorrect.
MT
MT101:
A SWIFT message enabling the transfer of funds from one account to another.
MT195:
A Swift message type used to inform the client about the outcome of banks validations, payment instruction file status, payment transaction status, warehouse response and maintenance notification.