It accelerate the path towards digital transformation and provides a microservices foundation
What do you like best?
Catalyst Accelerator for Banking provides a prescriptive reference architecture drawn from our work with industry leaders that promotes asset self-service and reuse. In the architecture, we've abstracted data from core banking systems, mainframes and other systems of record, and represented via a set of REST APIs. We also built experience APIs to enable the simple consumption of this data by end-users. And finally, we've developed an "Anypoint Bank" sandbox that shows how these APIs can be accessed.
Support for core business processes – Account information, payments initiation and legacy modernization use-cases.
Architecture best practice – Catalyst Accelerator for Banking provides a proposed architecture – one drawn from working with industry leaders – that promotes asset self-service and reuse.
Pre-built API designs and implementations – Following PSD2 trends and regulatory requirements, MuleSoft has built a series of AISP and PISP APIs that unlock core business data via secure APIs.
What do you dislike?
Security features needs to be improved more
Recommendations to others considering the product:
Legislative, market, and technology trends have created a digital transformation imperative in financial services. Catalyst Accelerator for Banking includes pre-built APIs and a prescriptive architecture to help IT teams jumpstart the development of common banking applications and provides a foundation for 3x faster project delivery.
What problems are you solving with the product? What benefits have you realized?
Open Banking requires banks to build a digital platform that exposes their core capabilities as APIs. MuleSoft's Catalyst Accelerator for Banking provides a set of connectivity assets that deliver on these use cases.
Process APIs decouple business processes that interact with and shape data from the source systems where the data originated. For example, the “process a payment” contains logic that is common across multiple entities, which can be called by product, geography, or channel-specific parent services.