The API Manager is the component enabling the Product Owner to be in control of the “relationship” with the API consumers. This includes configuring who should be able to see and invoke an API, managing its subscription process, handling the migration between versions but also running analytics on the actual usage metrics as well as managing its lifecycle once it is in use. We are listing below the core ones:

API Product Publishing: this include defining which third parties will be able to subscribe and use the API product.

API Product Subscriptions Management: a product manager can decide to have fine grained control on the approval of every single subscription request, authorize application developers depending on the organization they belong go, or make an API completely public.

API Product Lifecycle and Version Management. This aspect is particularly important in the context of a regulatory environment that is changing rapidly. PSD2 APIs are likely to evolved over time, as the standards are clarified and become more prescriptive.

IBM DataPower Gateway is a purpose-built security and integration platform for mobile, cloud, application programming interface (API), web, service-oriented architecture (SOA), B2B and cloud workloads.

IBM DataPower Gateway enables you to rapidly expand the scope of valuable IT assets to new channels – giving customers, employees and partners access to critical resources. It helps quickly secure, integrate, control and optimize access to a range of workloads through a single, extensible gateway platform.

IBM DataPower Gateway is available in both physical and virtual form factors

Why you need Consent Management?

The on-boarding of a TPP application service user requires the process of providing an electronic consent on behalf of the user to the application and its delivery to the bank.
The Bank should be duly informed about this consent and keep it in an appropriate form
The bank should be able to check the validity of the electronic consent for each transaction for each iteration of the third party application (TPP, AISP).
The Bank should enable the end user to manage (deactivate, renew) its consents through electronic channels (Internet and Mobile Banking or other specific application)

Why IBS Consent Management for PSD2

A solution that can be quickly adapted to any application and fit to any architecture

Build-in SOA architecture

Full package RESTful API integration documentation