search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
‘quite a lot of code’, with this still ongoing. He claimed at this stage to have won three LAPS orders in the first quarter of 2011 but was unable to name any of them. One turned out to be Westpac New Zealand (see below). Logica later announced a deal from Banco Popular de Puerto Rico (BPPR), which signed around December 2010 as the first LAPS customer in Central America/Caribbean. Logica declined to comment on another deal which was thought to have been signed, with the bank for the US military, USAA. Logica claimed to have built LAPS High Volume itself. There


were one or two early projects in central Europe that seemed to contribute, then an early implementation at Deutsche Bank. At this time the system was called Bafir. Deutsche Bank had used this system in the Czech Republic (which is where the system seems to have its roots) for its local payment processing requirements. This was successfully implemented and when its Austrian branch engine needed upgrading the bank chose the same platform. In mid-2006, this became the basis of Deutsche Bank’s SEPA engine and is at the heart of LAPS High Volume. Logica was working on a single orchestration layer in front of the two engines, with Turner stating that this was mainly being contributed by the High Volume solution and with nothing coming from the Dovetail system. This promised a consistent user interface. There was in parallel a plan to port Fastwire to Unix. While the number of users had fallen to between 80 and 90, from a one-time high of more than 200, the solution remained the mainstay of some banks. The shift of Fastwire from VMS was to be part conversion and part rewrite. The system was positioned for complex, high volume users where messaging was distinct from the applications. It was also appropriate for countries and communities (such as some areas of securities) that did not solely use Swift or did not use it at all. For other users, there was SwiftAlliance, which was available from Logica on a reseller basis. It took Logica a long while to commit to the migration of Fastwire, but the company now believed that there was a class of user that required such a solution. As well as a straight replacement for the existing version, this ‘Fastwire Open’ solution was also aimed, where appropriate, at users of Bess for the ‘wire room’ part rather than for the payments part. Again, there were a number of large-scale Bess users, such as Bank of Tokyo Mitsubishi, which used it on a global basis. Going forward, the supplier planned to develop components to be shared by both Fastwire and Bess as well as by a low-end Microsoft-based offering, QPH, which originated in India and was then offered elsewhere. The first component was a standalone application for managing correspondent relationships. Fastwire Open was launched in 2008. The Bankers’


Association of Turkey, representing 48 banks in the country, went public with its use of a version of the hub in mid-2009. Fastwire Open was also being tested with a separate client at the same time, and benchmark figures were released claiming that the platform could process five million Swift FIN messages per day. For Bess, the strategy was to move customers off the


system. From Logica’s perspective, this would hopefully mean a migration to LAPS but there have been losses. An example of this was BMO Financial Group in Canada, which opted in early 2012 to replace Bess and a host of other in-house and third party systems with Dovetail’s Payment Services Hub. Logica also sought to offer ‘extended payments’ functionality, and to this end launched an internet banking e-invoice and document gateway, ZoomIT, with Belgian company, Isabel. Dexia and KBC piloted the solution. It provides


consumers and corporates with consolidated


financial information, including invoices, payments, contracts and payslips, within a single service. Logica claimed it was both SEPA and Swift-compliant, and could be interfaced to ERP and accounting systems. With regards to SEPA, in May 2007 Logica announced


two SEPA-related initiatives: first, it teamed up with the UK payment network provider, Voca (Vocalink, as it became), to offer a test facility. Second, it planned to offer an IBAN and BIC directory based on the offering of data specialist, CB.Net. It is not clear whether either initiative produced tangible results. In 2011, Logica also launched a mandate manager for


corporates to support SEPA Direct Debits (SDDs). A year later it announced it was working with Rabobank to create a SEPA payments hub to support all incoming and outgoing SEPA transactions for the bank’s corporate clients. Logica would also convert payment instructions and bank account numbers to the European IBAN/BIC standard and provide mandate management services to support the implementation of the new European direct debit process. Towards the end of 2012, Citibank also selected Logica to support its mandate management service, with Sentenial believed to have been pipped at the shortlist stage to the deal. The bank already had a long-standing relationship with Logica and there was a feeling that it might be more able to mobilise resources than some others. Logica’s mandate management service was based on the LAPS High Volume platform and complemented Citi’s SDD offering.


CGI teamed up with Ripple in 2015 to offer distributed financial tech capabilities for payments. This new agreement will see Ripple’s distributed financial technology capabilities brought into CGI’s portfolio of payments solutions. CGI’s offering in this sector includes payments hubs, financial messaging, liquidity management and watch list filtering.


Payment Systems & Suppliers Report | www.ibsintelligence.com 101


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