Which certificates does Handelsbanken accept?
Before using our Live Data APIs, a TPP (Third Party Provider) must have one of the below from a Qualified Trust Service Provider (QTSP):
- A valid PSD2 eIDAS certificate (QWAC)
- A valid UK Open Banking certificate (OBWAC)
To read more about accessing our Live Data APIs and enrolling with us as a TPP, please see Live Data Enrollment
I am a new TPP that is trying to enroll but I am experiencing issues. What could be the problem?
Please see below for helpful tips if you are a TPP who is trying to enroll with us for the first time so you can use our Live Data APIs.
- You must follow Step 1. Request third party access on our Live Data Enrollment page and use the POST endpoint.
- If you encounter issues when enrolling, it could be that your QTSP is not on our trusted list and we need to add them. Please contact us and include the name of the QTSP and the link to the CRL distribution points (i.e. the URL where the revocation list can be located). You can send us a message here Contact us
- If you have already enrolled as a TPP and are having issues adding a new certificate, please see the below FAQ.
I have enrolled as a TPP and would like to add a new certificate but I am experiencing issues. What could be causing this?
Please see below for helpful tips if you are a TPP who has already enrolled with us to use Live Data APIs but would like to add another certificate.
- You must follow Step 1.1 Add an additional certificate on our Live Data Enrollment page and use the PUT endpoint, not the POST endpoint.
- If you encounter issues when enrolling, it could be that your QTSP is not on our trusted list and we need to add them. Please contact us and include the name of the QTSP and the link to the CRL distribution points (i.e. the URL where the revocation list can be located). You can send us a message here Contact us
- When adding a new certificate (and in order to successfully do Step 1.1), you must have the same organizationIdentifier (OID 2.5.4.97) as the previous certificate. If you have a new organizationIdentifier, you'll need to enroll as a new TPP, so follow Step 1. Request third party access
- It is very important that the new client certificate is used in both the TLS (Transport Layer Security) and in the payload of the request. There should be no line breaks or white spaces either.
- If you're an existing TPP, but used an integration platform and have some issues, please see the below FAQ.
I am a TPP that used an integration platform from a provider and I will migrate to another. Do I need to change anything?
Please see below for some tips if you are a TPP who has moved from one integration platform to another. (Note: we won't be able to provide support for issues you have with your integration platform!)
- If you intend to use the same client certificate as previously, you can continue using the same client IDs / subscriptions / applications.
- However, if you want to use a new client certificate and keep the same client IDs / subscriptions / applications, you must add a new client certificate to your current TPP registration. This can be done by following the instructions for Step 1.1 Add an additional certificate
How can I see my applications for the Live environment in the Developer Portal?
Our Developer Portal is only for the Sandbox (test) environment. Live and Sandbox are totally separate environments, which means you won't see any applications / subscriptions you have in the Live enironment when you log into our Developer Portal.
How can I query what apps are registered / see the app's subscriptions / delete an app in the Live environment?
At the moment, this functionality is not supported, but it is in our road map for future improvements.
Do you support multiple redirect_uris?
There is no support for multiple redirect_uris on a single app.
If you would like to add another redirect_uri, you will need to register a separate app. To do this, please follow Step 3. Register your app and subscribe to our APIs
If you would like that app to consume several APIs, please then follow 3.1 Add an additional API subscription (one per request)