PAYA - ACH Interface

New DPI-PAYA system (SEPAND) has been produced in order to establish interaction between each bank and the PAYA/ACH system in central bank.


After installation in bank, SEPAND with multiple services, on one hand communicates and interchanges files with MAP Server subsystem in central bank and on the other hand, communicating with Core in bank, provides all required services such as sending received orders to Core for determination, receiving response and sending the result to central bank, receiving payment orders issued by branches and sending them to central bank and receiving the result and preparing various reports. Design of SEPAND includes minimal operator interaction so that all the activities that do not need operator may be done automatically.


Some Features of SEPAND

·         Sending files to central bank (MAP Server) and receiving files from central bank (MAP Server) automatically and without the need for operator

·         Performing MCT activities including digital signature, coding and compression of transmitted files and controlling signature of central bank, encoding and opening files received from central bank automatically and without the need for operator

·         Independence of SEPAND from MCT

If in the future central bank changes the method of digital signature or coding and decoding, there is no need to change SEPAND.

·         Mechanized acceptance and payment order

Communication between SEPAND and Cores of banks is completely mechanized so that incoming payment orders and settlements are done automatically. If settlement is not possible, it is returned to central bank with reason and the operator is not involved in this process.

Besides that, payment orders that are issued after entering the information by user in branch (or other ports), are withdrawn automatically and sent to central bank by SEPAND.

·         Acceptance and payment order manually (semi-mechanized)

If for any reason the mechanized connection between SEPAND and Core is cut off, operator can receive payment orders from SEPAND and process them and announce the results to SEPAND so that they can be sent to central bank.

In addition to that, it is possible to issue payment orders using web-based method, without connection with core.

·         Monitoring

Possibility of observing and statistical analysis of all incoming and outgoing payment orders before receiving from/sending to central bank.

·         LOG

All events are registered in SEPAND and system administrator can do required follow up using reports including sufficient details.

·         Archive

·         Immediate payment order

Although central bank does not accept payment orders with effective date of the future, SEPAND can register and maintain such orders. SEPAND sends payment order to the Core on due date in order to do withdrawal and after that forwards it to central bank.

·         Security

Security of files exchanged between central bank and our bank is guaranteed by schemes of central bank (digital signature and encryption). In our bank, SEPAND registers information in database after encoding and does not allow any unauthorized access.

·         Ability to rollback and replay the files of central bank

If for any reason processing of files received from central bank fails, SEPAND rollbacks all operations after restart and begins processing of files again. Thus, the risk of data loss or information duplication will be removed.

·         Communication with some bank cores through channel management system

If there are several cores in a bank, SEPAND can communicate with all cores through communication with an interface (for example channel management system of DPI)

·         Basic information

SEPAND provides the ability to record and maintain basic information in ACHPROFILE module. It is possible to add information about cycle time changes, newly founded banks, and other basic information to this module.

·         Independent web interface

<<ROKSA>> is a program separated from SAMBA that provides the ability to use core services in a limited level. Part of this environment is used for users and part of it has administration usage. Administration usage includes user administration, defining and changing banks that are members of PAYA system, monitoring cycle of execution in the system.

·         Reports

Using ROKSA, it is possible to report settlements of other banks, issued payment orders, central bank bills, and creation and search of PAYA cycle profiles.



·         Reading/Writing and formatting messages exchanged with central bank through MCT

·         Reading orders/Writing responses to orders from banking cores from/in queue

·         Distribution and formatting of XML and text messages from banking core

·         Recording event messages to be exchanged between central bank and banking cores

·         Exchanging information entities with business processing section

·         Automatic communication with MAP server of PAYA system in central bank through FTP protocol and receiving and sending message files in specified time slices

·         Fully automatic coding/decoding, applying/verifying digital signature and message compression through MCT

·         Web based user interface that is independent from central core of bank

·         Administration of settlement notices, payment orders, semi automatic order of payments returned from other banks

·         Creating and retrieving file of settlement notice

·         Reports from settlement notice status, payment status, mutual cambium, central bank bill, PAYA cycles and …

·         Definition of basic information (active banks, PAYA cycle profiles)

·         Group settlement (validity check, document issuance, changing standard file to issued payment order)

·         Changing cycle of daily issued payment orders that have not been sent for any reason

·         Automatic sending of returned settlement notices that have not been sent to source banks



·         MCT terminal independence from main core of PAYA interface services (SAMBA) in terms of physical, operating system and used platform

·         Automatic sending and receiving of files without operator intervention, in specific phases of cycles

·         Security of exchanged messages due to mechanization of encryption process and sending and receiving , impossibility of fraud and changing messages by operator

·         Security of communication layer in MCT and SAMBA by security features of RMI