Frequently Asked Questions
about Open Banking & PSD2

What is Open Banking?

Open Banking is the standardized legislation that allows all of us to take control of our own financial data. We can choose to share our banking information with trusted third parties to get the financial products and services we want faster, cheaper and more easily than we do today.

What is PSD2?

PSD2 is a directive from the European Union, which sets requirements for banks and businesses in the financial services sector to improve consumer protection, make payments safer and more secure, and drive down the costs of payments services.

What is BankingSDK?

At BankingSDK we unify the way you can connect and retrieve information from multiple banks. We "hide" the complexity of each bank's API and provide you a simple API you can interact with.

Why BankingSDK is not an aggregation company like the others?

Traditional way of doing business of aggregation companies is to be the middleman: You connect to their APIs, they connect to the banks in your name, get the data, store the data and send back the data to your server.

BankingSDK is an API platform like no others because it does execute inside your own cloud infrastructure. You don't have to connect on our servers, you don't have to save your credentials on our server, you even don't have to save your data on our servers.
BankingSDK is hosted on your servers, you get the data directly from the banks.

Your business, your data, your rules.

Open Banking APIs vs Premium APIs.

There are two ways to connect to a bank.
The first one is to use the open banking related APIs. You have to be regulated by our NCA and become a TPP (Third Party Provider) able to access Account Information and/or Payment Initiation services. Once TPP, you can reach APIs in the name of your customers (PSU) and get balances, statements, etc.
The second option is through direct bank API (Premium API, Institutional API, Private API, etc). To be granted an access to those APIs you must partner with each bank. Once the partnership is done, you can access the API using your customer's certificate.

Premium APIs do offer more services than Open Banking APIs and sometimes they also have a cost while the Open Banking ones are free.

At BankingSDK, we do support connectivity to both types of APIs.

Is BankingSDK visible to my customers?

No.
BankingSDK is an API container. You have to design the screens which handle the user interactions. You have full control on User Experience and User Interface.

Do I need a specific license to use BankingSDK?

If you want to connect to Open Banking APIs, you have to be regulated by your NCA (National Competent Authority) and get in Europe for example the licenses 7 and or 8.

To connect to Premium APIs you'll need a certificate created by the bank you want to connect to. We already have lots of deals with banks, let's have a chat about this. You can reach us on support at bankingsdk.com .

How may I add connectivity to a new bank?

At BankingSDK our roadmap for connectors delivery is customer driven. You can ask us a new connector as soon as you need it.
We will check feasibility, your urgency and our planning then add it in the release plan.

How could we start using BankingSDK?

Using BankingSDK is a few steps process. You have to:
  • first, create an account in the Developer Portal: https://developer.bankingsdk.com
  • second, you read the one page documentation from developer portal
  • third, you can reach a Sandbox container we host ourselves for testing purposes
  • fourth, you can access client software for testing freely accessible from our GitHub repo
  • fifth, you got it. You're ready to implement BankingSDK inside your own solution

How could we use BankingSDK in our own Cloud?

Working with your own Docker Container is quite easy. Full documentation is accessible from the Developer Portal but here is a short description:
  • You download the latest version of the Docker container from DockerHub.
  • You install the Docker container inside your own Cloud solution.
  • You configure it with correct path to access certificates and configuration files.
  • You get a license key for BankingSDK (we have trial key, no worry).
  • That's it, you're able now to connect to sandboxes of the banks or production systems of the banks if you have the appropriate certificates.

Which are the Clouds currently supported?

BankingSDK is released as Docker container. Docker (c) is a well-known technology to handle containers in Cloud systems. We did test the Docker container compatibility with Microsoft Azure, Amazon Web Services (AWS), Google Cloud and IBM Financial Services Cloud.

What is the Developer Portal?

Our developer portal (https://developer.bankingsdk.com) is the central place where you'll be able to create applications key, see your company key but also list the traces of all the calls you did.
This is very very very useful for development purposes.

How long does it take to integrate BankingSDK?

If you check the sample code provided on GitHub, you can have something working with our sandbox in a few hours.
A full implementation, using your own BankingSDK Docker instance, storing data in your servers, using real certificates, handling real users: 5 days.
No more. And we do provide support during the integration process.

How does BankingSDK handle client certificates?

Your eIDAS certificates (in case you are a regulated TPP) or your bank certificates are stored in your Cloud system. We never manage, store or collect your certificates or your customers certificates.
Your certificates, your rules! ;)

I want to know more.

Just send us a mail to support at bankingsdk.com