Introduction to LHV Open Banking

Introduction to LHV Open Banking

Version History

23.09.2019Page initial version published

Getting started

Welcome to LHV Open Banking & PSD2 API page!
Here you will find all the much needed information to get started with our API, including:

  • access and usage
  • environments
  • introduction to services and details

Our PSD2 API covers the features listed in PSD2 regulation, including:

  • Account information service (AIS)
  • Payment initiation service (PIS)
  • Confirmation on the Availability of Funds Service (FCS or AIIS)

Our API is s RESTful API interface based on the Berlin Group Standard. You can obtain the full documentation here.

Access and Usage

You can integrate with our API if you are:

  • Third Party Payment Service Provider aka TPP - a company who is developing some app or system which requests access to private or corporate LHV customers accounts
  • Other bank or credit institution aka ASPSP.

To start using the Open Banking API in live you should first obtain a valid licence from the authorities - Estonian Finance Inspection.
Banks (ASPSPs) hold this licence already by default.
More information here.

To verify if you are authorized to use the services you can check the EBA online database:

We also provide a Sandbox testing environment which you can use when preparing for your live integration or just trying out the Open Banking features.
It is also free to use by everybody and no licence is required.

Access Certificates

Our API is using the PSD2 compliant eIDAS QWAC transport layer certificate for identifying and verifying the TPP. eIDAS QSEAL certificate is not required or supported for now.
Currently also no other methods or certificate types are supported.

You can order the QWAC certificate from a number of different providers across Europe - provided you have are holding the TPP licence mentioned above.
You can read about these here.

Opening access and first usage

We do not require signing any agreements or have extra validation procedures when granting access to live.
The first time you make a request towars any of the API endpoints using your certificate you will get SERVICE_BLOCKED error. Please contact us at and we will grant you access in a few hours.
This is a temporary safety procedure during the first months of the PSD2 era to verify that the whole infra behind the scenes also work correctly - including these not provided by LHV.



Sandbox test environment is our free to access testing environment. It is technically also very similar to live environment - the services, JSon structure etc. is the same.

Link to Sandbox -

There is no dedicated developers portal or account required to start using the Sandbox. You can use Sandbox directly in Swagger or similar to live -
executing the API endpoints directly using your own developed client application or some testing tool like Postman.

Base url of Sandbox is:

Access certificate

Sandbox is not using production QWAC certificates, but custom testing certificates which you can generate automatically.
Create your own certificate here.
Store the Private key and Certificate contents as *.key and *.crt files. You can use these like you would use official certificate and key in production.
Please extract your TPP id from the certificate file. It should be visible on Subject > field and should look like PSDEE-LHVTEST-[random combination]
For example - PSDEE-LHVTEST-c1dec9
Use this value in your OAuth request client_id. For example:

Sandbox Swagger is using built-in default access certificate with client_id value PSDEE-LHVTEST-01AAA

This TPP id value is similar and used the same way as your id in production. For example LHV Pank TPP id is PSDEE-FI-10539549.

Accounts and data

Sandbox has following default OAuth access tokens and accounts available:

  • bearer Liismarimannik: EE717700771001735865, EE277700771001735881, EE457700779900289935
  • bearer Donaldduck: EE857700771001735904

You can use these access tokens and accounts in combination provided or use the same account numbers with your own access tokens.


As described below in Access and Usage section you can get live access only with official licencing and production QWAC certificate.

Live base url is: