Open Space

Introduction 2018 is all set to be a game-changing year for European banking. The Revised Payment Services Directive (PSD2) has opened the door to new third party providers [TPPs] to connect with banks and manage finances of bank customers on behalf of them. The PSD2 regulation has mandated banks to expose their core-banking account data and payment services to authorized TPPs to consume. Thus as a bank it’s essential to have a solution which will securely expose their internal banking services to third party providers in a trusted manner. WSO2 Open Banking solution provides all required components to expose bank APIs in a well secured manner in order to become PSD2 compliant. This article explains about the importance of the TPP role in PSD2 domain, the requirements set that banks need to provide for TPPs by PSD2 regulations and how WSO2 Open Banking solution supports these requirements.  From my last blog ,I have given an introduction for PSD2 and WSO2 Open Banking soluti...

Overview of PSD2 The Revised Payment Services Directive (PSD2) of the European Union, seeks to improve the existing European rules for electronic payments. PSD2 deadline is already elapsed and being compliant of PSD2 has become top in the priority list of majority of EU banks and financial institutions. In short, PSD2 enables bank customers, both consumers and businesses, to allow third-party providers to manage their finances. PSD2 sets out rules concerning: Strict security requirements for electronic payments and the protection of consumers' financial data, guaranteeing safe authentication and reducing the risk of fraud; The transparency of conditions and information requirements for payment services; The rights and obligations of users and providers of payment services. The core of the directive is the requirement for banks to open bank data as APIs to third parties under the XS2A (access to account) rule. With the adoption of PSD2, the playing field is final...