This website uses cookies to give you the best possible experience. By continuing to browse this website, you consent for cookies to be used. For more details


Here you can find some frequently asked questions. If you can't find the answer you're looking for, please contact our support team at This email address is being protected from spambots. You need JavaScript enabled to view it..

1. PSD2

PSD2 is the new European Directive (2015/2366/EU) which incorporates, complements and substitutes the previous PSD (2007/64/CE), which provided the legal basis for the creation of an EU-wide single market for payment services.
The PSD2 applies to payment services in the European Union. It focuses mainly on electronic payments and does not include, among the others, paper based payment transactions like cash and cheques.

PSD2 aims to create a single and integrated payment services market, aligning standards for institutional banks and emerging Payment Service Providers (PSPs), and accelerating the digital transformation in payments.

Its main objectives are to:

  • contribute to a more integrated and efficient European payments market
  • open up payments market to new entrants increasing competition
  • promote innovative and internet payment services
  • introduce strict security rules for the initiation and processing of electronic payments and for the protection of consumers’ data

Authentication processes related to payment information and transactions must adhere to updated strong authentication requirements.

A significant change is the possibility for customers to allow licensed third party providers (TPPs) to access to their online payment account’s information and to initiate payments from their account.

Customer safety is at the basis of PSD2. No customer data can be accessed by any PSP without proper licensing and without having received the customer consent first.

UniCredit will never give to third parties access to customers’ data without the customer’s specific consent.

In order to access to PSD2 APIs you need:

  • to have obtained a license from your National Competent Authority (NCA) to operate as a PSP according to the PSD2 regulation (AISP and/or PISP and/or CBPII)
  • a passport license to other countries if you want to access PSD2 APIs not only in the country where you obtained the license, but also elsewhere
  • to have a qualified certificates for electronic seals as defined in Article 3(30) of Regulation (EU) No 910/2014 4 or website authentication as defined in Article 3(39) of that Regulation.

At the moment it is possible to access UniCredit PSD2 APIs in the Sandbox environment with an eIDAS Qualified Website Certificates (QWACs), provided by a qualified trust service provider published in the EU Trusted List of Trust Service Providers.

It also possible to access to the Sandbox environment with an eIDAS test certificate, provided that the certificate has to be considered trusted by UniCredit (please refer to Onboarding section for more details).

Production environment is available only for UniCredit Bank Czech Republic and Slovakia a.s., with an eIDAS QWAC certificate issued by a qualified trust service provider.

You can find the list of banks in the Getting started page.

Our PSD2 APIs are developed according to the Berlin Group API implementation guidelines.

For further information, please, visit the Berlin Group’s website.

For Czech Republic and Slovakia our APIs follow CZ standard and SK standard.

SK Standard:

CZ Standard:

We are committed to comply with further national standards and will follow up on this topic, as soon as official news will be available.

2. Developer Portal

It’s the UniCredit’s website where software developers of TPPs can:

  • browse the API catalog and discover our APIs
  • read about our overall APIs solution
  • find out how to use the APIs and download the Swagger documentation
  • find documentation about testing facility, or to interact with test environment APIs
  • access security policy information for APIs and generate Keys and APIs OAuth keys (only for Czech Republic and Slovakia)
  • contact our team for support
  • manage the own developer team

To get full access to UniCredit Developer Portal, the first step is to register here.

We then suggest to read our Getting Started page for further instructions and have a look at our API catalog.

The list of the offered APIs is shown in the API catalog page.

The complete developer documentation about API catalog and related APIs are accessible only after having completed the registration and the following onboarding process, as described in the Getting started page.

For UniCredit Bank Czech Republic and Slovakia a.s., following local API implementation standards, the registration (and onboarding) is needed in order to create an Oauth token to access UniCredit APIs, both for the Sandbox and production environment.

For the rest of UniCredit Group, having followed the Berlin Group guidelines for the APIs implementation, the access to both production APIs and the related Sandbox APIs, does not require any mandatory registration.

The Developer Portal has two types of users:

  • Organization administrator, who is allowed to:
    • create and manage other users;
    • create and manage applications (Czech Republic and Slovakia standards only);
    • access to the API catalog, according to his/her organization’s authorized roles and passporting, as an application developer.
  • Application developer, who is allowed to:
    • access to the API catalog, according to his/her organization’s authorized roles and passporting;
    • create and manage their own applications;
    • read only capabilities for applications shared by other users.

The Organization administrator can go to the Developer Portal registration page, and will be asked to provide the following information:

  • Company name
  • Organization Admin Email
  • Password
  • Password Confirmation

He/she will then receive a confirmation email to activate the account.

Please consider that the first user registering the TPP is by default an Organization administrator.

3. Onboarding

The onboarding process consists of a specific API call in which a TPP confirms its identity and with which it is authorized to access the functionalities offered by the developer portal, in particular access to the documentation about the API catalog and to the creation of applications as requested in the Czech Republic and Slovakia standards.

If your organization already has an eIDAS Qualified Website Certificate (QWAC), it is possible to invoke the API for TPP onboarding with your eIDAS certificate.

If your organization has not yet obtained on eIDAS QWAC, it is possible to onboard with an eIDAS test certificate, which enables access to the API catalog and to the functionalities of the developer portal until an eIDAS QWAC is obtained. The eIDAS QWAC will be however necessary to access UniCredit’s API production environment.

Please refer to the Getting started page for more information on this process.

To complete the onboarding process the eIDAS test certificate must be considered trustable by UniCredit.

To consider a test certificate trustable UniCredit must be able to trust the entire test certificate chain (ROOT, Intermediate) of the CA that signed the eIDAS test certificate used for onboarding.

If problems occur during onboarding with your eIDAS test certificate, send a request with the form available on the support page for the registered TPPs and attach to it the certificate chain, usually provided by the CAs during the provisioning of the certificate.


Please refer to the Getting started page for more details on this process.

It is possible to perform the onboarding with an eIDAS test certificate only once and therefore it will not be possible to use multiple eIDAS test certificates for the same organization.

Once the eIDAS QWAC certificate is obtained, it is possible to invoke the API for onboarding with the new certificate.

Roles and passporting of your organization will be aligned in accordance with the TPP registry (PRETA registry) and developers and applications previously added by the TPP will be deleted.

It is possible to onboard once with a single eIDAS certificate. Other onboarding calls will be rejected.