Solution, from the high level management screens, users are able to drill down into the detail level. BAM is Windows-based, using SQL Server. Users access the system via thick client and web browser variants. Interfaces are provided to monitoring agents (JMX, Oracle views and WebsphereMQ). The system is also integrated with Tivoli and HP OpenView. Also relevant is an anti-money laundering solution, HotScan. This is for payments filtering. The supplier claims a ‘self-learning’ aspect to this to reduce the number of false- positive alerts in the sanctions filtering processes. The system had been tested by CLS on all of its FX settlements and trades, with Logica claiming the tests showed scanning of around 400 messages per second. Logica claimed to have reengineered the solution to handle large volumes, resulting in a version called
All Payments 7.0
During 2017 CGI made a major investment in All Payments to continue to evolve the payments solution and position in the marketplace. All previous product functionality have been consolidated into a modern, configurable, future proof environment deployable on the cloud, with the market name CGI All Payments 7.0. During 2017, SEPTA Instant Credit Real Time Engine, updated user interfaces, MS Azure enabled and SWIFTgpi capability were added to the global product capabilities. Development is thought to be continuing through 2018 and early 2019 adding additional payment networks and an analytics module leveraging Hadoop.
All customers on previous code versions; BESS, LAPS, and LAPS HC, are being encouraged by the supplier to upgrade to this latest feature-rich release. CGI All Payments 7.0 (APS 7.0) is a real time, modular, scalable and configurable payments solution for financial institutions developing their payments infrastructure.. When deployed as a hub it supports financial institution payments modernization efforts by unifying a FI’s standalone solutions into a fully- integrated payments infrastructure. Its modularity also supports single payment engine deployments to add to or replace components of an existing payments infrastructure APS 7.0 utilises key technologies such as: Angular/Bootstrap for UI framework, Swagger/JAX-RS for REST API, JEE Message Driven Beans, Spring, Hibernate, Oracle Database, Prometheus and JETM for performance monitoring, IBM Websphere
HotScan Plus. Previously, it was mainly applied to international transactions but now that many regulators are extending their AML requirement to domestic traffic, the need was there for the ability to cover hundreds of thousands of transactions. Interestingly, in Brazil, as the result of a deal in the second half of 2009, Logica was working with Rede de Telecomunicações para o Mercado (RTM) as a local partner. RTM provides an extranet for the Brazilian financial market, connecting over 500 institutions in a single operational environment. It hosts HotScan in its data centres to provide a central ASP solution for international and domestic payment scanning for the Brazilian banking community. This was the first use of HotScan on this basis. In total, Logica claimed between 70 and 80 customers of HotScan.
Application Server as JEE container, JasperReports. Reflecting the global nature of the application APS 7.0 supports multiple languages and all localized strings are based on unicode AL32UTF8 character set. For UI localization Angular localization framework has been leveraged. Localized strings stored in database (such as various reference data / lookups) in multiple supported languages. Audit logs messages are stored in database as template and values separately glued together when displayed to user on UI. Reports are using JasperReports localization framework (based on resource bundles). System-level exceptions are not localized which allows easier troubleshooting. User can choose his language applicable to all UI functions using UI setting. Setting change requires browser window reload to be effective. User’s language preference is persisted in database and used for next user session. APS supports multi-entity processing, making this solution attractive to banks with presence in multiple jurisdictions. The architecture is based on multi-entity data model. Each key database table has entity id which typically represents subsidiary of bank or external financial parties on behalf which bank processes transactions (white labeling). Value of entity id is typically defined by input interface. Data is logically segregated using Oracle Virtual Private Database (known as Fine Grained Access Control). This allows the system to define row level access policy in form of predicates dynamically appended to all queries. These predicates filter rows based on visibility access rights granted to user id associated with the query. This robust mechanism allows defining access policy directly on database
Payment Systems & Suppliers Report |
www.ibsintelligence.com 103
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
