Share this post:


The European Union wants to make banking transactions on the internet convenient, cheaper and consistent. Regulators also wish to create an environment which fosters innovation and competition. Second Payment Services Directive (PSD2) is the directive that will be administered in European Union to achieve these goals.

Impact on Banks

From a business perspective, banks are required to allow third party providers (TPP) to offer services which were traditionally offered only by the bank. This change permits the bank’s customers to use third party services to access certain payment and account services instead of interacting directly with the bank.

From a technology perspective, banks need to expose APIs that will allow TPPs to consume account information and trigger payment transactions after the bank obtains the customer’s consent.

Worldwide initiative

Across the world different countries are implementing similar directives. Banks doing business in a region where the directive applies need to adhere to the regional directive’s standards. Open Banking in United Kingdom, STET in France, Open API in Hong Kong, Payments NZ in New Zealand are some examples of directives similar to PSD2.

Security Implications

There are security implications on the bank when these services are exposed via APIs. Banks need to ensure that customer data is protected, third party providers are trusted, customers give consent to third party providers after completing strong authentication, customers are protected from fraud and malware, transactions are safe, etc.

Meeting the PSD2 requirements

In order to meet the PSD2 requirements the bank needs to expose and manage APIs, implement strong customer authentication and protect the customer from fraud.  IBM has been working with many financial customers to design and deliver solutions to meet these challenges, using both IBM and non-IBM technologies. For more information, you can read the Beyond PSD2 Paper by clicking on the link below.


The paper captures the technology and architecture requirements.  This paper focuses on Identity and Access Management technologies in a vendor agnostic manner and will help you build a solution that will meet future requirements in this space.


This space is evolving fast. Please feel free to send any feedback to the author by sending email to


Click here to rate this article

Rate this article :

IT Security Specialist

More Access and Authentication stories
By Anthony Ferguson on March 15, 2019

Calling all IBM Tivoli Federated Identity Manager Customers

An open letter to our IBM Tivoli Federated Identity Manager customers,   As part of the IBM Security Access Manager development teams ongoing focus to support our customer base we are hoping to gain a better understanding as to how we can assist our IBM Tivoli Federated Identity Manager customers to migrate to our IBM […]

Continue reading

By on March 14, 2019

ISAM Advanced Access Control Infomap to run info.js

In the past Level II Support has received Cases asking for various ways to force the running of the info.js script which is needed for AAC device registration.  The Knowledge Center section Configuring the attribute collection service notes to add the URL of info.js to the <head> block in the HTML landing page of your application.  […]

Continue reading

By Scott Exton on March 6, 2019

Hybrid ISAM Environments

IBM Security Access Manager introduced support for Docker a few years ago with the publishing of the IBM Security Access Docker image.  The interest in Docker has recently increased and questions are now being asked around how to run both the appliance and Docker in the same environment.  This is especially useful for customers who have […]

Continue reading