About
Welcome to our PSD2 openAPI developer portal! Here you will find all the neccessary information on using our open banking solutions. These will help you to build amazing applications for your customers. We provide API solutions for
- Account Information Services (AIS)
- Payment Initiation Services (PIS) and
- Funds Confirmation Services (FCS)
Our open banking solution is based on the Berlin Group XS2A standard (version 1.3.3). This is the most often used API standard for fulfilling the EBA PSD2 (EU 2015/2366) and EBA RTS requirements.
The 'Berlin Group' is a pan-European payments interoperability standards and harmonisation initiative with the primary objective of defining open and common scheme- and processor-independent standards in the interbanking domain between Creditor Bank (Acquirer) and Debtor Bank (Issuer), complementing the work carried out by e.g. the European Payments Council. As such, the Berlin Group has been established as a pure technical standardisation body, focusing on detailed technical and organisational requirements to achieve this primary objective.
Learn MoreGetting Started
Start builing your application with our openAPI service as easy as 1-2-3! We've made our API access as easy as possible. With dynamic TPP registration you don't have to register yourself and create an account on our developer portal. This means there is no onboarding procedure, no filling out forms or sending emails.
To access the production open banking environment just present a valid TPP eIDAS certificate. To obtain a certificate register yourself as a third party provider (TPP) at your competent national authority. To access the production environment you need a Qualified Website Authentication Certificate (QWAC).
QWAC certificates can be obtained from Qualified Trusted Service Providers (QTSP, https://webgate.ec.europa.eu/tl-browser/#/).
Documentation
Please use the following manuals to get to know our API solution.
Release notes
Here you will find additional information on using our services, like which optional Berlin Group elements were implemented and how to use the sandbox solution.
Error Codes
This API uses standard RFC7807 error codes as proposed by the Berlin Group standard. This documentation contains all the possible error codes, their meaning and hints on how to resolve them.
Certificates
To use our sandbox API you must present a QWAC client certificate when you create the SSL connection. If you already registered with you National Competent Authority (NCA) then you can use the obtained eIDAS certificate to access the sandbox API services.
If you do not yet have a client certificate then you can use the following test keys and certificates. Download them on following links below and set up your testing environment so it presents them when you create the SSL connection. Select the certificate with the appropriate role and corresponsing key that best matches your testing scenario. Please note that the sandbox will only accept the certificates provided here.
All roles
This certificate contains all available roles: AISP, PISP, PIISP. You can can use it to get account information, initiate payments and check funds.
AISP
This certificate contains only the AISP role. You can can use it to get account information.
PISP
This certificate contains only the PISP role. You can can use it to initiate payments.
Endpoints
Out sandbox and production access endpoints are as follows
Sandbox
:
- URL prefix: /sb/v1/
- (e.g. https://:/sb/v1/accounts)
Production
:
- URL prefix: /v1/
- (e.g. https://:/v1/accounts)
Frequently Asked Questions
Do I need to register?
No. You can start using our sandbox services right away. However production environment requires a a Qualified Website Authentication Certificate (QWAC).
What financial services are available?
The following services are available through our PSD2 API: account information, account balance, transaction history and payment initiation.
What is the endpoint behind the service?
Electra openAPI is providing the API services.
Contact Us
KDB Bank
info@kdbbank.eu