Slowly ‘silo’ building payment channels (ATM, Internet, etc) as they have emerged overtime, banks have build an important legacy on difficult to maintain and conflict creating middleware. The unifying Prisma Payment Service Hub couples efficiency and cost reduction to the need to handle ever-growing volumes of payments with an increasing share of near-real time transactions. Orchestrating in one platform a multitude of existing and yet to come payment channels, the growing and irritating patchwork of middleware finally belongs to history.
Most banks have accumulated over time separate solutions for all the different payment channels that independently have emerged and been implemented independetly from each other as technology offered and individual banking needs required (ATM – internet – mobile – Mposa, etc). By consequence they sit on a criss-cross patchwork of complicated and problem causing middleware to service them (silo-architecture).
The traditional approach requires the legacy systems to provide different interfaces for different application.Same business processes are redefined across different silo approach, what enhances the inconsistency. These legacy systems are inflexible, increasingly expensive to maintain and difficult to integrate with new channels. And the number of different channels is gradually increasing over the years, thus only aggravating the already existing problems.
The PSH (Payment Service Hub) is the powerful next generation development of the volatile Prisma Gateway and integrates automated clearing house, wire, Check 21 and international settlement into a single, least-cost routing solution. The PSH can be deployed and integrated in orchestrated schedule in order not to interfere with going concern and business needs.
Putting into consideration the company structure in real life/day to day operational and various business scenarios, our Advanced Approval Matrix is able to cover from the most simple matrix (of 1 approval rule throughout the company) to multiple complex matrix based on various parameters.
Through our Rich Text editor, User may simply copy-and-paste (for e.g.) Invoice list from spreadsheet to system. Or User may opt to manually input into system through Tabular Header/Detail form.
To manage execution failure, normally due to expected/temporary host down-time, automatically by system (without human interference), be it sending to queue for Automatic Retry to host or executed using shadow balance mechanism.
For use by company for easier reconciliation purpose. It is mostly for collection (payment from its consumers).
Enable user to upload transaction into or download information from system right from/to his/her ERP/SAP.
The PSH (Payment Service Hub) consolidates different legacy systems into one single pool of services and it :
|Enables processing of bulk and individual payments on a unified platform, irrespective of amount, customers, channel or transaction type;|
|Ensures flexibility to deal with the changing payment landscape;|
|Provides re-usable services, component and business rules across different channels to improve quick time to market for new products;|
|Reduces the time, cost and risk for upgrading or installing new channels and products and overall hardware, software complexity and cost;|
|Aggregates data from different front-end systems that can be fed into ancillary system for further analysis;|
|Monitors & Manages incoming and outgoing traffic;|
|Time, resources and cost saving, reducing complexity and eliminating conflicts whilst enhancing performance.|
|Type||Platform + Solution|
|Core Banking System Integration||Extensive experience with core banking integrations such as Alltel, Bank Trade, Bank Vision, CardLink, Cardpac, Eximbill, F&S, Finacle, Fiserv, M&I, Murex, Silverlake, SilverCard, Stratus ON/2, Systematic, Tandem Base24, Temenos, Vision Link and others|
|Database||Oracle, PostgreSQL, and independent|
|User Interface||Any current internet browser with Java plugin enabled (JRE Installed)|
|Adapters||ISO 20022, FTP, SFTP, TN3270, TN5250, Web Service, SMTP, POP3, ISO8583, XML, Fixed Length|
|Engines||Business Rule, BPM|
|Authentication||In application layer : any third party hard/soft token - own soft token available|