PSD2 Reviews

Establishment of the platform for FinTech to promote ancilarry services (AISP & PISP); so the Financial Istitutions can concentrate on their COre Business

Establishing a Fraud Consortium apart from SCA provisioning, leaving less dependency on Financial Institutions to hunt for a solution

Banks provided Financial products for Retail & Business Customers. Solutions reqd. to be designed specifically.

.The regulatory architecture,

Security guidance

Country wise guidline

Authentication framework

I like that the user is asked for consent before giving his personal information, and is a standard in order to integrate all the banks and make payments with a 3 factor security. I also like that once you do the development for one bank, it is the same for the others.

The documentation is bad in a lot of cases, you have to try a lot in order to learn how to do the HTTP calls to the APIs. I also don't like that the sandbox is static, so if you make a payment, you will cannot see the transaction and the balance of the accounts will be the same always, so you cannot test completely all the steps of the development. But once you learn how to do the Signature and to retrieve the Token, everything is going easier each time.

It is really recommendable to ask someone who knows how does it works because now, the available documentation is really bad, it has a lot of mistakes and if you follow the instructions it is going to fail. I suggest to use Python with Crypto module, it allows to do de Digest and Signature headers easyly.

I can ask for available funds of a credit card or an account, make payments, instant payments, bulk payments and recurrent payments with it. Also you can know the accounts of an user if he gives consent.