Here you find information on how eIDAS certificates and how to handle certificate updates.
For your information Bankdata and IT partners will be investigating different options to improve certificate handling during Autumn 2023.
Sandbox certificate (embedded in zip-file)
Bankdata provides you with a link to a zip-file containing a test-certificate.
It is not possible to use your own test-certificate or production-certificate in Sandbox.
Only 1 active QWAC eIDAS certificate
Bankdata requires a valid QWAC eIDAS certificate issued by a Qualified Trust Service Provider (QTSP).
It is not possible to use QSealC eIDAS certificates.
You can only use 1 QWAC eIDAS certificate for your ThirdPartyProvider-ID.
Your new QWAC eIDAS certificate will replace your previous certificate.
That is why it is not possible to use both your current AND new certificate when you use the PSD2 APIs.
Who issued your QWAC eIDAS certificate?
If your QWAC eIDAS certificate is issued by a QTSP unknown at our IT hosting partners,
we have to schedule installation of full certificate chain at our IT hosting partners.
Expect up to 10-20 workingdays.
If your new certificate is issued by a different QTSP than your previous QWAC eIDAS certificate, there is a risk the QTSP is unknown at our IT hosting partners.
We recommend you send a copy of your new certificate to us ASAP to investigate,
if we will have to order a full certificate chain installation at our IT hosting partners.
Examples on known QTSPs
Here are examples on QTSPs already known at our IT hosting partners.
Please note: These are examples, not a complete list.
Please note: The names above must match 100% to the QTSP information in your certificate.
Send QWAC certificate in PEM-format
You must send your QWAC eIDAS certificate in PEM-format or text-format to our support email.
If you send the certificate in CER-format, it will be blocked by our servers.
We will contact you to schedule deployment of the new certificate.
Deployment is possible during office hours 09:00 - 14:00 (local danish time).
Expect downtime up to 2 minutes during deployment.
After deployment of new certificate all previous consent tokens are expired.