is simply a matter of adding loaders and extractors’. Meanwhile, the hub should allow all transactions to be housed together, and can be connected in real-time to another system. This, for example, should eliminate the need for multiple systems for AML or OFAC checking. The company claims there is the ability to process payments centrally but execute them on a regional or global basis. WebSeries is intended for enterprise ‘purchase to pay’, and as such is suited to businesses with payment processing requirements originating from multiple departments, business units and locations. It handles all types of low-value, bulk ACH payments and provides Bacs, laser cheque, and electronic document distribution. It provides a single point for audit, security and administrative management. The system also includes disaster recovery and contingency planning. The following components are available: International and
domestic ACH; real-time gross settlement for international and domestic ‘wires’; information reporting; cheque management; international payments; and a client access gateway. A hosted option is available. The components can be deployed individually or as an integrated whole. In 2010, Bottomline added mobile payment and reporting capabilities to its cash management offering. There had been a huge pick-up in this area in the last three or four months, said CTO, Eric Campbell, in part facilitated by the ability to now address different devices through a common layer. This was an example of the power of web services, he added, with Bottomline having developed these and now able to publish them via mobile. There is also C-Series/Paybase. C-Series Wires is
touted as a low-cost, web-based solution that automates domestic and international funds transfers and includes integrated confirmation and reporting capabilities. It allows organisations to accelerate approval and payment processes, lower risk and access a consolidated view of daily and historical funds transfer activities. There is integration with Swift Alliance Lite. Paybase is positioned as part of the C-Series suite and is
Bottomline’s corporate payment solution. It spans multiple payment types including Bacs, cheques, Faster Payments and international payments. It now has a browser-based user interface. It is meant to be bank agnostic and can accept any data format, from any ERP. The Sterci-derived GTExchange (formerly Stelink) is a financial messaging solution. It is intended to streamline the flows between business applications and network gateways. The Middleware EAI function includes multiple back-end connectors to business applications for payments and securities. It includes business rules, routing, mapping, XML formatting, business intelligence, archiving, AML filtering, bulking and enrichment. Network connectivity includes Swift, SEPA, FIX, SIC, Secom, Sarie (Saudi Arabia), fax and e-mail. There is a ‘single window access’ to all SwiftNet services (FIN, RMA, FileAct, InterAct). A Message Entry component is centred on a browser- based GUI providing message entry/verification (all MT and
MX message types), template creation, routing, printing, RMA, supervision and monitoring. GTExchange is intended for service bureau architectures, small to medium bank infrastructures, and Tier 1 institutions. Within benchmark tests carried out in 2006, Sterci claimed 550,000 messages per hour on a Fujitsu Siemens platform. GTExchange has been interfaced to plenty of banking applications over the years. There is an accredited interface to Avaloq’s private banking system, for instance. Sterci was traditionally proactive when it has came to Swift initiatives. This was reflected in it becoming the first to gain full accreditation in May 2011 for supporting SwiftNet 7.0. In doing so, it even beat Swift’s own AMH offering. SwiftNet 7.0 was the most extensive upgrade to the Swift network for a long while and to make GTExchange compliant took around four months of ‘heavy effort’ and testing. There are six qualification modules for software applications that send or receive InterAct or FileAct traffic. These comprise the communications interface, a full Relationship Management Application (RMA) interface (replacing the bi-lateral key exchange and currently only adopted for FIN), RMA for Score (for corporate access), InterAct store and forward, FileAct store and forward, and FileAct Real-Time. All banks were meant to have migrated by March 2012.
A Linux version of GTExchange was released in 2012. Sterci believed it would be the first Swift messaging system with this platform option. For large organisations with high volumes of traffic, there was likely to be a major cost saving, it was claimed. The migration was part of Sterci’s product roadmap and Hewlett-Packard had been involved with the project. The first taker was a foreign bank moving into Saudi Arabia. It was expected to take the new release in July, with cut-over before the end of 2012. There is also now a cloud deployment option, GTCloud.
GTExchange traditionally fits in the sector populated by the
likes of the Logica-derived Bess, IBM’s Merva and Sungard’s Mint. Unlike these, the Sterci system had been overhauled and moved forwards, so it remained a commercial offering. As such, it has been taken to replace all of these legacy systems. Part of the overhaul was a technology refresh, with support for J2EE and a thin client interface. The move of the matching system, GTMatch (previously Stematch), to J2EE followed, while the GTFrame EAI offering was brought into GTExchange as an embedded component. Bottomline Technologies entered into a strategic alliance
with payments giant Visa through which Visa’s commercial card solution. Within B2B, automation has a tailwind as electronic payments functions are moving toward adopting methods that include commercial payment cards. Given the relationships that both Bottomline and Visa maintain with banks, the initial integration and adoption would seem to gravitate toward those clients. In April 2017, Bottomline Technologies launched a new
payment fraud solution for members of the SWIFT payment network. The solution that will be made available to the users of SWIFT transactions on Bottomline’s cloud as well as on-
Payment Systems & Suppliers Report |
www.ibsintelligence.com 83
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176 |
Page 177 |
Page 178 |
Page 179 |
Page 180 |
Page 181 |
Page 182 |
Page 183 |
Page 184 |
Page 185 |
Page 186 |
Page 187 |
Page 188 |
Page 189 |
Page 190 |
Page 191 |
Page 192 |
Page 193 |
Page 194 |
Page 195 |
Page 196 |
Page 197 |
Page 198 |
Page 199 |
Page 200 |
Page 201 |
Page 202 |
Page 203 |
Page 204 |
Page 205 |
Page 206 |
Page 207 |
Page 208 |
Page 209 |
Page 210 |
Page 211 |
Page 212 |
Page 213 |
Page 214 |
Page 215 |
Page 216 |
Page 217 |
Page 218 |
Page 219 |
Page 220 |
Page 221 |
Page 222 |
Page 223 |
Page 224 |
Page 225 |
Page 226 |
Page 227 |
Page 228 |
Page 229 |
Page 230 |
Page 231 |
Page 232 |
Page 233 |
Page 234 |
Page 235 |
Page 236 |
Page 237 |
Page 238 |
Page 239 |
Page 240 |
Page 241 |
Page 242 |
Page 243 |
Page 244 |
Page 245 |
Page 246 |
Page 247 |
Page 248 |
Page 249 |
Page 250 |
Page 251 |
Page 252 |
Page 253 |
Page 254 |
Page 255 |
Page 256 |
Page 257 |
Page 258 |
Page 259 |
Page 260 |
Page 261 |
Page 262 |
Page 263 |
Page 264 |
Page 265 |
Page 266 |
Page 267 |
Page 268 |
Page 269 |
Page 270 |
Page 271 |
Page 272 |
Page 273 |
Page 274 |
Page 275 |
Page 276 |
Page 277 |
Page 278 |
Page 279 |
Page 280 |
Page 281 |
Page 282 |
Page 283 |
Page 284 |
Page 285 |
Page 286 |
Page 287 |
Page 288 |
Page 289 |
Page 290 |
Page 291 |
Page 292 |
Page 293
