Community
John Doyle’s blog about “The SWIFT Future” has had my fingers twitching for a couple of weeks, and as nobody else is joining in….
SWIFT plays a very important role in a changing market. Its role has changed, as the market has changed. It was created to put together a solution for cross-border payments in a world where there were no global networks, no standards for messaging, and no application structure for interchanging messages securely and globally. We all know how the market has changed, but SWIFT may not have changed in line with that. We didn’t know about Moore’s Law back when SWIFT was created.
There are about 8,000 banks on SWIFT globally, yet there are around 9,000 banks in Europe alone. There are about 25 million corporates in Europe alone that will need to adapt to SEPA, and yet there are only about 200 corporates on SWIFT globally. To save on per-message costs, banks bulk-ship transaction messages, and net out as many transactions as possible to reduce the bulk that they have to ship. There is no economy of scale, because the scale is too small.
The banking industry won’t increase its costs in order to generate economies of scale for SWIFT. Bulk doesn’t come from the back office, where there is one settlement per trade: it comes from the front office, where there can be 28,000 quotes per trade. Economies of scale don’t come from 30 gigabytes of traffic globally per day: they come from 30 gigabytes of traffic per customer per day (that’s around the capacity of one home’s 4 Mbps internet connection today).
This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.
Ruchi Rathor Founder at Payomatix Technologies
30 September
Dmytro Spilka Director and Founder at Solvid, Coinprompter
27 September
Ritesh Jain Founder at Infynit / Former COO HSBC
Luke Allchin Director - North America at RFI Global
26 September
Welcome to Finextra. We use cookies to help us to deliver our services. You may change your preferences at our Cookie Centre.
Please read our Privacy Policy.