# Which PSD2 sandbox is the best to get started with?

We have recently made our SDK in all 3 supported languages (Java, Javascript and Python) available for download from our website (opens new window). The SDK comes with one connector of the user choice and allows communication with sandbox PSD2 APIs of one or multiple banks (depending on the connector). We think it’s a good starting point for an individual developer just wanting to familiarize himself with the concepts and capabilities of PSD2 APIs, as well as for companies starting a project making use of Open Banking APIs.

PSD2 sandbox enviroment

So far we have implemented connectors providing access to account information (AIS) and payment initiation (PIS) APIs in 8 countries: Denmark, Estonia, Finland, Lithuania, Latvia, Norway, Poland and Sweden. As the SDK libraries provide direct access to these APIs, in order to get started one would also need to register to the sandbox of a chosen bank. So below we summarize the state of the PSD2 sandboxes for these countries and suggest where it’s easy to start and possible to have good data and UX nicely simulating a live environment. It’s good to remember that in Europe use of PSD2 live APIs requires corresponding license or registration from a National Competent Authority (opens new window), and some of the banks restrict access to their PSD2/Open Banking sandboxes only to those parties who already or in the official process towards the license or registration.

In Finland 🇫🇮, Enable Banking’s home country, we cover the majority of the banks providing open banking APIs and we see that the sandboxes are at pretty good level. All major banks except Danske provide access to the sandbox APIs and developer portals without restrictions. Danske Bank (opens new window) requires either being a part of the Open Banking UK Directory (opens new window) or TPP registration/license being in the official process. OP (opens new window)’s sandbox environment nicely simulates user authentication and consent handling and has all security mechanisms in place. Nordea (opens new window) lacks user authentication/consent handling UI, but their developer portal is really simple and easy to use. It’s also easy to get access with the S-Pankki sandbox environment (opens new window) (provided through Crosskey Open Banking Market) and it has good dynamic data (also for payments).

In Sweden 🇸🇪, where we also have good coverage, all major banks provide decent sandbox environments and they are available to everyone without restrictions. Swedbank (opens new window), SEB (opens new window) and Handelsbanken (opens new window) sandboxes provide nearly the same experience and are easy to get started with. Also Länsförsäkringar developer portal (opens new window) is good and its sandbox environment is as close to live as possible. The same applies to Ålandsbanken (opens new window) and you won't need to deal with Swedish BankID, because the SCA flow is simulated.

In Denmark 🇩🇰 and Norway 🇳🇴, with a large number of smaller local banks, the open banking APIs are mostly handled by IT service providers, such as Bankdata (opens new window), BEC (opens new window), Evry (opens new window) and SDC (opens new window). The PSD2 sandbox environments provided by them are usually good, but in most cases are restricted to the registered/in-the-process TPPs and require manual setup of the developer accounts. Danske Bank (opens new window) and Nordea (opens new window) are probably the easiest to get started with, if you are particularly interested in these countries and don’t bother dealing with service providers’ support.

In Baltics 🇪🇪🇱🇻🇱🇹, where the banking space is dominated by large foreign banks, you would probably want to get started either with the Swedbank (opens new window) or SEB (opens new window). Please note that while Swedbank’s APIs and developer portal is the same in the Baltic states as in Sweden, SEB provides a dedicated environment (although quite similar to the one provided in Sweden). Citadele (opens new window) and Luminor (opens new window), the local banking groups, provide sandbox environments, which are easy to get started with but quite limited in functionality with quite many omissions making them quite far from their live counterparts. Also one good example is LHV (opens new window), because it doesn't even require you to sign up to their developer portal; just generate sandbox certificate (opens new window) and you are good (and same in production but with real eIDAS certificates).

In Poland 🇵🇱, where the banking space is quite diverse and the national standard (opens new window) is being enforced, the situation is different from a bank to bank. Alior Bank (opens new window) and BNP Paribas (opens new window) are two banks, which would be the easiest to get access to sandbox environments, while Bank Pekao (opens new window) and ING Bank Śląski (opens new window) provide UX which is much closer to what users will see in live (both banks manually approve access to their sandbox environments, but do not strictly require being a TPP).

On our website we’ve collected the full list of APIs and developer portals (opens new window), available in the countries we currently support. Just navigate through it and you’ll direct links to the developer portals. There is also information whether a sandbox environment is available to everyone or the access is restricted. No matter what bank you pick to start with, Enable Banking SDK provides the same interface and you’ll be able to move along adding bank after bank using the same code. Drop as a message at openbanking@enablebanking.com, if you are still unsure where to get started. We are also happy to help you with on-boarding, especially if you are planning to integrate a large number of banks.