Professional Documents
Culture Documents
Prior to the establishment of BANKSERV in the first half of 1993, the banking industry in
South Africa jointly owned several companies that provided shared services to the banks in
a number of different payment channels. The companies in this sector each followed their
own direction and operated in their separate silo's. There was clearly a need to consolidate
them into a single structure. An Inter-bank task group was appointed to investigate the
feasibility of this proposal and in March 1993, the banking industry reached agreement and
founded BANKSERV.
WHY BANKSERV?
Now that you know who we are and what we do, here are a few reasons why your Bank
chooses BANKSERV as the partner of choice in the banking industry...
We are trusted
We have an excellent track record
We are non-competitive with our owners and clients
We have integrity
We are cost-effective
We have economies of scale
We have momentum
We have resources and capacity
Multiple participants share investments in joint projects
Having been successful, we are self-sufficient
Experienced industry experts maximise our intellectual capital
We have great relationships
We open doors and facilitate introductions through clients and Boards
We are viewed as a good opportunity for partners and vendors
We have an excellent service record
Our company culture and incentives are based on professional excellence
We have existing, successful, state-of-the-art products and services
Unique in Africa with a blue-chip client base
We have focused business units
Focusing current products on business principles
Managing new products and services
The Trusted Partner
We are proud of our position as the very nucleus of the banking industry and are determined
to grow our presence in previously uncharted territories. We have the expertise, the
intellectual capital, the heritage and an incomparable team of people that will lead us from
strength to strength.
Join us on our journey...
Billing
The Billing module allows for electronic invoicing, as well as electronic collection and
distribution of fees.
The collection and distribution of the fees is achieved by creating EFT files that are fed
through the EFT system to debit and credit the participating banks nominated accounts.
Risk Management
The increased velocity and value of transactions in the banking industry leads to the
common concern of the financial institutions ability to manage the process and concomitant
threats and risk, including:
Transaction based fraud
Business exposure risk
Containment of processing cost
The Bankserv solution addresses the transaction based fraud issue by focussing on:
A rules based transaction validation module
Delivering data timeously and correctly by means of its sophisticated delivery module
A modular, international standards based technology model that:
> contains costs
> eliminates single points of failure
> provides throughput capacity in compliance with stringent SLA demands
Industry benchmark DRP procedures
Parameter Files
The validation system is a core component of the Risk management suite. It is driven by a
set of rules and parameters that are the subject of continuous amendment depending on
business requirements and risk profiles.
Bankservs strict adherence to Service Level Agreements extends to controlling valid
processing dates and times in parameterised formats.
Data Encryption
Bankserv uses state-of the-art DES encryption algorithms for Personal Identification Number
(PIN) data for inward and outward transmission. Key exchanges occur on a regular basis.
BIN
Valid Bank Identification Numbers are maintained as part of the risk module parameters
Financial Limits
Bankserv applies an item limit validation to every financial transaction in terms of financial
regulatory requirements.
In any event, extensive financial and operational, fully auditable MIS reporting is made
available on a periodic and on demand basis. Daily reporting to sending banks may occur as
changes are effected to user security parameters.
Technology Model
Bankservs on-line, real-time system is implemented on an industry standard non-stop
Compaq. This approach allows a modular upgrade path with full access to the latest
developments in the industry.
Disaster Recovery
Compliance with strict Service Level Agreements is part of Bankservs culture. To this end,
the on-line, real-time system allows for the implementation of a parallel real-time process in
a remote location, which is part of the every day production suite.
Simultaneous system and financial parameter updates and other processes result in
successful daily, synchronised operations.
The remote location is subjected to the same stringent operational requirements as the main
production site, such as Uninterruptible Power Supply, no single point of failure, air
conditioning, water supply, etc.
Settlement Interface
The current settlement process is capable of providing Singular Settlement that may easily
be integrated into the settlement process for other payment streams.
End of Day Settlement
The Settlement Process provides daily inter-bank settlement information. This information is
delivered via a standard SWIFT interface to wherever these data are required. The end point
would typically be the central bank, with complementary data being delivered to participant
banks.
Upon reaching settlement for the EFT payment stream, the Settlement Process will deliver
the following information:
MT298 Settlement Instruction message to the central bank process via the SWIFT network
MT298 Settlement Notification messages to the participant member bank(s) via the SWIFT
network
Optional paper reports in support of the above messages
Scheduled List
The Settlement Process can deliver two types of settlement instruction messages:
Standard MT298 Settlement Instruction Messages
These are settlement instruction messages, which are for immediate settlement, once the
MT298 message has been delivered to the central bank system
Scheduled List MT298 Settlement Instruction Messages
These settlement instruction messages are delivered to the central bank system, placed in a
holding queue and then scheduled to effect settlement at a given date and time, as specified
in the MT298 message. These MT298 messages contain specific settlement tag fields,
which identify that it is a scheduled list instruction message.
BANKSERV believes that there is more than one possible solution and that the final choice
will be based on achieving a balance between risk and cost.
Network Requirements
A secure network should consist of a backbone Ethernet to which the existing equipment is
connected. (A direct connect x.25 network interface is also available optionally.) The firewall
must be a fail-over system with two separate sets of hardware so that, even if one device
fails, sessions or data will not be affected.
From the firewall the data itself will enter into an encrypted tunnel (Virtual Private Network -
VPN) to its endpoint, which will be a participating bank. Physically the data leaves the
firewall and hops to the router. This router should also be a fail-over system, and if the router
or line should fail, the second router may be used via Integrated Services Digital Network
(ISDN) dial-up connection. If all local leads fail, i.e. the leased line and dial-up connection,
then the alternate satellite path may be used. The VPN tunnel is used, because the satellite
transmission cannot be considered secure. A leased line is secure, because it is a point-to-
point line, but it should be encrypted using Internet Protocol Security to prevent possible
Telecommunications company personnel attempting to use sniffers. In addition, intrusion
detectors may be placed at the site to listen for any attack patterns.
Segregation and Confidentiality of Bank Data
The segregation of data between each bank is achieved by implementing internationally
accepted best practice in terms of firewall and router installations.
Validation
All received data are subjected to various validation actions in preparation for transferring
STP compliant transactions to the participating banks. The validation system is rules based
and parameter driven, and the subject of continuous amendment depending on business
requirements and risk profiles.
Typical validations are:
Compliance with bank and bank branch parameters
Clearing house or banking authority rules
Duplicate transaction detection
Transaction type, content validity and relational checking
Structural compliance
Valid processing dates
The results of the validation checking are supplied to submitting banks on a continuous
basis.
The output of the core Inter-Bank Credit Payment processing system results in balancing
and reconciliation settlement data for participating financial institutions.
Settlement Interface
The current settlement process is capable of providing Singular Settlement that may easily
be integrated into the settlement process for other payment streams.
End of Day Settlement
The Settlement Process provides daily inter-bank settlement information. This information is
delivered via a standard SWIFT interface to wherever these data are required. The end point
would typically be the central bank, with complementary data being delivered to participant
banks.
Upon reaching settlement for the Inter-bank Credit Payment stream, the Settlement Process
will deliver the following information:
MT298 Settlement Instruction message to the central bank process via the SWIFT network
MT298 Settlement Notification messages to the participant member bank(s) via the SWIFT
network
Optional paper reports in support of the above messages
Scheduled List
The Settlement Process can deliver two types of settlement instruction messages:
Standard MT298 Settlement Instruction Messages
These are settlement instruction messages, which are for immediate settlement, once the
MT298 message has been delivered to the central bank system
Scheduled List MT298 Settlement Instruction Messages
These settlement instruction messages are delivered to the central bank system, placed in a
holding queue and then scheduled to effect settlement at a given date and time, as specified
in the MT298 message. These MT298 messages contain specific settlement tag fields,
which identify that it is a scheduled list instruction message.
BANKSERV believes that there is more than one possible solution and that the final choice
will be based on achieving a balance between risk and cost.
System Overview
Bankservs Cheque Clearing System (CLC) is an electronic cheque clearing system whereby
data is transmitted to BANKSERV by collecting banks. After various processes, the validated
data is transmitted to the homing banks. The inter-bank settlement information is supplied to
the central bank and the banks treasury departments via a SWIFT link.
The original cheque paper is also forwarded to Bankserv at an agreed to later stage. An
electronic match and physical sort phase occurs, followed by cheque paper collection by
homing banks.
BANKSERV usually clears in excess of 10 million transactions per month and is experienced
in all the various operational requirements.
CLC Electronic Service
Cheques deposited at bank branches are processed at centralised depots. The cheques
MICR data line is captured electronically, assembled into electronic files, and transmitted to
Bankserv. The transmission occurs via high-speed Telecom lines from the banks processing
centre, to Bankservs Automated Transmission System (AXS).
Validation
All received data are subjected to various validation actions in preparation for transferring
STP compliant transactions to the participating banks, or to an optional generic clearing
process. The validation system is rules based and parameter driven, and the subject of
continuous amendment depending on business requirements and risk profiles.
Typical validations are:
Compliance with bank and bank branch parameters
Clearing house or banking authority rules
Duplicate file detection
Transaction type, content validity and relational checking
Structural compliance
Valid processing dates
The results of the validation checking are supplied to submitting banks on a continuous
basis.
The output of the core Cheque Clearing processing system results in switched Clearing and
balancing data for participating financial institutions.
Cheque paper processing
The physical cheques are delivered to Bankservs processing centres countrywide. This
process allows the optional matching of physical cheque paper received with a database of
electronic cheques submitted for clearing. In addition a sort of the cheques, either at bank
level, or down to serial number, occurs for the distribution of the physical cheques.
MIS suites provide information regarding the tracking of physical paper and a variety of
associated reports.
Settlement Interface
The current settlement process is capable of providing Singular Settlement that may easily
be integrated into the settlement process for other payment streams.
Settlement Interface: End of Day Settlement
The Settlement Process provides daily inter-bank settlement information. This information is
delivered via a standard SWIFT interface to wherever these data are required. The end point
would typically be the central bank, with complementary data being delivered to participant
banks.
Upon reaching settlement for the CLC payment stream, the Settlement Process will deliver
the following information:
MT298 Settlement Instruction message to the central bank process via the SWIFT network
MT298 Settlement Notification messages to the participant member bank(s) via the SWIFT
network
Optional paper reports in support of the above messages
Settlement Interface: Scheduled List
The Settlement Process can deliver two types of settlement instruction messages:
Standard MT298 Settlement Instruction Messages
These are settlement instruction messages, which are for immediate settlement, once the
MT298 message has been delivered to the central bank system
Scheduled List MT298 Settlement Instruction Messages
These settlement instruction messages are delivered to the central bank system, placed in a
holding queue and then scheduled to effect settlement at a given date and time, as specified
in the MT298 message. These MT298 messages contain specific settlement tag fields,
which identify that it is a scheduled list instruction message.
BANKSERV believes that there is more than one possible solution and that the final choice
will be based on achieving a balance between risk and cost.
Network Requirements
A secure network should consist of a backbone Ethernet to which the existing equipment is
connected. The firewall must be a fail-over system with two separate sets of hardware so
that, even if one device fails, sessions or data will not be affected.
From the firewall the data itself will enter into an encrypted tunnel (Virtual Private Network -
VPN) to its endpoint, which will be a participating bank. Physically the data leaves the
firewall and hops to the router. This router should also be a fail-over system, and if the router
or line should fail, the second router may be used via Integrated Services Digital Network
(ISDN) dial-up connection. If all local leads fail, i.e. the leased line and dial-up connection,
then the alternate satellite path may be used. The VPN tunnel is used, because the satellite
transmission cannot be considered secure. A leased line is secure, because it is a point-to-
point line, but it should be encrypted using Internet Protocol Security to prevent possible
Telecommunications company personnel attempting to use sniffers. In addition, intrusion
detectors may be placed at the site to listen for any attack patterns.
The network can be configured to utilise the SWIFT Network architecture.
Segregation and Confidentiality of Bank Data
The segregation of data between each bank is achieved by implementing internationally
accepted best practice in terms of firewall and router installations.
Term Description