Faster payments overview
Faster payments overview
Faster payments contact us
Faster payments related info
Faster payments new material
Faster payments new material
Faster payments Sponsors
Faster Payments and the IT Manager

The Faster Payments programme in a bank represents two very significant challenges for the IT manager.

  • To put together a development project for a mission critical new payments system.
  • To run a new 24 x 7, high volume service; a sort of cross between CHAPS and ATM support.

The following questions should help the IT manager on some of the key parameters to these two challenges. If you want more information contact us.

  • What type of IT programme should I be putting together?
  • What does the infrastructure challenge mean to an IT operations department?
  • What are the IT architecture implications of Faster Payments?
 
What does the infrastructure challenge mean to an IT operations department?
Faster Payments means two very different challenges related to IT service set-up and delivery.

The first is the establishment and ongoing running of 24 x 7, highly available, payments switch and gateway in the bank. This will, in many respects have the same characteristics of availability as a debit card switch or an ATM switch. Transactions hitting the switch will either be coming from the bank's own channels to be routed to the central infrastructure or from other banks to update the bank's customers' accounts. As if establishing a brand new payments switch was not challenging enough, there are two features of the faster payments service that the IT operations manager needs to keep in focus

  • The value of the individual transactions could be substantially higher than the average ATM transaction, so the financial impact of any outages or security breaches will be higher.
  • The scheme plans to run the bulk of the payments over the switches in the hours between midnight and 06:00 am. This is precisely when operations shifts are at their weakest.

The second idea of importance to the IT operations manager is a review of the channel security standards he has in place. Because Internet and Telephony channels can make real time, irrevocable payments, some forms of IT security employed in these channels, such as password access control, may be considered inadequate. It may well be the case that IT security upgrades are required in one or more channels, such as using CHIP and PIN or token based controls.

Back to top
What are the IT Architecture Implications of Faster Payments?
On the application architecture side of things there are probably two main areas of stress;
  • A multi-channel, 24 x 7 account balance capability
  • Credit decision making systems architecture.

Many banks have a 24 x 7 capability to support channels, e.g. ATM withdrawal on internet banking transactions. However, many banks do not have a shared intra day balance capability across all their channels, much less one that is 24 x 7. This becomes virtually a mandatory component with the advent of Faster Payments. For example, suppose a father wants use Faster Payments to move some money to his penniless student son urgently to allow him to go to the branch/ATM to collect his rent money. Both the branch/ATM systems and the Faster Payments "inwards" systems have to be using the same intra day balance data.

For a fuller description of the changes to Credit Decisions see the page "Credit Decisioning and Faster Payments". Suffice to say that there will be major software re-engineering required to get what is currently a 2-day batch process down to a same day/real time process.

On the infrastructure architecture side of things, most banks have some degree of capability to provide reliable 24 x 7 services. Faster Payments just increases the volumes and values running on these platforms. Similarly Faster Payments increases the demand for better quality customer authentication technologies in the channels (branches, internet, call centres).

Back to top
  Ask a question
   
 
Name  *
 
  Email *
 
  Question *
 
 
   
 Designed by: Sitec IT, 2006
| Privacy Statement | Legal Disclaimer |