Guidelines for PSD2 Implementation

Helping banks explore API strategies and options

Whitepaper

There are some tough decisions to make for you as a bank. The ndgit whitepaper outlines some of the key requirements and freedoms for APIs and explores how these impact strategic decision making and PSD2 implementation.

PSD2 for compliance or opportunity?
Which market standard to choose?
Make or buy?
Where to find support?
To host or not to host? On-Premise or SaaS?
Can fallback be avoided?

Compliance Only or Open Banking?

Putting minimal efforts into PSD2 whilst insuring compliance may sound attractive… short termed. Read in the ndgit Whitepaper what great potential you miss if you renounce open banking.

Make or buy?

Even before digging deeper into PSD2 you have to make your first decision: do it yourself or hire experts? Can you handle the workload? What about the knowhow? Are there advantages in buying?

Who supports?

Which tasks are better outsourced? What are the advantages? Any disadvantages? Clock is ticking – any chance to speed up? Some answers are awaiting you in this whitepaper.

On-Premise or SaaS?

So do you need your own server to be PSD2 compliant? What are the options without hosting yourself? Why can SaaS be helpful as starting point? Can you switch later on?

Berlin Group, STET or UK Open Banking

Which Standard fits best to your bank especially if your active globally? Do you have to choose? Enjoy ndgit’s answers…

Can fallback be avoided?

EBA forces you to provide a fallback to make sure users can always access the services. Always. Really?
ndgit has some tips for you about how to avoid a fallback solution.